Aastha Mehta
2013-Sep-08 11:23 UTC
clarification regarding paravirtualized kernel for dom0
Hello, I want to install paravirtualized dom0 kernel (from source) on my machine, but I seem to be missing something. Based on the configuration instructions at http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs, I am trying to configure linux kernel 3.10.10 for dom0 and domU. I do not find the CONFIG_PARAVIRT_GUEST flag in my .config at all. There are CONFIG_PARAVIRT and CONFIG_HYPERVISOR_GUEST (as mentioned that this is available 3.10+ onwards only). Currently the dom0 is installed with hvm capabilities only. # xl info release : 3.10.10-xen ... hw_caps : bfebfbff:28100800:00000000:00007f00:77bae3ff:00000000:00000001:00000281 virt_caps : hvm hvm_directio ... xen_version : 4.4-unstable xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 Am I trying to use a wrong kernel? Is it the case that pvops for dom0 is only available on kernel 2.6.32.x? Thanks, Aastha Mehta _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Matt Wilson
2013-Sep-08 22:40 UTC
Re: clarification regarding paravirtualized kernel for dom0
On Sun, Sep 08, 2013 at 01:23:19PM +0200, Aastha Mehta wrote:> Hello, > > I want to install paravirtualized dom0 kernel (from source) on my machine, > but I seem to be missing something. Based on the configuration instructions > at http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs, I am trying to > configure linux kernel 3.10.10 for dom0 and domU. I do not find the > CONFIG_PARAVIRT_GUEST flag in my .config at all. There are CONFIG_PARAVIRT > and CONFIG_HYPERVISOR_GUEST (as mentioned that this is available 3.10+ > onwards only). Currently the dom0 is installed with hvm capabilities only.Hi Aastha, The "virt_caps" field in "xl info" refers to capabilities of the hypervisor, not the dom0.> # xl info > release : 3.10.10-xen > ... > hw_caps : > bfebfbff:28100800:00000000:00007f00:77bae3ff:00000000:00000001:00000281 > virt_caps : hvm hvm_directio > ... > xen_version : 4.4-unstable > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > > Am I trying to use a wrong kernel? Is it the case that pvops for dom0 is > only available on kernel 2.6.32.x?If you have a system booting with the 3.10.10 kernel and "xl info" works (as it appears to have above), you''ve experienced success. --msw
Aastha Mehta
2013-Sep-08 23:08 UTC
Re: clarification regarding paravirtualized kernel for dom0
Hi Matt, Thank you very much for the clarification. This is good news then. Please also tell, what the xen_caps indicate as well. And, I still have some confusion regarding the different virtualization modes. When we say that we have, for example, a PV on HVM system, does the capability of hypervisor still remain HVM? The new virtualization mode available in xen-4.3 onwards - PV on H - does this only reflect how the guest OS may interact with dom0 and hypervisor? What do these things mean in the context of dom0? Regards On 9 September 2013 00:40, Matt Wilson <msw@linux.com> wrote:> On Sun, Sep 08, 2013 at 01:23:19PM +0200, Aastha Mehta wrote: > > Hello, > > > > I want to install paravirtualized dom0 kernel (from source) on my > machine, > > but I seem to be missing something. Based on the configuration > instructions > > at http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs, I am trying > to > > configure linux kernel 3.10.10 for dom0 and domU. I do not find the > > CONFIG_PARAVIRT_GUEST flag in my .config at all. There are > CONFIG_PARAVIRT > > and CONFIG_HYPERVISOR_GUEST (as mentioned that this is available 3.10+ > > onwards only). Currently the dom0 is installed with hvm capabilities > only. > > Hi Aastha, > > The "virt_caps" field in "xl info" refers to capabilities of the > hypervisor, not the dom0. > > > # xl info > > release : 3.10.10-xen > > ... > > hw_caps : > > bfebfbff:28100800:00000000:00007f00:77bae3ff:00000000:00000001:00000281 > > virt_caps : hvm hvm_directio > > ... > > xen_version : 4.4-unstable > > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > > hvm-3.0-x86_32p hvm-3.0-x86_64 > > > > Am I trying to use a wrong kernel? Is it the case that pvops for dom0 is > > only available on kernel 2.6.32.x? > > If you have a system booting with the 3.10.10 kernel and "xl info" > works (as it appears to have above), you''ve experienced success. > > --msw >-- Aastha Mehta MPI-SWS, Germany E-mail: aasthakm@mpi-sws.org <aasthakm@gmail.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Ian Campbell
2013-Sep-09 12:25 UTC
Re: clarification regarding paravirtualized kernel for dom0
On Mon, 2013-09-09 at 01:08 +0200, Aastha Mehta wrote: Please don''t top post.> Thank you very much for the clarification. This is good news then. > Please also tell, what the xen_caps indicate as well. And, I still > have some confusion regarding the different virtualization modes. When > we say that we have, for example, a PV on HVM system, does the > capability of hypervisor still remain HVM?PV and HVM (and PVH) are properties of the guest, not the hypervisor. The hypervisors ability to support HVM guests is predicated on the presence of the necessary hardware virtualisation features.> The new virtualization mode available in xen-4.3 onwards - PV on H - > does this only reflect how the guest OS may interact with dom0 and > hypervisor? What do these things mean in the context of dom0?PVH Is a new type of guest. Dom0 will be able to use PVH mode. Currently it can only be PV, not HVM. These modes have nothing to do with how a guest OS interacts with dom0. You might find it useful to have a look through some pof the wiki docs which go into the types of domain, perhaps starting from http://wiki.xen.org/wiki/Xen_Overview . http://wiki.xen.org/wiki/Virtualization_Spectrum too Ian.