[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 4/8] i386/kvm: implement 'hv-all' pass-through m
From: |
Vitaly Kuznetsov |
Subject: |
Re: [Qemu-devel] [PATCH 4/8] i386/kvm: implement 'hv-all' pass-through mode |
Date: |
Fri, 29 Mar 2019 17:03:32 +0100 |
"Dr. David Alan Gilbert" <address@hidden> writes:
> Yep, that's probably safest; although if you recorded the features used
> in the migration stream you could check for those on the destination and
> if they mismatch complain then.
>
There is no clear use-case for hv-all other than development at this
moment; as Daniel previously stated we may never support it in
libvirt. I decided to take the easiest path first and think about
migration later, when we understand why we would want to migrate such
guests.
In theory, yes, we may compare Hyper-V feature words on source and
destination and allow migration when the former is a subset of the
later.
--
Vitaly
- [Qemu-devel] [PATCH 0/8] i386/kvm/hyper-v: refactor and implement 'hv-stimer-direct' and 'hv-all' enlightenments, Vitaly Kuznetsov, 2019/03/29
- [Qemu-devel] [PATCH 8/8] i386/kvm: add support for Direct Mode for Hyper-V synthetic timers, Vitaly Kuznetsov, 2019/03/29
- [Qemu-devel] [PATCH 6/8] i386/kvm: hv-stimer requires hv-time and hv-synic, Vitaly Kuznetsov, 2019/03/29
- [Qemu-devel] [PATCH 1/8] i386/kvm: add support for KVM_GET_SUPPORTED_HV_CPUID, Vitaly Kuznetsov, 2019/03/29
- [Qemu-devel] [PATCH 4/8] i386/kvm: implement 'hv-all' pass-through mode, Vitaly Kuznetsov, 2019/03/29
- [Qemu-devel] [PATCH 2/8] i386/kvm: move Hyper-V CPUID filling to hyperv_handle_properties(), Vitaly Kuznetsov, 2019/03/29
- [Qemu-devel] [PATCH 3/8] i386/kvm: document existing Hyper-V enlightenments, Vitaly Kuznetsov, 2019/03/29
- [Qemu-devel] [PATCH 5/8] i386/kvm: hv-evmcs requires hv-vapic, Vitaly Kuznetsov, 2019/03/29
- [Qemu-devel] [PATCH 7/8] i386/kvm: hv-tlbflush/ipi require hv-vpindex, Vitaly Kuznetsov, 2019/03/29