Re: [Xen-devel] on starting HVM-domU whole system freezes with "soft lockup - CPU X stuck for XXs! [qemu-dm:...]" [xen 4.0, xen 4.1]

["MadLoisae@xxxxxxx" <MadLoisae@xxxxxxx>]

Hi Konrad,

thank you.
I've read in a small howto that touching the virtual disk is enough. So 
it isn't, I've filled it not with 2048MBytes.
I have now attached the virt-install command (i hope this is what you 
expect by ".xm").
Also I discovered now a behaviour: only initializing the vm needs so 
much time and stalls the machine, as soon as I can see i.e. the 
boot-screen from the iso the dom0 is back. The initialisation needs 
nearly 5 minutes (so wairing and hoping this 5 minutes ;) ).
I can see in "Bios"-Bootscreen and also in xm dmesg log IDE timeouts. 
Maybe they point to the reason?
I've attached xm dmesg and dom0 dmesg again after creating and booting 
the machine with the attached command and waiting for the iso-bootprompt.
Alois

On 04/18/2011 11:02 PM, Konrad Rzeszutek Wilk wrote:
> On Sat, Apr 16, 2011 at 12:11:34AM +0200, MadLoisae@xxxxxxx wrote:
>    
> > I just saw that I made two threads instead of one ... hopefully this
> > email now receives in the correct one. ;)
> >      
> The log file is a bit stange. The HVM says:
>
> (XEN) HVM1: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (   0 MBytes)
>
> Is your /home/guest1.dsk really 0 megabytes? Have you
> tried to use a physical device (say LVM logical volume) just to eliminate
> it being the blktap at fault here? (there was a bug in the blktap
> driver that Daniel posted recently here).
>
> Instead of using the configuration with the sxp expression can you just
> post the .xm one please? They are much easier to read.
>
>
>

dmesg_dom0_amd64xen41_loglvl=all_HVM-booted
Description: Text document

xm_dmesg_4.1_amd64_loglvl=all_HVM-booted
Description: Text document

virt-install-command
Description: Text document

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