Re: Unable to xm console into a virtualized server with Xen and Etch
- From: Thomas <iamkenzo@xxxxxxxxx>
- Date: Mon, 1 Sep 2008 21:09:56 +0200
Hi Steve,
Now I have removed any extra='...' line in my domU config file.
I have tried the following inittab lines:
---
1:2345:respawn:/sbin/getty 38400 console
---
1:2345:respawn:/sbin/getty 38400 tty1
---
1:2345:respawn:/sbin/getty 38400 xvc0
---
The first two give me the same result: I can only "xm console" into
the domU when it is booting or shutting down.
With xvc0 in the inittab, the console never shows up and I get the
following error message after a few minutes:
---
INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel
---
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- Follow-Ups:
- Re: Unable to xm console into a virtualized server with Xen and Etch
- From: Steve Kemp
- Re: Unable to xm console into a virtualized server with Xen and Etch
- References:
- Prev by Date: Re: ssh and X display forwarding
- Next by Date: Re: Unable to xm console into a virtualized server with Xen and Etch
- Previous by thread: Re: Unable to xm console into a virtualized server with Xen and Etch
- Next by thread: Re: Unable to xm console into a virtualized server with Xen and Etch
- Index(es):
Relevant Pages
|
