[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Re: exception looking up device number for sda1


  • To: "Xen Users" <Xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Anand Gupta" <xen.mails@xxxxxxxxx>
  • Date: Mon, 22 May 2006 05:28:52 +0530
  • Delivery-date: Sun, 21 May 2006 16:59:25 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=ZyPqPVq019fYFQ0i0ot3uDwySqwDhqMsPMSdYKvky4Wr0eBa9E2oyJpn9S5ab2ereKkCSYsH0CZLVjknigP31qJ5huZDdFicRVDLBWtuXJ5HRvLym/umoyDgII3KzqhTn2w+9GeL4Zi3RjdrV0FPE2qtcEi2nTIDfcghhhLXW1k=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I have a custom script which i use to start the domU.

It seems that my router is not able to direct traffic for the additional ips i have allocated to the first domU (i am running a routed network), hence the custom script.

ping -b -c 1 255.255.255.255
arp -s x.x.x.x z:z:z:z:z:z pub
ip route add x.x.x.x dev vm03 src y.y.y.y

Above x.x.x.x is my domU ip and y.y.y.y is my dom0 ip. The above enables me to get ping on the additional ips i have on my domU's. z:z:z:z:z:z is the macid for my nic.

Now when i remove these additional lines and just use xm create to start the domU, the second domU also starts up. After the second domU starts up i issue the above commands and the second domU is still working properly.

What in the above commands could be the cause of problems with starting up second domU.

Thanks.

--
regards,

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.