Hi, I am using "qemu-attach" in virsh to attach to an existing qemu process so I can send monitor commands to it. the VM is started using qemu-kvm -net none -hda ./out.img -m 4G -nographic The VM gets started and the OS boots fine. Then, I start virsh and do a "qemu-attach 44273" which is the PID of the qemu process. virsh # qemu-attach 44273 error: Failed to attach to pid 44273 error: Cannot check QEMU binary qemu-kvm: No such file or directory qemu-kvm is in /usr/libexec. There is a symlink to it from /usr/bin and /bin. The virsh command "create" (for a different VM) works fine. What could be missing? Are there any debug/log messages/config files that can shed some light. Thanks.
Nm, turns out qemu-kvm needs to be started with the full path (/usr/libexec/qemu-kvm -hda....) then virsh goes past this error. On Wed, Mar 8, 2017 at 12:22 PM, DS DS <dsvirt17@gmail.com> wrote:> Hi, > > I am using "qemu-attach" in virsh to attach to an existing qemu process so > I can send monitor commands to it. > > the VM is started using > qemu-kvm -net none -hda ./out.img -m 4G -nographic > > The VM gets started and the OS boots fine. > > Then, I start virsh and do a "qemu-attach 44273" which is the PID of the > qemu process. > virsh # qemu-attach 44273 > error: Failed to attach to pid 44273 > error: Cannot check QEMU binary qemu-kvm: No such file or directory > > qemu-kvm is in /usr/libexec. There is a symlink to it from /usr/bin and > /bin. > > The virsh command "create" (for a different VM) works fine. > > What could be missing? Are there any debug/log messages/config files that > can shed some light. > > Thanks. >
Maybe Matching Threads
- How to tell libvirt not to use qemu "accel=kvm" for a FreeBSD guest
- Re: How to tell libvirt not to use qemu "accel=kvm" for a FreeBSD guest
- Problems moving qemu machine to libvirt
- Re: Problems with qemu-system-arm and isa-serial
- Re: use of qemu-kvm --chardev pipe, id=X, path=... argument ?