search for: vmifs_test

...rocess exited while connecting to monitor: qemu-kvm: -qmp tcp:127.0.0.1:1235: Duplicate ID 'monitor' for mon duplicate chardev: monitor The VM I created, without “—qmp” option, has below options showing in “ps aux | grep qemu-kvm”: -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vmifs_test.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control Looks like libvirt automatically adds the monitor options upon VM creation. Is there a way to disable this and use “—qmp” instead when creating VM? Thanks for your help. Best Regards, Min

...27.0.0.1:1235: Duplicate ID >> 'monitor' for mon duplicate chardev: monitor >> >> The VM I created, without “—qmp” option, has below options showing in >> “ps aux | grep qemu-kvm”: >> >> -chardev >> socket,id=charmonitor,path=/var/lib/libvirt/qemu/vmifs_test.monitor,server,nowait >> -mon chardev=charmonitor,id=monitor,mode=control >> >> Looks like libvirt automatically adds the monitor options upon VM >> creation. > > As I understand it, libvirt uses its own APIs to handle interactions > with QEMU monitor console, e.g...

...onitor: qemu-kvm: -qmp tcp:127.0.0.1:1235: Duplicate ID > 'monitor' for mon duplicate chardev: monitor > > The VM I created, without “—qmp” option, has below options showing in > “ps aux | grep qemu-kvm”: > > -chardev > socket,id=charmonitor,path=/var/lib/libvirt/qemu/vmifs_test.monitor,server,nowait > -mon chardev=charmonitor,id=monitor,mode=control > > Looks like libvirt automatically adds the monitor options upon VM > creation. As I understand it, libvirt uses its own APIs to handle interactions with QEMU monitor console, e.g. qemuMonitorOpen(), etc. If y...