linux-kernel - Re: Cannot boot xen DomU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <479394D9.50104@goop.org>
Date:	Sun, 20 Jan 2008 10:37:13 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	xming <xmingske@...il.com>
CC:	linux-kernel@...r.kernel.org,
	Xen-devel <xen-devel@...ts.xensource.com>
Subject: Re: Cannot boot xen DomU > 2.6.23.1

xming wrote:
> ok I have done some of them, but I still don't know what I should be looking
> at. Do you mean code related to xen or code related to have_vcpu_info_placement?
> Please be patient with me :)
>
> I just paste some of the result (around those addresses) here:
>   

Thanks, that answers that particular question; the vcpu is blocked 
waiting for something to happen, which probably means it missed the 
event which was supposed to wake it up.  Why is another question.  At 
least there's a workaround, and that workaround gives me some clue where 
to look.

BTW, is it an SMP or UP domain?   Does it make a difference?

>> OK, good.  I Didn't Break It (tm) ;)
>>     
>
> So no fix from you? :)
>   

Maybe when I have nothing else to do.

    J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/