s:
libvirtd[26475]: This thread seems to be the async job owner; entering monitor
without asking for a nested job is dangerous
Which I haven't confirmed as being related, but doesn't seem to be
obviously unrelated either, and at worst is a separate bug.
Cheers,
Ron
--
libvir-list
When experimenting with libvirt and UML I found it necessary to add
support for additional kernel command line arguments.
Ron
diff -up libvirt-0.6.5/src/uml_conf.c.uml-cmdline libvirt-0.6.5/src/uml_conf.c
--- libvirt-0.6.5/src/uml_conf.c.uml-cmdline2009-07-10 16:28:51.0
+0100
-return 0;
>+return ret;
>
> }
info should be initialised to NULL, otherwise the VIR_FREE will fail.
With the umlMonitorCommand if'ed out this is also broken before the
patch, which is how I came to notice it.
Ron
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
"Daniel P. Berrange" <[EMAIL PROTECTED]> wrote:
>That's a symptom of a bug earlier on. Try this patch:
Thanks, Daniel, that seems to have fixed it.
Ron
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
At the top of umlInotifyEvent in uml_driver.c there is this test:
if (watch != driver->inotifyWatch)
return;
This doesn't seem to be correct. I have to comment out the test to get
libvirtd to work with UML.
Ron
--
Libvir-list mailing list
Libvir-list@redhat.c
