On Wed, 2007-11-21 at 09:13 +0200, Avi Kivity wrote:
> Where the device is implemented is an implementation detail that should
> be hidden from the guest, isn't that one of the strengths of
> virtualization? Two examples: a file-based block device implemented in
> qemu gives you fancy file for
Hi all,
I've been looking at the next steps to try to get Xen running fully on
top of pv_ops. To that end, I've (just) started looking at one of the
next major jobs --- i686 dom0 on pv_ops.
There are still a number of things needing done to reach parity with
xen-unstable:
x86_64 xen on pv_ops
Zachary Amsden wrote:
On Wed, 2007-11-21 at 09:13 +0200, Avi Kivity wrote:
Where the device is implemented is an implementation detail that should
be hidden from the guest, isn't that one of the strengths of
virtualization? Two examples: a file-based block device implemented in
qemu gives
