search for: virdomainundefine

...twice> Hello, I'm facing some strange behavior, and I hope you can provide a clarification. Consider the following code: virDomainPtr dom = virDomainLookupByName(virt, domain_name); if (dom) { printf("domain already defined...\n"); if (virDomainUndefine(dom)) printf("...unable to undefine!!!\n"); else { printf("...undefined."); free(dom); } } dom = virDomainDefineXML(virt, SOME_XML); if (dom != NULL) { const char *name = vir...

...g if there is a way to do this better of searching the XML strings of all domains, does anyone can suggest me something ? I also need to create a function to change the img file of a given domain. I intend to do the following: 1. virDomainGetXMLDesc (domain) 2. change the XML to other img file 3. virDomainUndefine (domain) 4. virDomainCreateXML (changed XML) Am i correct doing this ? There is a better method ? Thanks Ricardo

...ending on whether a feature is deemed important enough to be exposed. So please feel free to report if anything is missing or it would be helpful if we reported any feature. --- Now specifically to the question: I was asked on when it's safe to pass VIR_DOMAIN_UNDEFINE_CHECKPOINTS_METADATA to virDomainUndefine. In this case it's safe to pass it if <features> contains the <backup> element regardless of the value of 'supported' attribute. I'll also mention this in the documentation of the domain caps XML.

Hello, I'm facing some strange behavior, and I hope you can provide a clarification. Consider the following code: virDomainPtr dom = virDomainLookupByName(virt, domain_name); if (dom) { printf("domain already defined...\n"); if (virDomainUndefine(dom)) printf("...unable to undefine!!!\n"); else { printf("...undefined."); free(dom); } } dom = virDomainDefineXML(virt, SOME_XML); if (dom != NULL) { const char *name = vir...

...t" }, + { name => "virDomainShutdown", sig => "dom : unit" }, + { name => "virDomainReboot", sig => "dom, 0 : 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, st...

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