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: Mon, 16 Jun 2008 20:37:20 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 16 Jun 2008 11:37:50 -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=WeyAHdaaRvdydmsvVPqT9I3HeVBsT30zPrAnhSDar5c=; b=NR4uQ74VdrKQgdrMpv567wzxJ9EgThhBrHWRWRyAMJCwaBYmuLdMOd21KAekH3kKZ5 ojrUuUfANc3l/0MK+HLzbBd2HRwuT9LuE30OtlRCL4ZHcT+sLG/Mh+FmquHHxCkkA4qq wtHxa0eFOtLIIZngHzdH2828FW7ynKxtEOLdA=
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=Qi3POOblWprA3g8zRkTK/TJG8OdZgHf8jRqhwuvOeQlX6viu5NGKt5pHgLYZXab5ZD DYJb34EtPmk9ZNfKmcrRRm95jB1YiV8hUfZXvTlzpZ/+34gd0sAxvakl7UkPT0Y9IuCS NJRCcb4xpRxDD8F3o8qDEc/MrbOm/DOVwz6sY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200806101955.00343.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: <200806081626.26179.jim_burn@xxxxxxxxxxxxx> <55da14450806100415r3a0edd16m470a1c0b62bc2258@xxxxxxxxxxxxxx> <55da14450806100440u5d05c9f3n1e7f2d9537354758@xxxxxxxxxxxxxx> <200806101955.00343.jim_burn@xxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> Hi Again Thomas. This sounds like a symptom of the getty dying on xvc0. Are
> you getting messages of the form "co:init getty restarting too fast. delaying
> for 5 min." or something to that effect? The syslog is one
> of /var/log/{syslog,messages}.
Hi Jim,

I am back, and I have good news, I left my console opened after it was
created, and look what I have found after 5 minutes:
-------
INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel
-------

Here is the configuration file for my DomU:
------
#  -*- mode: python; -*-
kernel = "/boot/vmlinuz-2.6.18-4-xen-amd64"
ramdisk = "/boot/initrd.img-2.6.18-4-xen-amd64"
memory = "256"
maxmem = "512"
name = "VM1"
vcpus=1
vif = [ 'mac=00:16:3e:00:00:01, ip=10.0.0.1' ]
# example for LVM or partition
disk = [ 'phy:/dev/mapper/xenvg-VM1,/dev/hda1,w',
'phy:/dev/mapper/xenvg-VM1--swap,hda2,w' ]
root = "/dev/hda1"
extra='console=xvc0 xencons=xvc0'
nographics=0
-------

In the /etc/securetty of the DomU I have the following lines:
-----
console
# for xen:
xvc0
-----


And in the /etc/inittab of my DomU:
-----
1:2345:respawn:/sbin/getty 38400 xvc0
-----

I was previously set to 0:2345:respawn...., and give the same error message.

We are getting closer to the key!

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