[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-users] Running Xen on current Opteron family?
To run unmodified guests, you do need SVM (AMD
Virtualization Technology, formely codenamed Pacifiica). Nothing else will work.
And by the way, don't expect a 3-5% overhead when running unmodified OS's, it's
just not possible with that type of architecture, without further additions,
such as para-virtualized drivers. This obviously will depend on the amount of
hardware accesses that happen in the system, but it's most likely going to be a
fair bit higher. The 3-5% figure is based on para-virtulized guests, so guests
that have modified source-code. It would be possible to get pretty close to that
by having para-virtualized drivers, so that hardware accesses are not done by
intercepting the actual hardware access and translatiing each individual
hardware access into a packet of data-request for the service OS and then
transferring the result back to the guest with another set of intercepts - each
intercept is quite time-consuming, and a driver that had a more direct interface
(rather than using a "hardware" interface, we'd use a "software" interface, so
the information is more conveniently packaged for the service-OS, and there's
much less need to work out what's going on from multiple hardware accesses).
The current generation of Opteron processors does support
Para-virtualized Xen. There will be new models of Opteron processors
with SVM available later this year - I'm not sure exactly when, as I'm not part
of the team that launches new processors [and of course, even _IF_ I did know, I
would not be allowed to say, as release dates are supposed to
be secret...]
--
Mats
_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |