search for: asadullah

...ev 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 15:55, Asadullah Hussain <asadxflow@gmail.com> wrote: > > > > 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...

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...

...​Is there a way to tell libvirt to ​avoid using the default /dev/vhost-net file? I have tried using the pass-through arguments but libvirt still processes the command and throws the error. PS: I can successfully create a vhost VM using qemu command-line, so this is a libvirt issue. -- Cheers, Asadullah Hussain

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 option...

...t 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:* libvirt-users@redhat.com > *Subject:* [libvirt-users] vhost-net requested but could not be > initialized > > > > I am using a custom qemu to launch a vhost enabled VM. The qemu doesn't > use the default "...

...sum=off,gso=off,guest_tso4=off,guest_tso6=off,guest_ecn=off ​ As you can see I have created tap interfaces port3 & port4 and I just want to connect the VM to these VMs. On 24 July 2014 13:31, Daniel P. Berrange <berrange@redhat.com> wrote: > 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...

...m1.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 images/ISOs required for VM are read/write/executable. ​ -- Asadullah Hussain

...ys 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 (so that I can insert the option there). Regards -- Asadullah Hussain

...-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: Device 'tap' could not be initialized On 24 July 2014 13:47, Asadullah Hussain <asadxflow@gmail.com> wrote: > ​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 -boo...

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"...

...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 "/home/user/qemu" directory. -- Asadullah Hussain

...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 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 conn...

...n I make sure that these non-standard arguments are passed first i.e., My qemu command for a VM should be "qemu -c -n -- <Rest of the standard parameters>" On 31 March 2014 16:45, Daniel P. Berrange <berrange@redhat.com> wrote: > 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) "...

...t; I am using virt-manager GUI to see whether qemu is being detected by libvirt or not (is there a better/CLI method?) On 5 March 2014 15:51, Daniel P. Berrange <berrange@redhat.com> wrote: > 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 lo...

...pipermail/virt/2012-July/003358.html) but the solution suggested involves KVM which I cannot do (I just want to run simple qemu 1.4.0 ) libvirt version: 0.98 qemu: 1.4.0 On 19 March 2014 18:06, Daniel P. Berrange <berrange@redhat.com> wrote: > 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: > > > > &q...

...fault 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: libvirt-users@redhat.com Subject: [libvirt-users] vhost-net requested but could not be initialized 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...

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) > > > > The VHOST file descriptor is prese...

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 &...

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 &...

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 li...