- Devel - libvirt List Archives

[libvirt] libvirt Centos4
by Gian Mario 27 Mar '09

27 Mar '09

Hi to all, i need to compile libvirt-3.3.0 to Centos 4.7. Searching in mailing list i have seen a tread that help me to solve few problems. Actually i face with a error concern glibc, when i run make in libvirt directory, I obtain: /usr/lib64/libgcrypt.so.11: undefined reference to `__read_chk(a)GLIBC_2.4' /usr/lib/gcc/x86_64-redhat-linux/3.4.6/../../../../lib64/libgnutls.so: undefined reference to `__stack_chk_fail(a)GLIBC_2.4' collect2: ld returned 1 exit status make[2]: *** [virsh] Error 1 make[2]: Leaving directory `/root/XEN/libvirt-0.3.3/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/XEN/libvirt-0.3.3' make: *** [all] Error 2 Any one have some experience on compile libvirt on centos4? there is any possibilities to build it without upgrade glibc? tnks to any help. Ciao e statevi bene. GMario

3 2

[libvirt] PATCH: Support memory ballooning for QEMU
by Daniel P. Berrange 27 Mar '09

27 Mar '09

This patch implements full support for memory ballooning in the QEMU driver. - Fix qemudBuildCommandLine() to set the initial boot time VM memory allocation based off the 'maxmem' config field. - Add call to 'qemudDomainSetMemoryBalloon' immediately at startup to make the guest balloon to initial requested allocation. - In the qemudDomainGetInfo() and qemudDomainDumpXML calls, query the monitor to find current balloon allocation and update config - Implement qemudDomainSetMemory() for running guests using the monitor balloon command In all of these scenarios, if the QEMU being used is too old to support the memory balloon device, the user will get a suitable error or it'll report the statically defined memory allocation from boot time. Daniel diff -r 4bfef84f4d6f src/qemu_conf.c --- a/src/qemu_conf.c Tue Mar 10 12:09:41 2009 +0000 +++ b/src/qemu_conf.c Tue Mar 10 16:16:59 2009 +0000 @@ -870,7 +870,11 @@ int qemudBuildCommandLine(virConnectPtr } \ } while (0) - snprintf(memory, sizeof(memory), "%lu", vm->def->memory/1024); + /* Set '-m MB' based on maxmem, because the lower 'memory' limit + * is set post-startup using the balloon driver. If balloon driver + * is not supported, then they're out of luck anyway + */ + snprintf(memory, sizeof(memory), "%lu", vm->def->maxmem/1024); snprintf(vcpus, sizeof(vcpus), "%lu", vm->def->vcpus); snprintf(domid, sizeof(domid), "%d", vm->def->id); pidfile = virFilePid(driver->stateDir, vm->def->name); diff -r 4bfef84f4d6f src/qemu_driver.c --- a/src/qemu_driver.c Tue Mar 10 12:09:41 2009 +0000 +++ b/src/qemu_driver.c Tue Mar 10 16:16:59 2009 +0000 @@ -122,6 +122,9 @@ static int qemudMonitorCommandExtra(cons const char *extra, const char *extraPrompt, char **reply); +static int qemudDomainSetMemoryBalloon(virConnectPtr conn, + virDomainObjPtr vm, + unsigned long newmem); static struct qemud_driver *qemu_driver = NULL; @@ -1480,6 +1483,7 @@ static int qemudStartVMDaemon(virConnect (qemudDetectVcpuPIDs(conn, vm) < 0) || (qemudInitCpus(conn, vm, migrateFrom) < 0) || (qemudInitPasswords(conn, driver, vm) < 0) || + (qemudDomainSetMemoryBalloon(conn, vm, vm->def->memory) < 0) || (qemudSaveDomainStatus(conn, qemu_driver, vm) < 0)) { qemudShutdownVMDaemon(conn, driver, vm); return -1; @@ -2409,6 +2413,98 @@ cleanup: return ret; } + +#define BALLOON_PREFIX "balloon: actual=" + +/* + * Returns: 0 if balloon not supported, +1 if balloon query worked + * or -1 on failure + */ +static int qemudDomainGetMemoryBalloon(virConnectPtr conn, + virDomainObjPtr vm, + unsigned long *currmem) { + char *reply = NULL; + int ret = -1; + char *offset; + + if (qemudMonitorCommand(vm, "info balloon", &reply) < 0) { + qemudReportError(conn, dom, NULL, VIR_ERR_OPERATION_FAILED, + "%s", _("could not query memory balloon allocation")); + goto cleanup; + } + + /* If the command failed qemu prints: + * device not found, device is locked ... + * No message is printed on success it seems */ + DEBUG ("balloon reply: '%s'", reply); + if ((offset = strstr(reply, BALLOON_PREFIX)) != NULL) { + unsigned int memMB; + char *end; + offset += strlen(BALLOON_PREFIX); + if (virStrToLong_ui(offset, &end, 10, &memMB) < 0) { + qemudReportError(conn, dom, NULL, VIR_ERR_OPERATION_FAILED, + "%s", _("could not parse memory balloon allocation")); + goto cleanup; + } + *currmem = memMB * 1024; + ret = 1; + } else { + /* We don't raise an error here, since its to be expected that + * many QEMU's don't support ballooning + */ + ret = 0; + } + +cleanup: + VIR_FREE(reply); + return ret; +} + +/* + * Returns: 0 if balloon not supported, +1 if balloon query worked + * or -1 on failure + */ +static int qemudDomainSetMemoryBalloon(virConnectPtr conn, + virDomainObjPtr vm, + unsigned long newmem) { + char *cmd; + char *reply = NULL; + int ret = -1; + + /* + * 'newmem' is in KB, QEMU monitor works in MB, and we all wish + * we just worked in bytes with unsigned long long everywhere. + */ + if (virAsprintf(&cmd, "balloon %lu", (newmem / 1024)) < 0) { + virReportOOMError(conn); + goto cleanup; + } + + if (qemudMonitorCommand(vm, cmd, &reply) < 0) { + qemudReportError(conn, dom, NULL, VIR_ERR_OPERATION_FAILED, + "%s", _("could not balloon memory allocation")); + VIR_FREE(cmd); + goto cleanup; + } + VIR_FREE(cmd); + + /* If the command failed qemu prints: + * device not found, device is locked ... + * No message is printed on success it seems */ + DEBUG ("balloon reply: %s", reply); + if (strstr(reply, "\nunknown command:")) { + /* Don't set error - it is expected memory balloon fails on many qemu */ + ret = 0; + } else { + ret = 1; + } + +cleanup: + VIR_FREE(reply); + return ret; +} + + static int qemudDomainSetMemory(virDomainPtr dom, unsigned long newmem) { struct qemud_driver *driver = dom->conn->privateData; virDomainObjPtr vm; @@ -2426,20 +2522,21 @@ static int qemudDomainSetMemory(virDomai goto cleanup; } + if (newmem > vm->def->maxmem) { + qemudReportError(dom->conn, dom, NULL, VIR_ERR_INVALID_ARG, + "%s", _("cannot set memory higher than max memory")); + goto cleanup; + } + if (virDomainIsActive(vm)) { - qemudReportError(dom->conn, dom, NULL, VIR_ERR_NO_SUPPORT, - "%s", _("cannot set memory of an active domain")); - goto cleanup; - } - - if (newmem > vm->def->maxmem) { - qemudReportError(dom->conn, dom, NULL, VIR_ERR_INVALID_ARG, - "%s", _("cannot set memory higher than max memory")); - goto cleanup; - } - - vm->def->memory = newmem; - ret = 0; + ret = qemudDomainSetMemoryBalloon(dom->conn, vm, newmem); + if (ret == 0) + qemudReportError(dom->conn, dom, NULL, VIR_ERR_NO_SUPPORT, + "%s", _("cannot set memory of an active domain")); + } else { + vm->def->memory = newmem; + ret = 0; + } cleanup: if (vm) @@ -2452,6 +2549,8 @@ static int qemudDomainGetInfo(virDomainP struct qemud_driver *driver = dom->conn->privateData; virDomainObjPtr vm; int ret = -1; + int err; + unsigned long balloon; qemuDriverLock(driver); vm = virDomainFindByUUID(&driver->domains, dom->uuid); @@ -2473,8 +2572,15 @@ static int qemudDomainGetInfo(virDomainP } } + err = qemudDomainGetMemoryBalloon(dom->conn, vm, &balloon); + if (err < 0) + goto cleanup; + info->maxMem = vm->def->maxmem; - info->memory = vm->def->memory; + if (err == 0) /* Balloon not supported */ + info->memory = vm->def->memory; + else + info->memory = balloon; info->nrVirtCpu = vm->def->vcpus; ret = 0; @@ -3169,16 +3275,25 @@ static char *qemudDomainDumpXML(virDomai struct qemud_driver *driver = dom->conn->privateData; virDomainObjPtr vm; char *ret = NULL; - - qemuDriverLock(driver); - vm = virDomainFindByUUID(&driver->domains, dom->uuid); - qemuDriverUnlock(driver); - - if (!vm) { - qemudReportError(dom->conn, dom, NULL, VIR_ERR_INVALID_DOMAIN, - "%s", _("no domain with matching uuid")); - goto cleanup; - } + unsigned long balloon; + int err; + + qemuDriverLock(driver); + vm = virDomainFindByUUID(&driver->domains, dom->uuid); + qemuDriverUnlock(driver); + + if (!vm) { + qemudReportError(dom->conn, dom, NULL, VIR_ERR_INVALID_DOMAIN, + "%s", _("no domain with matching uuid")); + goto cleanup; + } + + /* Refresh current memory based on balloon info */ + err = qemudDomainGetMemoryBalloon(dom->conn, vm, &balloon); + if (err < 0) + goto cleanup; + if (err > 0) + vm->def->memory = balloon; ret = virDomainDefFormat(dom->conn, (flags & VIR_DOMAIN_XML_INACTIVE) && vm->newDef ? -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

3 4

[libvirt] Libvirt - Problems in different Versions
by Artur Baruchi 27 Mar '09

27 Mar '09

Hi Guys. Im writing a program that connects to Xen and gets some information (scheduller and memory informations). When executing the program using the libvirt 0.3.3 its working fine, BUT when running using libvirt 0.4.4 it doesnt work. I dont get any error message when compiling or executing, but the informations doesnt come. -> Using libvirt 0.3.3 # gcc -Wall -lxenstore `pkg-config --cflags --libs libvirt` test.c -o test # ./test DOMAINS IDENTIFIED 2 DomID: 0 Max Mem: 4294967292 Sched: 256 DomID: 3 Max Mem: 262144 Sched: 256 # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 616 2 r----- 4751.9 vm01 3 256 2 -b---- 379.7 -> Using libvirt 0.4.4 # gcc -Wall -lxenstore `pkg-config --cflags --libs libvirt` test.c -o test # ./test DOMAINS IDENTIFIED 0 # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 481 2 r----- 89.8 linuxprv01 1 512 1 -b---- 10.8 I executed the same program in other server, with 0.4.4 version, and got the same problem. Is there any difference between those versions? Thanks in advance. Att. Artur Baruchi

2 1

[libvirt] Using libvirt from PHP
by Radek Hladik 26 Mar '09

26 Mar '09

Hi, I am developing wimple web application in PHP to monitor and control VMs using libvirt. I hope it could become simple library for doing basic things with VMs. And I would like to ask for your opinion about different possibilities of calling libvirt. Option 1) I am calling virsh via exec command now (one virsh for every libvirt command). This can be used for local libvirt but it is very inefficient. The overhead for remote libvirt would be unbearable. I could run one virsh per page and use it "interactively" so the overhead gets lower. Option 2) The other option is to create Zend extension which should be able to call libvirt directly from C. However I've never done anything like that so I do not know, whether it is reasonable or not. Option 3) I could also create some "wrapper daemon" in C or other language with libvirt binding. But I think that this is an ugly way :-) Option 4) I could "talk" directly to the libvirt socket. But I am not sure how the communication goes there and whether it is stable or changes with every version. And I consider the socket to be internal thing of libvirt... Is there any other option I missed? And which one would you suggest? Radek

5 5

[libvirt] Monitoring VMs via java application
by Daniel Halle 26 Mar '09

26 Mar '09

Hello all, I want to monitor my VMs with a Java application. Is there a possibility to register an observer or the like which is triggered e.g. after the state of a VM has changed? Or is the only way to use a timer which polls all VMs every xy minutes? Thanks, Daniel -- Infinis GmbH - Taläckerstr. 30 - D-70437 Stuttgart Geschäftsführer: Daniel Schwager, Stefan Hörz - HRB Stuttgart 20964 Tel: 0711-849910-23 - Fax: 0711-849910-923 - daniel.halle(a)infinis.de

2 1

[libvirt] Restoring from a largish 'virsh save' file
by Matt McCowan 26 Mar '09

26 Mar '09

Running into an issue where, if I/O is hampered by load for example, reading a largish state file (created by 'virsh save') is not allowed to complete. qemudStartVMDaemon in src/qemu_driver.c has a loop that waits 10 seconds for the VM to be brought up. An strace against libvirt when doing a 'virsh restore' against a largish state file shows the VM being sent a kill when it's still happily reading from the file. inotify is used in the xen and uml drivers, so I thought it would be a suitable mechanism to delay the timeout loop if the state file was still being read. Is this the right way to solve this problem? I've inlined some (flimsy) mods for comment Regards Matt McCowan --- libvirt.orig/src/qemu_driver.c 2009-03-20 11:17:57.000000000 +0900 +++ libvirt-0.6.1.1/src/qemu_driver.c 2009-03-22 18:36:06.000000000 +0900 @@ -43,6 +43,7 @@ #include <stdio.h> #include <sys/wait.h> #include <sys/ioctl.h> +#include <sys/inotify.h> #if HAVE_NUMACTL #define NUMA_VERSION1_COMPATIBILITY 1 @@ -1310,6 +1309,11 @@ pid_t child; int pos = -1; char ebuf[1024]; + char rpathname[PATH_MAX]; + int fd = 0; + int wd = 0; + int got = 0; + char buf[1024]; struct gemudHookData hookData; hookData.conn = conn; @@ -1430,6 +1434,19 @@ qemudSecurityHook, &hookData); /* wait for qemu process to to show up */ + + /* Times out if using a restore file and that file + is big. Use inotify */ + if (stdin_fd > 0) { + fd = inotify_init(); + + if (snprintf(rpathname, sizeof(rpathname), "/proc/self/fd/%d", + stdin_fd) >= (int)sizeof(rpathname)) { + return -1; + } + wd = inotify_add_watch(fd, rpathname, IN_ACCESS); + } + if (ret == 0) { int retries = 100; int childstat; @@ -1442,7 +1459,15 @@ if ((ret = virFileReadPid(driver->stateDir, vm->def->name, &vm->pid)) == 0) break; usleep(100*1000); - retries--; + + /* Is state file being accessed? */ + got = read(fd, buf, sizeof(buf)); + if (got < 1) + retries--; + } + if (stdin_fd > 0) { + inotify_rm_watch(fd, wd); + close(fd); } if (ret) { qemudReportError(conn, NULL, NULL, VIR_ERR_INTERNAL_ERROR,

2 3

Re: [libvirt] Using libvirt from PHP
by Russell Haering 25 Mar '09

25 Mar '09

* Sorry, I somehow sent this to the wrong address * Radek, Not to advertise blatantly, but how attached are you to PHP? I'm currently working on a Django (python) WebApp that (although its *very* pre-release) could probably be adapted to what you're doing. If you are interested in assisting in development you'd be welcome to, or if you just wanted to fork off the code into your own thing you could do that too. My system consists of a python daemon used for actual libvirt interaction and a separate django web interface that interacts with the daemon via AMF over https. If you want to stick with what you have now, you could try doing something similar with a python daemon (you really need something like that for the sake of efficiency anyway, unless you can come up with a better way of maintaining libvirt connections from a stateless webapp) that your PHP frontend connects to. Or you could just steal my daemon code, although at the moment all it really does is monitoring and (as of yesterday) live migrations. What I have so far: http://trac.osuosl.org/trac/virtadmin -- Russell Haering Systems Administrator OSU Open Source Lab Radek Hladik wrote: > > Hi, > > I am developing wimple web application in PHP to monitor and control > > VMs using libvirt. I hope it could become simple library for doing basic > > things with VMs. And I would like to ask for your opinion about > > different possibilities of calling libvirt. > > > > Option 1) I am calling virsh via exec command now (one virsh for every > > libvirt command). This can be used for local libvirt but it is very > > inefficient. The overhead for remote libvirt would be unbearable. I > > could run one virsh per page and use it "interactively" so the overhead > > gets lower. > > Option 2) The other option is to create Zend extension which should be > > able to call libvirt directly from C. However I've never done anything > > like that so I do not know, whether it is reasonable or not. > > Option 3) I could also create some "wrapper daemon" in C or other > > language with libvirt binding. But I think that this is an ugly way :-) > > Option 4) I could "talk" directly to the libvirt socket. But I am not > > sure how the communication goes there and whether it is stable or > > changes with every version. And I consider the socket to be internal > > thing of libvirt... > > > > Is there any other option I missed? And which one would you suggest? > > > > Radek > > > > -- > > Libvir-list mailing list > > Libvir-list(a)redhat.com > > https://www.redhat.com/mailman/listinfo/libvir-list

1 0

[libvirt] Need help for thesis on Xen - disabling HAP for benchmarking purposes
by Alexander Sascha 25 Mar '09

25 Mar '09

Hi, I'm a German student, writing my thesis on "Virtualization with Xen. Analysis and Comparision of Different Techniques such as Paravirtualization, Full Virtualization, and Utilization of Hardware Support Provided by the Processor". I'd like to know how I can disable HAP/RVI/Nested Paging for benchmarking purposes. I read somewhere (http://markmail.org/message/bbnivuqx6vjz7jg4) that Xen developers decided to disable the global grub parameter introducing a per domain flag for HAP instead (hap=0/1). I used virt-manager built in CentOS for setting up all domUs; virt-manager uses libvirt so that no "old-style" configuration files are stored in /etc/xen. I actually don't know how if libvirt-XML-files already support something like <hap>0</hap>. How would you proceed to modify an already existing domain using libvirt/virt-manager? I really do apologize for my "newbie ignorance". Thanks in advance for any useful help. - Alex

2 1

[libvirt] [RFC]: Volume allocation progress reporting
by Cole Robinson 25 Mar '09

25 Mar '09

The attached patch implements storage volume allocation progress reporting for file volumes. Currently, the volume creation process looks like: - Grab the pool lock - Fully allocated the volume - 'define' the volume (so it shows up in 'virsh vol-list', etc) - Lookup the volume object to return - Drop the pool lock The new sequence is: - Grab the pool lock - 'define' the volume (even though nothing is on disk yet) - Drop the pool lock - Allocate the volume as needed - Regrab the pool lock - Lookup the volume object to return - Drop the pool lock (again) Since the volume is 'defined', the user can fetch an object reference in a separate thread, and continually poll the 'info' command for up to date numbers. This also has the benefit of dropping the pool lock during the potentially lengthy allocation, as currently 'virsh pool-list' etc. will block while any volume is being allocated. Non file volumes maintain existing behavior. I tried to make the implementation resistant to user error: say if the pool is deactivated or deleted while the volume is being allocated. The creation process may bail out, but I couldn't produce any bad errors (crashing). There are a few other small fixes in this patch: - Refresh volume info when doing volume dumpxml - Update volume capacity when doing a refresh I've also attached an ugly python script that can test this. Presuming you have a pool named 'default', running python sparse.py --vol-create-info Will launch an allocation, print vol.info in a loop. Feedback appreciated. Thanks, Cole import libvirt import threading import time import sys import optparse poolname = "default" volname = "nonsparsetest" testvol = "testvol" uri = "qemu:///system" testvolxml = """ <volume> <name>%s</name> <capacity>1048576000</capacity> <allocation>0</allocation> <target> <format type='raw'/> </target> </volume> """ % testvol volxml = """ <volume> <name>%s</name> <capacity>1048576000</capacity> <allocation>800000000</allocation> <target> <format type='raw'/> </target> </volume> """ % volname failvol = """ <volume> <name>%s</name> <capacity>1048576000</capacity> <allocation>1048576000</allocation> <target> <format type='bochs'/> </target> </volume> """ % volname poolxml = """ <pool type='dir'> <name>default</name> <target> <path>/var/lib/libvirt/images</path> </target> </pool> """ # Helper functions def exception_wrapper(cmd, args): try: cmd(*args) except Exception, e: print str(e) def make_test_vol(): pool = get_pool() pool.createXML(testvolxml, 0) def del_vol(name=volname): pool = get_pool() vol = pool.storageVolLookupByName(name) vol.delete(0) def del_pool(): pool = get_pool() pool.destroy() pool.undefine() def define_pool(): conn = libvirt.open(uri) pool = conn.storagePoolDefineXML(poolxml, 0) pool.create(0) pool.setAutostart(True) def allocate_thread(xml=volxml): try: del_vol() except: pass pool = get_pool() print "creating vol in thread" vol = pool.createXML(xml, 0) print "creating vol complete." def info_thread(vol): for i in range(0, 40): time.sleep(.5) print vol.info() def get_pool(name=poolname): conn = libvirt.open(uri) return conn.storagePoolLookupByName(name) def get_vol(name=volname): pool = get_pool() return pool.storageVolLookupByName(name) def cmd_vol_create(xml=volxml): exception_wrapper(define_pool, ()) pool = get_pool() print pool.listVolumes() t = threading.Thread(target=allocate_thread, name="Allocating", args=(xml,)) t.start() time.sleep(5) print "\nRefreshing pool and dumping list" pool.refresh(0) print pool.listVolumes() def cmd_vol_fail(): cmd_vol_create(failvol) def cmd_vol_poll(): cmd_vol_create() vol = get_vol() t = threading.Thread(target=info_thread, name="Getting info", args=(vol,)) t.start() def main(): import optparse parser = optparse.OptionParser() parser.add_option("", "--vol-create", action="store_true", dest="vol_create", help="Create a volume nonsparse volume that should " "succeed") parser.add_option("", "--vol-create-info", action="store_true", dest="vol_create_info", help="Create a volume nonsparse volume that should " "succeed, and list info in a loop") parser.add_option("", "--vol-create-fail", action="store_true", dest="vol_fail", help="Create a volume that will fail at the allocate " "stage") options, ignore = parser.parse_args() if options.vol_create: cmd_vol_create() elif options.vol_create_info: cmd_vol_poll() elif options.vol_fail: cmd_vol_fail() else: parser.print_help() sys.exit(1) if __name__ == "__main__": main()

2 2

[libvirt] first cut public API for physical host interface configuration
by Laine Stump 25 Mar '09

25 Mar '09

To get started integrating libnetcf support into libvirt, the attached libvirt.h diff has a first attempt at the public API that will hook up to libnetcf on the libvirtd side. I started out with the virNetwork* API, and modified/removed as seemed appropriate. A few points worth mentioning: virNetwork has "defined" and "active" interfaces, but so far virInterface just has interfaces, as the active/inactive status is really controlled by 1) the "onboot" property in the XML, and 2) whether or not virInterfaceStart() has been called yet. The _virInterface struct that is referenced here is more or less identical to _virnetwork. libnetcf works with netcf structs (one per library instance) and netcf_if structs (one per interface, multiple per library instance. As far as I can see right now, the netcf struct will not need to be referenced directly from the client side, but the netcf_if for each interface is needed, and I guess a cookie representing it will be sent to the client side and stored in the _virInterface. Is that what the UUID in _virNetwork is used for? (I know, I know - "read the code!", it's just quicker to (and avoids misreading on my part) to ask) As before, any and all advice/corrections gratefully accepted! diff --git a/include/libvirt/libvirt.h b/include/libvirt/libvirt.h index 779ea72..cac400e 100644 --- a/include/libvirt/libvirt.h +++ b/include/libvirt/libvirt.h @@ -854,7 +854,73 @@ int virNetworkGetAutostart (virNetworkPtr network, int virNetworkSetAutostart (virNetworkPtr network, int autostart); +/* + * Physical host interface configuration API + */ + +/** + * virInterface: + * + * a virInterface is a private structure representing a virtual interface. + */ +typedef struct _virInterface virInterface; + +/** + * virInterfacePtr: + * + * a virInterfacePtr is pointer to a virInterface private structure, this is the + * type used to reference a virtual interface in the API. + */ +typedef virInterface *virInterfacePtr; + +/* + * Get connection from interface. + */ +virConnectPtr virInterfaceGetConnect (virInterfacePtr interface); + +/* + * List defined interfaces + */ +int virConnectNumOfInterfaces (virConnectPtr conn); +int virConnectListInterfaces (virConnectPtr conn, + char **const names, + int maxnames); + +/* + * Lookup interface by name + */ +virInterfacePtr virInterfaceLookupByName (virConnectPtr conn, + const char *name); + const char *uuid); + +/* + * Define interface (or modify existing interface configuration) + */ +virInterfacePtr virInterfaceDefineXML (virConnectPtr conn, + const char *xmlDesc); + +/* + * Delete interface + */ +int virInterfaceUndefine (virInterfacePtr interface); + +/* + * Activate interface (ie call "ifup") + */ +int virInterfaceStart (virInterfacePtr interface); + +/* + * De-activate interface (call "ifdown") + */ +int virInterfaceStop (virInterfacePtr interface); + +/* + * Interface information + */ +const char* virInterfaceGetName (virInterfacePtr interface); +char * virInterfaceGetXMLDesc (virInterfacePtr interface, + int flags); /** * virStoragePool: *

1 0