search for: qemuprocesswaitformonitor

...0" directory instead of the default "/dev/vhost-net". When I try to give vhostfd in the XML I get a different error: 2014-07-24 10:42:22.507+0000: 3181: error : qemuMonitorOpenUnix:293 : failed to connect to monitor socket: No such process 2014-07-24 10:42:22.507+0000: 3181: error : qemuProcessWaitForMonitor:1806 : internal error process exited while connecting to monitor: qemu-system-x86_64: -netdev type=tap,id=net1,script=no,downscript=no,ifname=port4,vhost=on,vhostfd=/dev/vhost-0: Device 'tap' could not be initialized Whereas if I don't give the vhostfd option in the XML, it uses the d...

On Thu, Jul 24, 2014 at 03:48:06PM +0500, Asadullah Hussain wrote: > Let me clarify my question, I am using unmodified stock qemu (1.4.0) and > only the location of vhost file descriptor is different from default (I > don't remove the default /dev/vhost-net directory) > > The VHOST file descriptor is present in "/dev/vhost-0" directory instead of > the default

...ice name to /dev/vhost-net but still I get > the error, the error itself isn't telling much about the problem: > 2014-07-24 10:41:35.970+0000: 3183: error : qemuMonitorOpenUnix:293 : > failed to connect to monitor socket: No such process > 2014-07-24 10:41:35.970+0000: 3183: error : qemuProcessWaitForMonitor:1806 > : internal error process exited while connecting to monitor: > qemu-system-x86_64: -netdev > type=tap,id=net1,script=no,downscript=no,ifname=port4,vhost=on: vhost-net > requested but could not be initialized > qemu-system-x86_64: -netdev type=tap,id=net1,script=no, > downsc...

​The qemu that I am using isn't modified at all. It's the VHOST drivers that are mounted elsewhere i.e., not on default /dev/vhost-net. Here is the command that I use to launch my qemu VM: qemu-system-x86_64 -cpu host -boot order=c -hda /root/Disks/ubuntu1.qcow2 -m 1024M -smp 2 --enable-kvm -name 'client 1' -nographic -vnc :2 -net none -no-reboot -mem-path /dev/hugepages

...ble to change my device name to /dev/vhost-net but still I get the error, the error itself isn't telling much about the problem: 2014-07-24 10:41:35.970+0000: 3183: error : qemuMonitorOpenUnix:293 : failed to connect to monitor socket: No such process 2014-07-24 10:41:35.970+0000: 3183: error : qemuProcessWaitForMonitor:1806 : internal error process exited while connecting to monitor: qemu-system-x86_64: -netdev type=tap,id=net1,script=no,downscript=no,ifname=port4,vhost=on: vhost-net requested but could not be initialized qemu-system-x86_64: -netdev type=tap,id=net1,script=no, downscript=no,ifname=port4,vhost=on:...

...onsole 2012-06-16 19:56:39.807+0000: 32175: error : virNetSocketReadWire:911 : End of file while reading data: Input/output error 2012-06-16 20:15:23.672+0000: 32176: error : qemuMonitorOpenUnix:290 : failed to connect to monitor socket: No such process 2012-06-16 20:15:23.672+0000: 32176: error : qemuProcessWaitForMonitor:1289 : internal error process exited while connecting to monitor: char device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4,127.0.0.1,5902): Cannot assign requested address inet_listen_opts: FAILED Log messages in /var/log/libvirt/qemu/SequoiaVM.log are similar 2012-06-16 13:45:04.572: st...

...;ceph' uuid=e4412366-1f16-4c54-b121-dfb565672427 is tainted: high-privileges Detaching after fork from child process 23015. 2015-01-08 08:07:32.684+0000: 22552: error : qemuMonitorOpenUnix:309 : failed to connect to monitor socket: No such process 2015-01-08 08:07:32.684+0000: 22552: error : qemuProcessWaitForMonitor:2207 : internal error: process exited while connecting to monitor: 2015-01-08 08:07:32.684+0000: 22552: error : virDBusCall:1542 : error from service: TerminateMachine: No such file or directory 4. Start it by qemu cmd # cat /usr/local/var/log/libvirt/qemu/ceph.log 2015-01-08 08:08:12.179+000...