From: Gerd Hoffmann <kraxel@redhat.com>
To: Andrew Lyon <andrew.lyon@gmail.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
bderzhavets@yahoo.com,
"Marc - A. Dahlhaus [ Administration | Westermann GmbH ]"
<mad@wol.de>
Subject: Re: Build vmlinuz-2.6.29-rc5-tip
Date: Fri, 20 Feb 2009 10:36:27 +0100 [thread overview]
Message-ID: <499E799B.2080008@redhat.com> (raw)
In-Reply-To: <f4527be0902200104u3e683de1he474b76e36be48f1@mail.gmail.com>
Andrew Lyon wrote:
> Awesome, the kernel booted and ahci is working normally, and piix
> isnt actually used on this system as all the devices are sata.
>
> xend failed to start saying it was not a privileged domain, first
> thing I am going to try there is upgrading to Xen 3.3.1 final as I am
> still running rc4 on my test box, but what is the minimum Xen version
> to use pv_ops dom0?
Try adding this line to /etc/fstab:
xen /proc/xen xenfs defaults 0 0
vanilla 3.3.1 isn't going to work, you need a few patches backported
from unstable. Current rawhide package has these changesets:
xen-backport-hg18782.patch
xen-backport-hg19075.patch
xen-backport-hg19108.patch
xen-backport-hg19109.patch
xen-backport-hg19110.patch
cheers,
Gerd
next prev parent reply other threads:[~2009-02-20 9:36 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1234864748.30137.131.camel@zakaz.uk.xensource.com>
2009-02-17 10:06 ` How to build vmlinuz-2.6.29-rc5-tip ? Boris Derzhavets
2009-02-17 11:58 ` Build vmlinuz-2.6.29-rc5-tip Boris Derzhavets
2009-02-17 13:11 ` Pasi Kärkkäinen
2009-02-17 13:31 ` Boris Derzhavets
2009-02-17 13:57 ` Pasi Kärkkäinen
2009-02-17 18:40 ` Jeremy Fitzhardinge
2009-02-18 21:48 ` Pasi Kärkkäinen
2009-02-18 22:39 ` Jeremy Fitzhardinge
2009-02-19 7:21 ` Pasi Kärkkäinen
2009-02-19 3:13 ` Jeremy Fitzhardinge
2009-02-17 14:09 ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
2009-02-18 15:49 ` Boris Derzhavets
2009-02-18 17:40 ` Boris Derzhavets
2009-02-18 18:53 ` Andrew Lyon
2009-02-18 19:16 ` Boris Derzhavets
2009-02-18 19:40 ` Boris Derzhavets
2009-02-18 20:04 ` Jeremy Fitzhardinge
2009-02-19 7:04 ` Boris Derzhavets
2009-02-19 17:30 ` Jeremy Fitzhardinge
2009-02-19 18:17 ` Boris Derzhavets
2009-02-20 9:04 ` Andrew Lyon
2009-02-20 9:36 ` Gerd Hoffmann [this message]
2009-02-20 12:24 ` Andrew Lyon
2009-02-21 12:40 ` Andrew Lyon
2009-02-21 15:53 ` Jeremy Fitzhardinge
2009-02-22 13:48 ` "xm dmesg" report for the most recent vmlinuz-2.6.29-rc5-tip Boris Derzhavets
2009-02-22 17:12 ` Jeremy Fitzhardinge
2009-02-22 17:27 ` Boris Derzhavets
2009-02-22 14:20 ` Build vmlinuz-2.6.29-rc5-tip Andrew Lyon
2009-02-22 15:10 ` Boris Derzhavets
2009-02-22 15:19 ` Andrew Lyon
2009-02-22 17:13 ` Boris Derzhavets
2009-02-23 16:32 ` Ian Jackson
2009-02-20 14:58 ` Jeremy Fitzhardinge
2009-02-20 15:39 ` Andrew Lyon
2009-02-20 19:44 ` Andrew Lyon
2009-02-20 19:59 ` Boris Derzhavets
2009-02-23 2:39 ` Stefano Stabellini
2009-02-23 10:19 ` Boris Derzhavets
2009-02-23 10:48 ` Boris Derzhavets
2009-02-21 9:01 ` Reproduced error when creating Intrepid HVM at Xen Unstable Dom0(vmlinuz-2.6.29-rc5-tip) Boris Derzhavets
2009-02-23 16:42 ` Ian Jackson
2009-02-23 18:04 ` Boris Derzhavets
2009-02-17 18:41 ` Build vmlinuz-2.6.29-rc5-tip Jeremy Fitzhardinge
2009-02-18 6:36 ` Boris Derzhavets
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=499E799B.2080008@redhat.com \
--to=kraxel@redhat.com \
--cc=andrew.lyon@gmail.com \
--cc=bderzhavets@yahoo.com \
--cc=jeremy@goop.org \
--cc=mad@wol.de \
--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.