Re: [ANNOUNCE] kvm userspace release 6

[Michael Riepe <michael-0QoEqw4nQxo@public.gmane.org>]

Hi!

Dor Laor wrote:
>>Hi!
>>
>>I immediately tried the latest version (SVN release 4064) on my
> 
> Thinkpad
> 
>>(Core Duo T2400, Linux 2.6.19) but I still have the same problems I
> 
> had
> 
>>with release 5.
>>
>>Suse 10.1 (the German version) dies with:
>>
>>
>>>exception 13 (0)
>>>Aborted
>>
>>no matter if I boot from DVD or disk.
> 
> 
> Probably some real-mode emulation problem. I'm not absolutely sure, will
> take a look tomorrow when I'll see the code.

I suspect that it's caused by a segmentation limit violation.

> There are real-modes instructions that we might fail to emulate
> correctly. A temporal workaround is to try switch to textual boot mode,
> it might help till we fix it.
> Please tell if it worked for you.

I'm not sure what you mean. The -nographic option doesn't help, and Suse
doesn't even come far enough to switch to graphics mode. It dies in the
bootloader.

>>OpenSolaris XXL gets hit even worse:
>>
>>
>>>unhandled vm exit:  0x80000021
>>>rax 0000000060000010 rbx 0000000000002000 rcx 000000000102808c rdx
>>
>>0000000000101e50
>>
>>>rsi 0000000000004f15 rdi 0000000000000000 rsp 0000000000004ffc rbp
>>
>>0000000001028064
>>
>>>r8  00000000010113c8 r9  00000000000007ff r10 00000000e0000011 r11
>>
>>b7f04674b7f03ff4
>>
>>>r12 bfa68a80b7f044c8 r13 b7f04674b7efae3c r14 00000001b79a03f0 r15
>>
>>0000000000000001
>>
>>>rip 00000000000021ab rflags 00223002
>>>Aborted
>>
>>This one obviously points to an error on VM entry, according to the
>>Intel docs. Maybe the Solaris bootloader is messing with registers it
>>shouldn't touch?
> 
> 
> Right about this caused by problem in VM entry.
> 99% chance Solaris is not the blame (1% they are using the
> BIG-real-mode).
> Might be also a graphical boot loader problem, there is a debug.c file
> that I need to revive that tells what bothered Intel.
> In general, Intel tests to deeply before vmentery.

This also happens while loading the kernel, in text mode.

Did I mention that kvm dies a horrible death ("Aiee, killing interrupt
handler!") when I configure the kernel with CONFIG_PREEMPT=y? Currently
I use CONFIG_PREEMPT_NONE.

-- 
Michael "Tired" Riepe <michael-0QoEqw4nQxo@public.gmane.org>
X-Tired: Each morning I get up I die a little

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV