On 10/02/2018 08:50 AM, Olivier Léobal wrote:
Hello,
'Isolated' networks created in VMM (I’m running 1.4.3) still connect to
the host (as gateway). Is it possible to avoid this? It is my
understanding that QEMU provides a 'restrict' option for that, but I
don't understand it well, and can’t
On 10/02/2018 09:53 AM, Cole Robinson wrote:
> On 10/02/2018 08:50 AM, Olivier Léobal wrote:
>> Hello,
>>
>> 'Isolated' networks created in VMM (I’m running 1.4.3) still connect
>> to the host (as gateway). Is it possible to avoid this? It is my
>> understanding that QEMU provides a 'restrict'
I'm trying the following command on the source machine:
virsh migrate --live --copy-storage-all --verbose TEST qemu+ssh://
10.30.76.66/system
If I ssh into the destination machine when this command is running, I can
see NBD copying data as expected, and if I wait long enough it completes
and
For anyone who might find this thread from online searching, I was able to
determine this commit fixes the above issue:
https://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=dddcb601ebf97ef222a03bb27b2357e831e8a0cc
On Tue, Oct 2, 2018 at 8:42 AM Scott Sullivan <
scottgregorysulli...@gmail.com>
On 02/10/2018 09:19, Andrea Bolognani wrote:
Your assessment looks correct, and the controller is indeed compiled
out downstream. Filing a BZ sounds like a reasonable next step, but
you might also want to investigate virt-v2v, which I believe will
take care of switching to the more performant
On Tue, 2018-10-02 at 10:11 +0200, Gionatan Danti wrote:
> On 02/10/2018 09:19, Andrea Bolognani wrote:
> > Your assessment looks correct, and the controller is indeed compiled
> > out downstream. Filing a BZ sounds like a reasonable next step, but
> > you might also want to investigate virt-v2v,
