[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: Solution: apt-get (re)install hotplug (was Re: [Xen-devel] Re: Unable to find root device. domU??)
On 10/14/05, Nicholas Lee <emptysands@xxxxxxxxx> wrote: > No issue running using sda1 for /, which the same device name as used > by /boot in dom0. Actually I spoke to soon: nic@wuwei:/usr/src/xen/xen-unstable.hg$ sudo fdisk -l /dev/sda Disk /dev/sda: 73.2 GB, 73272393728 bytes 255 heads, 63 sectors/track, 8908 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 16 128488+ 82 Linux swap / Solaris /dev/sda2 17 78 498015 83 Linux /dev/sda3 79 564 3903795 83 Linux /dev/sda4 565 8908 67023180 8e Linux LVM The following works: disk = [ 'phy:ww/breezy-fs,sda1,w', 'phy:ww/breezy-swap,sda2,w', 'phy:ww/amd64-fs,sda4,w' ] However sda4 does not exist in domU: mount: special device /dev/sda4 does not exist the following does not work: disk = [ 'phy:ww/breezy-fs,sda1,w', 'phy:ww/breezy-swap,sda2,w', 'phy:ww/amd64-fs,sda3,w' ] This gives: VFS: Cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Changing to sda5 allows both breezy to boot as expected and /dev/sda5 to be mounted in the domU. -- Nicholas Lee http://stateless.geek.nz gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |