- Devel - libvirt List Archives

[libvirt] Looking for good example API function(s)
by Laine Stump 11 Mar '09

11 Mar '09

To help with lutter's network configuration project, I'm looking at adding API functions to libvirt which are essentially pass-throughs to netcf library APIs called by libvirtd. Can someone point me to good examples of APIs that are not hypervisor driver-dependent (and possibly not host OS-dependent either - I believe the final intent is for netcf to handle all host OS dependencies itself) to use as a basis for writing these new APIs? At a more detailed level, a quick trace through the code of some other APIs got me as far as the call to the "call" function, with an RPC code, but I didn't find where that call was caught (and the RPC code interpreted, eg REMOTE_PROC_NETWORK_CREATE_XML - cscope couldn't find any other reference to this value) on the libvirtd side. I'm about run virsh and libvirtd under gdb to learn this by experimentation, but if someone wants to take the fun out of it for me, hints would be gladly accepted! ;-)

4 3

[libvirt] PATCH: Support SASL auth for QEMU VNC servers
by Daniel P. Berrange 11 Mar '09

11 Mar '09

This patch adds a config option to /etc/libvirt/qemu.conf to allow the enablement of SASL authentication of the QEMU VNC servers. The patches to QEMU are posted upstream, and though their merge is delayed while the QEMU release is sorted out, I expect them to be merged in a week or so. I'm posting this patch for review now, though best not to commit it to CVS until the QEMU stuff is finally merged. Daniel diff -r 961d4b1ca1d3 qemud/libvirtd_qemu.aug --- a/qemud/libvirtd_qemu.aug Wed Mar 04 13:17:44 2009 +0000 +++ b/qemud/libvirtd_qemu.aug Thu Mar 05 14:22:50 2009 +0000 @@ -27,6 +27,8 @@ module Libvirtd_qemu = | str_entry "vnc_tls_x509_cert_dir" | bool_entry "vnc_tls_x509_verify" | str_entry "vnc_password" + | bool_entry "vnc_sasl" + | str_entry "vnc_sasl_dir" (* Each enty in the config is one of the following three ... *) let entry = vnc_entry diff -r 961d4b1ca1d3 qemud/test_libvirtd_qemu.aug --- a/qemud/test_libvirtd_qemu.aug Wed Mar 04 13:17:44 2009 +0000 +++ b/qemud/test_libvirtd_qemu.aug Thu Mar 05 14:22:50 2009 +0000 @@ -60,6 +60,25 @@ vnc_tls_x509_verify = 1 # example here before you set this # vnc_password = \"XYZ12345\" + + +# Enable use of SASL encryption on the VNC server. This requires +# a VNC client which supports the SASL protocol extension. +# Examples include vinagre, virt-viewer and virt-manager +# itself. UltraVNC, RealVNC, TightVNC do not support this +# +# It is necessary to configure /etc/sasl2/qemu.conf to choose +# the desired SASL plugin (eg, GSSPI for Kerberos) +# +vnc_sasl = 1 + + +# The default SASL configuration file is located in /etc/sasl2/ +# When running libvirtd unprivileged, it may be desirable to +# override the configs in this location. Set this parameter to +# point to the directory, and create a qemu.conf in that location +# +vnc_sasl_dir = \"/some/directory/sasl2\" " test Libvirtd_qemu.lns get conf = @@ -123,3 +142,22 @@ vnc_password = \"XYZ12345\" { "#comment" = "example here before you set this" } { "#comment" = "" } { "vnc_password" = "XYZ12345" } +{ "#empty" } +{ "#empty" } +{ "#comment" = "Enable use of SASL encryption on the VNC server. This requires" } +{ "#comment" = "a VNC client which supports the SASL protocol extension." } +{ "#comment" = "Examples include vinagre, virt-viewer and virt-manager" } +{ "#comment" = "itself. UltraVNC, RealVNC, TightVNC do not support this" } +{ "#comment" = "" } +{ "#comment" = "It is necessary to configure /etc/sasl2/qemu.conf to choose" } +{ "#comment" = "the desired SASL plugin (eg, GSSPI for Kerberos)" } +{ "#comment" = "" } +{ "vnc_sasl" = "1" } +{ "#empty" } +{ "#empty" } +{ "#comment" = "The default SASL configuration file is located in /etc/sasl2/" } +{ "#comment" = "When running libvirtd unprivileged, it may be desirable to" } +{ "#comment" = "override the configs in this location. Set this parameter to" } +{ "#comment" = "point to the directory, and create a qemu.conf in that location" } +{ "#comment" = "" } +{ "vnc_sasl_dir" = "/some/directory/sasl2" } diff -r 961d4b1ca1d3 src/qemu.conf --- a/src/qemu.conf Wed Mar 04 13:17:44 2009 +0000 +++ b/src/qemu.conf Thu Mar 05 14:22:50 2009 +0000 @@ -60,6 +60,27 @@ # vnc_password = "XYZ12345" +# Enable use of SASL encryption on the VNC server. This requires +# a VNC client which supports the SASL protocol extension. +# Examples include vinagre, virt-viewer and virt-manager +# itself. UltraVNC, RealVNC, TightVNC do not support this +# +# It is necessary to configure /etc/sasl2/qemu.conf to choose +# the desired SASL plugin (eg, GSSPI for Kerberos) +# +# vnc_sasl = 1 + + +# The default SASL configuration file is located in /etc/sasl2/ +# When running libvirtd unprivileged, it may be desirable to +# override the configs in this location. Set this parameter to +# point to the directory, and create a qemu.conf in that location +# +# vnc_sasl_dir = "/some/directory/sasl2" + + + + # The default security driver is SELinux. If SELinux is disabled # on the host, then the security driver will automatically disable # itself. If you wish to disable QEMU SELinux security driver while diff -r 961d4b1ca1d3 src/qemu_conf.c --- a/src/qemu_conf.c Wed Mar 04 13:17:44 2009 +0000 +++ b/src/qemu_conf.c Thu Mar 05 14:22:50 2009 +0000 @@ -161,6 +161,21 @@ int qemudLoadDriverConfig(struct qemud_d } } + p = virConfGetValue (conf, "vnc_sasl"); + CHECK_TYPE ("vnc_sasl", VIR_CONF_LONG); + if (p) driver->vncSASL = p->l; + + p = virConfGetValue (conf, "vnc_sasl_dir"); + CHECK_TYPE ("vnc_sasl_dir", VIR_CONF_STRING); + if (p && p->str) { + VIR_FREE(driver->vncSASLdir); + if (!(driver->vncSASLdir = strdup(p->str))) { + virReportOOMError(NULL); + virConfFree(conf); + return -1; + } + } + virConfFree (conf); return 0; } @@ -838,15 +853,20 @@ int qemudBuildCommandLine(virConnectPtr goto no_memory; \ } while (0) +#define ADD_ENV_PAIR(envname, val) \ + do { \ + char *envval; \ + ADD_ENV_SPACE; \ + if (virAsprintf(&envval, "%s=%s", envname, val) < 0) \ + goto no_memory; \ + qenv[qenvc++] = envval; \ + } while (0) + #define ADD_ENV_COPY(envname) \ do { \ char *val = getenv(envname); \ - char *envval; \ - ADD_ENV_SPACE; \ if (val != NULL) { \ - if (virAsprintf(&envval, "%s=%s", envname, val) < 0) \ - goto no_memory; \ - qenv[qenvc++] = envval; \ + ADD_ENV_PAIR(envname, val); \ } \ } while (0) @@ -1295,6 +1315,15 @@ int qemudBuildCommandLine(virConnectPtr driver->vncTLSx509certdir); } } + + if (driver->vncSASL) { + virBufferAddLit(&opt, ",sasl"); + + if (driver->vncSASLdir) + ADD_ENV_PAIR("SASL_CONF_DIR", driver->vncSASLdir); + + /* TODO: Support ACLs later */ + } } else { virBufferVSprintf(&opt, "%d", vm->def->graphics->data.vnc.port - 5900); diff -r 961d4b1ca1d3 src/qemu_conf.h --- a/src/qemu_conf.h Wed Mar 04 13:17:44 2009 +0000 +++ b/src/qemu_conf.h Thu Mar 05 14:22:50 2009 +0000 @@ -73,9 +73,11 @@ struct qemud_driver { char *stateDir; unsigned int vncTLS : 1; unsigned int vncTLSx509verify : 1; + unsigned int vncSASL : 1; char *vncTLSx509certdir; char *vncListen; char *vncPassword; + char *vncSASLdir; virCapsPtr caps; diff -r 961d4b1ca1d3 src/qemu_driver.c --- a/src/qemu_driver.c Wed Mar 04 13:17:44 2009 +0000 +++ b/src/qemu_driver.c Thu Mar 05 14:22:50 2009 +0000 @@ -620,6 +620,7 @@ qemudShutdown(void) { VIR_FREE(qemu_driver->vncTLSx509certdir); VIR_FREE(qemu_driver->vncListen); VIR_FREE(qemu_driver->vncPassword); + VIR_FREE(qemu_driver->vncSASLdir); /* Free domain callback list */ virDomainEventCallbackListFree(qemu_driver->domainEventCallbacks); diff -r 961d4b1ca1d3 tests/qemuxml2argvdata/qemuxml2argv-graphics-vnc-sasl.args --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tests/qemuxml2argvdata/qemuxml2argv-graphics-vnc-sasl.args Thu Mar 05 14:22:50 2009 +0000 @@ -0,0 +1,1 @@ +LC_ALL=C PATH=/bin HOME=/home/test USER=test LOGNAME=test SASL_CONF_DIR=/root/.sasl2 /usr/bin/qemu -S -M pc -m 214 -smp 1 -monitor pty -pidfile /nowhere/QEMUGuest1.pid -no-acpi -boot c -hda /dev/HostVG/QEMUGuest1 -net none -serial none -parallel none -usb -vnc 127.0.0.1:3,sasl diff -r 961d4b1ca1d3 tests/qemuxml2argvdata/qemuxml2argv-graphics-vnc-sasl.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tests/qemuxml2argvdata/qemuxml2argv-graphics-vnc-sasl.xml Thu Mar 05 14:22:50 2009 +0000 @@ -0,0 +1,24 @@ +<domain type='qemu'> + <name>QEMUGuest1</name> + <uuid>c7a5fdbd-edaf-9455-926a-d65c16db1809</uuid> + <memory>219200</memory> + <currentMemory>219200</currentMemory> + <vcpu>1</vcpu> + <os> + <type arch='i686' machine='pc'>hvm</type> + <boot dev='hd'/> + </os> + <clock offset='utc'/> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>destroy</on_crash> + <devices> + <emulator>/usr/bin/qemu</emulator> + <disk type='block' device='disk'> + <source dev='/dev/HostVG/QEMUGuest1'/> + <target dev='hda' bus='ide'/> + </disk> + <input type='mouse' bus='ps2'/> + <graphics type='vnc' port='5903' autoport='no' listen='127.0.0.1'/> + </devices> +</domain> diff -r 961d4b1ca1d3 tests/qemuxml2argvdata/qemuxml2argv-graphics-vnc-tls.args --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tests/qemuxml2argvdata/qemuxml2argv-graphics-vnc-tls.args Thu Mar 05 14:22:50 2009 +0000 @@ -0,0 +1,1 @@ +LC_ALL=C PATH=/bin HOME=/home/test USER=test LOGNAME=test SASL_CONF_DIR=/root/.sasl2 /usr/bin/qemu -S -M pc -m 214 -smp 1 -monitor pty -pidfile /nowhere/QEMUGuest1.pid -no-acpi -boot c -hda /dev/HostVG/QEMUGuest1 -net none -serial none -parallel none -usb -vnc 127.0.0.1:3,tls,x509verify=/etc/pki/tls/qemu,sasl diff -r 961d4b1ca1d3 tests/qemuxml2argvdata/qemuxml2argv-graphics-vnc-tls.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tests/qemuxml2argvdata/qemuxml2argv-graphics-vnc-tls.xml Thu Mar 05 14:22:50 2009 +0000 @@ -0,0 +1,24 @@ +<domain type='qemu'> + <name>QEMUGuest1</name> + <uuid>c7a5fdbd-edaf-9455-926a-d65c16db1809</uuid> + <memory>219200</memory> + <currentMemory>219200</currentMemory> + <vcpu>1</vcpu> + <os> + <type arch='i686' machine='pc'>hvm</type> + <boot dev='hd'/> + </os> + <clock offset='utc'/> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>destroy</on_crash> + <devices> + <emulator>/usr/bin/qemu</emulator> + <disk type='block' device='disk'> + <source dev='/dev/HostVG/QEMUGuest1'/> + <target dev='hda' bus='ide'/> + </disk> + <input type='mouse' bus='ps2'/> + <graphics type='vnc' port='5903' autoport='no' listen='127.0.0.1'/> + </devices> +</domain> diff -r 961d4b1ca1d3 tests/qemuxml2argvtest.c --- a/tests/qemuxml2argvtest.c Wed Mar 04 13:17:44 2009 +0000 +++ b/tests/qemuxml2argvtest.c Thu Mar 05 14:22:50 2009 +0000 @@ -213,6 +213,19 @@ mymain(int argc, char **argv) QEMUD_CMD_FLAG_DRIVE_CACHE_V2); DO_TEST("disk-usb", 0); DO_TEST("graphics-vnc", 0); + + driver.vncSASL = 1; + driver.vncSASLdir = strdup("/root/.sasl2"); + DO_TEST("graphics-vnc-sasl", 0); + driver.vncTLS = 1; + driver.vncTLSx509verify = 1; + driver.vncTLSx509certdir = strdup("/etc/pki/tls/qemu"); + DO_TEST("graphics-vnc-tls", 0); + driver.vncSASL = driver.vncTLSx509verify = driver.vncTLS = 0; + free(driver.vncSASLdir); + free(driver.vncTLSx509certdir); + driver.vncSASLdir = driver.vncTLSx509certdir = NULL; + DO_TEST("graphics-sdl", 0); DO_TEST("graphics-sdl-fullscreen", 0); DO_TEST("input-usbmouse", 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 0/4] checkpoint functionality
by Matt McCowan 11 Mar '09

11 Mar '09

OK. Another run at producing a function that helps the likes of me backup my kvm Windows servers. 'virsh checkpoint domain file [script]' is what the following patch set (against cvs) enables. Modelled on the virDomainSave function it takes an optional script which it will execute (and pass the name of the domain as an argument) while the domain is paused, then resume the domain. By the by stability is coming along nicely since 0.6.0. Thanks! Matt McCowan

4 5

[libvirt] [PATCH] storage: fix disregarding specified owner/group permissions
by Ryota Ozaki 11 Mar '09

11 Mar '09

Hi, storage_conf.c always sets owner/group permissions as 0, even if non-0 values are specified in XML. Because XPaths in DefParsePerms functions are wrong and XPath functions using the XPaths fail, as a result the values obtained by getpid()/getgid() are used instead. This patch fixes this and also unifies duplicated functions, virStoragePoolDefParsePerms and virStorageVolDefParsePerms, as a common function virStorageDefParsePerms to fix the bug prettily. One concern I have is the default value of mode permission in virStorageDefParsePerms is now 0700 but that in virStorageVolDefParsePerms was 0600. Is this considerable change? Thanks, ozaki-r

2 2

[libvirt] PATCH: Fix hang setting QEMU vcpu count
by Daniel P. Berrange 10 Mar '09

10 Mar '09

In the QEMu driver, the qemudDomainSetVcpus() entry point is calling into another entry point qemudDomainGetMaxVcpus(), this causes a deadlock due to recursive mutex locking. The qemudDomainSetVcpus() method should in fact be calling the internal method qemudGetMaxVCPUs(). This patch makes it do that, thus avoiding the recursive mutex locking. Daniel diff -r 6d2500176f31 src/qemu_driver.c --- a/src/qemu_driver.c Tue Mar 10 11:05:49 2009 +0000 +++ b/src/qemu_driver.c Tue Mar 10 12:09:41 2009 +0000 @@ -2725,6 +2725,7 @@ static int qemudDomainSetVcpus(virDomain virDomainObjPtr vm; int max; int ret = -1; + const char *type; qemuDriverLock(driver); vm = virDomainFindByUUID(&driver->domains, dom->uuid); @@ -2745,7 +2746,14 @@ static int qemudDomainSetVcpus(virDomain goto cleanup; } - if ((max = qemudDomainGetMaxVcpus(dom)) < 0) { + if (!(type = virDomainVirtTypeToString(vm->def->virtType))) { + qemudReportError(dom->conn, dom, NULL, VIR_ERR_INTERNAL_ERROR, + _("unknown virt type in domain definition '%d'"), + vm->def->virtType); + goto cleanup; + } + + if ((max = qemudGetMaxVCPUs(dom->conn, type)) < 0) { qemudReportError(dom->conn, dom, NULL, VIR_ERR_INTERNAL_ERROR, "%s", _("could not determine max vcpus for the domain")); goto cleanup; -- |: 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 1

[libvirt] some questions about libvirt features and limitations
by Florian Vichot 10 Mar '09

10 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone, I'm working on a open source project (http://www.hynesim.org) in which we needed libvirt-like functionalities. As at the time, libvirt did not support OpenVZ, and it did not support VirtualBox, we went and implemented our own wrappers around Kvm/Qemu, VirtualBox and OpenVz (Honeyd too, but our wrapper is such an ugly hack that it doesn't really deserve mention). Now that time has passed, we'd would like to stop duplicating efforts, and use libvirt instead, and concentrate on more innovating functionalities for Hynesim. Also our wrappers are terrible hacks, and do a lot less error checking than libvirt :) But before I can replace our wrappers with libvirt, we're missing some functionalities (that I will propose a patch for if required), and there are a few questions concerning libvirt I've not managed to find an answer for, so I'd be very grateful if I could get some advice on them. Here goes: ------- Is it possible to add a device for any type of domain that would correspond to a TAP device on the host, and would be seen as a regular ethernet interface with a specific MAC address in the virtualized domain ? The "raw" commands to achieve that in OpenVZ and Qemu, for example, are: # kvm ... -net nic,macaddr=00:11:22:33:44:55 -net tap,ifname=tap0,script=no # vzctl set 100 --netif_add eth0,00:11:22:33:44:55,tap0 Is that doable in every driver supported by libvirt ? ------- Is the libvirtd daemon necessary for drivers other than Qemu ? I've been using the openvz driver alone for some tests (by connecting to "openvz:///system"), and yet I get warning messages: # sudo ./hellolibvirt openvz:///system Attempting to connect to hypervisor libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory libvir: warning : Failed to find the network: Is the daemon running ? libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory libvir: warning : Failed to find a node driver: Is the libvirtd daemon running ? Connected to hypervisor at "openvz:///system" Hypervisor: "OpenVZ" version: 3.0.22 There are 0 active and 1 inactive domains Inactive domains: 897 Disconnected from hypervisor The libvirtd daemon is indeed not running, as I don't see why it should be: I thought it was only useful for qemu guests. Am I right ? What is the role of the daemon exactly ? ------- Apparently the only way to start an OpenVZ domain is by specifying a template. Only problem is, when the VE is stopped, and undefined, all modifications are lost in the "private" file system of the VE (as it is deleted). The way we circumvented this in Hynesim is by specifying the - --private option to "vzctl create" instead of the --ostemplate one. That way one can specify a dir that will be used directly as the filesystem for the VE. I was thinking maybe adding something along the lines of: <filesystem type='directory'> <source name='/path/to/ve/filesystem' /> <target dir='/'/> </filesystem> would do the trick. It looks simple enough to implement, so should I ? ------- Is there support in libvirt of "cloning" (duplicating a VM disk /filesystem) ? ------- Someone mentioned a VirtualBox driver. I'm highly interested in this. How is it going ? I'd be more than happy to beta test if required. Will it work with both PUEL and OSE versions ? When will it be ready for inclusion in libvirt ? How will you handle RDP access, as from what I saw only VNC is supported in libvirt currently ? ------- And last but not least, what are "node devices" ? The two pages about it are blank in the documentation. Are they the host machine, or a device of the host machine ? ------- I think that's all. Thank you for reading all this, Florian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmtcBwACgkQgRp+dNkqn68FjQCcDhoy0YuhUM37iRc2cbyDdh1N hE8AoKSAhoZJ7cSQ8zWSXr9XiOytTuLK =LSi9 -----END PGP SIGNATURE-----

3 10

[libvirt] Error in virt-install
by Nuno Fernandes 10 Mar '09

10 Mar '09

Hi, I've just installed an centos 5.2 with all the updates 'till now. Next i've tried the following install script that worked fine: virt-install -n test -r 512 --vnc --file=/dev/VolGroup00/test-os -- location=ftp://mirrors/centos/5/os/i386 -x 'text' Next i've rebuild rpm of libvirt to libvirt-0.6.1 (using --with-rhel5-api). The rpm build fine and installed without any errors. Next i've retried the virt-install script but i get the following error: [root@localhost ~]# virt-install -n test -r 512 --vnc -- file=/dev/VolGroup00/test-os --location=ftp://mirrors/centos/5/os/i386 -x 'text' Starting install... *** glibc detected *** /usr/bin/python: free(): invalid next size (fast): 0x0936a1b8 *** ======= Backtrace: ========= /lib/i686/nosegneg/libc.so.6[0x1e0906] /lib/i686/nosegneg/libc.so.6(cfree+0x90)[0x1e3e30] /usr/lib/libvirt.so.0(virFree+0x24)[0x8eb4e4] /usr/lib/libvirt.so.0[0x94793c] /usr/lib/libvirt.so.0[0x93abf1] /usr/lib/libvirt.so.0(virDomainLookupByUUID+0xb7)[0x8fda77] /usr/lib/libvirt.so.0(virDomainLookupByUUIDString+0x17f)[0x8ffbaf] /usr/lib/python2.4/site- packages/libvirtmod.so(libvirt_virDomainLookupByUUIDString+0x6d)[0xfa349d] /usr/lib/libpython2.4.so.1.0(PyCFunction_Call+0x14d)[0x67249d] /usr/lib/libpython2.4.so.1.0(PyEval_EvalFrame+0x498d)[0x6ac9cd] /usr/lib/libpython2.4.so.1.0(PyEval_EvalFrame+0x44ff)[0x6ac53f] /usr/lib/libpython2.4.so.1.0(PyEval_EvalFrame+0x44ff)[0x6ac53f] /usr/lib/libpython2.4.so.1.0(PyEval_EvalCodeEx+0x896)[0x6adc76] /usr/lib/libpython2.4.so.1.0[0x65fcba] /usr/lib/libpython2.4.so.1.0(PyObject_Call+0x37)[0x647d87] /usr/lib/libpython2.4.so.1.0[0x64e388] /usr/lib/libpython2.4.so.1.0(PyObject_Call+0x37)[0x647d87] /usr/lib/libpython2.4.so.1.0(PyEval_EvalFrame+0x2518)[0x6aa558] /usr/lib/libpython2.4.so.1.0(PyEval_EvalFrame+0x44ff)[0x6ac53f] /usr/lib/libpython2.4.so.1.0(PyEval_EvalCodeEx+0x896)[0x6adc76] /usr/lib/libpython2.4.so.1.0(PyEval_EvalFrame+0x43f6)[0x6ac436] /usr/lib/libpython2.4.so.1.0(PyEval_EvalCodeEx+0x896)[0x6adc76] /usr/lib/libpython2.4.so.1.0(PyEval_EvalFrame+0x43f6)[0x6ac436] /usr/lib/libpython2.4.so.1.0(PyEval_EvalCodeEx+0x896)[0x6adc76] /usr/lib/libpython2.4.so.1.0(PyEval_EvalCode+0x63)[0x6add03] /usr/lib/libpython2.4.so.1.0[0x6caad8] /usr/lib/libpython2.4.so.1.0(PyRun_SimpleFileExFlags+0x198)[0x6cc1e8] /usr/lib/libpython2.4.so.1.0(PyRun_AnyFileExFlags+0x7a)[0x6cc8ca] /usr/lib/libpython2.4.so.1.0(Py_Main+0xb85)[0x6d32d5] /usr/bin/python(main+0x32)[0x80485b2] /lib/i686/nosegneg/libc.so.6(__libc_start_main+0xdc)[0x18cdec] /usr/bin/python[0x80484c1] ======= Memory map: ======== 00110000-00112000 r-xp 00000000 fd:00 393272 /lib/libutil-2.5.so 00112000-00113000 r-xp 00001000 fd:00 393272 /lib/libutil-2.5.so 00113000-00114000 rwxp 00002000 fd:00 393272 /lib/libutil-2.5.so 00114000-00117000 r-xp 00000000 fd:00 1835042 /usr/lib/python2.4/lib- dynload/fcntlmodule.so 00117000-00118000 rwxp 00003000 fd:00 1835042 /usr/lib/python2.4/lib- dynload/fcntlmodule.so 00118000-0011b000 r-xp 00000000 fd:00 1835035 /usr/lib/python2.4/lib- dynload/cStringIO.so 0011b000-0011c000 rwxp 00003000 fd:00 1835035 /usr/lib/python2.4/lib- dynload/cStringIO.so 0011c000-0011f000 r-xp 00000000 fd:00 1835067 /usr/lib/python2.4/lib- dynload/timemodule.so 0011f000-00121000 rwxp 00002000 fd:00 1835067 /usr/lib/python2.4/lib- dynload/timemodule.so 00121000-00125000 r-xp 00000000 fd:00 1835037 /usr/lib/python2.4/lib- dynload/collectionsmodule.so 00125000-00126000 rwxp 00003000 fd:00 1835037 /usr/lib/python2.4/lib- dynload/collectionsmodule.so 00126000-0016c000 r-xp 00000000 fd:00 1835465 /usr/lib/python2.4/site- packages/libxml2mod.so 0016c000-00171000 rwxp 00046000 fd:00 1835465 /usr/lib/python2.4/site- packages/libxml2mod.so 00172000-00175000 r-xp 00000000 fd:00 1835023 /usr/lib/python2.4/lib- dynload/_localemodule.so 00175000-00176000 rwxp 00003000 fd:00 1835023 /usr/lib/python2.4/lib- dynload/_localemodule.so 00176000-00177000 r-xp 00176000 00:00 0 [vdso] 00177000-002b7000 r-xp 00000000 fd:00 393297 /lib/i686/nosegneg/libc-2.5.so 002b7000-002b9000 r-xp 00140000 fd:00 393297 /lib/i686/nosegneg/libc-2.5.so 002b9000-002ba000 rwxp 00142000 fd:00 393297 /lib/i686/nosegneg/libc-2.5.so 002ba000-002bd000 rwxp 002ba000 00:00 0 002bd000-003e9000 r-xp 00000000 fd:00 1642546 /usr/lib/libxml2.so.2.6.26 003e9000-003ee000 rwxp 0012c000 fd:00 1642546 /usr/lib/libxml2.so.2.6.26 003ee000-003ef000 rwxp 003ee000 00:00 0 003ef000-00401000 r-xp 00000000 fd:00 1642814 /usr/lib/libz.so.1.2.3 00401000-00402000 rwxp 00011000 fd:00 1642814 /usr/lib/libz.so.1.2.3 00402000-00405000 r-xp 00000000 fd:00 1835027 /usr/lib/python2.4/lib- dynload/_ssl.so 00405000-00406000 rwxp 00003000 fd:00 1835027 /usr/lib/python2.4/lib- dynload/_ssl.so 00406000-00447000 r-xp 00000000 fd:00 393226 /lib/libssl.so.0.9.8b 00447000-0044b000 rwxp 00040000 fd:00 393226 /lib/libssl.so.0.9.8b 0044b000-00477000 r-xp 00000000 fd:00 1642465 /usr/lib/libgssapi_krb5.so.2.2 00477000-00478000 rwxp 0002c000 fd:00 1642465 /usr/lib/libgssapi_krb5.so.2.2 00478000-00480000 r-xp 00000000 fd:00 1644106 /usr/lib/libkrb5support.so.0.1 00480000-00481000 rwxp 00007000 fd:00 1644106 /usr/lib/libkrb5support.so.0.1 00481000-00483000 r-xp 00000000 fd:00 1835049 /usr/lib/python2.4/lib- dynload/md5module.so 00483000-00484000 rwxp 00002000 fd:00 1835049 /usr/lib/python2.4/lib- dynload/md5module.so 00484000-00487000 r-xp 00000000 fd:00 1835061 /usr/lib/python2.4/lib- dynload/shamodule.so 00487000-00488000 rwxp 00002000 fd:00 1835061 /usr/lib/python2.4/lib- dynload/shamodule.so 00488000-00489000 r-xp 00000000 fd:00 1835029 /usr/lib/python2.4/lib- dynload/_weakref.so 00489000-0048a000 rwxp 00000000 fd:00 1835029 /usr/lib/python2.4/lib- dynload/_weakref.so 0048a000-0048e000 r-xp 00000000 fd:00 1835052 /usr/lib/python2.4/lib- dynload/operator.so 0048e000-0048f000 rwxp 00004000 fd:00 1835052 /usr/lib/python2.4/lib- dynload/operator.so 0048f000-00492000 r-xp 00000000 fd:00 1649254 /usr/lib/libgpg- error.so.0.3.0 00492000-00493000 rwxp 00002000 fd:00 1649254 /usr/lib/libgpg- error.so.0.3.0 00493000-00495000 r-xp 00000000 fd:00 394821 /lib/libcom_err.so.2.1 00495000-00496000 rwxp 00001000 fd:00 394821 /lib/libcom_err.so.2.1 00496000-0049a000 r-xp 00000000 fd:00 1649345 /usr/lib/libnuma.so.1 0049a000-0049b000 rwxp 00004000 fd:00 1649345 /usr/lib/libnuma.so.1 0049d000-0049f000 r-xp 00000000 fd:00 393246 /lib/libdl-2.5.so 0049f000-004a0000 r-xp 00001000 fd:00 393246 /lib/libdl-2.5.so 004a0000-004a1000 rwxp 00002000 fd:00 393246 /lib/libdl-2.5.so 004a1000-005be000 r-xp 00000000 fd:00 393218 /lib/libcrypto.so.0.9.8b 005be000-005d1000 rwxp 0011c000 fd:00 393218 /lib/libcrypto.so.0.9.8b 005d1000-005d4000 rwxp 005d1000 00:00 0 005d4000-005ea000 r-xp 00000000 fd:00 394806 /lib/libselinux.so.1 005ea000-005ec000 rwxp 00015000 fd:00 394806 /lib/libselinux.so.1 005ec000-005fa000 r-xp 00000000 fd:00 1835039 /usr/lib/python2.4/lib- dynload/datetime.so 005fa000-005fd000 rwxp 0000d000 fd:00 1835039 /usr/lib/python2.4/lib- dynload/datetime.so 005fd000-0060d000 r-xp 00000000 fd:00 1835034 /usr/lib/python2.4/lib- dynload/cPickle.so 0060d000-0060e000 rwxp 00010000 fd:00 1835034 /usr/lib/python2.4/lib- dynload/cPickle.so 0060e000-00612000 r-xp 00000000 fd:00 1646395 /usr/lib/libxenstore.so.3.0.0 00612000-00613000 rwxp 00003000 fd:00 1646395 /usr/lib/libxenstore.so.3.0.0 00613000-00616000 rwxp 00613000 00:00 0 00616000-00619000 r-xp 00000000 fd:00 1835071 /usr/lib/python2.4/lib- dynload/zlibmodule.so 00619000-0061a000 rwxp 00003000 fd:00 1835071 /usr/lib/python2.4/lib- dynload/zlibmodule.so 0061a000-00625000 r-xp 00000000 fd:00 394812 /lib/libgcc_s-4.1.2-20080102.so.1 00625000-00626000 rwxp 0000a000 fd:00 394812 /lib/libgcc_s-4.1.2-20080102.so.1 00628000-0071b000 r-xp 00000000 fd:00 1644304 /usr/lib/libpython2.4.so.1.0 0071b000-0073d000 rwxp 000f3000 fd:00 1644304 /usr/lib/libpython2.4.so.1.0 0073d000-00740000 rwxp 0073d000 00:00 0 00740000-0077b000 r-xp 00000000 fd:00 394805 /lib/libsepol.so.1 0077b000-0077c000 rwxp 0003a000 fd:00 394805 /lib/libsepol.so.1 0077c000-00786000 rwxp 0077c000 00:00 0 00786000-007ac000 r-xp 00000000 fd:00 1835055 /usr/lib/python2.4/lib- dynload/pyexpat.so 007ac000-007af000 rwxp 00026000 fd:00 1835055 /usr/lib/python2.4/lib- dynload/pyexpat.so 007af000-007c2000 r-xp 00000000 fd:00 393250 /lib/libnsl-2.5.so 007c2000-007c3000 r-xp 00012000 fd:00 393250 /lib/libnsl-2.5.so 007c3000-007c4000 rwxp 00013000 fd:00 393250 /lib/libnsl-2.5.so 007c4000-007c6000 rwxp 007c4000 00:00 0 007c8000-007cc000 r-xp 00000000 fd:00 1835032 /usr/lib/python2.4/lib- dynload/binascii.so 007cc000-007cd000 rwxp 00003000 fd:00 1835032 /usr/lib/python2.4/lib- dynload/binascii.so 007cd000-00819000 r-xp 00000000 fd:00 1870995 /usr/lib/python2.4/site- packages/M2Crypto/__m2crypto.so 00819000-0081d000 rwxp 0004b000 fd:00 1870995 /usr/lib/python2.4/site- packages/M2Crypto/__m2crypto.so 0081d000-0081e000 rwxp 0081d000 00:00 0 0083a000-00843000 r-xp 00000000 fd:00 1835026 /usr/lib/python2.4/lib- dynload/_socketmodule.so 00843000-00846000 rwxp 00009000 fd:00 1835026 /usr/lib/python2.4/lib- dynload/_socketmodule.so 00846000-008d6000 r-xp 00000000 fd:00 1643455 /usr/lib/libkrb5.so.3.3 008d6000-008d9000 rwxp 0008f000 fd:00 1643455 /usr/lib/libkrb5.so.3.3 008d9000-0096c000 r-xp 00000000 fd:00 1647990 /usr/lib/libvirt.so.0.6.1 0096c000-0096e000 rwxp 00092000 fd:00 1647990 /usr/lib/libvirt.so.0.6.1 0096e000-0097e000 rwxp 0096e000 00:00 0 009bb000-009ce000 r-xp 00000000 fd:00 393227 /lib/i686/nosegneg/libpthread-2.5.so 009ce000-009cf000 r-xp 00012000 fd:00 393227 /lib/i686/nosegneg/libpthread-2.5.so 009cf000-009d0000 rwxp 00013000 fd:00 393227 /lib/i686/nosegneg/libpthread-2.5.so 009d0000-009d2000 rwxp 009d0000 00:00 0 009d2000-00a25000 r-xp 00000000 fd:00 1651434 /usr/lib/libgcrypt.so.11.2.2 00a25000-00a27000 rwxp 00053000 fd:00 1651434 /usr/lib/libgcrypt.so.11.2.2 00a56000-00a58000 r-xp 00000000 fd:00 394819 /lib/libkeyutils-1.2.so 00a58000-00a59000 rwxp 00001000 fd:00 394819 /lib/libkeyutils-1.2.so 00b36000-00b5b000 r-xp 00000000 fd:00 1642678 /usr/lib/libk5crypto.so.3.1 00b5b000-00b5c000 rwxp 00025000 fd:00 1642678 /usr/lib/libk5crypto.so.3.1 00bd2000-00bf7000 r-xp 00000000 fd:00 393225 /lib/i686/nosegneg/libm-2.5.so 00bf7000-00bf8000 r-xp 00024000 fd:00 393225 /lib/i686/nosegneg/libm-2.5.so 00bf8000-00bf9000 rwxp 00025000 fd:00 393225 /lib/i686/nosegneg/libm-2.5.so 00c02000-00c0b000 r-xp 00000000 fd:00 393244 /lib/libcrypt-2.5.so 00c0b000-00c0c000 r-xp 00008000 fd:00 393244 /lib/libcrypt-2.5.so 00c0c000-00c0d000 rwxp 00009000 fd:00 393244 /lib/libcrypt-2.5.so 00c0d000-00c34000 rwxp 00c0d000 00:00 0 00cef000-00cf2000 r-xp 00000000 fd:00 1835060 /usr/lib/python2.4/lib- dynload/selectmodule.so 00cf2000-00cf3000 rwxp 00002000 fd:00 1835060 /usr/lib/python2.4/lib- dynload/selectmodule.so 00d03000-00d12000 r-xp 00000000 fd:00 393266 /lib/libresolv-2.5.so 00d12000-00d13000 r-xp 0000e000 fd:00 393266 /lib/libresolv-2.5.so 00d13000-00d14000 rwxp 0000f000 fd:00 393266 /lib/libresolv-2.5.so 00d14000-00d16000 rwxp 00d14000 00:00 0 00d2c000-00d30000 r-xp 00000000 fd:00 1835064 /usr/lib/python2.4/lib- dynload/structmodule.so 00d30000-00d31000 rwxp 00004000 fd:00 1835064 /usr/lib/python2.4/lib- dynload/structmodule.so 00dad000-00dae000 r-xp 00000000 fd:00 1835010 /usr/lib/python2.4/lib- dynload/_bisect.so 00dae000-00daf000 rwxp 00001000 fd:00 1835010 /usr/lib/python2.4/lib- dynload/_bisect.so 00daf000-00e26000 r-xp 00000000 fd:00 1642695 /usr/lib/libgnutls.so.13.0.6 00e26000-00e2c000 rwxp 00076000 fd:00 1642695 /usr/lib/libgnutls.so.13.0.6 00e31000-00e33000 r-xp 00000000 fd:00 1835025 /usr/lib/python2.4/lib- dynload/_randommodule.so 00e33000-00e34000 rwxp 00002000 fd:00 1835025 /usr/lib/python2.4/lib- dynload/_randommodule.so 00e7d000-00e81000 r-xp 00000000 fd:00 1835063 /usr/lib/python2.4/lib- dynload/stropmodule.so 00e81000-00e83000 rwxp 00003000 fd:00 1835063 /usr/lib/python2.4/lib- dynload/stropmodule.so 00eb5000-00eb8000 r-xp 00000000 fd:00 1835048 /usr/lib/python2.4/lib- dynload/mathmodule.so 00eb8000-00eb9000 rwxp 00002000 fd:00 1835048 /usr/lib/python2.4/lib- dynload/mathmodule.so 00f01000-00f1b000 r-xp 00000000 fd:00 393233 /lib/ld-2.5.so 00f1b000-00f1c000 r-xp 00019000 fd:00 393233 /lib/ld-2.5.so 00f1c000-00f1d000 rwxp 0001a000 fd:00 393233 /lib/ld-2.5.so 00f95000-00fa5000 r-xp 00000000 fd:00 1836431 /usr/lib/python2.4/site- packages/libvirtmod.so 00fa5000-00fa6000 rwxp 00010000 fd:00 1836431 /usr/lib/python2.4/site- packages/libvirtmod.so 07fe5000-07ffd000 r-xp 00000000 fd:00 1644078 /usr/lib/libsasl2.so.2.0.22 07ffd000-07ffe000 rwxp 00017000 fd:00 1644078 /usr/lib/libsasl2.so.2.0.22 08048000-08049000 r-xp 00000000 fd:00 1651446 /usr/bin/python 08049000-0804a000 rw-p 00000000 fd:00 1651446 /usr/bin/python 091d3000-093cb000 rw-p 091d3000 00:00 0 b6e00000-b6e21000 rw-p b6e00000 00:00 0 b6e21000-b6f00000 ---p b6e21000 00:00 0 b6fb6000-b6fbd000 r--s 00000000 fd:00 1704837 /usr/lib/gconv/gconv- modules.cache b6fbd000-b6ffe000 rw-p b6fbd000 00:00 0 b6ffe000-b6fff000 ---p b6ffe000 00:00 0 b6fff000-b7ac2000 rw-p b6fff000 00:00 0 b7ac3000-b7ceb000 rw-p b7ac3000 00:00 0 b7cec000-b7eec000 r--p 00000000 fd:00 1651479 /usr/lib/locale/locale- archive b7eec000-b7f70000 rw-p b7eec000 00:00 0 b7f75000-b7f78000 rw-p b7f75000 00:00 0 bfaea000-bfaff000 rw-p bfaea000 00:00 0 [stack] Aborted I've memtested the memory and its fine. If i use a file as the target (instead of a block device) it also works: virt-install -n test -r 512 --vnc --file=/tmp/test-os --file-size=2 -- location=ftp://mirrors/centos/5/os/i386 Any ideas? Thanks, Nuno Fernandes

3 7

[libvirt] PATCH: 0/25: Full thread support for libvirt public API
by Daniel P. Berrange 10 Mar '09

10 Mar '09

This patch series is (mostly) aimed at providing full support for threads in the libvirt API. Specifically we remove the restriction that a single virConnectPtr is tied to a thread. Multiple threads can safely use the same object (provided one doesn't free it behind another's back :-P ) This is tested to compile on Linux + Win32 (MinGW), hopefully doesn't break Solaris, but I'll be testing that soon too. I've tortured the patches in various nasty ways are they're now stable enough to let loose and probably merge for wider testing. It'll probably be easier to just fix future problems in tree, rather than maintain this patchset longer. The full patchset is also available here http://berrange.fedorapeople.org/libvirt-threads-2009-01-13/ Daniel -- |: 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 :|

7 166

[libvirt] OCaml libvirt bindings 0.6.1.0 released
by Richard W.M. Jones 10 Mar '09

10 Mar '09

http://libvirt.org/ocaml/ Not a lot of change, since the bindings are pretty much stable now. The main change, and reason for this release, was that since CVE-2008-5086 the virDomainBlockPeek and virDomainMemoryPeek bindings now require a read/write libvirt connection. This broke mlvirsh and virt-df which were requesting a read-only connection. I have now changed this (thanks David Lutterkort for pointing out the problem). Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top

1 0

[libvirt] [Patch] Fix detach tap device on Xen3.3.1
by Takahashi Tomohiro 10 Mar '09

10 Mar '09

Hi, I made the patch that corrected the following problem. It is that when I executed the "virsh detach-disk" command on Xen3.3.1, Libvirt could not detach tap device and output the following error message. # virsh detach-disk Fedora xvdd libvir: Xen Daemon error : POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 51760 not connected') The cause of this problem is incompatible of Xen3.3.0 and Xen3.3.1. I think Xen specific was changed by the following patch. http://xenbits.xensource.com/xen-3.3-testing.hg?rev/e0e17216ba70 If you have any comments, please suggest me. Signed-off-by: Tomohiro Takahashi <takatom(a)jp.fujitsu.com> Thanks, Tomohiro Takahashi diff -uNrp libvirt.orig/src/xend_internal.c libvirt/src/xend_internal.c --- libvirt.orig/src/xend_internal.c 2009-02-14 03:23:23.000000000 +0900 +++ libvirt/src/xend_internal.c 2009-03-09 12:28:48.000000000 +0900 @@ -5566,7 +5566,11 @@ virDomainXMLDevID(virDomainPtr domain, char *xref; if (dev->type == VIR_DOMAIN_DEVICE_DISK) { - strcpy(class, "vbd"); + if (!(strcmp(dev->data.disk->driverName, "tap"))) { + strcpy(class, "tap"); + } else { + strcpy(class, "vbd"); + } if (dev->data.disk->dst == NULL) return -1; xenUnifiedLock(priv);

2 3