[Fedora-xen] RHEL4 DomU Update Problem

[Jim Klein]

You are correct! Sorry, forgot that RHEL5 Xen sent output in a different direction. All is well now - thanks a million! You just saved me countless hours migrating domains! 


----- Original Message ----- 
From: "Chris Lalancette" <clalance at redhat.com> 
To: "Jim Klein" <jklein at saugus.k12.ca.us> 
Cc: "Fedora Xen" <fedora-xen at redhat.com> 
Sent: Friday, November 2, 2007 9:40:16 AM (GMT-0800) America/Los_Angeles 
Subject: Re: [Fedora-xen] RHEL4 DomU Update Problem 

Jim Klein wrote: 
> Closer. It doesn't panic any more and even sees all the partitions and 
> mounts, but stalls at the following point: 
> 
> SCSI subsystem initialized 
> Registering block device major 202 
> Using cfq io scheduler 
> xvda: xvda1 xvda2 xvda3 xvda4 < xvda5 > 
> device-mapper: 4.5.5-ioctl (2006-12-01) initialised: dm-devel at redhat.com 
> kjournald starting. Commit interval 5 seconds 
> EXT3-fs: mounted filesystem with ordered data mode. 
> SELinux: Disabled at runtime. 
> 
> Processor spins all the way up to 97 percent and sits there. An xm 
> shutdown works (md: stopping all md devices. md: md0 switched to 
> read-only mode. Power down.) so it seems to be stuck in a loop. 

OK. That probably means you are all the way booted, and just not seeing 
the init output. You can try one of two things here: 

1) Add "console=xvc0" to the kernel command-line when booting the 
RHEL-4 kernel; that should force the init output to go to the serial 
console. 

2) Use virt-manager to view the console. 

At least there you should be able to see what is going on. 

Chris Lalancette 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-xen/attachments/20071102/347f63a0/attachment.htm>