Nicholas Lee
2005-Oct-14 00:32 UTC
Solution: apt-get (re)install hotplug (was Re: [Xen-devel] Re: Unable to find root device. domU??)
On 10/14/05, Nicholas Lee <emptysands@gmail.com> wrote:> 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)Just realised the 3.0 depends on hotplug which I''d uninstalled over the weekend. I did this unintentionally when bringing using dpkg --set-selections from a Xen 2.0 machine. Reinstalling and createy the privileged domU provided this change: md: ... autorun DONE. Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1) Recompiling the standard domU and looks that the lack of hotplug was the problem. Or at least one of the problems. Only issue I seem to be seeing is: /dev/mem: mmap: Resource temporarily unavailable Couldnt get a file descriptor referring to the console No issue running using sda1 for /, which the same device name as used by /boot in dom0. nic@wuwei:/etc/xen$ sudo xm create breezy -c Using config file "breezy". Started domain breezy Linux version 2.6.12-xenU (nic@wuwei) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #3 SMP Fri Oct 14 12:58:11 NZDT 2005 kernel direct mapping tables upto 10000000 @ 4be000-540000 Built 1 zonelists Kernel command line: root=/dev/sda1 ro 4 Initializing CPU#0 ... Network now works: nic@breezy:~$ ifconfig eth0 Link encap:Ethernet HWaddr AA:00:00:88:02:40 inet addr:192.168.88.240 Bcast:192.168.88.255 Mask:255.255.255.0 ... breezy is a 32bit base Breezy ubuntu domain with ubuntu-desktop installed. Performances seems to be about as expected: nic@breezy:~/sys/ufc$ ./speedf Running UFC-crypt for 100 seconds of virtual time ... Did 147898.370000 fcrypt()s per second. 3.5% less vs native 32bit: nic@wuwei:~/sys/ufc$ ./speedf Running UFC-crypt for 100 seconds of virtual time ... Did 153237.030000 fcrypt()s per second. -- Nicholas Lee http://stateless.geek.nz gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Nicholas Lee
2005-Oct-14 01:11 UTC
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@gmail.com> 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@lists.xensource.com http://lists.xensource.com/xen-devel