>
> It'll be nice if James has a sure fire repro scenario then.
>
In my case, if I do 'xm create virtdemo && xm destroy virtdemo' I get a
leftover page:
(XEN) General information for domain 4:
(XEN) refcnt=1 nr_pages=1 xenheap_pages=0 dirty_cpus={}
(XEN) handle=ac933dee-fc59-98b0-3b0b-038b54a25096 vm_assist=00000000
(XEN) paging assistance: shadow refcounts translate external
(XEN) Rangesets belonging to domain 4:
(XEN) Interrupts { }
(XEN) I/O Memory { }
(XEN) I/O Ports { }
(XEN) Memory pages belonging to domain 4:
(XEN) DomPage 000000000019d1fd: caf=00000001, taf=00000000e8000000
(XEN) VCPU information and callbacks for domain 4:
(XEN) VCPU0: CPU0 [has=F] flags=0 upcall_pend = 00, upcall_mask = 00
dirty_cpus={} cpu_affinity={0-31}
(XEN) paging assistance: shadowed 2-on-3
(XEN) No periodic timer
(XEN) Notifying guest (virq 1, port 0, stat 0/0/0)
That's with no disk and no network devices published to the domain. I
guess I'd better try another kernel.
James
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel