From: Ritu kaur <ritu.kaur.us@gmail.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
Subject: Re: domU guest for xcp 0.1.1
Date: Sat, 13 Mar 2010 08:09:36 -0800 [thread overview]
Message-ID: <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> (raw)
In-Reply-To: <20100313111857.GS1878@reaktio.net>
[-- Attachment #1.1: Type: text/plain, Size: 4942 bytes --]
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.
Thanks
On Sat, Mar 13, 2010 at 3:18 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> On Fri, Mar 12, 2010 at 05:51:20PM -0800, Ritu kaur wrote:
> > Thanks Pasi. I looked at
> > [1]http://wiki.xensource.com/xenwiki/XenParavirtOps(my<http://wiki.xensource.com/xenwiki/XenParavirtOps%28my>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]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]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 kernel.orgkernel.
>
> -- Pasi
>
> > Thanks
> >
> > On Fri, Mar 12, 2010 at 9:51 AM, Pasi Kärkkäinen <[4]pasik@iki.fi>
> 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]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]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]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]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]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. http://wiki.xensource.com/xenwiki/XenParavirtOps(my<http://wiki.xensource.com/xenwiki/XenParavirtOps%28my>
> > 2. http://kernel.org/
> > 3. http://kernel.org/
> > 4. mailto:pasik@iki.fi
> > 5. http://wiki.xensource.com/xenwiki/Command_Line_Interface
> > 6. http://wiki.debian.org/Xen
> > 7. http://xenbits.xen.org/linux-2.6.18-xen.hg
> > 8. http://wiki.xensource.com/xenwiki/XenParavirtOps
> > 9. http://wiki.xensource.com/xenwiki/XenDom0Kernels
>
[-- Attachment #1.2: Type: text/html, Size: 7129 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-03-13 16:09 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 17:10 domU guest for xcp 0.1.1 Ritu kaur
2010-03-12 17:51 ` Pasi Kärkkäinen
2010-03-13 1:51 ` Ritu kaur
2010-03-13 11:18 ` Pasi Kärkkäinen
2010-03-13 16:09 ` Ritu kaur [this message]
2010-03-13 16:41 ` Pasi Kärkkäinen
2010-03-14 1:43 ` Ritu kaur
2010-03-14 9:04 ` pvops xen/master and xen/stable domU kernel compilation errors Pasi Kärkkäinen
2010-03-14 11:15 ` domU guest for xcp 0.1.1 Sander Eikelenboom
2010-03-14 20:29 ` Ritu kaur
2010-03-14 20:52 ` Sander Eikelenboom
2010-03-15 1:40 ` Ritu kaur
2010-03-15 3:30 ` Ritu kaur
2010-03-15 8:44 ` Ian Campbell
2010-03-15 13:42 ` Ritu kaur
2010-03-15 13:44 ` Ian Campbell
2010-03-15 13:46 ` Ritu kaur
2010-03-16 2:04 ` Ritu kaur
2010-03-16 7:37 ` Ian Campbell
2010-03-16 15:23 ` Pasi Kärkkäinen
2010-03-16 23:25 ` Ritu kaur
2010-03-17 18:44 ` Ritu kaur
2010-03-18 9:17 ` Ian Campbell
2010-03-18 13:43 ` Ritu kaur
2010-03-18 14:11 ` Ian Campbell
2010-03-18 14:23 ` Ritu kaur
2010-03-18 14:27 ` Ian Campbell
2010-03-18 14:32 ` Ian Campbell
2010-03-18 14:39 ` Konrad Rzeszutek Wilk
2010-03-18 15:28 ` Ritu kaur
2010-03-18 16:26 ` Konrad Rzeszutek Wilk
2010-03-19 15:27 ` Ritu kaur
2010-03-21 1:50 ` Ritu kaur
2010-03-21 17:22 ` Ritu kaur
2010-03-21 18:41 ` Pasi Kärkkäinen
2010-03-21 21:21 ` Ritu kaur
2010-03-22 8:58 ` Pasi Kärkkäinen
2010-03-22 21:02 ` Ritu kaur
2010-03-22 21:09 ` Pasi Kärkkäinen
2010-03-23 20:21 ` Ritu kaur
2010-03-26 19:11 ` Ritu kaur
2010-03-27 18:28 ` Ritu kaur
2010-03-27 18:43 ` Pasi Kärkkäinen
2010-03-28 1:32 ` Ritu kaur
2010-03-28 3:21 ` Ritu kaur
2010-03-28 11:34 ` Pasi Kärkkäinen
2010-03-28 11:55 ` Pasi Kärkkäinen
2010-03-31 0:28 ` Ritu kaur
2010-03-31 1:07 ` Ritu kaur
2010-03-31 6:30 ` Pasi Kärkkäinen
2010-03-31 13:15 ` Ritu kaur
2010-03-31 13:42 ` Konrad Rzeszutek Wilk
2010-03-31 13:55 ` Ritu kaur
2010-03-31 14:39 ` Pasi Kärkkäinen
2010-03-31 21:10 ` Ritu kaur
2010-04-01 12:48 ` Ritu kaur
2010-04-05 14:10 ` Ritu kaur
2010-04-05 17:00 ` Konrad Rzeszutek Wilk
2010-04-06 4:00 ` Ritu kaur
2010-04-06 6:03 ` Pasi Kärkkäinen
2010-04-06 13:31 ` Ritu kaur
2010-04-09 15:53 ` Ritu kaur
2010-04-11 17:11 ` Ritu kaur
2010-04-12 14:04 ` Konrad Rzeszutek Wilk
2010-04-12 22:14 ` Ritu kaur
2010-04-13 8:34 ` Ian Campbell
2010-04-13 22:06 ` Ritu kaur
2010-04-14 8:48 ` Ian Campbell
2010-03-28 11:33 ` Pasi Kärkkäinen
2010-03-31 23:23 ` Ritu kaur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com \
--to=ritu.kaur.us@gmail.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).