[Bug 643886] New: hvm crash: Out of populate-on-demand memory!
https://bugzilla.novell.com/show_bug.cgi?id=643886 https://bugzilla.novell.com/show_bug.cgi?id=643886#c0 Summary: hvm crash: Out of populate-on-demand memory! Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: jdouglas@novell.com ReportedBy: koenig@linux.de QAContact: qa@suse.de Found By: --- Blocker: --- # rpm -q xen kernel-xen xen-4.0.0_21091_06-0.1.1.x86_64 kernel-xen-2.6.34.7-0.3.1.x86_64 I'm trying to install RHEL6-beta2 into a hvm client on suse-11.3 dom0, the installation crashes before it it really starts the installation process. xm dmesg shows (XEN) p2m_pod_demand_populate: Out of populate-on-demand memory! tot_pages 263159 pod_entries 262144 (XEN) domain_crash called from p2m.c:1127 (XEN) Domain 42 reported crashed by domain 0 on cpu#1: using google to look for "Out of populate-on-demand memory" I found this hint http://lists.xensource.com/archives/html/xen-devel/2010-07/msg01404.html which sounds pretty similar to my problem ?! the memory setup in my xen config file: memory=1024 maxmem=2048 vcpus=4 boot="dc" disk=[ diskroot + 'os2-centos6.img,hda,w' , diskroot + 'RHEL6.0-20100715.2-Server-x86_64-DVD1.iso,hdc:cdrom,r' ] which other information do you need ? btw: if that rhel6-beta installation creates the paritioning and an mostly empty boot block, then using `boot="cd"' instead of "dc" will immedately crash the domU after creation, showing the following in "xm dmesg" : (XEN) realmode.c:115:d36 Failed to emulate insn. (XEN) realmode.c:165:d36 Real-mode emulation failed @ 0000:0000fd49: 0f 07 06 00 0f 1e (XEN) domain_crash called from realmode.c:166 (XEN) Domain 36 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.0.0_21091_06-0.1.1 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: 0000:[<000000000000fd49>] (XEN) RFLAGS: 0000000000010602 CONTEXT: hvm guest (XEN) rax: 0000000000000004 rbx: 0000000000007c06 rcx: 0000000000108025 (XEN) rdx: 0000000000002080 rsi: 000000000000283e rdi: 0000000000002880 (XEN) rbp: 0000000000000000 rsp: 000000000000d074 r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 (XEN) r15: 0000000000000000 cr0: 0000000000000010 cr4: 0000000000000000 (XEN) cr3: 0000000000000000 cr2: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 1000 cs: 0000 are you interested in such a disk image to test with ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=643886
https://bugzilla.novell.com/show_bug.cgi?id=643886#c1
Jason Douglas
https://bugzilla.novell.com/show_bug.cgi?id=643886
https://bugzilla.novell.com/show_bug.cgi?id=643886#c2
--- Comment #2 from Charles Arnold
https://bugzilla.novell.com/show_bug.cgi?id=643886
https://bugzilla.novell.com/show_bug.cgi?id=643886#c4
--- Comment #4 from Jan Beulich
btw: if that rhel6-beta installation creates the paritioning and an mostly empty boot block, then using `boot="cd"' instead of "dc" will immedately crash the domU after creation, showing the following in "xm dmesg" :
(XEN) realmode.c:115:d36 Failed to emulate insn. (XEN) realmode.c:165:d36 Real-mode emulation failed @ 0000:0000fd49: 0f 07 06 00 0f 1e
Hmm, I would guess that doing the same on real hardware would just hang the box (as a mostly empty boot block suggests that installation wasn't complete, and hence there's nothing to boot from)? In this case, the virtualized case would even be an improvement, as you at least get told something went wrong. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=643886
https://bugzilla.novell.com/show_bug.cgi?id=643886#c5
Harald Koenig
However, I'm pretty sure that you're simply running into a known issue that is caused by not having a balloon driver running, yet installing different memory and maxmem values.
Please set the memory and maxmem to the same value, and report your results.
ACK! with maxmem=1024 (and memory=1024 too) the installation starts and is running...
If it turns out that this adjustment resolves the issue, then I don't think there is much we can do since we don't have anyway of introducing a balloon driver into a RHEL OS.
dump question not knowing much about HVM: why does the client OS has anything to do with the xen (dom0/hypervisor) memory management ? so far I thought that HVM is really *full* virtualisation and I can run (almost?!) everything inside a HVM client ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=643886
https://bugzilla.novell.com/show_bug.cgi?id=643886#c6
Jan Beulich
dump question not knowing much about HVM: why does the client OS has anything to do with the xen (dom0/hypervisor) memory management ? so far I thought that HVM is really *full* virtualisation and I can run (almost?!) everything inside a HVM client ?
You can run what you want, but certain features (like maxmem > memory) require support in the guest. Just like for native: If you set firmware/BIOS values wrong, you may have to deal with a non-working OS. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com