- Devel - libvirt List Archives

[libvirt] PATCH: Fix DBus thread safety
by Daniel P. Berrange 02 Mar '09

02 Mar '09

We are using DBus from multiple threads in libvirtd. We are not calling dbus_threads_init_default(). Very bad things result. Happy-crashy-daemon This patch fixes that, and also stops DBus messing around with SIGPIPE and also stops it calling exit() when the bus disconnects, so we can actually see the error & continue with life. Daniel diff -rup libvirt-0.6.0.orig/qemud/qemud.c libvirt-0.6.0.new/qemud/qemud.c --- libvirt-0.6.0.orig/qemud/qemud.c 2009-02-18 10:56:34.000000000 +0000 +++ libvirt-0.6.0.new/qemud/qemud.c 2009-02-18 12:52:18.000000000 +0000 @@ -860,6 +860,10 @@ static struct qemud_server *qemudNetwork if (auth_unix_rw == REMOTE_AUTH_POLKIT || auth_unix_ro == REMOTE_AUTH_POLKIT) { DBusError derr; + + dbus_connection_set_change_sigpipe(FALSE); + dbus_threads_init_default(); + dbus_error_init(&derr); server->sysbus = dbus_bus_get(DBUS_BUS_SYSTEM, &derr); if (!(server->sysbus)) { @@ -868,6 +872,7 @@ static struct qemud_server *qemudNetwork dbus_error_free(&derr); goto cleanup; } + dbus_connection_set_exit_on_disconnect(server->sysbus, FALSE); } #endif diff -rup libvirt-0.6.0.orig/src/node_device_hal.c libvirt-0.6.0.new/src/node_device_hal.c --- libvirt-0.6.0.orig/src/node_device_hal.c 2009-01-16 12:44:22.000000000 +0000 +++ libvirt-0.6.0.new/src/node_device_hal.c 2009-02-18 12:52:48.000000000 +0000 @@ -685,6 +685,9 @@ static int halDeviceMonitorStartup(void) nodeDeviceLock(driverState); /* Allocate and initialize a new HAL context */ + dbus_connection_set_change_sigpipe(FALSE); + dbus_threads_init_default(); + dbus_error_init(&err); hal_ctx = libhal_ctx_new(); if (hal_ctx == NULL) { @@ -696,6 +699,8 @@ static int halDeviceMonitorStartup(void) fprintf(stderr, "%s: dbus_bus_get failed\n", __FUNCTION__); goto failure; } + dbus_connection_set_exit_on_disconnect(dbus_conn, FALSE); + if (!libhal_ctx_set_dbus_connection(hal_ctx, dbus_conn)) { fprintf(stderr, "%s: libhal_ctx_set_dbus_connection failed\n", __FUNCTION__); -- |: 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 :|

4 5

[libvirt] [PATCH] small fixes in storage_conf.c
by Ryota Ozaki 02 Mar '09

02 Mar '09

Hi, These patches fix: - missing VIR_FREE for the return value of virXPathString - wrong error message "missing owner element" where should be "missing group element" Signed-off-by: Ryota Ozaki <ozaki.ryota(a)gmail.com>

3 3

[libvirt] [PATCH] don't dereference uninitialized pointer
by Jim Meyering 02 Mar '09

02 Mar '09

>From a907d2da7e7f9d1f58009ff6a95454ac0eb2cbf1 Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering(a)redhat.com> Date: Mon, 2 Mar 2009 10:10:02 +0100 Subject: [PATCH] don't dereference uninitialized pointer * src/storage_conf.c (virStoragePoolDefParsePerms): Initialize "ptr" to NULL. --- ChangeLog | 6 ++++++ src/storage_conf.c | 2 +- 2 files changed, 7 insertions(+), 1 deletions(-) diff --git a/ChangeLog b/ChangeLog index 12715f5..ede7e0d 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2009-03-02 Jim Meyering <meyering(a)redhat.com> + + don't dereference uninitialized pointer + * src/storage_conf.c (virStoragePoolDefParsePerms): Initialize + "ptr" to NULL. + Fri Feb 27 17:15:00 CET 2009 Chris Lalancette <clalance(a)redhat.com> * src/qemu_driver.c: If there is a failure during offline migrate, diff --git a/src/storage_conf.c b/src/storage_conf.c index 70107a2..4a53ff4 100644 --- a/src/storage_conf.c +++ b/src/storage_conf.c @@ -381,7 +381,7 @@ virStoragePoolDefParsePerms(virConnectPtr conn, if (!mode) { perms->mode = 0700; } else { - char *end; + char *end = NULL; perms->mode = strtol(mode, &end, 8); if (*end || perms->mode < 0 || perms->mode > 0777) { virStorageReportError(conn, VIR_ERR_XML_ERROR, -- 1.6.2.rc1.285.gc5f54

2 2

[libvirt] Update on host interface configuration
by David Lutterkort 01 Mar '09

01 Mar '09

Hi, I thought I'd write an update of what I've been doing with the host interface configuration previously discussed[1] After talking with Dan Williams, who is working in NetworkManager, it is clear that the network interface functionality for libvirt is also useful for NM and would help them with handling system-wide interface configuration. To accomodate that, I will implement network interface configuration in a separate library (inspiringly called 'netcf', until somebody thinks of something catchier) and add public API to libvirt that will use netcf to do the actual work. One thorny issue is how libvirt's public API and netcf's public API relate to each other, especially since both libvirt and netcf use XML descriptions to describe network interfaces (netcf does that for exactly the same reasons that libvirt does it, since it will have to deal with similar stability issues) For the time being, I am assuming that the two XML descriptions are identical, with no guarantee that that will always be the case. If and when we run into a case where libvirt's and netcf's needs diverge, we'll break that identity. On the implementation side, that means that, for now, netcf will do all the validation and pass errors back to libvirt. In more concrete terms, I put up a git repo[2] for netcf. There's hardly any code in there, the things I'd particularly appreciate review/feedback on are * the RelaxNG specification of the interface XML (in xml/interface.rng) together with examples of such interface specifications (in tests/interface/) * the (very rough) sketch of the netcf public API, which should map almost 1-1 to the public libvirt API in src/netcf.h I know that the XML schema doesn't cover everything we've discussed in [1], but I think it's a small enough subset to tackle relatively quickly and large enough to be useful. So, one of the main things to think about when looking at the schema is places where the schema would make it hard to make desirable enhancements in the near future (like Marius' point about default routes/gateways) One important point about the model of network config in the schema is that it is centered around what NM calls a 'connection' (though it's called 'interface' in the schema): a grouping of the components that make up the interface the user really cares about (a bridge or a bond) together with the components subordinate to it (e.g. ethernet interfaces enslaved to the bridge or bond) It's those groups that netcf deals with, i.e. if eth0 is enslaved to br0, netcf won't list eth0 as an interface, but only br0, with eth0 as a subinterface. For the implementation, netcf will have a separate backend for each network configuration regime (initscripts for Fedora/RHEL, /etc/network/interfaces for Debian, ...) - once the initscripts backend is done, I'd be very grateful for contributions for the other backends. To sketch out the initscripts implementation, I wrote two XSL stylesheets, xml/initscripts-get.xml that goes from interface XML -> initscripts files (via Augeas) and xml/initscripts-put.xml to go the other way for querying; I'll use those for the core of the initscripts backend. Whether other backands can be done in a similar manner is TBD. David [1] https://www.redhat.com/archives/libvir-list/2009-January/msg00350.html [2] http://git.et.redhat.com/?p=netcf.git;a=tree

5 10

[libvirt] virsh and api
by Zvi Dubitzky 01 Mar '09

01 Mar '09

Hi How about adding the following info to the virsh / dominfo command ( and to the programmable libvirt API:): - IP address of the domain in case the host was configured as a bridge - cpu utilization (at least for Linux) Is that possible ? thanks Zvi Dubitzky Virtualization and System Architecture Email:dubi@il.ibm.com IBM Haifa Research Laboratory Phone: +972-4-8296182 Haifa, 31905, ISRAEL

1 0

[libvirt] Problem installing KVM Guest from command line
by aliahsan naqvi 28 Feb '09

28 Feb '09

Hi All >From past many days i am trying to install KVM Guest Machine from command line via virt-install.Below is many command i have testing this on Fedora 9 and fedora 10 but not able to do it. virt-install -n testing -r 256 -w bridge:virbr0 --location /mnt/Fedora-10-i386-DVD.iso --accelerate --os-type=linux --hvm --nographics -f /var/imgVM1 --force -x "console=ttyS0" I am installing from HTTP server.After give Network information.Following error comes.i have also tried with NFS and ftp but same result.It seem guest machine not able to get ip address.Because when i ping the ip address of the guest which is provided in Networking setting during guest installation.It was not pingable.And this http server is working fine.i can browse all the install directory with no problem and i have install other machine with the http install directory. I am getting following error after TCP/IP Manual/ DHCP Configuration Network Settings +-----------+ Error +------------+ | | | Unable to retrieve | | http://192.168.1.8/fedora | | /linux/releases/10/Fedora/i38 | | 6/os//images/install.img. | | | | +----+ | | | OK | | | +----+ | | | | | +--------------------------------+ Please Advise.Please let me if i am doing some thing wrong or this a bug. _________________________________________________________________ Windows Live™: Life without walls. http://windowslive.com/explore?ocid=TXT_TAGLM_WL_allup_1a_explore_032009

1 0

RE: [libvirt] Help with bridged networking
by Jesus Urroa 27 Feb '09

27 Feb '09

Hi, Thanks all for your help, I installed libvirt 0.6.0-4 and kvm 84-1 from fedora's rawhide and that solved the problem. However know I have a new problem I tried the other virtual machines and some of them just don't start, they seem to stop when the bios jumps to the disk and grub, any ideas? The only thing I can think of is to upgrade the host kernel but if I'm not wrong I have to upgrade to Fedora 9 or 10, and I would like to try something else before because I want to have everything running before leaving xen completely > Subject: RE: [libvirt] Help with bridged networking > From: lutter(a)redhat.com > To: observer1(a)hotmail.es > Date: Fri, 27 Feb 2009 08:48:13 -0800 > > On Fri, 2009-02-27 at 00:55 +0000, Jesus Urroa wrote: > > My mistake I see the lines for the ip config commented out in the file > > and I place them again > > Anyway I remove the card from the bridge to simplify the problem a > > little, this the output of brctl show for the bridge using only xen > > (no libvirt at all) and using kvm with libvirt and running only 2 vms: > > > > worknet 8000.feffffffffff no vif1.0 > > vif4.0 > > vif5.0 > > vif6.1 > > vif7.1 > > vif8.0 > > > > worknet 8000.00ff52959073 no vnet0 > > > > vnet3 > > With the non-Xen setup, your bridge should have the same IP address as > the enslaved NIC. > > What exactly is not working ? Can VM's on the same bridge ping each > other ? > > Did you add teh following iptables rule (to forward packages from the > bridge to the outside): > > # echo "-I FORWARD -m physdev --physdev-is-bridged -j ACCEPT" > /etc/sysconfig/iptables-forward-bridged > # lokkit --custom-rules=ipv4:filter:/etc/sysconfig/iptables-forward-bridged > # service libvirtd reload > > Otherwise, your VM;s can't talk to the outside. > > David > > _________________________________________________________________ Anímate y disfruta con los mejores juegos de Messenger, ¡descúbrelos! http://www.vivelive.com/juegos/

1 0

[libvirt] internal error Timed out while reading console log output
by jmandawg 27 Feb '09

27 Feb '09

Hi, I just compiled installed Libvirt from the latest git repo, and for some reason when I try to start a VM from virsh I get the following error: virsh # start XPTest error: Failed to start domain XPTest error: internal error unable to start guest: and the corresponding output from libvirtd running in verbose mode: 08:19:53.163: info : Received unexpected signal 17 08:20:00.083: info : Received unexpected signal 17 08:20:00.095: info : Received unexpected signal 17 08:20:03.200: error : internal error Timed out while reading console log output libvir: QEMU error : internal error Timed out while reading console log output 08:20:03.200: error : internal error unable to start guest: libvir: QEMU error : internal error unable to start guest: Here is the command virsh is trying to run from the Libvirt log file: LC_ALL=C PATH=/usr/bin:/bin:/root/bin:/usr/X11R6/bin:/usr/local/kvm/bin:/usr/local/sb in:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games HOME=/root USER=root LOGNAME=root /usr/bin/kvm -S -M pc -m 512 -smp 1 -name XPTest -uuid 732fcba8-b71f-face-e067-cf8431fc94aa -monitor pty -pidfile /var/run/libvirt/qemu//XPTest.pid -localtime -no-acpi -boot c -drive file=/var/kvm-images/XPTest/XP_Test.img,if=ide,index=0,boot=on -net nic,macaddr=00:0c:29:f6:c4:f8,vlan=0,model=e1000 -net tap,fd=20,script=,vlan=0,ifname=vnet3 -serial none -parallel none -usb -usbdevice tablet -vnc 0.0.0.0:9 If I start the VM from the commandline manually using this command and then shutdown, I can successfully start it from Virsh qemu-system-x86_64 -no-acpi -m 512 -hda XP_Test.img \ -net nic,macaddr=00:0C:29:F6:C4:F8 \ -net tap \ -usb -usbdevice tablet \ -monitor unix:monitor,server,nowait \ -soundhw all \ -pidfile pid & virsh # version Compiled against library: libvir 0.6.0 Using library: libvir 0.6.0 Using API: QEMU 0.6.0 Running hypervisor: QEMU 0.9.1 Any help would be appreciated. Thanks, John

1 1

[libvirt] [PATCH]: Fix non-live migration failure
by Chris Lalancette 27 Feb '09

27 Feb '09

There is a logic error in the Qemu driver when doing a non-live migrate. During a non-live migrate, on the source host during the Perform step, we pause the domain; however, if there was ever a failure, we were forgetting to unpause the domain, meaning that the domain was paused forever. Add a flag to tell us when we should unpause the domain after a failure. Also, as pointed out by DV, we were unnecessarily using a snprintf to a buffer to execute qemu monitor commands, when we could get away with just sending a static string. Fix that as well. Signed-off-by: Chris Lalancette <clalance(a)redhat.com>

2 2

[libvirt] libvirt tls vnc
by Michael Kress 27 Feb '09

27 Feb '09

Hi, is there a comprehensive howto/tutorial you can recommend me on how to set up libvirt with vnc over tls properly? What I'm trying to do is to use vnc for production use outside my local network and therefore I'd like to secure the vnc sessions. I already made some attempts with ssvnc and Ultr@VNC (both windows clients) but these attemps all failed. I can't get the vnc server (launched by virt-install / kvm) to be displayed via tls. It all runs perfectly without tls. Thanx for any hints! Michael

4 16

[libvirt] using virsh remotely
by Andreas Rittershofer 27 Feb '09

27 Feb '09

I can use virsh as a command line tool, for exampe virsh list gives me the list of the running machines and I am back to the prompt. When I make virsh -c qemu+ssh://maschine-2/system list I get the list of the running machine on the remote machine-2 - but that's it, I am not back to the prompt automatically. I want virsh to behave used remotely as used locally - execute the command and go back to the prompt. How this can be done? mfg ar -- Hier könnte keine Signatur stehen.

2 2

[libvirt] adding bandwidth control support
by Max Zhen 27 Feb '09

27 Feb '09

My last post failed, resend... Max Zhen at 2008-12-24 18:39 wrote: > Hi, > > I'm working on adding bandwidth control support in > virt-install/virsh/libvirt on Xen. > This support can allow setting bandwidth control in dom0 (I'm working on > Solaris dom0 now) for virtual nic devices used in a domU. > I've attached my design in this email. > Basically, this design is about how to represent bandwidth limit > information in command line for virsh/virt-install and how to represent > it in current XML configuration file for a domU. > > Your comments will be highly appreciated :). > > Thanks, > Max > > There are a few things to do to achieve this goal: 1. extend current command line syntax of 'virsh attach-interface' 2. extend current command line syntax of 'virt-install' 3. define bandwidth representation in XML format For 1. I will change the current command line syntax to: virsh attach-interface <domain> <type> <source> [--target <target>] [--mac <mac>] [--script <script>] [--rate <rate-string>] So that we are able to specify bandwidth as "--rate 100M" in command line, like: #virsh attach-interface domu bridge bge0 --rate 100M In this case, bandwidth is specified as an integer with one of the scale suffixes K, M, or G for Kbps, Mbps, or Gbps. For 2. I will add one more option "--rate=rate-string" to current option set of virt-install command. Users can repeatedly add more than one 'rate' options to set bandwidth for multiple nic devices respectively, if needed. For example, with below command line, we start installing a domain with two nic devices whose bandwidth are set to 100Mb/s and 200Mb/s respectively: #virt-install -n snv105 -r 2048 -p --file=/root/snv105 --location=/solarisdvd.iso -b bge0 --rate=100M -b bge1 --rate=200M In this case, bandwidth is specified as an integer with one of the scale suffixes K, M, or G for Kbps, Mbps, or Gbps. For 3. All user specified bandwidth will be represented as part of interface element currently defined in XML configuration file. The new format looks like: <interface type='bridge'> <source bridge='e1000g1'/> <flowcontrol> <rate unit='megabit' period='second' value='100'/> </flowcontrol> </interface> So, I create a new element, "flowcontrol", inside "interface" element. Inside "flowcontrol", I provide bandwidth by setting "rate" element with three attributes, "unit", "period" and "value" to express the bandwidth limit. The supported unit can be 'gigabit', 'megabit' and 'kilobit'. The supported period can be 'second', 'millisecond' and 'microsecond'. And value is an integer to express the amount of data in unit allowed to be transfered in period of time. More elements can be added inside "flowcontrol" element, if we want to add more flow control policies in the future.

2 5

[libvirt] Help with bridged networking
by watcher lines 26 Feb '09

26 Feb '09

Hi, I have setup my virtual networks with initscripts like in this link: http://wiki.libvirt.org/page/Networking#Bridged_networking_.28aka_.22shared…, but there is no networking whitin any system either between vms or with the host and the vms. This setup is for kvm, but with Xen in Fedora 8 it works perfect, but xen is now deprecated in Fedora. This is my setup: /etc/sysconfig/network-scripts/ifcfg-worknet: # worknet bridge DEVICE=worknet BOOTPROTO=none BROADCAST=172.16.1.255 #HWADDR=00:50:56:C0:00:01 IPADDR=172.16.1.1 NETMASK=255.255.255.0 NETWORK=172.16.1.0 ONBOOT=yes TYPE=Bridge STP=off DELAY=0 With Xen this alone lets ip traffic pass between host and to allow dhcp and other protocols i have this line in my iptables: -A FORWARD -i worknet -j ACCEPT This is the software I'm using: libvirt-0.4.4-2.fc8 kvm-60-7.fc8 Thanks for your attention. _________________________________________________________________ Consigue gratis el nuevo Messenger. ¡Descárgatelo! http://download.live.com/

1 0

[libvirt] networking with two hosts
by Andreas Rittershofer 26 Feb '09

26 Feb '09

The following situation is given: Host A with VM1 and VM2 running. Host B with VM3 und VM4 running. Task 1.) Each VM must have network access to each other VM and to the outside. Task 2.) When one host fails, all VMs are running on the remainig host and 1.) must still be fulfilled. Does somebody has any hints about realising this scenario with libvirt and KVM? mfg ar -- Hier könnte keine Signatur stehen.

3 7

[libvirt] Adding VirtualBox support to libvirt
by Pritesh Kothari 26 Feb '09

26 Feb '09

Hi, I am in the process of adding support for virtualbox in libvirt. Basically Virtualbox exports its API through XPCOM. Now to simplify things I was thinking of using C++ and already existing xpcom component in virtualbox but since libvirt exports C API i am not sure if i should use C++ or stick to plain C. I would like to request the libvirt community for its comment on this. Regards, Pritesh

4 10

[libvirt] PATCH: Support memory balloon device in QEMU (incomplete)
by Daniel P. Berrange 26 Feb '09

26 Feb '09

This is an incomplete patch starting to support the memory balloon device in QEMU guests. This requires the VirtIO Balloon driver be present in the guest. In much the same way as with Xen guests, this lets you adjust the memory allocation of the guest on the fly, ceiling limited by the initial memory allocation when booted. The missing bit is to use 'info balloon' to fetch the current allocation for the virDomainGetInfo() API call. Regards, Daniel diff -r 2662c220efc8 src/qemu_driver.c --- a/src/qemu_driver.c Thu Feb 26 15:31:11 2009 +0000 +++ b/src/qemu_driver.c Thu Feb 26 15:31:23 2009 +0000 @@ -2223,6 +2223,46 @@ cleanup: return ret; } + +static int qemudDomainSetMemoryBalloon(virConnectPtr conn, + virDomainObjPtr vm, + unsigned long newmem) { + char *cmd; + char *reply; + + /* + * '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); + return -1; + } + + if (qemudMonitorCommand(vm, cmd, &reply) < 0) { + qemudReportError(conn, dom, NULL, VIR_ERR_OPERATION_FAILED, + "%s", _("could not balloon memory allocation")); + VIR_FREE(cmd); + return -1; + } + 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:")) { + qemudReportError (conn, dom, NULL, VIR_ERR_OPERATION_FAILED, + _("memory ballooning is not supported %s"), reply); + VIR_FREE(reply); + return -1; + } + VIR_FREE(reply); + + return 0; +} + + static int qemudDomainSetMemory(virDomainPtr dom, unsigned long newmem) { struct qemud_driver *driver = dom->conn->privateData; virDomainObjPtr vm; @@ -2240,20 +2280,18 @@ 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); + } else { + vm->def->memory = newmem; + ret = 0; + } cleanup: if (vm) -- |: 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 :|

1 0

[libvirt] [PATCH]: Fix non-live migration failure case
by Chris Lalancette 26 Feb '09

26 Feb '09

All, There was a logic error in the Qemu driver when doing a non-live migrate. During a non-live migrate, on the source host during the Perform step, we pause the domain; however, if there was ever a failure, we were forgetting to unpause the domain, meaning that the domain was paused forever. Add a flag to tell us when we should unpause the domain after a failure. Signed-off-by: Chris Lalancette <clalance(a)redhat.com>

2 2

[libvirt] [PATCH 0/1] Resend of example program
by David Allan 26 Feb '09

26 Feb '09

I'm just resending this patch, as nobody objected to it after I incorporated the feedback I got, but it never got applied, either. Dave

2 2

[libvirt] PATCH: Fix autostart of session daemon
by Daniel P. Berrange 26 Feb '09

26 Feb '09

When connecting qemu:///session we can autostart the libvirtd daemon. With the node device APIs present, it can take upto a second to start up while talking to dbus. The remote driver was only waiting for a fraction of a second. This changes it to wait for upto 2 seconds, and also not to spawn multiple instances of the daemon. Daniel diff -rup libvirt-0.6.0.orig/src/remote_internal.c libvirt-0.6.0.new/src/remote_internal.c --- libvirt-0.6.0.orig/src/remote_internal.c 2009-02-18 10:56:34.000000000 +0000 +++ libvirt-0.6.0.new/src/remote_internal.c 2009-02-18 13:35:26.000000000 +0000 @@ -654,12 +654,13 @@ doRemoteOpen (virConnectPtr conn, */ if (errno == ECONNREFUSED && flags & VIR_DRV_OPEN_REMOTE_AUTOSTART && - trials < 5) { + trials < 20) { close(priv->sock); priv->sock = -1; - if (remoteForkDaemon(conn) == 0) { + if (trials > 0 || + remoteForkDaemon(conn) == 0) { trials++; - usleep(5000 * trials * trials); + usleep(1000 * 100 * trials); goto autostart_retry; } } -- |: 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] storage_backend_fs.c Bug
by Russell 26 Feb '09

26 Feb '09

Line 1133 of storage_backend_fs.c in 0.6.0: if (vol->target.backingStore != NULL) { virStorageReportError(conn, VIR_ERR_NO_SUPPORT, _("copy-on-write image not supported with " "qcow-create")); return -1; } virStorageVolTarget has no member called backingStore, resulting in compile errors.

5 5

[libvirt] [PATCH] Don't generate python bindings multiple times w/ parallel build
by Cole Robinson 26 Feb '09

26 Feb '09

The attached patch was posted by Michael Marineau at: https://bugzilla.redhat.com/show_bug.cgi?id=472702 It prevents generating the python bindings multiple times in a parallel build. Works fine in my testing, so I figured I'd pass it along here for better exposure, since it has been languishing in bugzilla. Thanks, Cole

3 2

[libvirt] [PATCH 0/5] Add device assignment related node device methods
by Mark McLoughlin 25 Feb '09

25 Feb '09

Hi, The following patches implement three new node device methods that are needed for KVM PCI device assignment. The dettach method unbinds the device from its device driver and binds it to the pci-stub driver, if available. This ensures the device is not being used by the host. The reattach method undos this operation. It unbinds the device from pci-stub and attempts to re-bind it to the original device driver. This allows the device to be used by the host again. The reset method is intended to be used on a dettached device before it is used by the guest or host. This operation may in future affect other devices, so it is intended that all devices to be assigned to a guest are first dettached before any device is reset. A writeup of some more background details are available here: http://marc.info/?l=kvm&m=123454366317045 Cheers, Mark.

2 13

[libvirt] [PATCH] document static host IP assignment
by Charles Duffy 25 Feb '09

25 Feb '09

Back in August 2008, DV added support for providing static IP/hostname assignments to dnsmasq via <host> elements in the network definition. Since this functionality isn't covered in the documentation, I wrote up a quick patch, attached.

3 2

[libvirt] [PATCH 0/2] Dettach and reset devices before assigning to guests
by Mark McLoughlin 25 Feb '09

25 Feb '09

Hi, The following two patches build on the previous series. The idea is simple - when starting a guest, we should automatically dettach and reset any devices assigned to it. Rather than change the semantics of the existing hostdev source, we only do this when the node device name is used as the hostdev source. Directly specifying the device address rather than its name can be seen as an option for people who know what they're doing. Cheers, Mark.

2 6

[libvirt] "type 'hvm' & arch 'i686' combination is not supported" error
by Frederik Himpe 25 Feb '09

25 Feb '09

I recently updated for libvirt 0.4.6 to libvirt 0.6.0. Now several of the virtual machines I defined, are not shown in virt-manager nor by virsh list --all, although the config files are still in /etc/libvirt/qemu. I tried to run virsh create, and this error is shown: libvir: Domain Config error : internal error os type 'hvm' & arch 'i686' combination is not supported This configuration was working perfectly with libvirt 0.4.6. I needed to change i686 to x86_64 in all config files of 32 bit systems to make them work again. Is there no way libvirt could migrate those configuration files automatically? -- Frederik Himpe

2 5