Bug 701251
Summary: | kernel panic when trying to install xen guest | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Alexander Todorov <atodorov> |
Component: | kernel-xen | Assignee: | Xen Maintainance List <xen-maint> |
Status: | CLOSED CANTFIX | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.7 | CC: | drjones, jzheng, leiwang, lersek, mbrodeur, qwan, rpacheco, xen-maint, yuzhang, yuzhou, zliu |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-06-09 11:57:33 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 693654 |
Description
Alexander Todorov
2011-05-02 09:51:22 UTC
How much memory are you trying to give the guest? Can you try adding dom0_mem=1G to the command line to see what happens? This backtrace really does match the one in the BZ you've pointed to. Maybe the patch for that bug only hid the problem, or we need to make another hacky bump of spare_hv_pages... Test 1: After the above crash the system rebooted. I logged in and tried to create xen guest: - FV, Generic/Generic with 512MB of memory (the default) and the with 1 GB. In both cases I got: (XEN) No enough contiguous memory(16384KB) for init_domain_vhpt and virt-manager refused to create the guest. Test 2: Try to create a Xen guest: FV, Linux/RHEL 5.4 or later => kernel panic Test 3: Added dom0_mem=1G to the boot command line => successfully created a guest with 512MB of memory. So I only get the kernel panic when I select for the guest to use the virtio drivers. Xen sort of never worked on this machine (hp-rx2660-04). Please open bug 661989 and read all the comments that contain the string "hp-rx2660-04" to see my earlier testing. I don't know why it crashes, but it is not a regression. (See in particular bug 661989 comment 27.) I think it is some hardware trait / config that Xen chokes on (even though it's probably not the NUMA config). Matt, may I ask if there's anything special about hp-rx2660-04 that prevents Xen from working? Thanks! (In reply to comment #4) > > I don't know why it crashes, but it is not a regression. (See in particular bug > 661989 comment 27.) I think it is some hardware trait / config that Xen chokes > on (even though it's probably not the NUMA config). > > Matt, may I ask if there's anything special about hp-rx2660-04 that prevents > Xen from working? Thanks! Not as far as I know. I would expect any rx2660 to be Xen capable, but there could be something wrong with that one. If you can determine that this panic is specific to that host I'll get our HP expert to dig into it. (In reply to comment #5) > (In reply to comment #4) > > Matt, may I ask if there's anything special about hp-rx2660-04 that prevents > > Xen from working? Thanks! > > Not as far as I know. I would expect any rx2660 to be Xen capable, but there > could be something wrong with that one. If you can determine that this panic > is specific to that host I'll get our HP expert to dig into it. That would be great, thanks! Based on the (XEN) No enough contiguous memory(16384KB) for init_domain_vhpt messages, perhaps it is still a memory layout problem on hp-rx2660-04. The problem does seem to be unique to this machine. Under bug 661989 the following machines worked okay with Xen: hp-rx2660-03.rhts.eng.bos.redhat.com (bug 661989 comment 19) hp-rx2660-01.rhts.eng.brq.redhat.com (bug 661989 comment 27) *** Bug 750741 has been marked as a duplicate of this bug. *** |