From: Andrew Lyon <andrew.lyon@gmail.com>
To: Mike Viau <viaum@sheridanc.on.ca>
Cc: bderzhavets@yahoo.com, xen-devel@lists.xensource.com,
xen-users@lists.xensource.com
Subject: Re: RE: [Xen-users] (Xenlinux) gentoo-xen-kernel patches questions?
Date: Sat, 3 Apr 2010 15:17:47 +0100 [thread overview]
Message-ID: <m2tf4527be1004030717oa5c03ea4y835c8541da782002@mail.gmail.com> (raw)
In-Reply-To: <BAY107-W19E5BB6E9E30C95EB76D65EF1B0@phx.gbl>
[-- Attachment #1.1: Type: text/plain, Size: 6168 bytes --]
On Sat, Apr 3, 2010 at 4:11 AM, Mike Viau <viaum@sheridanc.on.ca> wrote:
> Fri, 2 Apr 2010 17:21:35 -0700 <bderzhavets@yahoo.com> wrote:
>
> >>Would compiling the pv_ops kernel from the git repository produce any
> additional stability?
>
> >Good question. It completely depends on speed of your internet connection
> and :-
> ># git checkout -b xen/linux-2.6.32.X-stable
> origin/xen/linux-2.6.32.X-stable
> ># make menuconfig ( to enable Xen Dom0 support)
> ># make -j(x)number_of_cores
> ># make modules_install install
> ># mkinitramfs -o /boot/initrd-2.6.32.10.img 2.6.32.10
>
> Yes I was in my plans to compare the debian pvops kernel against a pvops
> compiled kernel from Jeremy's git repo.
>
> Additionally I hoped to acquire a 2.6.33 Xenified kernel .config to compile
> a forward ported 2.6.33 Xenlinux kernel for testing with.
>
Hi Mike,
I depreciated the 2.6.33 patches because they turned out to be very
unstable, I've left 2.6.31 because it is very much stable, in fact in the
next few days I have a updated 2.6.31 patchset and ebuild to release which I
hope to get unmasked in Gentoo portage so that it is just keyword ~ rather
than being masked out as it currently is.
I've also got a 2.6.32 ebuild which is stable so far on all of my Xen
systems, provided there are no problems in the next few days I will release
that as well, both .31 and .32 will be maintained for a while as they are
the official kernels for openSUSE 11.2 and SLE 11 SP1.
While there are branches in the openSUSE/Novell git tree for openSUSE 11.2
and SLE11-SP1 the master tree tracks kernel.org and has already passed
2.6.33 so there doesn't seem much value in trying to make a Xenlinux forward
ported 2.6.33, I might do .34 when it is released but I tend to wait until
they branch for a distro release so that there is long-term support.
I release these patches because people have asked me to, and I make them
because pv_ops is not fully functional yet and doesn't work with all of the
3rd party kernel modules etc that I have to use, for example I run Xen on 3
very powerful workstations and all of them have nvidia and acronis snapapi
drivers loaded.
Andy
> My current 2.6.33 .config is attached. I was hoping to have acquired a more
> generic config rather than just targeting primarily for my system. I do not
> mind if it will take longer to build the kernel :-)
>
> Thanks.
>
>
> -M
>
>
> --- On *Fri, 4/2/10, Mike Viau <viaum@sheridanc.on.ca>* wrote:
>
>
> >>Hi,
> >>
> >>I noticed that the Xenlinux 2.6.33 patches are tagged as being
> "Deprecated" but the 2.6.31 are not.
> >>
> >>May I ask why?
> >>
>
> >>http://code.google.com/p/gentoo-xen-kernel/downloads/list?can=1&q=&colspec=Filename+Summary+Uploaded+Size+DownloadCount<http://code.google.com/p/gentoo-xen-kernel/downloads/list?can=1&q=&colspec=Filename+Summary+Uploaded+Size+DownloadCount>
> >>
> >>
> > Fri, 2 Apr 2010 13:15:09 -0400 <konrad.wilk@oracle.com> wrote:
> >
> > No idea. But those patches are pursuing an entirely different method of
> > getting Linux to work in privileged state (Dom0). The current
> > development is with the pv-ops one:
> >
> > http://wiki.xensource.com/xenwiki/XenParavirtOps
> >
>
> I am currently using the unstable version of debain's pvops xen kernel.
>
> http://packages.debian.org/sid/linux-image-2.6.32-4-xen-amd64
>
> It appears to have functioning networking and block devices which is nice,
> but I have experienced some instabilities such as kernel dumping on reboots.
> Unfortunately I do not have a console setup to log kernel messages for this
> machine.
>
> Would compiling the pv_ops kernel from the git repository produce any
> additional stability?
>
> It was my understanding that one could run a stable Xen systems today with
> a Xenlinux kernel, as pv_ops was still in development. I've read on the
> XenParavirtsOps page that there are features available to Xen but are not
> yet available in the pv_ops kernel (perhaps this wiki has not been updated
> as I understand Xen 4.0 release is just around the corner!):
>
>
>
> - Work in progress:
> - dom0 support, currently planned for Linux 2.6.35 (latest pv_ops
> dom0 patches can be found from jeremy's git tree, see instructions below)
> - pv-on-hvm driver support
> - Balloon expansion (using memory hotplug) to grow bigger than
> initial domU memory size
> - To be done:
> - Device hotplug
> - Other device drivers
> - kdump/kexec
> - pvscsi backend (dom0)
> - pvusb backend (dom0)
> - ...?
>
>
>
> >>Also is there somewhere one could view list xen features added into linux
> kernel source (e.g: netchannel2, blktap, etc) ?
> >>
>
> Does anyone have a graph or something showing the state of these Xen
> features/modules in the two predominate Dom 0 capable kernels (Xenlinux &
> PV_OPS) to share or post to a wiki?
>
> root@localhost:~# tree /lib/modules/2.6.32-4-xen-amd64/kernel/drivers/xen
> /lib/modules/2.6.32-4-xen-amd64/kernel/drivers/xen
> |-- blktap
> | `-- blktap.ko
> |-- xen-evtchn.ko
> `-- xenfs
> `-- xenfs.ko
>
> 2 directories, 3 files
>
> Other XEN features are compiled as (=y) in the unstable version of debain's
> pvops xen kernel .config file.
>
> >>
> >>Lastly could someone provide perhaps a few xenlinux kernel .configs that
> works. I have attached my working config used with 2.6.33 source, but I am
> hoping to get a copy of a more generic + working .config
> >>
>
> Recently pv_ops kernel configs for both the 2.6.31 and 2.6.32 kernels have
> been in circulation. Can anyone share some .configs that were used on
> Xenlinux kernels (not 2.6.18) when they were in their prime?
>
>
> Thanks!
>
>
> -M
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com<http:///mc/compose?to=Xen-users@lists.xensource.com>
> http://lists.xensource.com/xen-users
>
>
>
> ------------------------------
> Live connected. Get Hotmail & Messenger for mobile.<http://go.microsoft.com/?linkid=9724459>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
[-- Attachment #1.2: Type: text/html, Size: 8576 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-04-03 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 3:11 RE: [Xen-users] (Xenlinux) gentoo-xen-kernel patches questions? Mike Viau
2010-04-03 3:18 ` Mike Viau
2010-04-03 14:17 ` Andrew Lyon [this message]
2010-04-03 14:49 ` [Xen-devel] " Mike Viau
2010-04-04 12:59 ` Andrew Lyon
-- strict thread matches above, loose matches on Subject: below --
2010-04-02 18:03 Mike Viau
2010-04-05 18:17 ` RE: [Xen-users] " Jeremy Fitzhardinge
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=m2tf4527be1004030717oa5c03ea4y835c8541da782002@mail.gmail.com \
--to=andrew.lyon@gmail.com \
--cc=bderzhavets@yahoo.com \
--cc=viaum@sheridanc.on.ca \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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).