From: Boris Derzhavets <bderzhavets@yahoo.com>
To: xen-devel@lists.xensource.com
Subject: Install OpenSuse 11.1 PV DomU via VFB at Xen Unstable Dom0 (2.6.29-rc3)
Date: Wed, 11 Feb 2009 07:14:47 -0800 (PST) [thread overview]
Message-ID: <699035.18315.qm@web56102.mail.re3.yahoo.com> (raw)
In-Reply-To: <315631.33436.qm@web56107.mail.re3.yahoo.com>
[-- Attachment #1.1: Type: text/plain, Size: 4408 bytes --]
OpenSuse 11.1 PV DomU has been also successfully tested ( utilizing VFB for installation and runtime profile) at Xen Unstable Dom0 (2.6.29-rc3).
Extracting phase for for Suse's images is noticeably slow versus same
install running at Xen 3.3.1 CentOS 5.2 Dom0 ( same hardware just
multibooting several Xen Dom0)
--- On Tue, 2/10/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] pv_ops with xen-3.3
To: xen-devel@lists.xensource.com, jonr@destar.net
Date: Tuesday, February 10, 2009, 1:18 PM
I was able successfully installed and ran Ubuntu Intrepid Server PV DomU
and F10 PV DomU (both 64-bit) at mentioned Xen Unstable Dom0s.
One network issue came up on two boxes have been tested:-
1. C2D E8400,8 GB RAM , ASUS P5K Premium/WIFI, 2x250 GB SATA drives
2. C2D E6600,4 GB RAM, ASUS P5B Deluxe, 2x160 GB SATA drives.
Per "dmesg" report:-
South bridges ICH8R ,ICH9R (AHCI Bios Setup for both) have been
detected by the most recent version of 2.6.29-rc3 with no problems
as well as SATA drives parameters. NCQ depth set to (31/32) .
However , only Matvell Yukon 8056 was able to function as xen bridge
supporting LAN&WAN communications for Dom0.
RTL 8110SC (first board) and RTL 8169 (plugged into second board)
failed to function as required
--- On Tue, 2/10/09, Boris
Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] pv_ops with xen-3.3
To: xen-devel@lists.xensource.com, jonr@destar.net
Date: Tuesday, February 10, 2009, 12:52 PM
The way it worked for me on Ubuntu Intrepid Server (x86_64)
First installed the most recent xen unstable:-
# 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
Compiled kernel supporting PV_OPS in Dom0 & INTEL AHCI (ICH(X)R)
# hg clone http://www.kernel.org/hg/linux-2.6
# cd linux-2.6/.hg
# hg clone http://xenbits.xensource.com/paravirt_ops/patches.hg patches
# cd ..
# ln -s .hg/patches . # for convenience
# hg update `cat patches/KERNEL_VERSION`
# hg qpush -a
# make menuconfig
# make
# make modules_install install
# depmod 2.6.29-rc3-tip
# mkinitramfs -o /boot/initrd-2.6.29-rc3-tip.img 2.6.29-rc3-tip
Created grub entry :-
title Xen 3.4 / Ubuntu 8.10, kernel 2.6.29-tip
kernel /boot/xen-3.4.gz dom0_mem=1024M
module /boot/vmlinuz-2.6.29-rc3-tip root=/dev/sdb1 ro console=tty0 pci=nomsi
module /boot/initrd-2.6.29-rc3-tip.img
I was able to load 2.6.23-rc3 only under the most recent version of Xen Unstable Hypervisor. Xen 3.3.1 was unable to recognize kernel image:-
Printed "Not ELF format" to console and hanged.
Details here:-
http://bderzhavets.wordpress.com/2009/02/07/attempt-of-install-xen-unstable-dom0-via-2629-rc3-pv_ops-enabled-kernel-on-intel-sataahci-box/
--- On Tue, 2/10/09, jonr@destar.net <jonr@destar.net> wrote:
From: jonr@destar.net <jonr@destar.net>
Subject: [Xen-devel] pv_ops with xen-3.3
To: xen-devel@lists.xensource.com
Date: Tuesday, February 10, 2009, 11:55 AM
I would like to try and test out the 2.6.29-rc4 kernel and see if I
can't get Xen-3.3-1 booting. I have patched the 2.6.28 kernel and have
a 2.6.29-rc4 kernel. I
have
configured the kernel to use xen by
following http://wiki.xensource.com/xenwiki/XenParavirtOps.
Now I have the kernel configured and built but am not quite sure how
to use this kernel with xen-3.3. When I downloaded the latest xen and
ran 'make world' it downloaded the 2.6.18 kernel and is building xen
against that. How do I make xen build against my kernel or do I even
need to?
Once xen-3.3 is done building do I just substitute my 2.6.29-rc4
kernel in the grub menu.conf or am I missing something?
Thanks for any help,
Jon
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 5947 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:[~2009-02-11 15:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 16:55 pv_ops with xen-3.3 jonr
2009-02-10 17:09 ` Mark Williamson
2009-02-10 17:26 ` jonr
2009-02-10 17:50 ` Keir Fraser
2009-02-10 18:53 ` jonr
2009-02-10 19:01 ` jonr
2009-02-10 18:25 ` Mark Williamson
2009-02-11 5:49 ` Jeremy Fitzhardinge
2009-02-10 17:52 ` Boris Derzhavets
2009-02-10 18:18 ` Boris Derzhavets
2009-02-11 15:14 ` Boris Derzhavets [this message]
2009-02-10 21:01 ` jonr
2009-02-10 21:09 ` Mark Williamson
2009-02-10 21:23 ` jonr
2009-02-10 21:36 ` Boris Derzhavets
2009-02-10 22:29 ` jonr
2009-02-11 5:51 ` 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=699035.18315.qm@web56102.mail.re3.yahoo.com \
--to=bderzhavets@yahoo.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.