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-users] Xen virtual interface settings

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen virtual interface settings
From: "Grant McWilliams" <grantmasterflash@xxxxxxxxx>
Date: Thu, 11 Dec 2008 12:36:35 -0800
Delivery-date: Thu, 11 Dec 2008 12:37:16 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=jNtRd3De2SdkxzKmM0UM3RyYm+0oRiQ8C74v22p3rFo=; b=C7pTa5B6cPCl2dBW4Xa4kpQ1qtb2jaXR+OE2PbPPJrSgxYRI43wqk9+VQooXOnMMok olqz4u+zgUd34FWIV1j8DGfIXeWRP1ngRu/YukC45W4JVeJoTXot/D3ey0NoX3yy2Zgv z1sUhi9GCZhG2s/RyYGmYwYHYbrLB5cXK5T2k=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=DTFMGdC7hsPN0TUNjpdI96i/WzZqoC/rpCsq/tBXldjzxpEz62v+yJB1h6ldsShhv/ 4S4zH7LWtGyS08E274a1W1LuY7c4QBJQo4M+9BV4qMynIOZXbM74ijmDA1s1R21JjK7Y Zuvm4hoQpd/bT0le1GtU942dNllkTwZFKe6KU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I've been mucking with xen for quite a while but recently started focusing on custom network setups. I'd like to be able to create VMs on the fly from a base image and set network settings in each without booting the image up.

This strange setup is for a classroom environment. At the beginning of the quarter the instructor would run a script that creates all the student's DomUs and assigns a route to them on the Dom0 from the WAN . The goal is to have a remote port (say 10001) be redirected to the students virtual machine's port 22. Each student would access their VM using a different remote port. All of the students VMs will be copies (or using qcow2 backing file) of  a base image so will be identical to save space and setup time.

It seems like I had it easy by setting vif = [ 'ip=x.x.x.x' ] but this doesn't seem to do anything. According to Running Xen you need to statically set the ip inside the DomU as well as setting it in the domU config file. Doesn't setting it in both places defeat the purpose of having it in the DomU config file to start with?

My next thought was to set the mac address in the DomU config file and then have the client OS request an IP from a DHCP server which would IP addresses based on the mac address noted in the domU config file. The mac address assigned also doesn't seem to do anything.

Does anyone have any ideas how to accomplish this? I'm sure I could power up each VM, access it via ssh and reset the IP then power it down via script but for 30 students this will take a while. I assumed that I'd be able to differentiate between the DomUs from the Dom0 without modification of the DomU network files.



Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>