On Thu, Nov 02, 2006 at 05:15:56PM -0600, Mike Freemon wrote:
Was there any responses on this email from 10/17? I'm seeing the
problem on my system:
I posted a reply to the same problem reported in another thread - I mised
this thread originally. The solution is to install new kudzu in the DomU
from updates-testing. This new kudzu ensures that the agetty process gets
spawned on the xvc0 console as well as the paravirt framebuffer.
# uname -a
Linux grids1 2.6.18-1.2200.fc5xen0 #1 SMP Sat Oct 14 17:49:47 EDT 2006 i686
i686 i386 GNU/Linux
# rpm -qa|grep xen
At 10/17/2006 10:14 AM Tuesday, Stan Larson wrote:
>Sorry if this is a repeat. I haven't found searchable archives for this
>1. I installed FC5 + xen on a base system and performed "yum -y upgrade".
>2. I then created and booted a DomU using the original FC5 disk. So far,
>3. In the DomU, I performed "yum -y upgrade" and rebooted the DomU using
>the new kernel, 2.6.18-1.2200.fc5xenU.
>The DomU boots OK, but returns control or starts a shell. The console
>starts all services and then just hangs. I can ssh into the domain
>from another window and all is well. If I break from the console using
>CRTL-] and then return using xm console, I'm still stuck. If I boot to
>the old kernel (the one provided by the FC5 install disk, aka
>2.6.15-1.2054_FC5xenU) the problem doesn't occur.
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/
|=- Projects: http://freshmeat.net/~danielpb/
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|