WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] domU guest for xcp 0.1.1

On Sat, Mar 13, 2010 at 08:09:36AM -0800, Ritu kaur wrote:
>    Thanks again. As I understand from wiki page, Jeremy's xen.git and
>    xen/stable code are for building dom0 kernel. Can dom0 kernel be used as a
>    domU? At least last time I checked I was told I cannot use it.
> 

Yes, you can use the dom0 kernel also as domU, just make sure you build 
the frontend drivers aswell.

Actually you've been able to use the same kernel for both dom0 and domU for 
years,
this is how distributions like RHEL5/CentOS5, Debian etch/lenny, Fedora 6/7/8,
SLES10/11, OpenSUSE, etc ship their kernels. The same kernel image works for 
both dom0 and domU.

Actually pvops makes it possible to boot the exact same kernel image on 
baremetal (non-Xen),
Xen dom0 and domU!

-- Pasi

>    Thanks
> 
>    On Sat, Mar 13, 2010 at 3:18 AM, Pasi Kärkkäinen <[1]pasik@xxxxxx> wrote:
> 
>      On Fri, Mar 12, 2010 at 05:51:20PM -0800, Ritu kaur wrote:
>      >    Thanks Pasi. I looked at
>      >    [1][2]http://wiki.xensource.com/xenwiki/XenParavirtOps(my foray
>      into linux is
>      >    via xen, so please pardon by silly questions)
>      >
>      > Using Xen/paravirt_ops
>      >
>      >   Building with domU support
>      >
>      >     1. Get a current kernel. The latest [2][3]kernel.org kernel is
>      generally a
>      >        good choice.
>      >     2. Configure as normal; you can start with your current .config
>      file
>      >     3. If building 32 bit kernel make sure you have CONFIG_X86_PAE
>      enabled
>      >        (which is set by selecting CONFIG_HIGHMEM64G)
>      >
>      >           * non-PAE mode doesn't work in 2.6.25, and has been dropped
>      >             altogether from 2.6.26 and newer kernel versions.
>      >
>      >     4. Enable these core options:
>      >
>      >          1. CONFIG_PARAVIRT_GUEST
>      >          2. CONFIG_XEN
>      >
>      >     5. And Xen pv device support
>      >
>      >          1. CONFIG_HVC_DRIVER and CONFIG_HVC_XEN
>      >          2. CONFIG_XEN_BLKDEV_FRONTEND
>      >          3. CONFIG_XEN_NETDEV_FRONTEND
>      >
>      >     6. And build as usual
>      >
>      >    Config doesn't have pcifront in it? don't I need it for pci
>      passthrough? I
>      >    have copied linux 2.6.33 source from [3][4]kernel.org and started
>      building
>      >    kernel(irrespective of above questions), but what distribution is
>      this
>      >    kernel associated with i.e I thought I should first install linux
>      from a
>      >    distribution and rebuild kernel for any modification, but in this
>      case I
>      >    don't understand what distribution this is associated with. Inputs
>      much
>      >    appreciated.
>      >
> 
>      You need to check out Jeremy's xen.git, and possibly xen/stable branch
>      from there,
>      to have the pcifront driver. It's not yet in the upstream [5]kernel.org
>      kernel.
> 
>      -- Pasi
> 
>      >    Thanks
>      >
>      >    On Fri, Mar 12, 2010 at 9:51 AM, Pasi Kärkkäinen
>      <[4][6]pasik@xxxxxx> wrote:
>      >
>      >      On Fri, Mar 12, 2010 at 09:10:31AM -0800, Ritu kaur wrote:
>      >      >    Hi,
>      >      >
>      >      >    I am expanding my question to developers forum to get some
>      quick
>      >      help on
>      >      >    pci passthrough. I am using xcp 0.1.1 as a dom0 and
>      installed
>      >      Debian Lenny
>      >      >    as a domU(as mentioned in
>      >      >
>       [1][5][7]http://wiki.xensource.com/xenwiki/Command_Line_Interface).
>      >      >    Unfortunately, Debian Lenny which the wiki points to doesn't
>      come
>      >      with PV
>      >      >    drivers(I need pcifront driver). I looked up in
>      >      [2][6][8]wiki.debian.org/Xen and
>      >      >    I found following snippets
>      >      >
>      >      >    /***The default Lenny kernel is the newer paravirt_ops
>      version
>      >      (2.6.26),
>      >      >    which does not function as a dom0 (except for the -xen
>      variants,
>      >      which
>      >      >    have dom0 support but also some issues running as domU
>      (please
>      >      clarify?).
>      >      >    It will also not support PCI passthrough in a domU. For PCI
>      >      passthrough,
>      >      >    you have to run the 2.6.18 etch kernel as both dom0 and
>      domU. ***/
>      >      >
>      >
>      >      I don't know if there are pre-packaged kernels for lenny with
>      pcifront
>      >      driver.
>      >
>      >      Links to kernel sources that have the pcifront driver:
>      >
>      >             - [7][9]http://xenbits.xen.org/linux-2.6.18-xen.hg
>      >             - pv_ops xen.git xen/stable 2.6.32.9 and xen/master
>      2.6.31.6
>      >               (See:
>      [8][10]http://wiki.xensource.com/xenwiki/XenParavirtOps)
>      >             - Kernels with the forward-ported Novell/opensuse Xen
>      patches
>      >      (2.6.29, 2.6.31, 2.6.33)
>      >               (See:
>      [9][11]http://wiki.xensource.com/xenwiki/XenDom0Kernels)
>      >      >    Can someone let me know what domU has been tested with XCP
>      0.1.1
>      >      for pci
>      >      >    passthrough and any pointers to that domU kernel binary or
>      source
>      >      will
>      >      >    help me out.
>      >      >
>      >
>      >      Unfortunately I don't know what kernel has been tested.
>      >      -- Pasi
>      >
>      > References
>      >
>      >    Visible links
>      >    1. [12]http://wiki.xensource.com/xenwiki/XenParavirtOps(my
>      >    2. [13]http://kernel.org/
>      >    3. [14]http://kernel.org/
>      >    4. mailto:[15]pasik@xxxxxx
>      >    5. [16]http://wiki.xensource.com/xenwiki/Command_Line_Interface
>      >    6. [17]http://wiki.debian.org/Xen
>      >    7. [18]http://xenbits.xen.org/linux-2.6.18-xen.hg
>      >    8. [19]http://wiki.xensource.com/xenwiki/XenParavirtOps
>      >    9. [20]http://wiki.xensource.com/xenwiki/XenDom0Kernels
> 
> References
> 
>    Visible links
>    1. mailto:pasik@xxxxxx
>    2. http://wiki.xensource.com/xenwiki/XenParavirtOps%28my
>    3. http://kernel.org/
>    4. http://kernel.org/
>    5. http://kernel.org/
>    6. mailto:pasik@xxxxxx
>    7. http://wiki.xensource.com/xenwiki/Command_Line_Interface
>    8. http://wiki.debian.org/Xen
>    9. http://xenbits.xen.org/linux-2.6.18-xen.hg
>   10. http://wiki.xensource.com/xenwiki/XenParavirtOps
>   11. http://wiki.xensource.com/xenwiki/XenDom0Kernels
>   12. http://wiki.xensource.com/xenwiki/XenParavirtOps%28my
>   13. http://kernel.org/
>   14. http://kernel.org/
>   15. mailto:pasik@xxxxxx
>   16. http://wiki.xensource.com/xenwiki/Command_Line_Interface
>   17. http://wiki.debian.org/Xen
>   18. http://xenbits.xen.org/linux-2.6.18-xen.hg
>   19. http://wiki.xensource.com/xenwiki/XenParavirtOps
>   20. http://wiki.xensource.com/xenwiki/XenDom0Kernels

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel