On Sun, Oct 30, 2011 at 7:41 AM, Avi Kivity <[email protected]> wrote: > On 10/20/2011 05:30 AM, Jorge Lucangeli Obes wrote: >> https://docs.google.com/leaf?id=0B78o7gMWkuFeNmJlYzNiNWYtMGQ4MS00NzhiLWIyNTMtY2NlNWEzNzQ5NGYx&hl=en_US >> >> > > The logs show lots of accesses to the vga region at 0xa0000 instead of > the linear framebuffer. Please diff the Xorg logs in the guest for the > working and non-working cases (and post them, too).
I've uploaded the logs here: https://docs.google.com/open?id=0B78o7gMWkuFeY2FkNjllNjgtNDQyZC00NDU5LWFjODctNzMzNzU3NjNjODkz 'Xorg.0.log.outside' is the result of running KVM outside the chroot, which is fast as normal. 'Xorg.0.log.inside' is the result of running KVM inside the chroot, which is slow. 'diff' is the diff obtained by first removing the timestamps from the log files. I think you're right re: linear framebuffer Avi. The last part of the diff shows (< fast > slow) 1377c2113 < (II) VESA(0): VESA VBE Total Mem: 8192 kB --- > (II) VESA(0): VESA VBE Total Mem: 16384 kB 1383,1385c2119,2123 < (II) VESA(0): virtual address = 0x75f11000, < physical address = 0xe0000000, size = 8388608 < (II) VESA(0): Setting up VESA Mode 0x145 (1280x1024) --- > (II) VESA(0): virtual address = (nil), <========== HERE > physical address = 0xe0000000, size = 16777216 > (II) VESA(0): virtual address = 0x76e6a000, > physical address = 0xa0000, size = 65536 > (II) VESA(0): Setting up VESA Mode 0x186 (1680x1050) 1409c2147 FWIW: (outside-OK) $ qemu-system-x86_64 -version QEMU emulator version 0.15.0 (qemu-kvm-0.15.0) (inside-slow) $ qemu-system-x86_64 -version QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5) However, running outside the chroot was also OK with 0.12.3. What could be causing this? Thanks, Jorge -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
