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

[Xen-users] static ip for hvm's


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Tommie McAfee" <tahmmee@xxxxxxxxx>
  • Date: Fri, 10 Nov 2006 16:20:49 -0500
  • Delivery-date: Fri, 10 Nov 2006 13:21:12 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=YOPkESsQuhwFqPWL46wTIvsKeW8vxpE/z01Qa3YwymJXcfx/9QehWwQ6DLTpK9fuQuIZ/xTLRAULkK47dKkoJES9EpOU/hR3yTqMd+uoaM6ngub/9T5lsD643+VtoZhSq/mB7FI7GLlUUXq2MSuDDn6FNJSriSl7Q0NolVzRvdU=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I've been able to successfully start paravirtualized guests with static ip address' by using the network-route and vif-route scripts, but this method doesn't seem to work in the fully virtualized realm of things.  For testing purposes I want to have guests started with predetermined ip's and not have to console into them and set the address my self.  I think there's a way to do this with qemu, and so it seems like it should be possible with xen as well, but I can't figure it out?  I've considered running a special domU as a dhcp server and having it assign IP's to my guests, but this option is reserved as my last resort. 

Any suggestions?

--------
a.out
_______________________________________________
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®.