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>]

I just saw that I made two threads instead of one ... hopefully this 
email now receives in the correct one. ;)
---
Hi Keir, Hi Konrad,

thanks for your time.
at first, Keir: I've added the lines to xen boot, attached a new xm 
dmesg. until the line "(XEN) HVM1: HVM Loader" all logs were generated 
from boot, the logs afterwards from starting/killing the domU-machine. 
also attached a dmesg from dom0. My config is still xen-4.1-amd64 with 
dom0 debian squeeze kernel i686.
my hvm domain config is also attached here.
I am sure that to this domU I've configured 512MB ram, my dom0 is 
limited to 1024MB ram, so there should be no bottleneck (host with 
2048MB ram, if I do not limit dom0 memory with xen I can allocate there 
about 1800MB). nevertheless the issue also occurs with a 256MB ram domU.
Konrad, I do not know if this is happening also to other machines, first 
time for me with xen, have never tried or seen on other hardware - or do 
you mean other domUs on my host? if last then yes, this happens if I use 
HVM, as soon as I try paravirt it works flawless. I have tried about 10 
or 15 different configurations of HVM domUs, always the same problem.
I ran your code, the output is attached. also xen ran this time with 
loglvl=all.
If I was running only dom0 the first 4 lines in the output of your code 
always repeated, the two big output blocks with 8 lines were generated 
in the about 15 to 20 seconds stucking, afterwards the 4 lines like on 
beginning repeated again.
hopefully this helps, just contact me if you need more information.

Alois
---


On 04/14/2011 03:23 PM, Konrad Rzeszutek Wilk wrote:
> On Wed, Apr 13, 2011 at 11:04:04PM +0100, Keir Fraser wrote:
>    
> > On 13/04/2011 22:38, "MadLoisae@xxxxxxx"<MadLoisae@xxxxxxx>  wrote:
> >
> >      
> > > Hello Keir,
> > >
> > > thanks for your idea.
> > > Have installed xen 4.1 amd64 packages, boots correctly but sadly the
> > > same issue.
> > > I've attached xm dmesg and dmesg from dom0 (and also attached this time
> > > missing logs from my last mail)
> > >
> > > Thanks in advance for further hints.
> > >        
> > The logs don't show much, except that dom0 seems to be losing interrupts
> > after the HVM guest starts. Do you get more from 'xm dmesg' if you boot Xen
> > with the extra boot parameters "loglvl=all guest_loglvl=all"? What is your
> > HVM domain config?
> >      
> Keir, didn't we have a problem with hvmloader where it would call 
> populate_physmap
> and take a very long time when moving the PFNs around? I can't remember the 
> details though :-(
>
>

Attachment: config.sxp
Description: Text document

Attachment: dmesg_dom0_amd64xen41_loglvl=all
Description: Text document

Attachment: read_interrupts_output
Description: Text document

Attachment: xm_dmesg_4.1_amd64_loglvl=all
Description: Text document

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