Re: Thoughts about introducing virtio-cpu

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>  This will also have a lot of churn in the guest operating
>>> systems.
>>
>> Do you have some examples in mind?
>>
>>>
>>> Is your main goal to avoid ACPI?
>>
>> Yes. In the context of supporting general hotplug
>> (CPU/Memory/devices(PCI)), CPU is the last bit that will force us to
>> use ACPI.
>>
> 
> This may also have problem on Windows guest. CPU info needs to
> be enumerated at early boot time. Not sure whether Windows 
> provides such hook to install a new CPU enumeration driver other
> than ACPI.

The same applies to virtio-mem (there are MM interfaces in Windows used
by Hyper-V that could allow to make it work, however they are marked as
not supported). At least for virtio-mem, only Linux is the focus for
now. We can't fix closed-source operating systems, Microsoft itself
would have to provide new interfaces, or mark the existing once as
supported.

> 
> Thanks
> Kevin
> 
> 


-- 

Thanks,

David / dhildenb



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux