[RFC] First (incomplete) cut of Xen paravirt binding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> From: virtualization-bounces at lists.osdl.org 
> [mailto:virtualization-bounces at lists.osdl.org] On Behalf Of 
> Rusty Russell
> 
> 2) The hypervisor type is handed through %ebx to the startup_paravirt
>    function at boot.  Currently 0 = Xen 3.0, 1 = VMI.

I think this is a really really bad idea because you're requiring that
all operating systems agree on these values or you impose it upon the
hypervisor's domain builder to be operating system specific.  I really
don't think either of those are very appealing, especially considering
that there's a much simpler solution using hypervisor specific entry
points.

That said, %ebx = 0 works for us, so maybe I should just not care...

    Christian



[Index of Archives]     [KVM Development]     [Libvirt Development]     [Libvirt Users]     [CentOS Virtualization]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux