[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-bugs] [Bug 292] New: rebooting while domU is up causes domUs to no longer come up
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=292 Summary: rebooting while domU is up causes domUs to no longer come up Product: Xen Version: unstable Platform: x86 OS/Version: Linux-2.6 Status: NEW Severity: normal Priority: P2 Component: Tools AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx ReportedBy: jdmason@xxxxxxxxxx Rebooting dom0 while a domU is up causes all subsequent domU creations to fail (see error below). This error is persistent after reboots. ...... xen_blk: Initialising virtual block device driver xen_blk: Timeout connecting to device! xen_net: Initialising virtual ethernet driver. NET: Registered protocol family 2 IP: routing cache hash table of 256 buckets, 4Kbytes TCP established hash table entries: 4096 (order: 4, 65536 bytes) TCP bind hash table entries: 4096 (order: 3, 49152 bytes) TCP: Hash tables configured (established 4096 bind 4096) NET: Registered protocol family 1 NET: Registered protocol family 17 Root-NFS: No NFS server available, giving up. VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "hda1" or unknown-block(2,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) "make uninstall && make install" seems to fix the problem. I have been able to recreate this problem on demand (4 times so far). Clearing the store does not seem to make a difference. Currently running latest Mercurial build (last changeset: 4083eb31def0 tip) -- Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ Xen-bugs mailing list Xen-bugs@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-bugs
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |