- Devel - libvirt List Archives

[libvirt] PATCH: Clear reference after closing connection object
by Daniel P. Berrange 01 Apr '09

01 Apr '09

In the python bindings, if you call close() it will close the connection and release the handle, but it doesn't clear the python reference to the C object - self._o. So later in garbage colection __del__ runs and tries to free the already free'd object Daniel diff -r a76dc8c27d72 python/generator.py --- a/python/generator.py Tue Mar 31 12:36:02 2009 +0100 +++ b/python/generator.py Tue Mar 31 13:09:38 2009 +0100 @@ -1072,6 +1072,9 @@ def buildWrappers(): n = n + 1 classes.write(")\n"); + if name == "virConnectClose": + classes.write(" self._o = None\n") + # For functions returning object types: if ret[0] != "void": if classes_type.has_key(ret[0]): -- |: 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 :|

2 2

[libvirt] PATCH: Fix duplicate methods in python binding
by Daniel P. Berrange 01 Apr '09

01 Apr '09

There are three methods with the same name in the python binding due to a generator bug. This patch fixes them, so we get methods networkCreateXML() and storagePoolCreateXML() instad of three called createXML() Daniel diff -r e26692afef21 python/generator.py --- a/python/generator.py Tue Mar 31 12:26:01 2009 +0100 +++ b/python/generator.py Tue Mar 31 12:36:02 2009 +0100 @@ -684,12 +684,18 @@ def nameFixup(name, classe, type, file): elif name[0:16] == "virNetworkDefine": func = name[3:] func = string.lower(func[0:1]) + func[1:] + elif name[0:19] == "virNetworkCreateXML": + func = name[3:] + func = string.lower(func[0:1]) + func[1:] elif name[0:16] == "virNetworkLookup": func = name[3:] func = string.lower(func[0:1]) + func[1:] elif name[0:20] == "virStoragePoolDefine": func = name[3:] func = string.lower(func[0:1]) + func[1:] + elif name[0:23] == "virStoragePoolCreateXML": + func = name[3:] + func = string.lower(func[0:1]) + func[1:] elif name[0:20] == "virStoragePoolLookup": func = name[3:] func = string.lower(func[0:1]) + func[1:] -- |: 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 :|

2 2

[libvirt] f11 virt release notes freezing
by Dale Bewley 01 Apr '09

01 Apr '09

I've been busy at my day job and not paying close enough attention to Fedora 11 docs deadlines. Apparently the window for changes essentially closes Wednesday (today).[1] The notes are essentially in place. I don't think there are any gaping holes, but I should have prompted for feedback much sooner. If you could apply any love to the release notes[2] it would be appreciated. = QEMU / KVM = It is noted that QEMU and KVM are merging as a package, but I've also separately listed the fact that QEMU is now 0.10.0 and KVM is now 84. With the merge, might it be confusing or inaccurate to mention a distinct new version of KVM? I'll admit to being somewhat fuzzy on where/how that line is drawn. I see[3] QEMU 0.10.0 in rawhide, but not 0.10.1, so I adjusted the version in the relnotes. I copied the feature list from the 0.10.0 release announcement. If you'd care to suggest deletes or enhancements of the list please do. The KVM changelog since 74 (version at initial F10 release) is quite long and not easily digestible by me at this late hour. Would anyone care to offer some highlights or fill them into the wiki? Or, again, should those be folded into QEMU? = Libvirt = I previously copied the list of changes from the releases, but did not try to prune them down. It may be fine. = The Current Outline = 1 Virtualization * 1.1 Improved VNC Authentication for Virtual Machine Management * 1.2 Improved Graphical Console for Virtual Machines * 1.3 KVM PCI Device Assignment * 1.4 KVM and QEMU merge * 1.5 SVirt Mandatory Access Control * 1.6 Other Improvements * 1.6.1 QEMU Updated to 0.10.0 * 1.6.2 KVM Updated to 84 * 1.6.3 libvirt Updated to 0.6.1 * 1.6.4 virt-manager Updated to 0.7.0 * 1.6.5 virtinst Updated to 0.400.3 * 1.6.6 Xen Updated to 3.3.1 * 1.7 Xen Kernel Support Thanks for any edits or suggestions you can offer. [1] http://www.redhat.com/archives/fedora-docs-list/2009-March/msg00232.html [2] http://fedoraproject.org/wiki/Documentation_Virtualization_Beat [3] http://fedoraproject.org/wiki/User:Dale#Packages

1 0

[libvirt] [Fwd: first cut public API for physical host interface configuration]
by Laine Stump 01 Apr '09

01 Apr '09

(Oops, I originally sent this with the wrong return address, which probably caused it to be silently swallowed...) 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: *

4 10

[libvirt] [PATCH 2/2]: Remove getURI internal driver call
by Chris Lalancette 01 Apr '09

01 Apr '09

This patch removes the internal getURI() driver callback. It was *never* overridden by any of the drivers, so it seems kind of pointless (I even checked the "in-progress" VirtualBox, OpenNebula, and Power Hypervisor drivers). In addition, the code to actually use it in src/libvirt.c:virConnectGetURI() was buggy; if a driver did decide to have their own callback, then their callback would be called, and then immediately overwritten by the generic stuff. This wouldn't do what the driver expected, and would also probably leak memory. Just rip out this internal callback; if a future driver ever needs it, we can add it back in. Signed-off-by: Chris Lalancette <clalance(a)redhat.com>

3 3

[libvirt] [PATCH 1/2]: Convert internal drivers to old style struct initializers
by Chris Lalancette 01 Apr '09

01 Apr '09

This patch converts the internal drivers to use the old-style struct initializers, which kind of gives us a self-documenting TODO list for each of the drivers. It also fixes up some bad comments in the internal driver list. It does not touch the storage or network driver initializers. Signed-off-by: Chris Lalancette <clalance(a)redhat.com>

3 3

[libvirt] [PATCH] additional options in the spec file for storage drivers and numactl
by Ryota Ozaki 31 Mar '09

31 Mar '09

Hi, This patch adds switches in the spec file for storage drivers and numactl to be easy to turn on/off options of configure. Thanks, ozaki-r Signed-off-by: Ryota Ozaki <ozaki.ryota(a)gmail.com>

3 2

[libvirt] [PATCH] prevent an executed external process to be a zombie
by Ryota Ozaki 31 Mar '09

31 Mar '09

Hi, This patch prevents an executed external process to be a zombie by doing waitpid() even if virPipeReadUntilEOF() fails. Thanks, ozaki-r Signed-off-by: Ryota Ozaki <ozaki.ryota(a)gmail.com>

3 3

[libvirt] Patch to allow setting of svirt XML.
by Daniel J Walsh 31 Mar '09

31 Mar '09

This patch fixes the seclabel handling in domain_conf.c to allow virt-manager to set the seclabel model, type and label. Also adds missing error messages when the xml is incorrect. How much verification should we be doing on this? I have another patch that verifies the model as being a known model and a patch to verify the label is a correct label. (IE SELinux verifies the label is understood by the kernel.) The problem with this second patch is it sucks in security.[ch], security_selinux.[ch] into the libvirt_lxc. Should I be doing this?

2 3

[libvirt] Upcoming 0.6.2 release
by Daniel Veillard 31 Mar '09

31 Mar '09

I would like to make a new release mid or end of next week, considering the number of fixes accumulated in CVS compared to 0.6.1, I guess 0.6.2 makes sense. I think we should look at integrating the new SCSI pool patch, hopefully there is no big issues. If there are mails or patchs which are pending and we forgot to review or ACK, please raise them again so that we can try to get them in time for next release, thanks, Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel(a)veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/

4 4