(2010/10/15 15:41), Takuya Yoshikawa wrote:
(2010/10/14 21:38), Avi Kivity wrote:
On 10/14/2010 02:36 PM, Jan Kiszka wrote:
and this commit just makes the
corruptions more likely. This may even be a QEMU issue in the cirrus/vga
model (both qemu-kvm and upstream show the effect).
What
Am 18.10.2010 14:14, Takuya Yoshikawa wrote:
(2010/10/15 15:41), Takuya Yoshikawa wrote:
(2010/10/14 21:38), Avi Kivity wrote:
On 10/14/2010 02:36 PM, Jan Kiszka wrote:
and this commit just makes the
corruptions more likely. This may even be a QEMU issue in the cirrus/vga
model (both
(2010/10/14 21:38), Avi Kivity wrote:
On 10/14/2010 02:36 PM, Jan Kiszka wrote:
and this commit just makes the
corruptions more likely. This may even be a QEMU issue in the cirrus/vga
model (both qemu-kvm and upstream show the effect).
What about -no-kvm?
Just booted it (took ages), and
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm currently running -rc7). Effects disappears when
downgrading to kvm-kmod-2.6.35.6. Will see if I can bisect later, but
maybe someone
On 10/14/2010 09:27 AM, Jan Kiszka wrote:
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm currently running -rc7). Effects disappears when
downgrading to kvm-kmod-2.6.35.6. Will
Am 14.10.2010 09:27, Jan Kiszka wrote:
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm currently running -rc7). Effects disappears when
downgrading to kvm-kmod-2.6.35.6. Will
On 10/14/2010 02:04 PM, Avi Kivity wrote:
On 10/14/2010 09:27 AM, Jan Kiszka wrote:
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm currently running -rc7). Effects disappears
Am 14.10.2010 14:11, Avi Kivity wrote:
On 10/14/2010 02:04 PM, Avi Kivity wrote:
On 10/14/2010 09:27 AM, Jan Kiszka wrote:
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm
On 10/14/2010 02:10 PM, Jan Kiszka wrote:
Am 14.10.2010 09:27, Jan Kiszka wrote:
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm currently running -rc7). Effects
On 10/14/2010 02:13 PM, Avi Kivity wrote:
and this commit just makes the
corruptions more likely. This may even be a QEMU issue in the cirrus/vga
model (both qemu-kvm and upstream show the effect).
What about -no-kvm?
Doesn't happen there.
My guess is the initial dirty log after the
Am 14.10.2010 14:13, Avi Kivity wrote:
On 10/14/2010 02:10 PM, Jan Kiszka wrote:
Am 14.10.2010 09:27, Jan Kiszka wrote:
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm
On 10/14/2010 02:36 PM, Jan Kiszka wrote:
and this commit just makes the
corruptions more likely. This may even be a QEMU issue in the cirrus/vga
model (both qemu-kvm and upstream show the effect).
What about -no-kvm?
Just booted it (took ages), and the result was actually a
12 matches
Mail list logo
