Re: Running KVM inside a chroot

[Avi Kivity <avi@redhat.com>]

On 10/18/2011 07:39 PM, Jorge Lucangeli Obes wrote:
> On Tue, Oct 18, 2011 at 10:28 AM, Avi Kivity <avi@redhat.com> 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.

>
> >> 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?

-- 
error compiling committee.c: too many arguments to function