From: "Michael R. Hines"
The switch from x-rdma => rdma has not yet happened,
but at least we can review the patch until it goes
through on qemu-devel.
USAGE: $ virsh migrate --live --migrateuri x-rdma:hostname domain
qemu+ssh://hostname/system
Full documenation of the feature:
http://wiki.qe
From: "Michael R. Hines"
Changes since v1:
1. This series uses 'rdma' instead of 'x-rdma', even though QEMU
has has not yet renamed URI for live migraiton yet, but this
series is just an RFC, so at least we can get some agreement.
2. We've fixed the job stats to be in the right place inst
From: "Michael R. Hines"
RDMA Live migration requires registering memory with the hardware,
and thus QEMU offers a new 'capability' which supports the ability
to pre-register / mlock() the guest memory in advance for higher
RDMA performance before the migration begins.
This patch exposes this ca
From: "Michael R. Hines"
RDMA migration uses the 'setup' state in QEMU to optionally lock
all memory before the migration starts. The total time spent in
this state is already exposed by QEMU, so expose it in libvirt.
Additionally, QEMU also now exports migration throughput (mbps),
so let's see
On Sun, Jan 12, 2014 at 6:09 PM, Teto wrote:
> Hi,
> Thanks to your advice, I was able to make it work using nokogiri.
> I am now trying to attach new devices (shared folders) via my custom function:
> =
> def attach_device(uuid , device)
> puts "CAlled with uuid #{uuid}"
>
>
Hi,
Thanks to your advice, I was able to make it work using nokogiri.
I am now trying to attach new devices (shared folders) via my custom function:
=
def attach_device(uuid , device)
puts "CAlled with uuid #{uuid}"
client.lookup_domain_by_uuid(uuid).update_device(d
On 11.01.2014 04:06, yue wrote:
> hi, Michal Privoznik
>
> i am a bit confusion about type of vm's interface .
> and
> do the Qos in libvirt can apply to both case?
>
>
> thanks
>
>
Yes, the works on both.
Michal
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/
