search for: virdomainattachdevice

Hi All, I find that I am able to attach a disk device do a Xen domain, using virDomainAttachDevice(), running as a non-root user, but I am unable to use virDomainDetachDevice() - it results in an "unknown failure". Using "virsh [attach|detach]-device" exhibits this behviour. $ virsh attach-device domu1 attach.xml Device attached successfully $ virsh detach-device domu1 atta...

Hi, buddy, I want to create a virtual device attachment to backend. The domain is running, and my code phase is as below: xmlConfiguration = "<devices><sound model='es1370'/></devices>"; virDomainAttachDevice(dom,xmlConfiguration); But the exception "libvir: Domain Config error : XML error: unknown device type " happen when running. Is it something wrong in the XML configuration? What should i do to deal with such Config error ? ps: the hypervisor is KVM. -------------- next part -----------...

Good day to all. i have problems with cdrom hot adding code. currently i using virDomainAttachDevice with type=file, device=cdrom, dev=hdc, this code works for machine with one ide hdd and one ide cdrom, but this not work for machine with only one ide hdd, and i looking for solution to hot add cdrom to machine independent of existing devices or i need way to determinate which target device can...

On Thu, Dec 05, 2013 at 01:28:07PM +0200, Alexandr Gluzskiy wrote: > Alexandr писал 2013-12-02 09:36: > >Good day to all. i have problems with cdrom hot adding code. currently > >i using virDomainAttachDevice with type=file, device=cdrom, dev=hdc, > >this code works for machine with one ide hdd and one ide cdrom, but > >this not work for machine with only one ide hdd, and i looking for > >solution to hot add cdrom to machine independent of existing devices > >or i need way to det...

...self.vm.attach_device(self._dev) File "/usr/share/virt-manager/virtManager/domain.py", line 756, in attach_device self._backend.attachDevice(devxml) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 403, in attachDevice if ret == -1: raise libvirtError ('virDomainAttachDevice() failed', dom=self) libvirtError: Requested operation is not valid: cannot do live update a device on inactive domain Shutdown domain: Error shutting down domain: Requested operation is not valid: domain is not running Traceback (most recent call last): File "/usr/share/virt-manager...

...self.vm.attach_device(dev) File "/usr/share/virt-manager/virtManager/object/domain.py", line 920, in attach_device self._backend.attachDevice(devxml) File "/usr/lib/python3.8/site-packages/libvirt.py", line 590, in attachDevice if ret == -1: raise libvirtError ('virDomainAttachDevice() failed', dom=self) libvirt.libvirtError: failed to load cgroup BPF prog: Operation not permitted Now, libvirtd is running as root, so I don't understand why any operation on BPF programs is not permitted. I've dug into libvirt's code a bit to see what is throwing this error and...

...rovided there's a working implementation which is likely to go upstream. - - - - Here are some ideas about how we might add hotplugging without breaking existing clients. (1) The "raw libvirt" option In this one we'd simply provide thin wrappers around virDomainAttachDevice and virDomainDetactDevice, and leave it up to the user to know what they're doing. The problem with this is the hidden appliance disk. We certainly don't want the user to accidentally detach that(!) It's also undesirable for there to be a "hole" in the naming scheme so that...

...self.vm.attach_device(self._dev) File "/usr/share/virt-manager/virtManager/domain.py", line 698, in attach_device self._backend.attachDevice(devxml) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 400, in attachDevice if ret == -1: raise libvirtError ('virDomainAttachDevice() failed', dom=self) libvirtError: XML error: unknown device type We wish to have at least two, preferably three, andf ideally all four, serial ports enabled on the virtual guest. Does anyone know how this is accomplished? -- *** E-Mail is NOT a SECURE channel *** James B....

Hi, Is there an equivalent of "virsh attach-device -live -persistent " within libvirt API : virDomainAttachDevice() or virDomainAttachDeviceFlags() or ??? Thanks for help. Regards, J.P. Ribeauville P: +33.(0).1.47.17.20.49 . Puteaux 3 Etage 5 Bureau 4 jpribeauville@axway.com<mailto:jpribeauville@axway.com> http://www.axway.com<http://www.axway.com/> P Pensez à l'environnement avan...

.../share/virt-manager/virtManager/object/domain.py", line 920, in attach_device > > > self._backend.attachDevice(devxml) > > > File "/usr/lib/python3.8/site-packages/libvirt.py", line 590, in attachDevice > > > if ret == -1: raise libvirtError ('virDomainAttachDevice() failed', dom=self) > > > libvirt.libvirtError: failed to load cgroup BPF prog: Operation not permitted > > > > > > > > > Now, libvirtd is running as root, so I don't understand why any > > > operation on BPF programs is not permitted. I'v...

Alexandr писал 2013-12-02 09:36: > Good day to all. i have problems with cdrom hot adding code. currently > i using virDomainAttachDevice with type=file, device=cdrom, dev=hdc, > this code works for machine with one ide hdd and one ide cdrom, but > this not work for machine with only one ide hdd, and i looking for > solution to hot add cdrom to machine independent of existing devices > or i need way to determinate which t...

...ager/virtManager/object/domain.py", line 920, in attach_device > > > > self._backend.attachDevice(devxml) > > > > File "/usr/lib/python3.8/site-packages/libvirt.py", line 590, in attachDevice > > > > if ret == -1: raise libvirtError ('virDomainAttachDevice() failed', dom=self) > > > > libvirt.libvirtError: failed to load cgroup BPF prog: Operation not permitted > > > > > > > > > > > > Now, libvirtd is running as root, so I don't understand why any > > > > operation on BPF programs...

...09230 "<interface type=\"bridge\">\n <source bridge=\"xenbr0\" />\n <model type=\"rtl8139\" />\n <mac address=\"00:27:0e:0c:01:09\" />\n </interface>") at libxl/libxl_driver.c:3745 #17 0x00007f793b18422c in virDomainAttachDevice (domain=0x7f791c009150, xml=0x7f791c009230 "<interface type=\"bridge\">\n <source bridge=\"xenbr0\" />\n <model type=\"rtl8139\" />\n <mac address=\"00:27:0e:0c:01:09\" />\n </interface>") at libvirt-domain...

...unit" }, + { name => "virDomainDefineXML", sig => "conn, string : dom" }, + { name => "virDomainUndefine", sig => "dom : unit" }, + { name => "virDomainCreate", sig => "dom : unit" }, + { name => "virDomainAttachDevice", sig => "dom, string : unit" }, + { name => "virDomainDetachDevice", sig => "dom, string : unit" }, + { name => "virDomainGetAutostart", sig => "dom : bool" }, + { name => "virDomainSetAutostart", sig =>...

libvirt-ocaml is used only by virt-v2v, so move it to this repository, instead of having it around in the common submodule. The removal from common will happen later. Pino Toscano (2): common: Bundle the libvirt-ocaml library for use by virt-v2v build: switch embedded copy of libvirt-ocaml .gitignore | 2 + 3rdparty/libvirt-ocaml/Makefile.am |

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all