Re: Fwd: [Xen-users] Unable to create more than 1 VM

[jim burns <jim_burn@xxxxxxxxxxxxx>]

On Sunday June 08 2008 08:32:47 am Thomas wrote:
> @Jim: mac address in vif? I thought it was an IPv4 address I had to
> put. What should I put then? Any figures?

Xen recommends using a mac address in the block starting with 00:16:3e, so:

> vif = [ 'ip=10.0.0.1' ]

becomes vif = [ 'mac=00:16:3e:jk:lm:no' ]. Substitute unique numbers for 
jklmno in each different vm. You may keep the ip= parm, but it doesn't seem 
to be doing what you want - see below.

> disk = [ 'phy:/dev/mapper/xenvg-node01,/dev/hda1,w',
> 'phy:/dev/mapper/xenvg-node01--swap,hda2,w' ]

If you are using xen 3.1 or up, you can substitute xvda for each hda above for 
a small performance increase.

> kernel="/boot/domU_32/vmlinuz-2.6.21-xxxx-xenU-ipv4-32"

> kernel="/boot/domU_32/vmlinuz-2.6.21-xxxx-xenU-ipv4-64"

Little confused: is one a 32 bit domain, and one a 64 bit domain? With xen 
3.0.3, this may not work. Should work fine with xen 3.1 and up.

> bind() failed

Have no clue what that means.

> vif56.0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet addr:10.0.0.128  Bcast:0.0.0.0  Mask:255.255.255.255
>
> vif57.0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet addr:10.0.0.129  Bcast:0.0.0.0  Mask:255.255.255.255
> --------------------------------------------------------------
>
> I have noticed that when only 1 VM is running I only have 1 vifxx.0
> When I start a second VM (although it hangs) I see a second vif that
> appears, is that normal?

Sounds normal. Part of domain creation is device creation. Once the 2nd domain 
is created tho', it hangs.

What concerns me is that one of your vifs has your gateway address. Not only 
that, vifs don't normally have an ip at all in bridging mode. What's the 
ifconfig output of your working vm? I don't know how long the ip= parm in 
your config lasts during domain creation, but once the vm is up, it gets it's 
own ip the same way any physical machine gets it - the way you set it up in 
system-config-network, or your distro's equivalent. Make sure the vm has a 
static address set to 10.0.0.1 for the first vm, .02 for the second, etc.

Good luck.

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