RE: [Xen-devel] can't create any more pv-on-hvm domains after~38under 3.3-testing

["James Harper" <james.harper@xxxxxxxxxxxxxxxx>]

> 
> Another thing I just noticed, after 'xm create leaktest && xm destroy
> leaktest':
> 
> (XEN) General information for domain 5:
> (XEN)     refcnt=1 nr_pages=2 xenheap_pages=0 dirty_cpus={}
> (XEN)     handle=dfe46b73-1207-6a4a-f1ce-6e4b3d090e86
vm_assist=00000004
> (XEN) Rangesets belonging to domain 5:
> (XEN)     Interrupts { }
> (XEN)     I/O Memory { }
> (XEN)     I/O Ports  { }
> (XEN) Memory pages belonging to domain 5:
> (XEN)     DomPage 00000000001bb5c3: caf=00000001, taf=00000000e8000001
> (XEN)     DomPage 00000000001bb5c2: caf=00000001, taf=00000000e8000001
> (XEN) VCPU information and callbacks for domain 5:
> (XEN)     VCPU0: CPU1 [has=F] flags=1 upcall_pend = 00, upcall_mask =
00
> dirty_cpus={} cpu_affinity={0-31}
> (XEN)     250 Hz periodic timer (period 4 ms)
> (XEN)     Notifying guest (virq 1, port 0, stat 0/-1/0)
> 
> notice 2 DomPage entries? After I then create another domain (any
domain):
> 
> (XEN) General information for domain 5:
> (XEN)     refcnt=1 nr_pages=1 xenheap_pages=0 dirty_cpus={}
> (XEN)     handle=dfe46b73-1207-6a4a-f1ce-6e4b3d090e86
vm_assist=00000004
> (XEN) Rangesets belonging to domain 5:
> (XEN)     Interrupts { }
> (XEN)     I/O Memory { }
> (XEN)     I/O Ports  { }
> (XEN) Memory pages belonging to domain 5:
> (XEN)     DomPage 00000000001bb5c3: caf=00000001, taf=00000000e8000001
> (XEN) VCPU information and callbacks for domain 5:
> (XEN)     VCPU0: CPU1 [has=F] flags=1 upcall_pend = 00, upcall_mask =
00
> dirty_cpus={} cpu_affinity={0-31}
> (XEN)     250 Hz periodic timer (period 4 ms)
> (XEN)     Notifying guest (virq 1, port 0, stat 0/-1/0)
> 
> Notice only 1 DomPage entry now? Does that mean anything?
> 

I have identified the two pages - if I do 'xm create leaktest' then 'xm
list -l leaktest' it gives me the store_mfn and console_mfn. Those two
mfn's match the two pages left over once the domain is destroyed. Does
that help?

James


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel