Hi *,
as this is my first post I want to say hello to everybody.
Well, and unfortunatly I''ve already got a question for you:
I''ve installed a guest domain (OS: CentOS 4) on my xen-machine and
it''s para-virtualised (just to provide the information ;) ).
After the installation and mount the image containing the guest to copy
the necessary modules for the xen-kernel, umount it and boot the
guest domain with
the xen-kernel. Everything seems fine except that udev seems to not
create any
console/tty or similar. Heres a snipped of the boot log:
==
Welcome to CentOS release 4.5 (Final)
Press ''I'' to enter interactive startup.
Starting udev: [ OK ]
Initializing hardware... storage network audio done[ OK ]
Configuring kernel parameters: [ OK ]
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access
method.
Setting clock (localtime): Mon Jun 18 12:04:30 CEST 2007 [ OK ]
Loading default keymap (us): [FAILED]
Checking root filesystem
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1
/: clean, 34637/512000 files, 241019/1022127 blocks
[ OK ]
Remounting root filesystem in read-write mode: [ OK ]
no block devices found
Setting up Logical Volume Management: [ OK ]
Checking filesystems
Checking all file systems.
[ OK ]
Mounting local filesystems: [ OK ]
Enabling local filesystem quotas: [ OK ]
Enabling swap space: [ OK ]
INIT: Entering runlevel: 3
Entering non-interactive startup
No volume groups found
Checking for new hardware [ OK ]
Starting pcmcia: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Starting system logger: [ OK ]
Starting kernel logger: [ OK ]
Starting portmap: [ OK ]
Starting NFS statd: [ OK ]
Starting RPC idmapd: [ OK ]
Mounting other filesystems: [ OK ]
Starting automount: No Mountpoints Defined[ OK ]
Starting smartd: [FAILED]
Starting cups: [ OK ]
Starting sshd:[ OK ]
Starting xinetd: [ OK ]
Starting sendmail: [ OK ]
Starting sm-client: [ OK ]
Starting console mouse services: no console device found
[FAILED]
Starting crond: [ OK ]
Starting xfs: [ OK ]
Starting anacron: [ OK ]
Starting atd: [ OK ]
Starting system message bus: [ OK ]
Starting HAL daemon: [ OK ]
INIT: Id "co" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel
==
There are some error-messages which compplain about not finding any
consoles.
I would normally try to make some new ttys with mknod but
unfortunatly I can''t
even login to the quest, after the last line the guest seems to hang
(the last two
lines beginning with "INIT" appear after a short time (about 2mins or
something)).
I''ve already searched here at the mailing list without success. I
hope I do not double post
a problem which is already known and solved (in this case maybe would
somebody post me the link
to the solution?)
Thanks i advance for any help.
Best Regards,
Marcel
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
U have to add this line to /etc/inittab of guest to get the console up. "co:2345:respawn:/sbin/mingetty console" to /etc/inittab of guest Thanks, -Trilok On 6/18/07, Marcel Schroers <schroers@physik.uni-wuppertal.de> wrote:> > Hi *, > > as this is my first post I want to say hello to everybody. > > Well, and unfortunatly I''ve already got a question for you: > > I''ve installed a guest domain (OS: CentOS 4) on my xen-machine and > it''s para-virtualised (just to provide the information ;) ). > > After the installation and mount the image containing the guest to copy > the necessary modules for the xen-kernel, umount it and boot the > guest domain with > the xen-kernel. Everything seems fine except that udev seems to not > create any > console/tty or similar. Heres a snipped of the boot log: > ==> > Welcome to CentOS release 4.5 (Final) > Press ''I'' to enter interactive startup. > Starting udev: [ OK ] > Initializing hardware... storage network audio done[ OK ] > Configuring kernel parameters: [ OK ] > Cannot access the Hardware Clock via any known method. > Use the --debug option to see the details of our search for an access > method. > Setting clock (localtime): Mon Jun 18 12:04:30 CEST 2007 [ OK ] > Loading default keymap (us): [FAILED] > Checking root filesystem > [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1 > /: clean, 34637/512000 files, 241019/1022127 blocks > [ OK ] > Remounting root filesystem in read-write mode: [ OK ] > no block devices found > Setting up Logical Volume Management: [ OK ] > Checking filesystems > Checking all file systems. > [ OK ] > Mounting local filesystems: [ OK ] > Enabling local filesystem quotas: [ OK ] > Enabling swap space: [ OK ] > INIT: Entering runlevel: 3 > Entering non-interactive startup > No volume groups found > Checking for new hardware [ OK ] > Starting pcmcia: [ OK ] > Setting network parameters: [ OK ] > Bringing up loopback interface: [ OK ] > Bringing up interface eth0: [ OK ] > Starting system logger: [ OK ] > Starting kernel logger: [ OK ] > Starting portmap: [ OK ] > Starting NFS statd: [ OK ] > Starting RPC idmapd: [ OK ] > Mounting other filesystems: [ OK ] > Starting automount: No Mountpoints Defined[ OK ] > Starting smartd: [FAILED] > Starting cups: [ OK ] > Starting sshd:[ OK ] > Starting xinetd: [ OK ] > Starting sendmail: [ OK ] > Starting sm-client: [ OK ] > Starting console mouse services: no console device found > [FAILED] > Starting crond: [ OK ] > Starting xfs: [ OK ] > Starting anacron: [ OK ] > Starting atd: [ OK ] > Starting system message bus: [ OK ] > Starting HAL daemon: [ OK ] > INIT: Id "co" respawning too fast: disabled for 5 minutes > INIT: no more processes left in this runlevel > ==> > There are some error-messages which compplain about not finding any > consoles. > I would normally try to make some new ttys with mknod but > unfortunatly I can''t > even login to the quest, after the last line the guest seems to hang > (the last two > lines beginning with "INIT" appear after a short time (about 2mins or > something)). > > I''ve already searched here at the mailing list without success. I > hope I do not double post > a problem which is already known and solved (in this case maybe would > somebody post me the link > to the solution?) > > > Thanks i advance for any help. > > > Best Regards, > Marcel > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Trilok, thanks for the quick reply. It worked :) but I had to comment out another line (because the init-routine compplained about a double "co" entry.) For anybody having the same strange behaviour and looking for a solution, heres my /etc/inittab of the guest domain (including the comment out line): ==# # inittab This file describes how the INIT process should set up # the system in a certain run-level. # # Author: Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org> # Modified for RHS Linux by Marc Ewing and Donnie Barnes # # Default runlevel. The runlevels used by RHS are: # 0 - halt (Do NOT set initdefault to this) # 1 - Single user mode # 2 - Multiuser, without NFS (The same as 3, if you do not have networking) # 3 - Full multiuser mode # 4 - unused # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # id:3:initdefault: # System initialization. si::sysinit:/etc/rc.d/rc.sysinit l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 # Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now # When our UPS tells us power has failed, assume we have a few minutes # of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have powerd installed and your # UPS connected and working correctly. pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" # If power was restored before the shutdown kicked in, cancel it. pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled" # Run gettys in standard runlevels # #line added to get a login prompt: #(dont forget to comment out the following line) # co:2345:respawn:/sbin/mingetty console #co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav #1:2345:respawn:/sbin/mingetty tty1 #2:2345:respawn:/sbin/mingetty tty2 #3:2345:respawn:/sbin/mingetty tty3 #4:2345:respawn:/sbin/mingetty tty4 #5:2345:respawn:/sbin/mingetty tty5 #6:2345:respawn:/sbin/mingetty tty6 # Run xdm in runlevel 5 x:5:respawn:/etc/X11/prefdm -nodaemon == Am 18.06.2007 um 12:38 schrieb trilok nuwal:> U have to add this line to /etc/inittab of guest to get the console > up. > "co:2345:respawn:/sbin/mingetty console" to /etc/inittab of guest > > Thanks, > -Trilok > On 6/18/07, Marcel Schroers <schroers@physik.uni-wuppertal.de> > wrote: Hi *, > > as this is my first post I want to say hello to everybody. > > Well, and unfortunatly I''ve already got a question for you: > > I''ve installed a guest domain (OS: CentOS 4) on my xen-machine and > it''s para-virtualised (just to provide the information ;) ). > > After the installation and mount the image containing the guest to > copy > the necessary modules for the xen-kernel, umount it and boot the > guest domain with > the xen-kernel. Everything seems fine except that udev seems to not > create any > console/tty or similar. Heres a snipped of the boot log: > ==> > Welcome to CentOS release 4.5 (Final) > Press ''I'' to enter interactive startup. > Starting udev: [ OK ] > Initializing hardware... storage network audio done[ OK ] > Configuring kernel parameters: [ OK ] > Cannot access the Hardware Clock via any known method. > Use the --debug option to see the details of our search for an access > method. > Setting clock (localtime): Mon Jun 18 12:04:30 CEST 2007 [ OK ] > Loading default keymap (us): [FAILED] > Checking root filesystem > [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1 > /: clean, 34637/512000 files, 241019/1022127 blocks > [ OK ] > Remounting root filesystem in read-write mode: [ OK ] > no block devices found > Setting up Logical Volume Management: [ OK ] > Checking filesystems > Checking all file systems. > [ OK ] > Mounting local filesystems: [ OK ] > Enabling local filesystem quotas: [ OK ] > Enabling swap space: [ OK ] > INIT: Entering runlevel: 3 > Entering non-interactive startup > No volume groups found > Checking for new hardware [ OK ] > Starting pcmcia: [ OK ] > Setting network parameters: [ OK ] > Bringing up loopback interface: [ OK ] > Bringing up interface eth0: [ OK ] > Starting system logger: [ OK ] > Starting kernel logger: [ OK ] > Starting portmap: [ OK ] > Starting NFS statd: [ OK ] > Starting RPC idmapd: [ OK ] > Mounting other filesystems: [ OK ] > Starting automount: No Mountpoints Defined[ OK ] > Starting smartd: [FAILED] > Starting cups: [ OK ] > Starting sshd:[ OK ] > Starting xinetd: [ OK ] > Starting sendmail: [ OK ] > Starting sm-client: [ OK ] > Starting console mouse services: no console device found > [FAILED] > Starting crond: [ OK ] > Starting xfs: [ OK ] > Starting anacron: [ OK ] > Starting atd: [ OK ] > Starting system message bus: [ OK ] > Starting HAL daemon: [ OK ] > INIT: Id "co" respawning too fast: disabled for 5 minutes > INIT: no more processes left in this runlevel > ==> > There are some error-messages which compplain about not finding any > consoles. > I would normally try to make some new ttys with mknod but > unfortunatly I can''t > even login to the quest, after the last line the guest seems to hang > (the last two > lines beginning with "INIT" appear after a short time (about 2mins or > something)). > > I''ve already searched here at the mailing list without success. I > hope I do not double post > a problem which is already known and solved (in this case maybe would > somebody post me the link > to the solution?) > > > Thanks i advance for any help. > > > Best Regards, > Marcel > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Paul, I''m not sure, but maybe you have the same problem I had a cupple of days ago. Here''s the solution which actually worked fine for me. Hope it will help you also... cheers, marcel Anfang der weitergeleiteten E-Mail:> Von: Marcel Schroers <schroers@physik.uni-wuppertal.de> > Datum: 18. Juni 2007 12:58:15 MESZ > An: trilok nuwal <tc.nuwal@gmail.com> > Kopie: xen-users@lists.xensource.com > Betreff: Re: [Xen-users] Guest-domain has no login [SOLVED] > > Hi Trilok, > > thanks for the quick reply. It worked :) > > but I had to comment out another line (because the init-routine > compplained > about a double "co" entry.) For anybody having the same strange > behaviour > and looking for a solution, heres my /etc/inittab of the guest > domain (including > the comment out line): > > ==> # > # inittab This file describes how the INIT process should set up > # the system in a certain run-level. > # > # Author: Miquel van Smoorenburg, > <miquels@drinkel.nl.mugnet.org> > # Modified for RHS Linux by Marc Ewing and Donnie Barnes > # > > # Default runlevel. The runlevels used by RHS are: > # 0 - halt (Do NOT set initdefault to this) > # 1 - Single user mode > # 2 - Multiuser, without NFS (The same as 3, if you do not have > networking) > # 3 - Full multiuser mode > # 4 - unused > # 5 - X11 > # 6 - reboot (Do NOT set initdefault to this) > # > id:3:initdefault: > > # System initialization. > si::sysinit:/etc/rc.d/rc.sysinit > > l0:0:wait:/etc/rc.d/rc 0 > l1:1:wait:/etc/rc.d/rc 1 > l2:2:wait:/etc/rc.d/rc 2 > l3:3:wait:/etc/rc.d/rc 3 > l4:4:wait:/etc/rc.d/rc 4 > l5:5:wait:/etc/rc.d/rc 5 > l6:6:wait:/etc/rc.d/rc 6 > > # Trap CTRL-ALT-DELETE > ca::ctrlaltdel:/sbin/shutdown -t3 -r now > > # When our UPS tells us power has failed, assume we have a few minutes > # of power left. Schedule a shutdown for 2 minutes from now. > # This does, of course, assume you have powerd installed and your > # UPS connected and working correctly. > pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System > Shutting Down" > > # If power was restored before the shutdown kicked in, cancel it. > pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown > Cancelled" > > > # Run gettys in standard runlevels > # > #line added to get a login prompt: > #(dont forget to comment out the following line) > # > co:2345:respawn:/sbin/mingetty console > #co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav > > #1:2345:respawn:/sbin/mingetty tty1 > #2:2345:respawn:/sbin/mingetty tty2 > #3:2345:respawn:/sbin/mingetty tty3 > #4:2345:respawn:/sbin/mingetty tty4 > #5:2345:respawn:/sbin/mingetty tty5 > #6:2345:respawn:/sbin/mingetty tty6 > > # Run xdm in runlevel 5 > x:5:respawn:/etc/X11/prefdm -nodaemon > ==> > Am 18.06.2007 um 12:38 schrieb trilok nuwal: > >> U have to add this line to /etc/inittab of guest to get the >> console up. >> "co:2345:respawn:/sbin/mingetty console" to /etc/inittab of guest >> >> Thanks, >> -Trilok >> On 6/18/07, Marcel Schroers <schroers@physik.uni-wuppertal.de> >> wrote: Hi *, >> >> as this is my first post I want to say hello to everybody. >> >> Well, and unfortunatly I''ve already got a question for you: >> >> I''ve installed a guest domain (OS: CentOS 4) on my xen-machine and >> it''s para-virtualised (just to provide the information ;) ). >> >> After the installation and mount the image containing the guest to >> copy >> the necessary modules for the xen-kernel, umount it and boot the >> guest domain with >> the xen-kernel. Everything seems fine except that udev seems to not >> create any >> console/tty or similar. Heres a snipped of the boot log: >> ==>> >> Welcome to CentOS release 4.5 (Final) >> Press ''I'' to enter interactive startup. >> Starting udev: [ OK ] >> Initializing hardware... storage network audio done[ OK ] >> Configuring kernel parameters: [ OK ] >> Cannot access the Hardware Clock via any known method. >> Use the --debug option to see the details of our search for an access >> method. >> Setting clock (localtime): Mon Jun 18 12:04:30 CEST 2007 [ OK ] >> Loading default keymap (us): [FAILED] >> Checking root filesystem >> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1 >> /: clean, 34637/512000 files, 241019/1022127 blocks >> [ OK ] >> Remounting root filesystem in read-write mode: [ OK ] >> no block devices found >> Setting up Logical Volume Management: [ OK ] >> Checking filesystems >> Checking all file systems. >> [ OK ] >> Mounting local filesystems: [ OK ] >> Enabling local filesystem quotas: [ OK ] >> Enabling swap space: [ OK ] >> INIT: Entering runlevel: 3 >> Entering non-interactive startup >> No volume groups found >> Checking for new hardware [ OK ] >> Starting pcmcia: [ OK ] >> Setting network parameters: [ OK ] >> Bringing up loopback interface: [ OK ] >> Bringing up interface eth0: [ OK ] >> Starting system logger: [ OK ] >> Starting kernel logger: [ OK ] >> Starting portmap: [ OK ] >> Starting NFS statd: [ OK ] >> Starting RPC idmapd: [ OK ] >> Mounting other filesystems: [ OK ] >> Starting automount: No Mountpoints Defined[ OK ] >> Starting smartd: [FAILED] >> Starting cups: [ OK ] >> Starting sshd:[ OK ] >> Starting xinetd: [ OK ] >> Starting sendmail: [ OK ] >> Starting sm-client: [ OK ] >> Starting console mouse services: no console device found >> [FAILED] >> Starting crond: [ OK ] >> Starting xfs: [ OK ] >> Starting anacron: [ OK ] >> Starting atd: [ OK ] >> Starting system message bus: [ OK ] >> Starting HAL daemon: [ OK ] >> INIT: Id "co" respawning too fast: disabled for 5 minutes >> INIT: no more processes left in this runlevel >> ==>> >> There are some error-messages which compplain about not finding any >> consoles. >> I would normally try to make some new ttys with mknod but >> unfortunatly I can''t >> even login to the quest, after the last line the guest seems to hang >> (the last two >> lines beginning with "INIT" appear after a short time (about 2mins or >> something)). >> >> I''ve already searched here at the mailing list without success. I >> hope I do not double post >> a problem which is already known and solved (in this case maybe would >> somebody post me the link >> to the solution?) >> >> >> Thanks i advance for any help. >> >> >> Best Regards, >> Marcel >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Marcel Schroers wrote:> > Hi Paul, > > I''m not sure, but maybe you have the same problem I had a cupple of > days ago. > Here''s the solution which actually worked fine for me. > Hope it will help you also...Hi Marcel, This did help! Ubuntu has no /etc/inittab, so it took me a while to figure it out. Ubuntu uses files in /etc/event.d to spawn ttys. There were entries for tty[2-6], but none for tty[0-1] :-O. I don''t know why... I had to make a copy of /etc/event.d/tty2, name it tty0, and change all occurrences of tty2 to tty0. A reboot later, I had a console. Thanks so much! Paul _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
trilok nuwal wrote:> U have to add this line to /etc/inittab of guest to get the console up. > "co:2345:respawn:/sbin/mingetty console" to /etc/inittab of guestHi, I tried that with no success :-( Tried on both Jailtime Centos 4 and 5 under FC7. These works well under FC6 recompiled Xen guest images (as it would NOT work with FC6 version) Looks like moving domU onto other (or newer) dom0 is far from an easy task. Anyone with a success story to share?> > Thanks, > -Trilok > On 6/18/07, *Marcel Schroers* <schroers@physik.uni-wuppertal.de > <mailto:schroers@physik.uni-wuppertal.de>> wrote: > > Hi *, > > as this is my first post I want to say hello to everybody. > > Well, and unfortunatly I''ve already got a question for you: > > I''ve installed a guest domain (OS: CentOS 4) on my xen-machine and > it''s para-virtualised (just to provide the information ;) ). > > After the installation and mount the image containing the guest to > copy > the necessary modules for the xen-kernel, umount it and boot the > guest domain with > the xen-kernel. Everything seems fine except that udev seems to not > create any > console/tty or similar. Heres a snipped of the boot log: > ==> > Welcome to CentOS release 4.5 (Final) > Press ''I'' to enter interactive startup. > Starting udev: [ OK ] > Initializing hardware... storage network audio done[ OK ] > Configuring kernel parameters: [ OK ] > Cannot access the Hardware Clock via any known method. > Use the --debug option to see the details of our search for an access > method. > Setting clock (localtime): Mon Jun 18 12:04:30 CEST 2007 [ OK ] > Loading default keymap (us): [FAILED] > Checking root filesystem > [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1 > /: clean, 34637/512000 files, 241019/1022127 blocks > [ OK ] > Remounting root filesystem in read-write mode: [ OK ] > no block devices found > Setting up Logical Volume Management: [ OK ] > Checking filesystems > Checking all file systems. > [ OK ] > Mounting local filesystems: [ OK ] > Enabling local filesystem quotas: [ OK ] > Enabling swap space: [ OK ] > INIT: Entering runlevel: 3 > Entering non-interactive startup > No volume groups found > Checking for new hardware [ OK ] > Starting pcmcia: [ OK ] > Setting network parameters: [ OK ] > Bringing up loopback interface: [ OK ] > Bringing up interface eth0: [ OK ] > Starting system logger: [ OK ] > Starting kernel logger: [ OK ] > Starting portmap: [ OK ] > Starting NFS statd: [ OK ] > Starting RPC idmapd: [ OK ] > Mounting other filesystems: [ OK ] > Starting automount: No Mountpoints Defined[ OK ] > Starting smartd: [FAILED] > Starting cups: [ OK ] > Starting sshd:[ OK ] > Starting xinetd: [ OK ] > Starting sendmail: [ OK ] > Starting sm-client: [ OK ] > Starting console mouse services: no console device found > [FAILED] > Starting crond: [ OK ] > Starting xfs: [ OK ] > Starting anacron: [ OK ] > Starting atd: [ OK ] > Starting system message bus: [ OK ] > Starting HAL daemon: [ OK ] > INIT: Id "co" respawning too fast: disabled for 5 minutes > INIT: no more processes left in this runlevel > ==> > There are some error-messages which compplain about not finding any > consoles. > I would normally try to make some new ttys with mknod but > unfortunatly I can''t > even login to the quest, after the last line the guest seems to hang > (the last two > lines beginning with "INIT" appear after a short time (about 2mins or > something)). > > I''ve already searched here at the mailing list without success. I > hope I do not double post > a problem which is already known and solved (in this case maybe would > somebody post me the link > to the solution?) > > > Thanks i advance for any help. > > > Best Regards, > Marcel > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> > http://lists.xensource.com/xen-users > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Frank Morane (Free Thinker) http://www.adventuresinlegalland.com http://www.lysanderspooner.org http://thoreau.eserver.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Seemingly Similar Threads
- xenconsole: Could not read tty from store: No such file or directory
- Opensuse 10.3 does not charge dom0
- what''s wrong with my pv domU console? INIT: Id "1" respawning too fast: disabled for 5 minutes
- How to get remote access to domU console using VNC？
- VM boots BUT keep throwing: "INIT: Id "X" respawning too fast: disabled for 5 minutes"