search for: elementsnicsethernet

I'm trying to create a free standing VM that doesn't connect to a bridge. This is supposedly do able according to the WIKI: https://libvirt.org/formatdomain.html#elementsNICSEthernet But with a config similar to: <interface type='ethernet'> <target dev='mytap1' managed='no'/> <model type='virtio'/> </interface> When starting the domain I get the error: error: internal error: process exited while connecting t...

Hi, I hope this is the right place to ask this question. I was wondering if there is a way to set up a KVM VM using an XML document as input into Virsh that uses bridged networking over a wireless card. I understand that wireless cards to not natively support, but I was able to find a working solution here: http://blog.ericwhite.ca/articles/2011/04/creating-a-wireless-bridge/. The issue is, I

...> input into Virsh for the creation of a VM. > > > > My understanding is that libvirt calls KVM/QEMU at some point, but I may > be > > mistaken. > > You might be able to get it working using the generic ethernet config > > http://libvirt.org/formatdomain.html#elementsNICSEthernet > > That setup you specify a pre-created TAP device for the VM to use. > Of course it is upto you todo the manal config steps described in > that blog, so is more tedious from an admin pov. > > > Daniel > -- > |: http://berrange.com -o- http://www.flickr.com/photo...

...e configuration on an XML file that I > input into Virsh for the creation of a VM. > > My understanding is that libvirt calls KVM/QEMU at some point, but I may be > mistaken. You might be able to get it working using the generic ethernet config http://libvirt.org/formatdomain.html#elementsNICSEthernet That setup you specify a pre-created TAP device for the VM to use. Of course it is upto you todo the manal config steps described in that blog, so is more tedious from an admin pov. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org...

...reation of a VM. >> > >> > My understanding is that libvirt calls KVM/QEMU at some point, but I >> may be >> > mistaken. >> >> You might be able to get it working using the generic ethernet config >> >> http://libvirt.org/formatdomain.html#elementsNICSEthernet >> >> That setup you specify a pre-created TAP device for the VM to use. >> Of course it is upto you todo the manal config steps described in >> that blog, so is more tedious from an admin pov. >> >> >> Daniel >> -- >> |: http://berrange.com...

...And the logs? tx_queue_size='512' will not work in the guest with direct type interface, in fact, no matter what you set, it will not work and guest will get the default '256'. We only support vhost-user backend to have more than 256. refer to https://libvirt.org/formatdomain.html#elementsNICSEthernet tx_queue_size The optional tx_queue_size attribute controls the size of virtio ring for each queue as described above. The default value is hypervisor dependent and may change across its releases. Moreover, some hypervisors may pose some restrictions on actual value. For instance, QEMU v2.9 requir...

...ueue_size='512' will not work in the guest with direct type interface, > in fact, no matter what you set, it will not work and guest will get the > default '256'. > We only support vhost-user backend to have more than 256. refer to > https://libvirt.org/formatdomain.html#elementsNICSEthernet > > tx_queue_size > The optional tx_queue_size attribute controls the size of virtio ring for > each queue as described above. The default value is hypervisor dependent > and may change across its releases. Moreover, some hypervisors may pose > some restrictions on actual value. F...

...ype >>>>> interface, in fact, no matter what you set, it will not work and guest will >>>>> get the default '256'. >>>>> We only support vhost-user backend to have more than 256. refer to >>>>> https://libvirt.org/formatdomain.html#elementsNICSEthernet >>>>> >>>>> tx_queue_size >>>>> The optional tx_queue_size attribute controls the size of virtio ring >>>>> for each queue as described above. The default value is hypervisor >>>>> dependent and may change across its release...

...st with direct type >>>> interface, in fact, no matter what you set, it will not work and guest will >>>> get the default '256'. >>>> We only support vhost-user backend to have more than 256. refer to >>>> https://libvirt.org/formatdomain.html#elementsNICSEthernet >>>> >>>> tx_queue_size >>>> The optional tx_queue_size attribute controls the size of virtio ring >>>> for each queue as described above. The default value is hypervisor >>>> dependent and may change across its releases. Moreover, some hy...

...>>> interface, in fact, no matter what you set, it will not work and guest will >>>>>> get the default '256'. >>>>>> We only support vhost-user backend to have more than 256. refer to >>>>>> https://libvirt.org/formatdomain.html#elementsNICSEthernet >>>>>> >>>>>> tx_queue_size >>>>>> The optional tx_queue_size attribute controls the size of virtio >>>>>> ring for each queue as described above. The default value is hypervisor >>>>>> dependent and may chang...

Hi Michal, What I found was that when I restarted the machine and did a virsh edit command to see the xml config, I see that it is was not actually changed. This suggests why I saw 256 again after restarting. So now I tried again to edit the xml via virsh edit command and used the following to set the parameters. <driver name='qemu' txmode='iothread' ioeventfd='on'