Bug 424421
Summary: | Xen Domain crashes when installing DomU via anaconda | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Andreas Thienemann <athienem> | ||||||
Component: | xen | Assignee: | Xen Maintainance List <xen-maint> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 5.1 | CC: | jpazdziora | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2007-12-14 14:31:10 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: | |||||||||
Attachments: |
|
Description
Andreas Thienemann
2007-12-13 23:13:50 UTC
a) use virt-install/virt-manager instead of xm and attach the /root/.virtinst/*.log files or /root/.virt-manager/*log files if any are created b) give the domain enough memory - xen defaults to '128' which is not enough for anaconda - it'll crash & burn with this little c) attach the *full* /var/log/xen/xend.log d) Do *not* use a 32-bit paravirt DomU on a 64-bit Dom0 - this is known to randomly crash. (In reply to comment #1) > a) use virt-install/virt-manager instead of xm and attach the > /root/.virtinst/*.log files or /root/.virt-manager/*log files if any are > created gonna try that > b) give the domain enough memory - xen defaults to '128' which is not enough > for anaconda - it'll crash & burn with this little The domain had 1024M assigned via the config file > c) attach the *full* /var/log/xen/xend.log Done > d) Do *not* use a 32-bit paravirt DomU on a 64-bit Dom0 - this is known to > randomly crash. Urgh. Fixes in sight? Created attachment 288661 [details]
xend.log
An additional note to b) Anaconda does usually just seem to freeze, no messages at all. Some times however, I can see some remnants of /dev/ram0 or something similar written on the console. This is all symptomatic of running a 32-bit guest on a 64-bit HV. We know this doesn't work in 5.1 and we can't fix it - we don't even know why its broken - it simply doesn't work. It may work in 5.2 - we won't know until we try the full QA cycle on it though. Hi Daniel, I've got a bit more info, reconnecting the vnc viewer gives some trace information. Created attachment 289111 [details]
kernel trace
Hi Daniel,
I've got a bit more info, reconnecting the vnc viewer gives some trace
information.
Unless you can reproduce the problems with a 64-bit guest, we're not going to spend any time on this ticket. 32-on-64 is known to randomly, non-reproducably crash - it is simply not possible to debug it. We've wasted weeks attempting to do so in the past. Ihis is a dpulicate of 250427. This has been fixed in the RHEL 5.2 stream. If there is a separate Anaconda issue please file a separate BZ. Also if this happens on non-PV guests, please reopen. *** This bug has been marked as a duplicate of 250427 *** As discussed in private mail, installing 2.6.18-59.el5bbHPmgmtxen as the Dom0 kernel fixes this issue. |