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

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


  • To: "jim burns" <jim_burn@xxxxxxxxxxxxx>
  • From: Thomas <iamkenzo@xxxxxxxxx>
  • Date: Tue, 17 Jun 2008 12:22:17 +0200
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 17 Jun 2008 03:22:49 -0700
  • 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=F2qSRe88U2GvhhMQYDLUUAyxGHJRqd7Gtr5Qc99DDk8owqp/YjZjGlwE9VgUYs1r0I vXXL/TUfI6IuF+q4ZGVVmoFg3I5yKFD2LW+VJHe5lrGnhpEDwXt2PnofOmvd8RNAOpic Fp8VLEWxMJPhmSPuz67AyrOM6S5j2Oj4pGh1A=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

It still doesn't work. And my kernel is the one from the Debian
package for Xen 2.6.18. I still don't have any /dev/xvc0. I do have a
/dev/xen/evtchn though. Does it help?

Now what's interesting is that when I do "xm create -c VM1", I can
login to my DomU, and if I let it hang there for a while, while I am
logged in, I still get the error message printed on my screen, I found
that out while editing a file in vim, and suddenly after a few minutes
of inactivity:
INIT: Id "co" respawning too fast: disabled for 5 minutes.

However I still have control over the console. We are just so close of
the solution...


So here is my DomU configuration file:
----
#  -*- mode: python; -*-
kernel = "/boot/vmlinuz-2.6.18-4-xen-amd64"
ramdisk = "/boot/initrd.img-2.6.18-4-xen-amd64"
memory = "256"
name = "VM1"
vif = [ 'mac=00:16:3e:00:00:01, ip=10.0.0.1' ]
disk = [ 'phy:/dev/mapper/xenvg-VM1,/dev/hda1,w',
'phy:/dev/mapper/xenvg-VM1--swap,hda2,w' ]
root = "/dev/hda1"
extra = "console=xvc0 xencons=tty"
----

And the inittab of my DomU (I have removed some commented lines for brevity):
----
# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.
id:2:initdefault:

# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS

# What to do in single-user mode.
~~:S:wait:/sbin/sulogin

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin

# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now

# What to do when the power fails/returns.
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop

co:2345:respawn:/sbin/getty xvc0 9600 vt100-nav
1:2345:respawn:/sbin/getty 38400 tty1
----

And here is my /etc/securetty of DomU:
----
# /etc/securetty: list of terminals on which root is allowed to login.
# See securetty(5) and login(1).
console
# for xen:
xvc0
# for people with serial port consoles
ttyS0

# for devfs
tts/0

# Standard consoles
tty1
tty2
[...]
----

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