Automatically allocate PCI addresses for devices instead
of hardcoding them in the driver code. The current
allocation schema is to dedicate an entire slot for each devices.
Also, allow having arbitrary number of devices.
---
po/POTFILES.in | 1 +
src/Makefil
Introduce new files (domain_addr.[ch]) to provide
an API for domain device handling that could be
shared across the drivers.
A list of data types were extracted and moved there:
qemuDomainPCIAddressBus -> virDomainPCIAddressBus
qemuDomainPCIAddressBusPtr -> virDomainPCIAddressBusPtr
_qemuDomai
Changes from v3:
- Instead of adding pci allocation code to utils/virpci.[ch],
create new files conf/domain_addr.[ch] to contain only
domain device addresses management
Changes from v2:
- Base on PCI allocation code from Qemu driver
Changes from v1:
- Reserve slot 1 for LPC PCI-ISA brid
Hi,
Is it accurate to say that:
*To virtualize the hardware memory, VMware ESX forces the real hardware MMU
point to the shadow page table.*
I guess it's true, isn't it?
Sincerely,
Matthew
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
2014-04-25 20:20 GMT+02:00 Dawid Zamirski :
> Since the ESX storage implements VMFS and iSCSI storage backends and
> chooses relevant backend dynamically at runtime, there was a segfault
> when issuing vol-info on iSCSI volume due to unimplemented
> virStorageGetInfo function. This patch implements
2014-05-06 10:10 GMT+02:00 Martin Kletzander :
> On Mon, May 05, 2014 at 01:48:03PM -0600, Eric Blake wrote:
>>
>> On 05/05/2014 03:47 AM, Martin Kletzander wrote:
>>>
>>> Signed-off-by: Martin Kletzander
>>> ---
>>> docs/drvesx.html.in | 14 ++
>>> src/esx/esx_util.c | 13 ++
The original implementation of the VMX config parser assumed that the
virtualHW.version would have more influence on the content of the VMX
file than it actually seems to have. It started with accepting only
version 4. Additonal versions were added later without any additional
changes in the parser