search for: netdev_del

On 04/27/2017 04:31 PM, Stefano Ricci wrote: > Here is the backtrace of the libvirt process just started [Just a side note, you shouldn't top post on technical lists. Gmail sucks at this.] > > https://pastebin.com/R66myzFp Looks like libvirtd is trying to spawn /usr/bin/qemu-system-x86_64 but it takes ages to init. In the debug logs you might see the actual command line that

..., {"name": "qom-list"}, {"name": "qom-get"}, {"name": > "qmp_capabilities"}, {"name": "pmemsave"}, {"name": "object-del"}, > {"name": "object-add"}, {"name": "netdev_del"} ....... > So it would not look like a qemu bug. Well, this does not prove that qemu replies to all commands issued by libvirt. For that we would need debug logs as referred to above. BTW: The stack trace looks a bit old (the line number do not match with the current git HEAD) - what'...

...pes"}, {"name": "qom-list"}, {"name": "qom-get"}, {"name": "qmp_capabilities"}, {"name": "pmemsave"}, {"name": "object-del"}, {"name": "object-add"}, {"name": "netdev_del"} ....... So it would not look like a qemu bug. Stefano

...;name": "qom-list"}, {"name": "qom-get"}, {"name": >> "qmp_capabilities"}, {"name": "pmemsave"}, {"name": "object-del"}, >> {"name": "object-add"}, {"name": "netdev_del"} ....... >> So it would not look like a qemu bug. > > Well, this does not prove that qemu replies to all commands issued by > libvirt. For that we would need debug logs as referred to above. > > BTW: The stack trace looks a bit old (the line number do not match with >...

...migrate"}, {"name": "migrate_cancel"}, {"name": "migrate_set_speed"}, {"name": "client_migrate_info"}, {"name": "migrate_set_downtime"}, {"name": "netdev_add"}, {"name": "netdev_del"}, {"name": "block_resize"}, {"name": "balloon"}, {"name": "set_link"}, {"name": "getfd"}, {"name": "closefd"}, {"name": "block_passwd"}, {"name": "set_p...