Re: Running KVM inside a chroot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Oct 18, 2011 at 10:46 AM, Avi Kivity <avi@xxxxxxxxxx> wrote:
> On 10/18/2011 07:39 PM, Jorge Lucangeli Obes wrote:
>> On Tue, Oct 18, 2011 at 10:28 AM, Avi Kivity <avi@xxxxxxxxxx> wrote:
>> > On 10/18/2011 06:43 PM, Jorge Lucangeli Obes wrote:
>> >> https://docs.google.com/leaf?id=0B78o7gMWkuFeYzUzODViMjUtNzliNy00ODc5LWIwY2YtOGYyMTI3MzMxNjI5&hl=en_US
>> >
>> > Dumping a lot of junk to the display.  What's the guest doing?
>>
>> This trace is taken while Chromium OS presents the login screen. The
>> mouse pointer is almost completely unresponsive (i.e. it's impossible
>> to click on the text areas for username and password).
>>
>> The really weird thing is that the same screen is completely fine
>> outside of the chroot
>
> Perhaps you miss the vga bios?  Or maybe you have different versions?
>
> Please check /usr/local/share/qemu or the equivalent for your system.

This is inside the chroot:

$ ls /usr/share/qemu/
bamboo.dtb   keymaps        openbios-ppc      petalogix-s3adsp1800.dtb
 pxe-i82559er.bin  pxe-rtl8139.bin  vgabios.bin
bios.bin     linuxboot.bin  openbios-sparc32  ppc_rom.bin
 pxe-ne2k_pci.bin  pxe-virtio.bin   vgabios-cirrus.bin
extboot.bin  multiboot.bin  openbios-sparc64  pxe-e1000.bin
 pxe-pcnet.bin     vapic.bin        video.x

The VGA bios seems to be there.

>>
>> >> However, running trace-cmd gives:
>> >>
>> >> $ trace-cmd report trace_report
>> >>   error reading header for trace_report
>> >> jorgelo@tegan:~/local$ trace-cmd report trace.dat > trace_report2
>> >>   cound not load plugin '/usr/local/share/trace-cmd/plugins/plugin_kvm.so'
>> >> /usr/local/share/trace-cmd/plugins/plugin_kvm.so: undefined symbol:
>> >> ud_translate_att
>> >>
>> >
>> > Looks like udis86 isn't loaded correctly, is it installed in /usr/lib[64]?
>>
>> $ ls /usr/local/lib/libudis*
>> /usr/local/lib/libudis86.a  /usr/local/lib/libudis86.la
>>
>> Does "/usr/local/lib" vs "/usr/lib" make a difference?
>
> Shoudn't.  I have a .so instead of .a, maybe trace-cmd's Makefile isn't
> prepared for static libraries?

'configure' doesn't seem to enable building shared libs by default. I
had to pass '--enable-shared'. Once the shared libs were installed, I
ran 'ldconfig' and the problem was solved. I've uploaded a new version
of the trace report, now generated without any errors. I see lots of:

kvm_exit:             reason EPT_VIOLATION

But maybe that's expected.

https://docs.google.com/leaf?id=0B78o7gMWkuFeNmJlYzNiNWYtMGQ4MS00NzhiLWIyNTMtY2NlNWEzNzQ5NGYx&hl=en_US

I'll get a trace of the VM outside the chroot to see if there are
noticeable differences.

Could ksmd have anything to do with this? The daemon is running on my host.

Thanks,
Jorge
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux