Bug 461601

Summary: kernel running as xen guest hangs when booting with serial console
Product: [Fedora] Fedora Reporter: Jeff Layton <jlayton>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: rawhideCC: steved, yaneti
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-09 14:28: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:
Attachments:
Description Flags
console output from hung boot none

Description Jeff Layton 2008-09-09 11:58:13 UTC
Created attachment 316181 [details]
console output from hung boot

I have a rawhide xen guest that I use for testing. It's been working fine (aside from some weirdo timing stuff that I attribute to xen), but recent rawhide kernels have started hanging at boot time when I set them up to boot with a serial console. i.e. kernel hangs when I boot with this:

Command line: ro root=/dev/VolGroup00/LogVol00 console=ttyS0,115200

...but not with this:

Command line: ro root=/dev/VolGroup00/LogVol00

...the last kernel that I've been able to successfully boot with a serial console is 2.6.27-0.287.rc4.git7.fc10.x86_64. Every kernel that I've tested since then has hung like this. I've played with some other options (only assigning 1 CPU to the guest, playing with ACPI and APIC settings, etc), but nothing seems to make a difference.

This may have absolutely nothing to do with xen, but I don't have any bare-metal machines provisioned for serial console, so I haven't been able to test this anywhere else.

Comment 1 Yanko Kaneti 2008-09-09 13:00:07 UTC
This is probably another offshoot of bug 460565.

Comment 2 Jeff Layton 2008-09-09 14:28:33 UTC

*** This bug has been marked as a duplicate of bug 460565 ***