On Thursday 07 February 2008 15:19:39 H. Peter Anvin wrote:
> Rob Landley wrote:
> > Specifically, qemu isn't paravirtualized, it's fully virtualized. The
> > same kernel can run on real hardware just fine. (Sort of the point of
> > the project...)
> >
> > I can yank the warning for the kernels
Rob Landley wrote:
Specifically, qemu isn't paravirtualized, it's fully virtualized. The same
kernel can run on real hardware just fine. (Sort of the point of the
project...)
I can yank the warning for the kernels I build (or set PASS_LIMIT to 999),
but I'd rather not carry any more
Rob Landley wrote:
Specifically, qemu isn't paravirtualized, it's fully virtualized. The same
kernel can run on real hardware just fine. (Sort of the point of the
project...)
I can yank the warning for the kernels I build (or set PASS_LIMIT to 999),
but I'd rather not carry any more
On Thursday 07 February 2008 11:37:12 H. Peter Anvin wrote:
> > actually, the way i solved it for qemu+KVM+paravirt was to just turn off
> > this rather silly check in the serial driver if inside a paravirt guest.
> > When we are emulated then the serial 'hardware' is totally reliable and
> > we
Ingo Molnar wrote:
* H. Peter Anvin <[EMAIL PROTECTED]> wrote:
(If it's a qemu issue, I can go bother them. It's possible that qemu
isn't delivering interrupts as often as it expects, since that's
limited by the granularity of the host timer; I know the clock in
qemu can run a bit slow
* H. Peter Anvin <[EMAIL PROTECTED]> wrote:
>> (If it's a qemu issue, I can go bother them. It's possible that qemu
>> isn't delivering interrupts as often as it expects, since that's
>> limited by the granularity of the host timer; I know the clock in
>> qemu can run a bit slow because it
* H. Peter Anvin [EMAIL PROTECTED] wrote:
(If it's a qemu issue, I can go bother them. It's possible that qemu
isn't delivering interrupts as often as it expects, since that's
limited by the granularity of the host timer; I know the clock in
qemu can run a bit slow because it only gets
On Thursday 07 February 2008 11:37:12 H. Peter Anvin wrote:
actually, the way i solved it for qemu+KVM+paravirt was to just turn off
this rather silly check in the serial driver if inside a paravirt guest.
When we are emulated then the serial 'hardware' is totally reliable and
we should
Rob Landley wrote:
Specifically, qemu isn't paravirtualized, it's fully virtualized. The same
kernel can run on real hardware just fine. (Sort of the point of the
project...)
I can yank the warning for the kernels I build (or set PASS_LIMIT to 999),
but I'd rather not carry any more
Rob Landley wrote:
Specifically, qemu isn't paravirtualized, it's fully virtualized. The same
kernel can run on real hardware just fine. (Sort of the point of the
project...)
I can yank the warning for the kernels I build (or set PASS_LIMIT to 999),
but I'd rather not carry any more
Ingo Molnar wrote:
* H. Peter Anvin [EMAIL PROTECTED] wrote:
(If it's a qemu issue, I can go bother them. It's possible that qemu
isn't delivering interrupts as often as it expects, since that's
limited by the granularity of the host timer; I know the clock in
qemu can run a bit slow
On Thursday 07 February 2008 15:19:39 H. Peter Anvin wrote:
Rob Landley wrote:
Specifically, qemu isn't paravirtualized, it's fully virtualized. The
same kernel can run on real hardware just fine. (Sort of the point of
the project...)
I can yank the warning for the kernels I build (or
Rob Landley wrote:
When running a 2.6.24 kernel built for x86-64 under qemu via serial console,
doing CPU-intensive things that also produce a lot of output (such as
compiling software) tends to produce the error message in the title.
Anybody have a clue why? It doesn't seem to cause an
When running a 2.6.24 kernel built for x86-64 under qemu via serial console,
doing CPU-intensive things that also produce a lot of output (such as
compiling software) tends to produce the error message in the title.
Anybody have a clue why? It doesn't seem to cause an actual problem, but it's
Rob Landley wrote:
When running a 2.6.24 kernel built for x86-64 under qemu via serial console,
doing CPU-intensive things that also produce a lot of output (such as
compiling software) tends to produce the error message in the title.
Anybody have a clue why? It doesn't seem to cause an
When running a 2.6.24 kernel built for x86-64 under qemu via serial console,
doing CPU-intensive things that also produce a lot of output (such as
compiling software) tends to produce the error message in the title.
Anybody have a clue why? It doesn't seem to cause an actual problem, but it's
16 matches
Mail list logo
