This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-API] Unable to start a domain with nfsroot (no ip conf passed)

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] Unable to start a domain with nfsroot (no ip conf passed)
From: Saurabh Garg <saurabh.g.garg@xxxxxxxxxx>
Date: Fri, 13 Jul 2007 15:23:59 +0530
Delivery-date: Fri, 13 Jul 2007 02:52:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <AFA5A607-0703-49B2-B255-2B508F46BD4C@xxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <4695D9D8.9080400@xxxxxxxxxx> <06774390-4A3D-423D-83FC-989DF7EE2BD6@xxxxxxxxx> <4695FB6D.9030808@xxxxxxxxxx> <AFA5A607-0703-49B2-B255-2B508F46BD4C@xxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20070509)

I am trying to create a domU, which has its root file system on the nfsserver. I put the pvArgs fieds as follows:

ip=DHCP nfsroot=<NFS_SERVER_IP>:/vm

where NFS_SERVER_IP is the address of my nfs server, with the roor partition available at /vm location.

While starting this machine however, I get the following

IP-Config: Guessing netmask
IP-Config: Complete:
    device=eth0, addr=, mask=, gw=,
    host=, domain=, nis-domain=(none),
    bootserver=, rootserver=<NFS_SERVER_IP>, rootpath=

And the nfs server can not be connected after this, following which the vm start fails.

However, if I specify the ip string completely, as <client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:eth0:off, I'm able to get my domain up. The kernel is patched for nfsroot support.

I guess I'm, missing out some configuration, that will enable all the ip parameters to be auto-configured. Can some one please provide some insight into what the exact ip string should look like in this case.


xen-api mailing list

<Prev in Thread] Current Thread [Next in Thread>