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

On Tuesday June 17 2008 06:22:17 am Thomas wrote:
> t 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?

Not important to your problem.

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

If you look at a listing from '/bin/ps a -HA' (threaded child process 
display), you will see that getty is no longer in control of your login 
console. 'login' is, with a child process for your login shell. So long as 
you don't log out, 'co' can respawn to it's heart's content :-) It's after 
you log out, that the getty can't be reestablished, and so control can't be 
passed back to 'login'. (The fact that you can login at all tells me 
that /dev/xvc0 does exist, at least for the initial login. What happens after 
that is a mystery.)

My guess is since you can't find 'agetty', that 'getty' is a less stable 
substitute. (That, and the instability of xvc0 itself.) I'm going to chalk 
this up to problems with 2.6.18, and you may have to live with it. (That is, 
don't log out after the initial login in 'xm create -c'.)

With 'yum', you can do slick things like say 'yum install /sbin/agetty', and 
it will find the package that contains that program. Don't know if there are 
any 'apt' tools that can do the same.

> # The default runlevel.
> id:2:initdefault:

This is telling Debian to boot into multiuser mode w/o nfs or X11. You might 
want to change that '2' to '5', tho' I'm sure that Debian is doing an 'init 
5' somewhere along the way if you are getting vnc access now. (Just an 
interesting aside.)

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