Re: kvm kernel backtrace 2.6.27.3 using kvm 78 userspace

[Avi Kivity <avi@redhat.com>]

Kasper Sandberg wrote:
>> What guest are you running?
>>     
>
> Yeah sorry, i was gonna include that in the mail, i apparently forgot. 
>
> I have been running debian, both 32 and 64bit inside it, .18, .24
> and .26 kernels, and ubuntu 8.10 .27 kernels, ATLEAST 32bit, i do not
> remember if i have run 64bit ubuntu 8.10
>
> I can however give some information that _MIGHT_ (i have no clue myself)
> be relevant
>
> on one of the debian guests i had xrandr crash the X server while trying
> to change resolution, i did this a few times. Using -vga std.
>
> also, on the ubuntu 32bit guest, i ran qemu with debian stable, where X
> crashed during start inside the qemu on the ubuntu guest. This happened
> only once.
>
> im quite certain my ram and that is fine, no errors when doing memory
> testing etc.
>
>
> but as said, the kernel is tainted, i dont know if that affects the
> results or not, i just wanted to inform in case this can help someone.
> That being said, the box has NOT been rebooted since, and i can confirm
> that kvm works excellently, i have spawned several VMs and used a tad,
> since i wrote the mail

Well, if you can find a recipe that reliably reproduces the problems, we 
want to hear of it.

-- 
error compiling committee.c: too many arguments to function