Re: xen.git branch reorg - patches for dom0 in 2.6.29 or 2.6.30?

[Boris Derzhavets <bderzhavets@yahoo.com>]

[-- Attachment #1.1: Type: text/plain, Size: 3326 bytes --]

************************

Update on 04/23/2009

************************

Per Jeremy Fitzhardinge :-

The new branch structure is similar to the old one in overall layout.  There are two “merged” branches:

* xen-tip/master - will try to keep as a known-working branch, with   only tested changes

* xen-tip/next - current bleeding edge; should at least compile

Just a way to build on Ubuntu Server 8.10 (64-bit) :-

# cd /usr/src

# hg clone http://xenbits.xensource.com/xen-unstable.hg

# cd xen-unstable.hg

# make xen

# make install-xen

# make tools

# make install-tools



Install packages



# apt-get install build-essential libncurses5-dev gawk mercurial



To check out a working tree, use :-



# git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen

# cd linux-2.6-xen
# git checkout origin/xen-tip/next -b xen-tip/next
# make menuconfig
# make

# make modules_install install
# mkinitramfs -o /boot/initrd-2.6.30-rc3-tip.img 2.6.30-rc3-tip



Add to /etc/fstab :-



none /proc/xen xenfs defaults 0 0



Boot with grub entry :-



title Xen 3.4 / Ubuntu 8.10, kernel 2.6.29-tip

uuid    9efba9a5-9f2b-4bf6-b8b5-7d6d53eb02d9

kernel  /boot/xen-3.4.gz

module  /boot/vmlinuz-2.6.30-rc3-tip root=/dev/sdb14 ro console=tty0

module  /boot/initrd-2.6.30-rc3-tip.img

Details:-
http://bderzhavets.wordpress.com/2009/03/29/setup-xen-unstable-dom0-with-2629-tip-pvops-enabled-kernel/

Boris



--- On Mon, 4/27/09, Anthony Wright <anthony@overnetdata.com> wrote:
From: Anthony Wright <anthony@overnetdata.com>
Subject: Re: [Xen-devel] xen.git branch reorg - patches for dom0 in 2.6.29 or 2.6.30?
To: xen-devel@lists.xensource.com
Cc: jeremy@goop.org
Date: Monday, April 27, 2009, 10:17 AM

Jeremy Fitzhardinge wrote:
>Pasi Kärkkäinen wrote:
>>Btw how does dom0 upstreaming look at the moment? Ingo sent pull
>>request about some changes, and those got merged, but how about the
>>rest?
>
>Ingo basically ignored all the Xen changes in the leadup to the merge
>window, then stomped on my attempt to get them merged with Linus, which
>was all pretty annoying. It had the doubly-irritating side-effect of
>casting doubt over the controversy-free domU changes, so they didn't
>get merged in the merge window either; by the time Ingo got around to
>OKing them, the window had closed. So all that got merged in the end
>was the must-have bug fixes.

>Linus isn't going to pull any more major functionality changes in the
>-rc kernels, and certainly isn't going to make an exception for Xen. So
>we're stuck with waiting for the .31 merge window.
>
>   J

Given that you think it'll be 2.6.31 before the linux kernel contains
dom0 support (which I guess will be released around Sept/Oct '09), will
you do a release of the code so that people like me who *really* want to
have the latest kernel running as dom0 (to get up to date driver
support) can patch their 2.6.29 (or 2.6.30) kernel. Alternatively could
you give some pointers on how to extract it from git and patch the kernel.

thanks,

Anthony Wright.

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



      

[-- Attachment #1.2: Type: text/html, Size: 3934 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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