On 11/6/07, Carsten Emde <[EMAIL PROTECTED]> wrote:
> Dor,
>
> I tried to recreate your problem using 2.6.23-1 and latest rt patch
> (rt5).
> The problem is that the kernel is not stable at all, I can't even
> compile the code over vnc -
> my connection is constantly lost.
Dor,
I tried to recreate your problem using 2.6.23-1 and latest rt patch
(rt5).
The problem is that the kernel is not stable at all, I can't even
compile the code over vnc -
my connection is constantly lost. So it might not be kvm problem?
Can you try is with -no-kvm
David Brown wrote:
I tried to recreate your problem using 2.6.23-1 and latest rt patch (rt5).
The problem is that the kernel is not stable at all, I can't even
compile the code over vnc -
my connection is constantly lost. So it might not be kvm problem?
Can you try is with -no-kvm and see if it's
> > I tried to recreate your problem using 2.6.23-1 and latest rt patch (rt5).
> > The problem is that the kernel is not stable at all, I can't even
> > compile the code over vnc -
> > my connection is constantly lost. So it might not be kvm problem?
> > Can you try is with -no-kvm and see if it's
Dor,
>> [..]
>> It got to the point of bringing up the tap interface and attaching it
>> to the bridge but that was about it for the console messages.
> I tried to recreate your problem using 2.6.23-1 and latest rt patch (rt5).
> The problem is that the kernel is not stable at all, I can't even
>
David Brown wrote:
> Uhm, not sure who to send this too...
>
> I thought I'd try out the realtime patch set and it didn't work at all
> with kvm. The console didn't dump anything and the system completely
> locked up.
>
> Anyone have any suggestions as to how to get more output on this issue?
>
> I
Jan Kiszka wrote:
> Avi Kivity wrote:
>
>> Jan Kiszka wrote:
>>
>>> Interesting result - you've read about the wbinvd issues? Is there no
>>> wbinvd in the bios shipped with older kvm? Which VM extension did you
>>> test, both Intel and AMD? I would bet that your X issues are due to the
>>>
Avi Kivity wrote:
> Jan Kiszka wrote:
>> Interesting result - you've read about the wbinvd issues? Is there no
>> wbinvd in the bios shipped with older kvm? Which VM extension did you
>> test, both Intel and AMD? I would bet that your X issues are due to the
>> same effect. X startup/shutdown invol
Jan Kiszka wrote:
> Interesting result - you've read about the wbinvd issues? Is there no
> wbinvd in the bios shipped with older kvm? Which VM extension did you
> test, both Intel and AMD? I would bet that your X issues are due to the
> same effect. X startup/shutdown involves a lot of wbinvd call
On Oct 30, 2007, at 10:49 AM, Jan Kiszka wrote:
> Carsten Emde wrote:
>> Avi Kivity wrote:
>>> David Brown wrote:
I thought I'd try out the realtime patch set and it didn't work
at all
with kvm. The console didn't dump anything and the system
completely
locked up.
>>
Carsten Emde wrote:
> Avi Kivity wrote:
>> David Brown wrote:
>>> I thought I'd try out the realtime patch set and it didn't work at all
>>> with kvm. The console didn't dump anything and the system completely
>>> locked up.
> Up to now, the unmodified kvm module never worked with any RT kernel.
>
Avi Kivity wrote:
> David Brown wrote:
>> I thought I'd try out the realtime patch set and it didn't work at all
>> with kvm. The console didn't dump anything and the system completely
>> locked up.
Up to now, the unmodified kvm module never worked with any RT kernel.
This would only change, if RT
David Brown wrote:
> Uhm, not sure who to send this too...
>
> I thought I'd try out the realtime patch set and it didn't work at all
> with kvm. The console didn't dump anything and the system completely
> locked up.
>
> Anyone have any suggestions as to how to get more output on this issue?
>
13 matches
Mail list logo
