On Thu, Jun 08, 2006 at 01:07:15PM +0100, Ian Pratt wrote:
> Great!
>
> I think the updated task list probably looks something like:
> 1. update qemu-dm to use latest QEMU version (Christian is working on
> this)
> 2. modify the xen/qemu interface to use the 'v2e' approach (Leendert is
> looking at this)
> 3. implement 'stub domains' -- rings 1-3 in the root VMCS (normally
> used by PV guests) are free for use in HVM domains (we need to have some
> discussion on the best way of doing this [*])
Is anyone currently working on this? Have any discussions been had
previously about the best way to hook the stub domain into the HVM
domain?
It looks like this work may have to be done outside of the xen-unstable
tree, especially if we're modifying xen data structures. Will there 
be/is there a public tree available for this effort? 
Thanks,
Natasha
> 4. run linux in the stub domain with qemu running from an initrd
> 5a. link qemu directly against the linux kernel to avoid system calls
> 5b. or, link qemu against minios if we have IO support in minios.
>
> Thanks,
> Ian
>
> [*] do we have a separate domain struct that the scheduler knows is
> actually the same as another domain for scheduling/accounting purposes,
> or do we modify the domain struct so hvm and pv guests don't share the
> same fields? Probably the latter. 
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel