05-Jan-17 19:53, John Ferlan пишет:
On 12/09/2016 09:28 AM, Maxim Nestratov wrote:
As specifying both QEMU_CAPS_NO_KVM_PIT and QEMU_CAPS_KVM_PIT_TICK_POLICY
capabilities has no practical sense in tests, and we already have tests
for QEMU_CAPS_KVM_PIT_TICK_POLICY, it's better to add a separate
On 12/09/2016 09:28 AM, Maxim Nestratov wrote:
> As specifying both QEMU_CAPS_NO_KVM_PIT and QEMU_CAPS_KVM_PIT_TICK_POLICY
> capabilities has no practical sense in tests, and we already have tests
> for QEMU_CAPS_KVM_PIT_TICK_POLICY, it's better to add a separate one with
> QEMU_CAPS_NO_KVM_PIT s
As specifying both QEMU_CAPS_NO_KVM_PIT and QEMU_CAPS_KVM_PIT_TICK_POLICY
capabilities has no practical sense in tests, and we already have tests
for QEMU_CAPS_KVM_PIT_TICK_POLICY, it's better to add a separate one with
QEMU_CAPS_NO_KVM_PIT set.
Signed-off-by: Maxim Nestratov
---
.../qemuxml2arg
