Bug 230672
Summary: | Strange migration problem (RHEL5 beta2 with -8.el5 kernel) | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Fai Wong <ywong> | ||||||
Component: | xen | Assignee: | Xen Maintainance List <xen-maint> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 5.0 | CC: | clalance, ddutile, kenchan | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | i386 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | 5.1 | Doc Type: | Bug Fix | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2007-12-07 20:38:16 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
Fai Wong
2007-03-02 01:06:31 UTC
Created attachment 149080 [details]
Log files collected on both machines
OK, it looks like there are two separate problems you are reporting: failure to start 75% of the time due to the xvda: hang, and failure to migrate. Given that they are both in the same bugzilla, I think it will be much less confusing if we take them one at a time. We need to understand the failure to boot first; the "xvda:" hang indicates a failure of some sort in accessing or connecting up the block devices for the guest, and any such failure could easily also affect connection of a new guest arriving on migrate. Can I assume that the logs you posted are all from the migrate case and don't show the xvda: hang case? Do you have logs for the fail-to-boot case? Does it fail to boot on both hosts in the same way? Is the exact same kernel/xen being used on both hosts, with the same kernel on the guest? Thanks. I think at this moment, I cannot give logs for fail-to-boot case yet. So let's deal with the migration problem first, and I have cleared the log files and restart xend service after each test cases, so we can assume that the log file is for clean booting. And yes, the kernel version on both machines, both guest and host OS are -8.el5. We really need to attack the boot case first, for the reasons I said above --- it is quite possible that the boot problem is causing the migrate problem too, and the boot case is likely to be simpler to debug, so we need to get that working before we tackle the more complex case. Created attachment 149127 [details]
Boot crash log
This is the log file for boot failure. It will crash at a line like scanning
partition on xvda.
Guest and host are both rhel5 beta with -8.el5 kernel.
Please also attach the crash output itself. Thanks! The output is nearly same with normal bootup, just crash suddenly, before mounting root, after detecting hard disk and scanning partition. But I cannot get the crash output at the moment, but i will attach it asap. Thanks. In the passed 2 weeks I cannot reproduce the "Cannot start" problem anymore, and I am busying with other stuffs recently, will update when have new finding. Numerous fixes were added to 5.1 to improve migration stability/repeatability. If the reporter still sees problems with 5.1, please re-open this ticket for 5.2. |