I cannot start my domU: 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 4096 buckets, 64Kbytes TCP established hash table entries: 131072 (order: 9, 2097152 bytes) TCP bind hash table entries: 65536 (order: 7, 786432 bytes) TCP: Hash tables configured (established 131072 bind 65536) NET: Registered protocol family 1 NET: Registered protocol family 17 IP-Config: Incomplete network configuration information. 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) Perhaps i have to add something to the menuconfig before compiling the domU? Because it will not found my virtual hda1. (I don''t use a root-NFS.) disk = [ ''phy:xenvg/test-root,hda1,w'' ] Any sugesstions? Thanks Stephan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tuesday 27 September 2005 17:32, Stephan Böni wrote:> I cannot start my domU: > > xen_blk: Initialising virtual block device driver > xen_blk: Timeout connecting to device!^^^^ looks like this is the problem.... the domU can''t connect the virtual hda1 device.> 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) > > Perhaps i have to add something to the menuconfig before compiling the > domU? Because it will not found my virtual hda1. (I don''t use a root-NFS.) > > disk = [ ''phy:xenvg/test-root,hda1,w'' ] > > Any sugesstions?Well, doesn''t neccessarily look like a domU kernel problem to me, maybe check the xen logs inside dom0 if there are some problems on that side. /Ernst _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Ursprüngliche Nachricht----- > Von: David F Barrera [mailto:dfbp@us.ibm.com] > Gesendet: Dienstag, 27. September 2005 18:07 > > On Tue, 2005-09-27 at 17:55 +0200, Stephan Böni wrote: > > > -----Ursprüngliche Nachricht----- > > > Von: Ernst Bachmann [mailto:e.bachmann@xebec.de] > > > Gesendet: Dienstag, 27. September 2005 17:37 > > > > > > On Tuesday 27 September 2005 17:32, Stephan Böni wrote: > > > > I cannot start my domU: > > > > > > > > xen_blk: Initialising virtual block device driver > > > > xen_blk: Timeout connecting to device! > > > ^^^^ > > > looks like this is the problem.... > > > the domU can't connect the virtual hda1 device. > > > > > > Well, doesn't neccessarily look like a domU kernel problem to > > > me, maybe check > > > the xen logs inside dom0 if there are some problems on that side. > > > > Right. I've build my own Dom0 kernel. But using this kernel i can't > > even find my volume group. Do you know what i have to activate in > > the menuconfig for my Dom0 kernel for using lvm devices? i haven't > > found anything how looks like this. > > Device Drivers > Multi-device support (RAID and LVM) > Device mapper > supportThat's already selected. :-( Stephan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
You need absolute paths for devices. -Kip On 9/27/05, Stephan Böni <boeni@bpm.ch> wrote:> > > > > -----Ursprüngliche Nachricht----- > > Von: David F Barrera [mailto:dfbp@us.ibm.com] > > Gesendet: Dienstag, 27. September 2005 18:07 > > > > On Tue, 2005-09-27 at 17:55 +0200, Stephan Böni wrote: > > > > -----Ursprüngliche Nachricht----- > > > > Von: Ernst Bachmann [mailto:e.bachmann@xebec.de] > > > > Gesendet: Dienstag, 27. September 2005 17:37 > > > > > > > > On Tuesday 27 September 2005 17:32, Stephan Böni wrote: > > > > > I cannot start my domU: > > > > > > > > > > xen_blk: Initialising virtual block device driver > > > > > xen_blk: Timeout connecting to device! > > > > ^^^^ > > > > looks like this is the problem.... > > > > the domU can''t connect the virtual hda1 device. > > > > > > > > Well, doesn''t neccessarily look like a domU kernel problem to > > > > me, maybe check > > > > the xen logs inside dom0 if there are some problems on that side. > > > > > > Right. I''ve build my own Dom0 kernel. But using this kernel i can''t > > > even find my volume group. Do you know what i have to activate in > > > the menuconfig for my Dom0 kernel for using lvm devices? i haven''t > > > found anything how looks like this. > > > > Device Drivers > Multi-device support (RAID and LVM) > Device mapper > > support > > That''s already selected. :-( > > Stephan > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Sep 27, 2005 at 11:18:09AM -0700, Kip Macy wrote: " You need absolute paths for devices. I use absolute paths and have the same problem starting xenUs with the current pull. Latest ChangeSet: Wed Sep 28 11:15:20 2005 ce54669c70fced4e8647065bfe6acf5efb147f98 $ xm create -c name=devel kernel=/boot/vmlinuz-2.6-xenU builder=linux memory=190 cpu=-1 disk=phy:/dev/xenvg/devel.root,hda1,rw disk=phy:/dev/xenvg/devel.swap,hda2,rw vcpus=1 vif=mac=aa:00:98:03:91:14 root=/dev/hda1 [...] Xen virtual console successfully installed as tty1 Event-channel device installed. xen_blk: Initialising virtual block device driver xen_blk: Timeout connecting to device! xen_net: Initialising virtual ethernet driver. [...] VFS: Cannot open root device "hda1" or unknown-block(2,0) Same symptoms as bug 176 from August. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=176 The comments on 176 include this: Problem resolved as of: changeset: 6401:98a6eb458c783cbbb8f19e5713a4ad8a1ea830c6 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Thu Aug 25 11:25:26 2005 summary: Memory management fixes. Page tables are created, buddy allocator now changeset: 6400:b88c5350de57a1fc18943cbb33fa72c348004fc8 user: kaf24@firebug.cl.cam.ac.uk date: Thu Aug 25 11:21:19 2005 summary: This patch fixes Bugzilla #169. (It should fix #187 too -- Keir). _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I realized after I sent the message that you only need absolute paths for loopback files, the /dev/ is implicit. If you're using this on a machine that has udev or hotplug then I'm not sure. -Kip On 9/28/05, David Becker <becker@cs.duke.edu> wrote:> > > On Tue, Sep 27, 2005 at 11:18:09AM -0700, Kip Macy wrote: > " You need absolute paths for devices. > > I use absolute paths and have the same problem starting xenUs with the > current pull. > Latest ChangeSet: Wed Sep 28 11:15:20 2005 > ce54669c70fced4e8647065bfe6acf5efb147f98 > > > $ xm create -c name=devel kernel=/boot/vmlinuz-2.6-xenU builder=linux > memory=190 cpu=-1 disk=phy:/dev/xenvg/devel.root,hda1,rw > disk=phy:/dev/xenvg/devel.swap,hda2,rw vcpus=1 vif=mac=aa:00:98:03:91:14 > root=/dev/hda1 > [...] > Xen virtual console successfully installed as tty1 > Event-channel device installed. > xen_blk: Initialising virtual block device driver > xen_blk: Timeout connecting to device! > xen_net: Initialising virtual ethernet driver. > [...] > VFS: Cannot open root device "hda1" or unknown-block(2,0) > > > Same symptoms as bug 176 from August. > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=176 > > The comments on 176 include this: > Problem resolved as of: > changeset: 6401:98a6eb458c783cbbb8f19e5713a4ad8a1ea830c6 > tag: tip > user: kaf24@firebug.cl.cam.ac.uk > date: Thu Aug 25 11:25:26 2005 > summary: Memory management fixes. Page tables are created, > buddy allocator now > > changeset: 6400:b88c5350de57a1fc18943cbb33fa72c348004fc8 > user: kaf24@firebug.cl.cam.ac.uk > date: Thu Aug 25 11:21:19 2005 > summary: This patch fixes Bugzilla #169. (It should fix #187 too -- Keir). >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
" [...] " Xen virtual console successfully installed as tty1 " Event-channel device installed. " xen_blk: Initialising virtual block device driver " xen_blk: Timeout connecting to device! " xen_net: Initialising virtual ethernet driver. " [...] " VFS: Cannot open root device "hda1" or unknown-block(2,0) " Turns out dom-0 was missing the hotplug scripts so apt-get install hotplug fixed the problem and got domU booting again. boeni@bpm.ch _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users