Description of problem: During the booting of xen0, the kernel locks up with no apparent error message. Version-Release number of selected component (if applicable): xen.gz-2.6.16-1.2122_FC5 How reproducible: very Steps to Reproduce: 1. install zen 2. reboot 3. Actual results: lockup, this is seen on terminal server: PCI: Bridge: 000:06:01.0 IO window: disabled MEM window: disabled PREFETCH window: disabled PCI: Bridgew: 0000:06:02.0 IO window: disabled MEM window: disabled PREFETCH window: disabled IA-32 Microcode Update Driver: v1.14-xen <tigran> audit: initializing netlink socket (disabled) audit(1149271190:1): initialized highmem bounce pool size: 64 pages VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key 43645308A4C9E5AD - User ID: Red Hat, Inc. (Kernel Module GPC key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfg registered (default) Expected results: system booted into xen Additional info: This is a Penguin Computing Altus 1300, an AMD64 2-processor system with 16GB RAM & 2x120GB HD configured with FC5 and updated. I'm using this at Cisco for server consolidation. I changed grub.conf to run level 3, after seeing graphics boot hang. I tried the console_sync trick, it didn't work. It consistently freezes at the same point (see console messages above). Thanks, -Kirk Franks Cisco Systems kifranks
Is this still reproducible on the latest stable release+updates? Thanks.
I've moved on to FC6 and don't see the problem. However there was a different installation problem we found; we can't install FC6 on a machine with over 4GB of RAM. I've switched to a smaller (RAM) machine and have been able to continue. Has anyone else seen this? Is there a workaround? Thanks, -Kirk
Do you mean you can't install FC-6 at all, even using the non-xen kernel?
change QA contact
This report targets FC5, which is now end-of-life. Please re-test against Fedora 7 or later, and if the issue persists, open a new bug. Thanks