> Great, that increases the probability that the patch is a net gain.
>
> I don't think you need to run the SLES installer as both Sergey and me
> have it working. Instead, running with your regular workload (possibly
> stressing it) would be a good test.
Okay yeah I don't seem to have problems a
David Brown wrote:
>>
>> I see. Consider it pushed. I'll send it linuswards if there's no
>> negative feedback in a day or two.
>>
>
> Oooo, patch!
>
> What was the method for reproduction? since I was unable to reproduce
> the bug maybe I could with your method.
>
It was the SLES 9 installer/in
It fixes the problem, at least for me...
Thanks,
Sergey
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Avi Kivity
Sent: 18 April 2007 11:22
To: David Brown
Cc: [email protected]
Subject: Re: [kvm-devel] Oopse in kvm
Avi Kivity wrote
>
> I see. Consider it pushed. I'll send it linuswards if there's no
> negative feedback in a day or two.
>
Oooo, patch!
What was the method for reproduction? since I was unable to reproduce
the bug maybe I could with your method.
Don't worry I'll be on this thread until the problem is fixed,
Thomas Glanzmann wrote:
>
>> Ok. You mean you're running linus -rc?
>>
>
> In fact I do. But I didn't meant that upstream. I was talking about your
> repository[1]. But it isn't in the kvm kernel repository yet. So I commited it
> local. And thanks to git if you commit it, it will merge th
Hello Avi,
> hehe, the 4g4g patch.
I see. I thought noone would use that anymore because of the overhead
during context switches.
> It's the same bug.
perfect.
> Ok. You mean you're running linus -rc?
In fact I do. But I didn't meant that upstream. I was talking about your
repository[1]. But
Thomas Glanzmann wrote:
> Hello Avi,
> I had an kernel OOPS that morning with RHEL_5_ it isn't reproducable.
>
> Apr 18 08:57:42 thinkpad kernel: BUG: unable to handle kernel NULL pointer
> dereference at virtual address 0024
> Apr 18 08:57:42 thinkpad kernel: printing eip:
> Apr 18 08:57:42
Hello Avi,
I had an kernel OOPS that morning with RHEL_5_ it isn't reproducable.
Apr 18 08:57:42 thinkpad kernel: BUG: unable to handle kernel NULL pointer
dereference at virtual address 0024
Apr 18 08:57:42 thinkpad kernel: printing eip:
Apr 18 08:57:42 thinkpad kernel: 78351d8c
Apr 18 08:5
Avi Kivity wrote:
David Brown wrote:
I was wondering of anyone could help out on this, just found an oopse
when trying to start rhel4 on i386 box. I was wondering if anyone else
has seen this with kvm-18 and if I should submit a bug for it.
[10937.52] BUG: unable to handle kernel NULL po
> I've seen a few reports like this, but never managed to get one of my own.
>
> Is this reproducible? If so, a recipe would be _very_ valuable.
>
> At what stage in the boot process does it crash?
>
No its not entirely reproducible, I made it happen using the standard
rhel4 kernel and it was tr
David Brown wrote:
> I was wondering of anyone could help out on this, just found an oopse
> when trying to start rhel4 on i386 box. I was wondering if anyone else
> has seen this with kvm-18 and if I should submit a bug for it.
>
> [10937.52] BUG: unable to handle kernel NULL pointer dereferen
Just realized kvm-19 is out I'll go update and try again.
- David Brown
On 4/17/07, David Brown <[EMAIL PROTECTED]> wrote:
> I was wondering of anyone could help out on this, just found an oopse
> when trying to start rhel4 on i386 box. I was wondering if anyone else
> has seen this with kvm-18 a
I was wondering of anyone could help out on this, just found an oopse
when trying to start rhel4 on i386 box. I was wondering if anyone else
has seen this with kvm-18 and if I should submit a bug for it.
[10937.52] BUG: unable to handle kernel NULL pointer dereference
at virtual address 00
13 matches
Mail list logo
