> Your /usr/bin/kvm symlink is bad. It's pointing to
> /usr/bin/qemu-x86_64, instead of /usr/bin/qemu-system-x86_64.
Thanks for the reply. This fixed my problem.
-bryan
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mail
I'm running libvirt 1.0.1 and qemu 1.3. I see the following error of
libvirtd startup:
2013-01-19 04:51:06.183+: 1459: error : virCommandWait:2287 :
internal error Child process (LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
HOME=/ /usr/bin/kvm -help) unexpected e
> Though it's not that convenient as you have a independant monitor to talk
> directly, you could use "qemu-monitor-command" of communicate
> with the qemu monitor. And with the latest qemu, which supports monitor
> command "human-monitor-command", it's more compact, e.g.
Very interesting, thanks
Is there any way to get virsh / libvirt to create a domain such that I
can later connect to it via QMP (without hacking the code)?
The command line that libvirt creates for my current setup looks like this:
/usr/local/bin/qemu-system-x86_64 -S -M pc-0.12 -enable-kvm -m 512
-smp 1,sockets=1,cores=
