[libvirt] virsh migrate with libvirt-0.6.2: failed to start listening VM

Hello, I'm trying to migrate a vm from a fedora 11 host to another fedora 11 host. Both hosts are on the same subnet. Both machines have identical architectures. We use an nfs shared storage mounted, but both machines also have their own hard drives. I get the machines up and running alright. Here

Re: [libvirt] Some problem with the save function

Chris Lalancette wrote: No, you are right. This was part of the refactoring, and I just didn't re-read the code. I would prefer to move prog to the top of the block myself, and add args there; it just seems tidier. I agree that it's tidier -- but looking at things in context, I'm not very

[libvirt] [PATCH 8/9] Factor out the method to get the PCI address of a controller for a given disk

We need this multiple times later on. Signed-off-by: Wolfgang Mauerer Signed-off-by: Jan Kiszka --- src/qemu_driver.c | 155 + 1 files changed, 97 insertions(+), 58 deletions(-) diff --git a/src/qemu_driver.c b/src/qemu_driver.c index f1c2a4

[libvirt] [PATCH 1/9] Clarify documentation for private symbols

The instruction "See Makefile.am" in libvirt.private_syms always makes me think that this file is autogenerated and should not be touched manually. This patch spares every reader of libvirt.private_syms the hassle of reading Makefile.am before augmenting libvirt.private_syms. Signed-off-by: Wolfga

[libvirt] [PATCH 6/9] Allow controller selection by ID

... by simply traversing the list of controllers to find the associated PCI address. Signed-off-by: Wolfgang Mauerer Signed-off-by: Jan Kiszka --- src/qemu_driver.c | 41 +++-- 1 files changed, 31 insertions(+), 10 deletions(-) diff --git a/src/qemu_driver

[libvirt] [PATCH 2/9] Extend element with controller information

This allows us to connect a disk with a specific controller, which is required for disk hotadd/remove. A new XML child element is added to the container: ... Either id _or_ pci_addr can be specified. When the controller has been brought into the system via tghe hotplug mechanism also

[libvirt] [PATCH 5/9] Implement controller hotplugging

This enables to hot-add disk controllers without attached disks into the system. Previously, it was only possible to (implicitly) add disk controllers in the static machine configuration. Notice that the actual functionality is only available for qemu at present, but other emulators can be extende

[libvirt] [PATCH 9/9] Implement disk- and controller hotremove

Since both disks and disk controllers can be dynamically added to the system, it makes sense to be also able to remove them. Signed-off-by: Wolfgang Mauerer Signed-off-by: Jan Kiszka --- src/domain_conf.h |8 +++ src/qemu_driver.c | 161 +++-

[libvirt] [PATCH 3/9] Add new domain device: "controller"

This augments virDomainDevice with a element that is used to represent disk controllers (e.g., scsi controllers). The XML format is given by where type denotes the disk interface (scsi, ide,...), id is an arbitrary string that identifies the controller for disk hotadd/remove, and bus addr

[libvirt] [PATCH 4/9] Add disk-based hotplugging for the qemu backend

When disks are added to a qemu backend with attach-device, not just the disk, but a complete new PCI controller with the disk attached is brought into the system. This patch implements a proper disk hotplugging scheme for qemu. Signed-off-by: Wolfgang Mauerer Signed-off-by: Jan Kiszka --- src/d

[libvirt] [PATCH 7/9] Remove surprises in the semantics of disk-hotadd

When a disk is added without an explicitly specified controller as host, then try to find the first available controller. If none exists, do not (as in previous versions) add a new PCI controller device with the disk attached, but bail out with an error. Notice that this patch changes the behaviour

[libvirt] [PATCH 0/9] Support disk-hotremove and controller hotplugging

Hi, this patch reworks libvirt's disk-hotadd support and introduces support for disk controller hotplugging and disk-hotremove (see http://thread.gmane.org/gmane.comp.emulators.libvirt/15860 for more details). Currently, it targets only qemu and also requires some additions to qemu that have on

Re: [libvirt] Some problem with the save function

Charles Duffy wrote: > On Fri, Sep 18, 2009 at 1:53 AM, Chris Lalancette > wrote: > > > diff --git a/src/qemu_driver.c b/src/qemu_driver.c > > index a65334f..ff30421 100644 > > --- a/src/qemu_driver.c > > +++ b/src/qemu_driver.c > > @@ -3912,10 +391

Re: [libvirt] Some problem with the save function

On Fri, Sep 18, 2009 at 1:53 AM, Chris Lalancette wrote: > > diff --git a/src/qemu_driver.c b/src/qemu_driver.c > > index a65334f..ff30421 100644 > > --- a/src/qemu_driver.c > > +++ b/src/qemu_driver.c > > @@ -3912,10 +3912,15 @@ static int qemudDomainSave(virDomainPtr dom, > > goto clean

Re: [libvirt] regarding the network information for Domain

Le vendredi 18 septembre 2009 à 18:26 +0530, anuj rampal a écrit : > Hi all, > > im trying to call libvirt api from windows. > > I have created a guest OS(windows) using the libvirt api from my > windows machine. > It gets created fine it also gets the the IP address from the DHCP > also. > So

[libvirt] regarding the network information for Domain

Hi all, im trying to call libvirt api from windows. I have created a guest OS(windows) using the libvirt api from my windows machine. It gets created fine it also gets the the IP address from the DHCP also. So all works fine. Now to RDP into the machine what I have to do is 1. logon to my host m