thr3ads.net - Xen users - [Xen-users] problem with booting domU via NFS root [Jul 2007]

If this information is useful, please help other people find it:
Share via:

xen xen

2007-Jul-22 00:37 UTC

[Xen-users] problem with booting domU via NFS root

Hi all,

I have a problem with booting domU with its file system on an NFS server.
Here is the error I get after "xm create":

asds55:/home/xen/virtualmachines/asds-xen-187-nfs # xm create -c
dom-nfs.conf
Using config file "./dom-nfs.conf".
Started domain asds-xen-187
                           Bootdata ok (command line is
ipxxx.xx.150.187:xxx.xx.150.136:xxx.xx.150.254:255.255.255.0:asds-xen-187:eth0:offnfsrootxxx.xx.150.136:/home/xen/virtualmachines/asds-xen-187-fs
3)
Linux version 2.6.18-xen (root@asds58) (gcc version 4.1.2 20061115
(prerelease) (SUSE Linux)) #1 SMP Fri May 25 10:44:18 EDT 2007
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)

...
netfront: Initialising virtual ethernet driver.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
NET: Registered protocol family 17
netfront: device eth0 has copying receive path.
XENBUS: Device with no driver: device/console/0
IP-Config: Complete:
      device=eth0, addr=xxx.xx.150.135, mask=255.255.255.0, gwxxx.xx.xxx.xxx,
     host=asds-xen-187, domain=, nis-domain=(none),
     bootserver=xxx.xx.150.136, rootserver=xxx.xx.150.136, rootpathFreeing
unused kernel memory: 172k freed
Boot logging started on /dev/tty1(/dev/console) at Sat Jul 21 22:54:29 2007
Creating device nodes with udev
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised:
dm-devel@redhat.com
Loading dm-mod
Loading dm-snapshot
Waiting for /dev/mapper/control to appear: . ok
Loading jbd
Loading ext3
  Volume group "system" not found
Mounting root xxx.xx.150.136:/home/xen/virtualmachines/asds-xen-187-fs
mount: unknown filesystem type ''nfs''
umount: /dev: device is busy
umount: /dev: device is busy
umount: /dev/pts: device is busy
umount: /dev/pts: device is busy
Kernel panic - not syncing: Attempted to kill init!


On the NFS server this is how the /etc/exports looks:
/home/xen/virtualmachines/asds-xen-187-fs       *(rw,all_squash,sync)
I have no problem with regularly mounting this remote directory in dom0.


Here is some info about my system:
release                : 2.6.18-xen
version                : #1 SMP Fri May 25 10:44:18 EDT 2007
machine                : x86_64
xen_changeset          : Thu May 17 11:42:46 2007 +0100 15080:089696e0c603

I''m running the same kernel for both dom0 and domU and the distribution
is
Suse 10.2.

Here is the config file:
name    = "asds-xen-187"
memory  = 256
kernel   = "/boot/vmlinuz-2.6-xen"
ramdisk  = "/boot/initrd-2.6.18-xen"
# boot device:
root     = "/dev/nfs"
# boot to run level:
extra    = "3"
# storage devices:
nfs_server = ''xxx.xx.150.136''
nfs_root = ''/home/xen/virtualmachines/asds-xen-187-fs''
# network interface:
vif = [ ''bridge=xenbr0'' ]
ip = "xxx.xx.150.187"
gateway = "xxx.xx.150.254"
netmask="255.255.255.0"
hostname="asds-xen-187"



And these are the related modules I have in /boot/config-2.6.18-xen:
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_XEN=y
CONFIG_XEN_INTERFACE_VERSION=0x00030205
# XEN
CONFIG_XEN_PRIVILEGED_GUEST=y
# CONFIG_XEN_UNPRIVILEGED_GUEST is not set
CONFIG_XEN_PRIVCMD=y
CONFIG_XEN_XENBUS_DEV=y
CONFIG_XEN_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_BLKDEV_TAP=y
CONFIG_XEN_NETDEV_BACKEND=y
# CONFIG_XEN_NETDEV_PIPELINED_TRANSMITTER is not set
CONFIG_XEN_NETDEV_LOOPBACK=y
CONFIG_XEN_PCIDEV_BACKEND=m
# CONFIG_XEN_PCIDEV_BACKEND_VPCI is not set
CONFIG_XEN_PCIDEV_BACKEND_PASS=y
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BE_DEBUG is not set
CONFIG_XEN_TPMDEV_BACKEND=m
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y


Your help is appreciated, Thanks!


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

ardy mardy

2007-Jul-22 13:58 UTC

head link

[Xen-users] problem with booting domU via NFS root

Hi all,

I have a problem with booting domU with its file system on an NFS server.
Here is the error I get after "xm create":

asds55:/home/xen/virtualmachines/asds-xen-187-nfs # xm create -c
dom-nfs.conf
Using config file "./dom-nfs.conf".
Started domain asds-xen-187
                           Bootdata ok (command line is
ipxxx.xx.150.187:xxx.xx.150.136:xxx.xx.150.254:255.255.255.0:asds-xen-187:eth0:offnfsrootxxx.xx.150.136:/home/xen/virtualmachines/asds-xen-187-fs
3)
Linux version 2.6.18-xen (root@asds58) (gcc version 4.1.2 20061115
(prerelease) (SUSE Linux)) #1 SMP Fri May 25 10:44:18 EDT 2007
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)

...
netfront: Initialising virtual ethernet driver.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
NET: Registered protocol family 17
netfront: device eth0 has copying receive path.
XENBUS: Device with no driver: device/console/0
IP-Config: Complete:
      device=eth0, addr=xxx.xx.150.135, mask=255.255.255.0, gwxxx.xx.xxx.xxx,
     host=asds-xen-187, domain=, nis-domain=(none),
     bootserver=xxx.xx.150.136, rootserver=xxx.xx.150.136, rootpathFreeing
unused kernel memory: 172k freed
Boot logging started on /dev/tty1(/dev/console) at Sat Jul 21 22:54:29 2007
Creating device nodes with udev
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised:
dm-devel@redhat.com
Loading dm-mod
Loading dm-snapshot
Waiting for /dev/mapper/control to appear: . ok
Loading jbd
Loading ext3
  Volume group "system" not found
Mounting root xxx.xx.150.136:/home/xen/virtualmachines/asds-xen-187-fs
mount: unknown filesystem type ''nfs''
umount: /dev: device is busy
umount: /dev: device is busy
umount: /dev/pts: device is busy
umount: /dev/pts: device is busy
Kernel panic - not syncing: Attempted to kill init!


On the NFS server this is how the /etc/exports looks:
/home/xen/virtualmachines/asds-xen-187-fs       *(rw,all_squash,sync)
I have no problem with regularly mounting this remote directory in dom0.


Here is some info about my system:
release                : 2.6.18-xen
version                : #1 SMP Fri May 25 10:44:18 EDT 2007
machine                : x86_64
xen_changeset          : Thu May 17 11:42:46 2007 +0100 15080:089696e0c603

I''m running the same kernel for both dom0 and domU and the distribution
is
Suse 10.2.

Here is the config file:
name    = "asds-xen-187"
memory  = 256
kernel   = "/boot/vmlinuz-2.6-xen"
ramdisk  = "/boot/initrd-2.6.18-xen"
# boot device:
root     = "/dev/nfs"
# boot to run level:
extra    = "3"
# storage devices:
nfs_server = ''xxx.xx.150.136''
nfs_root = ''/home/xen/virtualmachines/asds-xen-187-fs''
# network interface:
vif = [ ''bridge=xenbr0'' ]
ip = "xxx.xx.150.187"
gateway = "xxx.xx.150.254"
netmask="255.255.255.0"
hostname="asds-xen-187"



And these are the related modules I have in /boot/config-2.6.18-xen:
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_XEN=y
CONFIG_XEN_INTERFACE_VERSION=0x00030205
# XEN
CONFIG_XEN_PRIVILEGED_GUEST=y
# CONFIG_XEN_UNPRIVILEGED_GUEST is not set
CONFIG_XEN_PRIVCMD=y
CONFIG_XEN_XENBUS_DEV=y
CONFIG_XEN_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_BLKDEV_TAP=y
CONFIG_XEN_NETDEV_BACKEND=y
# CONFIG_XEN_NETDEV_PIPELINED_TRANSMITTER is not set
CONFIG_XEN_NETDEV_LOOPBACK=y
CONFIG_XEN_PCIDEV_BACKEND=m
# CONFIG_XEN_PCIDEV_BACKEND_VPCI is not set
CONFIG_XEN_PCIDEV_BACKEND_PASS=y
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BE_DEBUG is not set
CONFIG_XEN_TPMDEV_BACKEND=m
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y


Your help is appreciated, Thanks!


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Steve Kemp

2007-Jul-22 21:24 UTC

head link

Re: [Xen-users] problem with booting domU via NFS root

On Sat Jul 21, 2007 at 20:37:12 -0400, xen xen wrote:
>    mount: unknown filesystem type ''nfs''
  There''s your error.
>    And these are the related modules I have in /boot/config-2.6.18-xen:
>    CONFIG_NFS_FS=m
>    CONFIG_NFS_V3=y
>    CONFIG_NFS_V3_ACL=y
>    CONFIG_NFS_V4=y
>    CONFIG_NFS_DIRECTIO=y
>    CONFIG_NFSD=m
>    CONFIG_NFSD_V2_ACL=y
>    CONFIG_NFSD_V3=y
>    CONFIG_NFSD_V3_ACL=y
>    CONFIG_NFSD_V4=y
>    CONFIG_NFSD_TCP=y
>    CONFIG_NFS_ACL_SUPPORT=m
>    CONFIG_NFS_COMMON=y
  You need "CONFIG_ROOT_NFS" - that allows the root filesystem to
 come from NFS.

  This article gives a brief overview from the last time I did this,
 obviously not your distribution but it might be helpful:

    http://www.debian-administration.org/articles/505

Steve
-- 

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

ardy mardy

2007-Jul-23 17:26 UTC

head link

Re: [Xen-users] problem with booting domU via NFS root

Thanks Steve. For some reason I don''t have the CONFIG_ROOT_NFS option
in my
kernel.
My problem is much the same as the one described on this page:
http://forums.gentoo.org/viewtopic-t-337239-highlight-.html?sid=f0de502989c707746fcebef76a1267d1

However, I had all the following enabled but still to no avail:
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=yCONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y

I also tried "make CONFIG_ROOT_NFS=y world" and no luck there either.

Thanks,
Ardy

On 7/22/07, Steve Kemp <steve@steve.org.uk> wrote:>
> On Sat Jul 21, 2007 at 20:37:12 -0400, xen xen wrote:
>
> >    mount: unknown filesystem type ''nfs''
>
>   There''s your error.
>
> >    And these are the related modules I have in
/boot/config-2.6.18-xen:
> >    CONFIG_NFS_FS=m
> >    CONFIG_NFS_V3=y
> >    CONFIG_NFS_V3_ACL=y
> >    CONFIG_NFS_V4=y
> >    CONFIG_NFS_DIRECTIO=y
> >    CONFIG_NFSD=m
> >    CONFIG_NFSD_V2_ACL=y
> >    CONFIG_NFSD_V3=y
> >    CONFIG_NFSD_V3_ACL=y
> >    CONFIG_NFSD_V4=y
> >    CONFIG_NFSD_TCP=y
> >    CONFIG_NFS_ACL_SUPPORT=m
> >    CONFIG_NFS_COMMON=y
>
>   You need "CONFIG_ROOT_NFS" - that allows the root filesystem to
> come from NFS.
>
>   This article gives a brief overview from the last time I did this,
> obviously not your distribution but it might be helpful:
>
>     http://www.debian-administration.org/articles/505
>
> Steve
> --
>
> _______________________________________________
> 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

Steve Kemp

2007-Jul-23 18:36 UTC

head link

Re: [Xen-users] problem with booting domU via NFS root

On Mon Jul 23, 2007 at 13:26:08 -0400, ardy mardy wrote:
>    I also tried "make CONFIG_ROOT_NFS=y world" and no luck there
either.
  I pointed you at an article describing where to enable the relevant
 option.  The Gentoo page you reference also describes where to enable
 the option.  Typing random commands and expecting it to work by magic
 isn''t going to get you anywhere.

  Follow the instructions in the Xen README for building a kernel:

    # make linux-2.6-xen-config CONFIGMODE=menuconfig
    # make linux-2.6-xen-build
    # make linux-2.6-xen-install

  When you''re in the "menuconfig" stage enable:

  Device Drivers --> Networking support ---> Networking options --->
IP: kernel level autoconfiguration
  Device Drivers --> Networking support ---> Networking options --->
IP: DHCP Support
  File Systems ---> Network File Systems ---> Root file system on NFS >

  Once you do that you''ll have a working system.  Simply by following
 instructions.  No magic!

Steve
-- 

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

ardy mardy

2007-Jul-23 20:09 UTC

head link

Re: [Xen-users] problem with booting domU via NFS root

Thanks. I apologize if I was n''t clear enough in my previous post. When
I
get into the menuconfig stage ( after "make
linux-2.6-xen-configCONFIGMODE=menuconfig" as you also suggested), I
don''t see an option for
enabling CONFIG_ROOT_NFS.  The Gentoo page also starts by saying this option
did not exist for the user at the menuconfig stage, not until the the
following options were set:
 Device Drivers --> Networking support ---> Networking options ---> IP:
kernel level autoconfiguration
 Device Drivers --> Networking support ---> Networking options ---> IP:
DHCP
Support

However, even by having the above options set, I still do n''t have a
away to
set CONFIG_ROOT_NFS!
This is my view of options in File Systems ->  Network File Systems:
x x              <M> NFS file system support
                         x x
  x x              [*]   Provide NFSv3 client support
                            x x
  x x              [*]     Provide client support for the NFSv3 ACL protocol
extension                  x x
  x x              [*]   Provide NFSv4 client support (EXPERIMENTAL)
                           x x
  x x              [*]   Allow direct I/O on NFS files (EXPERIMENTAL)
                            x x
  x x              <M> NFS server support
                            x x
  x x              [*]   Provide NFSv3 server support
                            x x
  x x              [*]     Provide server support for the NFSv3 ACL protocol
extension                  x x
  x x              [*]     Provide NFSv4 server support (EXPERIMENTAL)
                           x x
  x x              ---   Provide NFS server over TCP support
                           x x
  x x              --- Secure RPC: Kerberos V mechanism (EXPERIMENTAL)
                           x x
  x x              <M> Secure RPC: SPKM3 mechanism (EXPERIMENTAL)
                            x x
  x x              <M> SMB file system support (to mount Windows shares
etc.)                           x x
  x x              [*]   Use a default NLS
                           x x
  x x              (cp850) Default Remote NLS Option
                           x x
  x x              <M> CIFS support (advanced network filesystem for
Samba,
Window and other CIFS complix x
  x x              [*]   CIFS statistics
                           x x
  x x              [ ]     Extended statistics
                           x x
  x x              [ ]   Support legacy servers which use weaker LANMAN
security                        x x

<M> CIFS support (advanced network filesystem for Samba, Window and other
CIFS complix x
  x x              [*]   CIFS statistics
                           x x
  x x              [ ]     Extended statistics
                           x x
  x x              [ ]   Support legacy servers which use weaker LANMAN
security                        x x
  x x              [*]   CIFS extended attributes
                            x x
  x x              [*]     CIFS POSIX Extensions
                           x x
  x x              [ ]   Enable additional CIFS debugging routines
                           x x
  x x              [ ]   CIFS Experimental Features (EXPERIMENTAL)
                           x x
  x x              <M> NCP file system support (to mount NetWare volumes)
                            x x
  x x              [*]   Packet signatures
                           x x
  x x              [*]   Proprietary file locking
                            x x
  x x              [*]   Clear remove/delete inhibit when needed
                           x x
  x x              [*]   Use NFS namespace if available
                            x x
  x x              [*]   Use LONG (OS/2) namespace if available
                            x x
  x x              [*]   Lowercase DOS filenames
                           x x
  x x              [*]   Use Native Language Support
                           x x
  x x              [*]   Enable symbolic links and execute flags
                           x x
  x x              <M> Coda file system support (advanced network fs)
                            x x
  x x              [ ]   Use 96-bit Coda file identifiers
                            x x
  x x              <M> Andrew File System support (AFS) (Experimental)
                           x x
  x x              <M> Plan 9 Resource Sharing Support (9P2000)
(Experimental)                          x x

And the reason I tried "make CONFIG_ROOT_NFS=y world" was the
following
post:
http://lists.xensource.com/archives/html/xen-users/2006-08/msg00711.html

I''m no linux/xen expert, but I know this much that there is no magic.
That''s
why I looked around for a solution.
Thanks to you and others on the list for taking the time to help beginners
like me despite our stupid questions/problems!



On 7/23/07, Steve Kemp <steve@steve.org.uk> wrote:>
> On Mon Jul 23, 2007 at 13:26:08 -0400, ardy mardy wrote:
>
> >    I also tried "make CONFIG_ROOT_NFS=y world" and no luck
there either.
>
>   I pointed you at an article describing where to enable the relevant
> option.  The Gentoo page you reference also describes where to enable
> the option.  Typing random commands and expecting it to work by magic
> isn''t going to get you anywhere.
>
>   Follow the instructions in the Xen README for building a kernel:
>
>     # make linux-2.6-xen-config CONFIGMODE=menuconfig
>     # make linux-2.6-xen-build
>     # make linux-2.6-xen-install
>
>   When you''re in the "menuconfig" stage enable:
>
>   Device Drivers --> Networking support ---> Networking options
---> IP:
> kernel level autoconfiguration
>   Device Drivers --> Networking support ---> Networking options
---> IP:
> DHCP Support
>   File Systems ---> Network File Systems ---> Root file system on NFS
>
>
>   Once you do that you''ll have a working system.  Simply by
following
> instructions.  No magic!
>
> Steve
> --
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Stephan Seitz

2007-Jul-24 07:30 UTC

head link

[Xen-users] Re: problem with booting domU via NFS root

On Mon, Jul 23, 2007 at 04:09:27PM -0400, ardy mardy
wrote:> However, even by having the above options set, I still do n''t have
> a away to set CONFIG_ROOT_NFS!
> This is my view of options in File Systems ->  Network File Systems:
> x x              <M> NFS file system support
How do you expect to get ROOT NFS working if your NFS support is only 
a module and must be loaded from the root filesystem which you want to 
have via NFS? ;-)
To get ROOT NFS working you need everything for this situation static in 
the kernel. So you have to say <*> (yes) for „NFS file system support”.  
Then you should get the new option for CONFIG_ROOT_NFS.

Your network drivers must be in the kernel as well including IP support.

Shade and sweet water!

	Stephan

-- 
| Stephan Seitz                    E-Mail: Nur-Ab-Sal@gmx.de |
| PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html |


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

ardy mardy

2007-Jul-24 17:50 UTC

head link

Re: [Xen-users] Re: problem with booting domU via NFS root

Thanks Stephan.  I did what you suggested and NFS boot + live migration
worked flawlessly. I was under the impression that since during boot we use
the kernel and initrd in /boot directory of the local machine, and not the
one on the server, module support should work fine through initrd.
Apparently, initrd is only used for certain modules at the initial stage of
boot?

For those who may come across this thread later to setup NFS + live
migration, I had to change /etc/exports from having the option all_squash to
no_root_squash; yes silly! :)

Ardy


On 7/24/07, Stephan Seitz <nur-ab-sal@gmx.de>
wrote:>
> On Mon, Jul 23, 2007 at 04:09:27PM -0400, ardy mardy wrote:
> > However, even by having the above options set, I still do n''t
have
> > a away to set CONFIG_ROOT_NFS!
> > This is my view of options in File Systems ->  Network File
Systems:
> > x x              <M> NFS file system support
>
> How do you expect to get ROOT NFS working if your NFS support is only
> a module and must be loaded from the root filesystem which you want to
> have via NFS? ;-)
> To get ROOT NFS working you need everything for this situation static in
> the kernel. So you have to say <*> (yes) for „NFS file system
support".
> Then you should get the new option for CONFIG_ROOT_NFS.
>
> Your network drivers must be in the kernel as well including IP support.
>
> Shade and sweet water!
>
>         Stephan
>
> --
> | Stephan Seitz                    E-Mail: Nur-Ab-Sal@gmx.de |
> | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html |
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGpaqXXse+NwPOAZ4RAnwoAJ9kKVJDow/ADeaR1Mhe82bRsJoEawCeJ+Xq
> Aylef5Q2oUQf6+zmhiqghDE> =NKBH
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> 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

Xen users - Jul 2007 - problem with booting domU via NFS root

[Xen-users] problem with booting domU via NFS root

[Xen-users] problem with booting domU via NFS root

Re: [Xen-users] problem with booting domU via NFS root

Re: [Xen-users] problem with booting domU via NFS root

Re: [Xen-users] problem with booting domU via NFS root

Re: [Xen-users] problem with booting domU via NFS root

[Xen-users] Re: problem with booting domU via NFS root

Re: [Xen-users] Re: problem with booting domU via NFS root