Hi, I am new to xen and am trying to boot a VM from an NFS server. I am using the default FC6-xen kernel and I do not have a /dev/nfs in dom0. My config file is : kernel = "/boot/vmlinuz-2.6.18-1.2798.fc6xen" name = "test8" memory = "512" uuid = "2cc550ec-550a-6ad2-8121-7b089fc7d051" vcpus=1 root = ''/dev/nfs'' nfs_server = ''xx.xx.xx.xx'' nfs_root = ''/home/xen-images/fc4'' I run into the following problem during boot: TCP bic registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vif/0 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "nfs" or unknown-block(0,255) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255) Please let me know what is that I am doing wrong. Thanks, Abhishek. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Tom, Sorry about the missing vif line in my previous post. I do have a vif line in my config file like "vif = [ ''mac=00:16:3e:20:5d:c9, bridge=xenbr0'', ]". I think its going down even before bringing up eth0 (the complete boot log is attached to this mail). I am suspecting of the missing /dev/nfs in dom0, which is required for the ''root'' parameter, as pointed out in xen user guide. Any suggestions ? -Abhishek Tom Brown wrote:> On Sun, 25 Feb 2007, Abhishek Gaurav wrote: > >> Hi, I am new to xen and am trying to boot a VM from an NFS server. I >> am using the default FC6-xen kernel and I do not have a /dev/nfs in >> dom0. My config file is : >> >> kernel = "/boot/vmlinuz-2.6.18-1.2798.fc6xen" >> name = "test8" >> memory = "512" >> uuid = "2cc550ec-550a-6ad2-8121-7b089fc7d051" >> vcpus=1 >> root = ''/dev/nfs'' >> nfs_server = ''xx.xx.xx.xx'' >> nfs_root = ''/home/xen-images/fc4'' > > if you''re running a current version of xen you''re going to need to > specify a vif line to get a virtual network interface... > > vif = [ '''' ] > > should suffice. > > >> >> I run into the following problem during boot: >> >> TCP bic registered >> Initializing IPsec netlink socket >> NET: Registered protocol family 1 >> NET: Registered protocol family 17 >> XENBUS: Device with no driver: device/vif/0 >> md: Autodetecting RAID arrays. >> md: autorun ... >> md: ... autorun DONE. >> VFS: Cannot open root device "nfs" or unknown-block(0,255) >> Please append a correct "root=" boot option >> Kernel panic - not syncing: VFS: Unable to mount root fs on >> unknown-block(0,255) >> >> >> Please let me know what is that I am doing wrong. > > if there is no reference to eth0 in your boot messages, you''re not > going to have a network, without a network you''re not going to have a > network file system... > > -Tom_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Tom, Sorry about the missing vif line in my previous post. I do have a vif line in my config file like "vif = [ ''mac=00:16:3e:20:5d:c9, bridge=xenbr0'', ]". I think its going down even before bringing up eth0 (the complete boot log is attached to this mail). I am suspecting of the missing /dev/nfs in dom0, which is required for the ''root'' parameter, as pointed out in xen user guide. Any suggestions ? -Abhishek Tom Brown wrote:> On Sun, 25 Feb 2007, Abhishek Gaurav wrote: > >> Hi, I am new to xen and am trying to boot a VM from an NFS server. I >> am using the default FC6-xen kernel and I do not have a /dev/nfs in >> dom0. My config file is : >> >> kernel = "/boot/vmlinuz-2.6.18-1.2798.fc6xen" >> name = "test8" >> memory = "512" >> uuid = "2cc550ec-550a-6ad2-8121-7b089fc7d051" >> vcpus=1 >> root = ''/dev/nfs'' >> nfs_server = ''xx.xx.xx.xx'' >> nfs_root = ''/home/xen-images/fc4'' > > if you''re running a current version of xen you''re going to need to > specify a vif line to get a virtual network interface... > > vif = [ '''' ] > > should suffice. > > >> >> I run into the following problem during boot: >> >> TCP bic registered >> Initializing IPsec netlink socket >> NET: Registered protocol family 1 >> NET: Registered protocol family 17 >> XENBUS: Device with no driver: device/vif/0 >> md: Autodetecting RAID arrays. >> md: autorun ... >> md: ... autorun DONE. >> VFS: Cannot open root device "nfs" or unknown-block(0,255) >> Please append a correct "root=" boot option >> Kernel panic - not syncing: VFS: Unable to mount root fs on >> unknown-block(0,255) >> >> >> Please let me know what is that I am doing wrong. > > if there is no reference to eth0 in your boot messages, you''re not > going to have a network, without a network you''re not going to have a > network file system... > > -Tom_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I am new to xen and am trying to boot a VM from an NFS server. > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,255) > > > Please let me know what is that I am doing wrong.Almost certainly do not have NFS_ROOT support compiled into your kernel. Not sure, but think you might be able to bypass that if you use the proper liturgy of invocations to your mkinitrd call. BTW, if you are attempting to merely get live migration going, a shared image file (through ordinary NFS sharing in the dom0) will work fine. Joe. p.s., "unknown block" comes up most often on my side of things when the kernel doesn''t quite understand how to grok the file system that it is attempting to mount from; can happen because of non-comprehension of SCSI, IDE, or NFS-based file systems all three. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users