Izik Eidus wrote:
b) It is brute force. I'm not sure it really matters all that much to
limit a 32-bit (non-PAE) guest to 3G, but it's a little extreme for the
cases that don't care about the large hole.
Is there anyway to make it dynamic based on the requirements of the
devices that are part of the launched VM?
There is (you need to transfer data to the bios but it is
possible...), the thing is - there was concern that
it will make windows crazy if you keep changing the devices physical
mapping
Avi what do you think?
It's possible for the bios to size the resources needed by PCI devices
(excluding hotplug) and tell qemu where to map RAM. However I don't
think that's what standard bioses do.
On a barcelona I have here the hole is 0.75GB; I think either 0.5 or 1
GB holes are reasonable. I prefer 1GB so we can accommodate large
assigned framebuffers; I don't see people running 4GB Windows guests
(and Linux guests can use PAE).
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
