Zhao, Yunfeng
2006-Apr-28 07:28 UTC
RE: [Xen-devel] Problem booting fully virtualized (Intel VT) 32b gueston XEN32 unstable
You need to add dom0_mem=XXXm to xen or scale back the memory of domain0 with using "xm mem-set <DomId> <Mem>" command. Your domain0 used up almost all physical mem.>total_memory : 1023 >free_memory : 62Thanks Yunfeng>-----Original Message----- >From: xen-devel-bounces@lists.xensource.com >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Ed Smith >Sent: 2006年4月28日 4:56 >To: xen-devel@lists.xensource.com >Subject: [Xen-devel] Problem booting fully virtualized (Intel VT) 32b gueston >XEN32 unstable > >Has anyone been able to boot a fully virtualized (Intel VT) 32bit guest >on XEN32 unstable? I''m trying to setup a nightly test environment for >this configuration and XEN32 nosmp hangs when launching a 32bit guest, >and XEN32 smp gets a double fault launching a 32bit guest. It happens >pretty early as the SDL window doesn''t come up. I tried with apic, >pae, and acpi all on and all off, same problem. Example config attached. > >Here is my XEN32 nosmp console: > >Red Hat Enterprise Linux ES release 4 (Nahant Update 2) >Kernel 2.6.16-xen on an i686 > >tst122 login: root >Password: >Last login: Thu Apr 27 16:13:40 from 10.1.2.13 >[root@tst122 ~]# /etc/init.d/xend start >Bridge firewalling registered >ip_tables: (C) 2000-2006 Netfilter Core Team >[root@tst122 ~]# xm info >host : tst122 >release : 2.6.16-xen >version : #1 SMP Wed Apr 26 00:58:26 EDT 2006 >machine : i686 >nr_cpus : 1 >nr_nodes : 1 >sockets_per_node : 1 >cores_per_socket : 1 >threads_per_core : 1 >cpu_mhz : 2793 >hw_caps : >bfebfbff:20000000:00000000:00000180:0000e43d:00000000:00000001 >total_memory : 1023 >free_memory : 62 >xen_major : 3 >xen_minor : 0 >xen_extra : -unstable >xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 >platform_params : virt_start=0xfc000000 >xen_changeset : Tue Apr 25 18:22:11 2006 +0100 9744:1ad06bd6832d >cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8) >cc_compile_by : build >cc_compile_domain : katana-technology.com >cc_compile_date : Wed Apr 26 00:10:30 EDT 2006 >[root@tst122 ~]# xm list >Name ID Mem(MiB) VCPUs State Time(s) >Domain-0 0 939 1 r----- 27.7 >[root@tst122 ~]# xm create /boot/vs179_sdl.hvm >Using config file "/boot/vs179_sdl.hvm". >ip_tables: (C) 2000-2006 Netfilter Core Team >Started domain vs > >*** HUNG *** > > >Here is my XEN32 smp console: > >Red Hat Enterprise Linux ES release 4 (Nahant Update 2) >Kernel 2.6.16-xen on an i686 > >tst122 login: root >Password: >Last login: Thu Apr 27 16:22:46 from 10.1.2.13 >[root@tst122 ~]# /etc/init.d/xend start >Bridge firewalling registered >ip_tables: (C) 2000-2006 Netfilter Core Team >[root@tst122 ~]# xm info >host : tst122 >release : 2.6.16-xen >version : #1 SMP Wed Apr 26 00:58:26 EDT 2006 >machine : i686 >nr_cpus : 2 >nr_nodes : 1 >sockets_per_node : 1 >cores_per_socket : 2 >threads_per_core : 1 >cpu_mhz : 2793 >hw_caps : >bfebfbff:20000000:00000000:00000180:0000e43d:00000000:00000001 >total_memory : 1023 >free_memory : 62 >xen_major : 3 >xen_minor : 0 >xen_extra : -unstable >xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 >platform_params : virt_start=0xfc000000 >xen_changeset : Tue Apr 25 18:22:11 2006 +0100 9744:1ad06bd6832d >cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8) >cc_compile_by : build >cc_compile_domain : katana-technology.com >cc_compile_date : Wed Apr 26 00:10:30 EDT 2006 >[root@tst122 ~]# xm list >Name ID Mem(MiB) VCPUs State Time(s) >Domain-0 0 939 2 r----- 31.2 >[root@tst122 ~]# xm create /boot/vs179_sdl.hvm >Using config file "/boot/vs179_sdl.hvm". >ip_tables: (C) 2000-2006 Netfilter Core Team >Started domain vs179 >[root@tst122 ~]# (XEN) CPU: 1 >(XEN) EIP: e008:[<ff1282f3>] do_page_fault+0x53/0x410 >(XEN) EFLAGS: 00010213 >(XEN) CR3: 00000000 >(XEN) eax: 00000000 ebx: 00000000 ecx: 00000073 edx: ff1ddfb4 >(XEN) esi: ff1dd0e8 edi: 0000000c ebp: 00000000 esp: ff1dd0b4 >(XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 >(XEN) ************************************ >(XEN) CPU1 DOUBLE FAULT -- system shutdown >(XEN) System needs manual reset. >(XEN) ************************************ >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ed Smith
2006-Apr-28 14:56 UTC
Re: [Xen-devel] Problem booting fully virtualized (Intel VT) 32b gueston XEN32 unstable
That worked. I set my dom0_mem=256M and my domUs now boot fine. Is this currently a restriction in 32bit XEN? I don''t have to adjust the dom0 memory on 64bit XEN. I thought the balloon driver was supposed to allow dom0 to allocate up all the available memory for the hypervisor and then let the hypervisor give it out to domU''s as needed. Thanks, Ed Smith Zhao, Yunfeng wrote:> You need to add dom0_mem=XXXm to xen or scale back the memory of domain0 with using "xm mem-set <DomId> <Mem>" command. > Your domain0 used up almost all physical mem. >> total_memory : 1023 >> free_memory : 62 > > > Thanks > Yunfeng > >> -----Original Message----- >> From: xen-devel-bounces@lists.xensource.com >> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Ed Smith >> Sent: 2006年4月28日 4:56 >> To: xen-devel@lists.xensource.com >> Subject: [Xen-devel] Problem booting fully virtualized (Intel VT) 32b gueston >> XEN32 unstable >> >> Has anyone been able to boot a fully virtualized (Intel VT) 32bit guest >> on XEN32 unstable? I''m trying to setup a nightly test environment for >> this configuration and XEN32 nosmp hangs when launching a 32bit guest, >> and XEN32 smp gets a double fault launching a 32bit guest. It happens >> pretty early as the SDL window doesn''t come up. I tried with apic, >> pae, and acpi all on and all off, same problem. Example config attached. >> >> Here is my XEN32 nosmp console: >> >> Red Hat Enterprise Linux ES release 4 (Nahant Update 2) >> Kernel 2.6.16-xen on an i686 >> >> tst122 login: root >> Password: >> Last login: Thu Apr 27 16:13:40 from 10.1.2.13 >> [root@tst122 ~]# /etc/init.d/xend start >> Bridge firewalling registered >> ip_tables: (C) 2000-2006 Netfilter Core Team >> [root@tst122 ~]# xm info >> host : tst122 >> release : 2.6.16-xen >> version : #1 SMP Wed Apr 26 00:58:26 EDT 2006 >> machine : i686 >> nr_cpus : 1 >> nr_nodes : 1 >> sockets_per_node : 1 >> cores_per_socket : 1 >> threads_per_core : 1 >> cpu_mhz : 2793 >> hw_caps : >> bfebfbff:20000000:00000000:00000180:0000e43d:00000000:00000001 >> total_memory : 1023 >> free_memory : 62 >> xen_major : 3 >> xen_minor : 0 >> xen_extra : -unstable >> xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 >> platform_params : virt_start=0xfc000000 >> xen_changeset : Tue Apr 25 18:22:11 2006 +0100 9744:1ad06bd6832d >> cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8) >> cc_compile_by : build >> cc_compile_domain : katana-technology.com >> cc_compile_date : Wed Apr 26 00:10:30 EDT 2006 >> [root@tst122 ~]# xm list >> Name ID Mem(MiB) VCPUs State Time(s) >> Domain-0 0 939 1 r----- 27.7 >> [root@tst122 ~]# xm create /boot/vs179_sdl.hvm >> Using config file "/boot/vs179_sdl.hvm". >> ip_tables: (C) 2000-2006 Netfilter Core Team >> Started domain vs >> >> *** HUNG *** >> >> >> Here is my XEN32 smp console: >> >> Red Hat Enterprise Linux ES release 4 (Nahant Update 2) >> Kernel 2.6.16-xen on an i686 >> >> tst122 login: root >> Password: >> Last login: Thu Apr 27 16:22:46 from 10.1.2.13 >> [root@tst122 ~]# /etc/init.d/xend start >> Bridge firewalling registered >> ip_tables: (C) 2000-2006 Netfilter Core Team >> [root@tst122 ~]# xm info >> host : tst122 >> release : 2.6.16-xen >> version : #1 SMP Wed Apr 26 00:58:26 EDT 2006 >> machine : i686 >> nr_cpus : 2 >> nr_nodes : 1 >> sockets_per_node : 1 >> cores_per_socket : 2 >> threads_per_core : 1 >> cpu_mhz : 2793 >> hw_caps : >> bfebfbff:20000000:00000000:00000180:0000e43d:00000000:00000001 >> total_memory : 1023 >> free_memory : 62 >> xen_major : 3 >> xen_minor : 0 >> xen_extra : -unstable >> xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 >> platform_params : virt_start=0xfc000000 >> xen_changeset : Tue Apr 25 18:22:11 2006 +0100 9744:1ad06bd6832d >> cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8) >> cc_compile_by : build >> cc_compile_domain : katana-technology.com >> cc_compile_date : Wed Apr 26 00:10:30 EDT 2006 >> [root@tst122 ~]# xm list >> Name ID Mem(MiB) VCPUs State Time(s) >> Domain-0 0 939 2 r----- 31.2 >> [root@tst122 ~]# xm create /boot/vs179_sdl.hvm >> Using config file "/boot/vs179_sdl.hvm". >> ip_tables: (C) 2000-2006 Netfilter Core Team >> Started domain vs179 >> [root@tst122 ~]# (XEN) CPU: 1 >> (XEN) EIP: e008:[<ff1282f3>] do_page_fault+0x53/0x410 >> (XEN) EFLAGS: 00010213 >> (XEN) CR3: 00000000 >> (XEN) eax: 00000000 ebx: 00000000 ecx: 00000073 edx: ff1ddfb4 >> (XEN) esi: ff1dd0e8 edi: 0000000c ebp: 00000000 esp: ff1dd0b4 >> (XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 >> (XEN) ************************************ >> (XEN) CPU1 DOUBLE FAULT -- system shutdown >> (XEN) System needs manual reset. >> (XEN) ************************************ >>_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ewan Mellor
2006-Apr-28 15:31 UTC
Re: [Xen-devel] Problem booting fully virtualized (Intel VT) 32b gueston XEN32 unstable
On Fri, Apr 28, 2006 at 10:56:24AM -0400, Ed Smith wrote:> That worked. I set my dom0_mem=256M and my domUs now boot fine. > > Is this currently a restriction in 32bit XEN? I don''t have to adjust > the dom0 memory on 64bit XEN. I thought the balloon driver was supposed > to allow dom0 to allocate up all the available memory for the hypervisor > and then let the hypervisor give it out to domU''s as needed.That all works for paravirt domains. For VT domains, there''s certainly one outstanding bug with not enough memory being ballooned out, because it''s not taking proper account of the video memory required for the domain -- perhaps you could look into that? I''m suprised by the double-fault though -- that''s obviously a more serious bug than merely failing to balloon. Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Possibly Parallel Threads
- Problem booting fully virtualized (Intel VT) 32b guest on XEN32 unstable
- Xend can not start
- Daily Xen-HVM Builds
- Bug#665433: xen hypervisor FATAL PAGE FAULT after linux kernel BUG: unable to handle kernel paging request
- Re: [PATCH 00 of 10 [RFC]] Automatically place gueston host's NUMA nodes with xl