similar to: Connecting libvirt to manually compiled QEMU

On Tue, Mar 04, 2014 at 02:09:19PM -0700, Eric Blake wrote: > On 03/04/2014 05:12 AM, Asadullah Hussain wrote: > > Hello I have manually compiled a customized qemu (1.4.0) which runs fine on > > its own (create VM etc) but I want to access this qemu through libvirt > > (virt-manager, virsh etc). > > > > But the libvirt driver only looks into "/usr/bin"

On Wed, Mar 19, 2014 at 05:17:52PM +0500, Asadullah Hussain wrote: > Guys thanks a lot for taking the time out to reply, Although adding the > $PATH & symbolic link methods both solved the "No hypervisor found" error > on virt-manager but when I try to create a VM using the wizard it says: > > "No hypervisor options were found for this connection" > >

Currently in the VM XML, I am passing the following command line argument as a passthrough argument: -netdev type=tap,id=net1,script=no,downscript=no,ifname=port3,vhost=on -device virtio-net-pci,netdev=net1,mac=00:00:00:00:00:01,csum=off,gso=off,guest_tso4=off,guest_tso6=off,guest_ecn=off Is there another way to represent this in the XML file? maybe that may solve the problem. On 24 July 2014

Guys thanks a lot for taking the time out to reply, Although adding the $PATH & symbolic link methods both solved the "No hypervisor found" error on virt-manager but when I try to create a VM using the wizard it says: "No hypervisor options were found for this connection" "This usually means that QEMU or KVM is not installed on your machine, or the KVM modules are

Hello, I have a custom QEMU which requires some non-standard command line arguments to launch a VM. e.g., "--proc-type=secondary" option is always required to launch a QEMU VM. To launch the VM through libvirt (virsh) "How do I specify these non-standard options in XML? OR if thats not possible ,Can you guide me at which point (code file) libvirt converts the XML to QEMU command

​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

There are a couple of problems with passthrough qemu: 1. virsh version/capabilities command executes "qemu -help" but this gives an error in my case because my customized qemu has to receive mandatory non-standard parameters "qemu -c -n -- -help". 2. Similarly when passing arguments as passthrough in a VMs XML. How can I make sure that these non-standard arguments are passed

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

Hello, I am trying run a simple VM (qemu1.4.2) on RHEL 6.5 through libvirt (0.10). virsh create throws the error: *​error: Failed to create domain from vm1.xml* *error: internal error process exited while connecting to monitor:*​ The libvirt log for VM shows: *libvir: error : cannot execute binary /usr/bin/qemu-system-x86_64: Permission denied* ​I am running VM as root and all disk

Still no success virsh capabilities doesn't return any "emulator" output. When I check the "libvirtd.log" there is an error: 2014-03-20 11:25:00.056+0000: 1014: error : virCommandWait:2188 : internal error Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/ local/bin:/usr/bin:/usr/sbin:/sbin:/bin /usr/local/bin/qemu-system-x86_64 -help) status unexpected: exit status 1 I

The qemu binary is accessible as I can create VM through command line. That is why I thought it may be a libvirt issue. I have also contacted Red Hat support and will post my findings here if the issue is resolved. On 23 April 2014 17:16, Eric Blake <eblake@redhat.com> wrote: > On 04/23/2014 05:44 AM, Asadullah Hussain wrote: > > Hello, > > > > I am trying run a

On 03/04/2014 05:12 AM, Asadullah Hussain wrote: > Hello I have manually compiled a customized qemu (1.4.0) which runs fine on > its own (create VM etc) but I want to access this qemu through libvirt > (virt-manager, virsh etc). > > But the libvirt driver only looks into "/usr/bin" for qemu binaries, how > can I tell libvirt to connect to my qemu which is placed at

Thanks Wangkai but libvirt infact pre-configures network tap devices and pre-opens /dev/vhost-net file and passes these to qemu as open, ready to use file descriptors. My issue is that my qemu requires that /dev/vhost-net directory is removed and it's kernel module be unloaded. Then it creates a vhost -net device using its own configuration. On 24 July 2014 07:35, Wangkai (Kevin,C)

I am using a custom qemu to launch a vhost enabled VM. The qemu doesn't use the default "/dev/vhost-net" directory as character device. Due to this I am getting the error: qemu-system-x86_64: -netdev type=tap,id=net1,script=no,downscript=no,ifname=port3,vhost=on: vhost-net requested but could not be initialized ​Is there a way to tell libvirt to ​avoid using the default

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 "/dev/vhost-net". When I try to give vhostfd in the XML I get a different error:

On Mon, Mar 31, 2014 at 04:33:40PM +0500, Asadullah Hussain wrote: > Hello, I have a custom QEMU which requires some non-standard command line > arguments to launch a VM. e.g., "--proc-type=secondary" option is always > required to launch a QEMU VM. > > To launch the VM through libvirt (virsh) "How do I specify these > non-standard options in XML? See this page

On 04/23/2014 05:44 AM, Asadullah Hussain wrote: > Hello, > > I am trying run a simple VM (qemu1.4.2) on RHEL 6.5 through libvirt (0.10). > virsh create throws the error: > > *​error: Failed to create domain from vm1.xml* > *error: internal error process exited while connecting to monitor:*​ > > The libvirt log for VM shows: > > > *libvir: error : cannot

On 24 July 2014 15:52, Daniel P. Berrange <berrange@redhat.com> wrote: > 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) > > > >

For qemu, the default vhost drive file is “/dev/vhost-net”, when you configured vhost on. Give the command “modprobe vhost-net” to add host kernel support for vhost. This is cannot controlled by libvirt I think. Wangkai From: libvirt-users-bounces@redhat.com [mailto:libvirt-users-bounces@redhat.com] On Behalf Of Asadullah Hussain Sent: Thursday, July 24, 2014 12:43 AM To:

On Thu, Jul 24, 2014 at 08:42:47AM +0500, Asadullah Hussain wrote: > Thanks Wangkai but libvirt infact pre-configures network tap devices and > pre-opens /dev/vhost-net file and passes these to qemu as open, ready to > use file descriptors. > > My issue is that my qemu requires that /dev/vhost-net directory is removed > and it's kernel module be unloaded. Then it creates a