I did more tests and if kill the qemu process without stopping
libvirtd and relaunching it with the following command
/usr/bin/qemu-system-x86_64 -S --no-user-config -nodefaults -nographic
-M none -qmp unix: /var /lib /libvirt /qemu
/capabilities.monitor.sock,server, nowait -pidfile
it does still hang.
The strange thing is that I launched qemu, without libvirtd,
independently creating a linux virtual machine, functions regularly
and reading the state with qmp is regularly running.
Stefano
2016-10-13 2:57 GMT+02:00 Michal Privoznik :
> On 12.10.2016
On Thu, Oct 13, 2016 at 01:47:08PM +0100, Andrei Perietanu wrote:
Hi all,
I have to admit Martin might have been right: I upgraded to qemu 2.6.0
and still I see the same problem with virtio disks on my custom built Linux
box.
I create domain using the previously mentioned domain xml
Hi all,
I have to admit Martin might have been right: I upgraded to qemu 2.6.0
and still I see the same problem with virtio disks on my custom built Linux
box.
I create domain using the previously mentioned domain xml definition and
try to install ubuntu from an iso. Earty on during the
On Thu, Oct 13, 2016 at 11:49:44AM +0200, Marina Danial wrote:
Hello,
In my C++ code, I generate my own domain XML file and I
use virDomainCreateXML or virDomainDefineXML to launch my qemu VM. However,
when I get to check which commands are sent to the qemu commandline, I find
that libvirt has
Hello,
In my C++ code, I generate my own domain XML file and I
use virDomainCreateXML or virDomainDefineXML to launch my qemu VM. However,
when I get to check which commands are sent to the qemu commandline, I find
that libvirt has added so many extra parameters to the ones I have already
set.