Displaying 7 results from an estimated 7 matches for "virt01".
Did you mean:
ovirt01
2010 Aug 30
1
Is it possible to live migrate guest OS'es between different versions of kvm/qemu-kvm with libvirt?
...est to a server running a newer (or
older) version of qemu-kvm, I run into problems. I think this is because
the xml configuration differs slightly between version.
For example, if I try to migrate from a server running qemu-kvm 0.11.0
to one running qemu-kvm 0.12.4, I get the following error:
virt01:~# virsh migrate --live testserver qemu+ssh://192.168.1.7/system
error: internal error unable to reserve PCI address 0:0:3
When migrating from kvm 85 to qemu-kvm 0.11.0:
virt02:~# virsh migrate --live testserver qemu+ssh://192.168.1.2/system
error: Unknown failure
Migrating one from 0.12.4 to 0....
2014 Nov 12
0
[PATCH net] Revert "drivers/net: Disable UFO through virtio" in macvtap and tun
...hings <ben at decadent.org.uk>
> ---
> Compile-tested only.
Jelle, care to test this and reply with "Tested-by: Jelle de Jong
<jelledejong at powercraft.nl>" if it solves the live migration problem you
reported?
It requires applying the patch to the host kernel on your virt01 host.
Thanks!
> Ben.
>
> drivers/net/macvtap.c | 13 ++++++++-----
> drivers/net/tun.c | 19 ++++++++-----------
> 2 files changed, 16 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
> index 6f226de..aeaeb6d 100644
>...
2014 Nov 11
1
[PATCH net] Revert "drivers/net: Disable UFO through virtio" in macvtap and tun
This reverts commit 88e0e0e5aa722b193c8758c8b45d041de5316924 for
the tap drivers, but leaves UFO disabled in virtio_net.
libvirt at least assumes that tap features will never be dropped
in new kernel versions, and doing so prevents migration of VMs to
the never kernel version while they are running with virtio net
devices.
Fixes: 88e0e0e5aa7a ("drivers/net: Disable UFO through virtio")
2014 Nov 11
1
[PATCH net] Revert "drivers/net: Disable UFO through virtio" in macvtap and tun
This reverts commit 88e0e0e5aa722b193c8758c8b45d041de5316924 for
the tap drivers, but leaves UFO disabled in virtio_net.
libvirt at least assumes that tap features will never be dropped
in new kernel versions, and doing so prevents migration of VMs to
the never kernel version while they are running with virtio net
devices.
Fixes: 88e0e0e5aa7a ("drivers/net: Disable UFO through virtio")
2012 Jun 22
1
Fedora 17 GlusterFS 3.3.0 problmes
...5.679652] I [client.c:2142:notify] 0-share-client-7: parent
translators are ready, attempting connect on transport
Given volfile:
+------------------------------------------------------------------------------+
1: volume share-client-0
2: type protocol/client
3: option remote-host virt01.casabi.net
4: option remote-subvolume /export
5: option transport-type tcp
6: option username f0a71b3a-1cb2-4a38-8620-f3853aa90798
7: option password 9641cac2-de93-4621-b94b-9320ada20fd7
8: end-volume
9:
10: volume share-client-1
11: type protocol/client...
2014 Nov 11
7
TUN_F_UFO change breaks live migration
On Tue, Nov 11, 2014 at 12:17:26PM +0000, Ben Hutchings wrote:
> On Tue, 2014-11-11 at 10:58 +0000, Stefan Hajnoczi wrote:
> > Commit 3d0ad09412ffe00c9afa201d01effdb6023d09b4 ("drivers/net: Disable
> > UFO through virtio") breaks live migration of KVM guests from older to
> > newer host kernels:
> >
> >
2014 Nov 11
7
TUN_F_UFO change breaks live migration
On Tue, Nov 11, 2014 at 12:17:26PM +0000, Ben Hutchings wrote:
> On Tue, 2014-11-11 at 10:58 +0000, Stefan Hajnoczi wrote:
> > Commit 3d0ad09412ffe00c9afa201d01effdb6023d09b4 ("drivers/net: Disable
> > UFO through virtio") breaks live migration of KVM guests from older to
> > newer host kernels:
> >
> >