From mboxrd@z Thu Jan 1 00:00:00 1970 From: "James Harper" Subject: RE: can't create any more pv-on-hvm domains after~38under 3.3-testing Date: Wed, 3 Dec 2008 21:51:24 +1100 Message-ID: References: <4933BE6A.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Content-class: urn:content-classes:message In-Reply-To: <4933BE6A.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >=20 > And this is not a leak due to the misplaced > DOMAIN_DESTRUCT_AVOID_RECURSION > conditionals in free_l[234]_table()? What does the 'q' debugging command > tell you about the domains (i.e. do they still have all their memory, or > is it rather looking like they only have a bunch of page tables left? I > assume you tried -unstable and the issue isn't present there. I am not easily able to try -unstable on this machine, but I am using the latest 3.3-testing. The machine is right now at a point where 'xm create' doesn't work - 'xm dmesg' reports '(XEN) Cannot handle page request order 1!' 'xm debug q' gives this sort of information: " (XEN) General information for domain 26: (XEN) refcnt=3D1 nr_pages=3D1 xenheap_pages=3D0 dirty_cpus=3D{} (XEN) handle=3D8d9543b4-a16b-7e28-080d-ff243ba715b6 = vm_assist=3D00000000 (XEN) paging assistance: shadow refcounts translate external (XEN) Rangesets belonging to domain 26: (XEN) Interrupts { } (XEN) I/O Memory { } (XEN) I/O Ports { } (XEN) Memory pages belonging to domain 26: (XEN) DomPage 00000000001b7bfd: caf=3D00000001, = taf=3D00000000e8000000 (XEN) VCPU information and callbacks for domain 26: (XEN) VCPU0: CPU0 [has=3DF] flags=3D0 upcall_pend =3D 01, = upcall_mask =3D 00 dirty_cpus=3D{} cpu_affinity=3D{0-31} (XEN) paging assistance: shadowed 3-on-3 (XEN) No periodic timer (XEN) Notifying guest (virq 1, port 0, stat 0/-1/-1) (XEN) General information for domain 27: (XEN) refcnt=3D1 nr_pages=3D1 xenheap_pages=3D0 dirty_cpus=3D{} (XEN) handle=3D8d9543b4-a16b-7e28-080d-ff243ba715b6 = vm_assist=3D00000000 (XEN) paging assistance: shadow refcounts translate external (XEN) Rangesets belonging to domain 27: (XEN) Interrupts { } (XEN) I/O Memory { } (XEN) I/O Ports { } (XEN) Memory pages belonging to domain 27: (XEN) DomPage 00000000001a55fd: caf=3D00000001, = taf=3D00000000e8000000 (XEN) VCPU information and callbacks for domain 27: (XEN) VCPU0: CPU1 [has=3DF] flags=3D0 upcall_pend =3D 01, = upcall_mask =3D 00 dirty_cpus=3D{} cpu_affinity=3D{0-31} (XEN) paging assistance: shadowed 3-on-3 (XEN) No periodic timer (XEN) Notifying guest (virq 1, port 0, stat 0/-1/-1) " And so on up until domain 35 which is the last one I was able to create... none of those domains exist anymore, but when they did exist they were all x32 HVM domains running Windows 2003 x32. Xen and Dom0 are both amd64. James