WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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

To: "jim burns" <jim_burn@xxxxxxxxxxxxx>
Subject: Re: Fwd: [Xen-users] Unable to create more than 1 VM
From: Thomas <iamkenzo@xxxxxxxxx>
Date: Sun, 8 Jun 2008 14:32:47 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 08 Jun 2008 05:33:20 -0700
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:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=uP1CqFaL8GSyNAXcO+PEoRUphcEgnE3lt3EElqhTDYw=; b=D/HNM6l1mmTgTVBflxHq0IirIqUDzLPEI+8FSnm3NZUPyIzz6Ew9tODuh6B2l9Qa/5 CwQGPxGNU2CMqGncER4XY2lRr++R9l7Wsg9jxrmk6jQsteNli5+LOQMG7LvPxxNhjDk4 LdOHDMoq+PmwPEF3xhirRjdUEqYJx4SK8+ahU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=xpgUQZSyyLixnbtuPwGEAKxnmXErL99QhjZ/0m5MxtbAH+LYdoiw8uqTO2LV4+H767 na4p4uKT8mrALHKaDsz3X6EGzo4EkWN0BtcqvPBzUrDnGPrc1H46hEydbG6fs2XqOKbj i3wYdFJSWh0rGGB5LGXo72bBvsTw32opdv9M0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200806071852.17031.jim_burn@xxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <55da14450806071104m397f9346v3ee0ea82052bc3b8@xxxxxxxxxxxxxx> <55da14450806071228o4709536cje5d6756ad085c52f@xxxxxxxxxxxxxx> <55da14450806071236i10959459g8201071696b0b725@xxxxxxxxxxxxxx> <200806071852.17031.jim_burn@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi, Thank you all for your help. Here is a very long email, with all
the info I thought might be interesting.

@Stephan: I use different lvms for each VM.

@Felix, yes I am using a KimsufiXL server.

@Jim: mac address in vif? I thought it was an IPv4 address I had to
put. What should I put then? Any figures?


Here are my config files:

node01:
--------------------------------------------------------------
#  -*- mode: python; -*-
kernel="/boot/domU_32/vmlinuz-2.6.21-xxxx-xenU-ipv4-32"
memory = "256"
maxmem = "512"
name = "node01"
vcpus=1
interface=eth0
dhcp="off"
vif = [ 'ip=10.0.0.1' ]         # replace with DomU's IP
ip = "10.0.0.1"
gateway= "10.0.0.128"                   # Dom0
netmask = "255.255.255.0"
# example for LVM or partition
disk = [ 'phy:/dev/mapper/xenvg-node01,/dev/hda1,w',
'phy:/dev/mapper/xenvg-node01--swap,hda2,w' ]

# example for image file
#disk = [ 'file:xen/xenvg-node0001.img,hda1,w',
'file:/xen/xenvg-node0001-swap.img,hda2,w' ]

# This uses environment variables XAUTHORITY and DISPLAY.  You
# can override that:
# vfb = [ 'type=sdl,xauthority=/home/bozo/.Xauthority,display=:1' ]
#
# To create one using the VNC backend and sensible defaults:
vfb = [ 'type=vnc' ]
# The backend listens on 127.0.0.1 port 5900+N by default, where N is
# the domain ID.  You can override both address and N:
#
# Or you can bind the first unused port above 5900:
# vfb = [ 'type=vnc,vnclisten=0.0.0.0,vnunused=1' ]
# You can override the password:
# vfb = [ 'type=vnc,vncpasswd=MYPASSWD' ]

# Set the hostname.
#hostname= "node%d" % vmid

# Set root device.
root = "/dev/hda1"

# Sets runlevel 2.
#extra = "2"
extra='console=xvc0 xencons=xvc0'
#sdl=0
#vnc=0
nographics=0
--------------------------------------------------------------

node02:
--------------------------------------------------------------
#  -*- mode: python; -*-
kernel="/boot/domU_64/vmlinuz-2.6.21-xxxx-xenU-ipv4-64"
memory = "256"
maxmem = "512"
name = "node02"
vcpus=1
#interface=eth0
dhcp="off"
vif = [ 'ip=10.0.0.2' ]         # replace with DomU's IP
ip = "10.0.0.2"
gateway= "10.0.0.128"                   # Dom0
netmask = "255.255.255.0"
# example for LVM or partition
disk = [ 'phy:/dev/mapper/xenvg-node02,/dev/hda1,w',
'phy:/dev/mapper/xenvg-node02--swap,hda2,w' ]

# example for image file
#disk = [ 'file:xen/xenvg-node0001.img,hda1,w',
'file:/xen/xenvg-node0001-swap.img,hda2,w' ]

# This uses environment variables XAUTHORITY and DISPLAY.  You
# can override that:
# vfb = [ 'type=sdl,xauthority=/home/bozo/.Xauthority,display=:1' ]
#
# To create one using the VNC backend and sensible defaults:
vfb = [ 'type=vnc' ]
# The backend listens on 127.0.0.1 port 5900+N by default, where N is
# the domain ID.  You can override both address and N:
#
# Or you can bind the first unused port above 5900:
# vfb = [ 'type=vnc,vnclisten=0.0.0.0,vnunused=1' ]
# You can override the password:
# vfb = [ 'type=vnc,vncpasswd=MYPASSWD' ]

# Set the hostname.
#hostname= "node%d" % vmid

# Set root device.
root = "/dev/hda1"

# Sets runlevel 2.
#extra = "2"
extra='console=xvc0 xencons=xvc0'
#sdl=0
#vnc=0
nographics=0
--------------------------------------------------------------

In node02 configuration file, if I specify interface=eth0, I get the
following error message: "Error: name 'eth0' is not defined". Also for
node02 I have tested with a 32bits Debian release and I had the same
problem.



Now here is the log file of a working VM:
--------------------------------------------------------------
Watching /local/domain/0/device-model/56/logdirty/next-active
Watching /local/domain/0/device-model/56/command
shift keysym 003e keycode 86
[...]
shift keysym 003f keycode 53
xs_read(): vncpasswd get error.
/vm/55ba1747-eb73-8321-da9c-44db8f906295-1/vncpasswd.
char device redirected to /dev/pts/1
Console: prepared domain, waiting for ringref at
/local/domain/56/console or /local/domain/56/serial/0
FB: Waiting for KBD backend creation
Doing backend watch on /local/domain/0/backend/vkbd/56/0
FB: Waiting for FB backend creation
Doing backend watch on /local/domain/0/backend/vfb/56/0
Console: got watch
Console: got ring-ref 149301 port 2
Console: connected to guest frontend
FB: Waiting for KBD frontend initialization
Doing frontend watch on /local/domain/56/device/vkbd/0
FB: Carry on waiting
--------------------------------------------------------------


And the log file of a VM that doesn't start and uses 100% cpu in xentop:
--------------------------------------------------------------
Watching /local/domain/0/device-model/57/logdirty/next-active
Watching /local/domain/0/device-model/57/command
shift keysym 003e keycode 86
[...]
shift keysym 003f keycode 53
xs_read(): vncpasswd get error.
/vm/a318301b-7221-8082-f302-4f2e4bec156b/vncpasswd.
bind() failed
--------------------------------------------------------------


And here is the ifconfig output on Dom0: (I have removed some data
that didn't seem relevant)
--------------------------------------------------------------
# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1B:FC:19:19:36
          inet addr:91.121.77.156  Bcast:91.121.77.255  Mask:255.255.255.0

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0

peth0     Link encap:Ethernet  HWaddr 00:1B:FC:19:19:36
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

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?

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