From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Bryan D. Payne" <bryan@thepaynes.cc>
Cc: Ian,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: New release candidate for Xen 3.4.3
Date: Thu, 22 Apr 2010 22:11:12 +0100 [thread overview]
Message-ID: <C7F67A00.BFF%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <o2m64bddf0e1004221350u40363161ud23c91fe61026bcf@mail.gmail.com>
On 22/04/2010 21:50, "Bryan D. Payne" <bryan@thepaynes.cc> wrote:
>> You are building from the wrong qemu repository. Probably you are trying to
>> build from qemu-xen-unstable.git rather than qemu-xen-3.4-testing.git -- do
>> you perhaps override CONFIG_QEMU in your environment, or something like
>> that.
>
> Just checked, there's no CONFIG_QEMU in my environment.
>
>> However I do note that the tag xen-3.4.3-rc5 that I was promised in the
>> qemu-xen-3.4-testing.git repo does appear to be missing. Ian?
>
> Sounds like this could be the culprit. I'll await word on this and
> try testing again.
Um, yes, I can see the rc5 tag now but the qemu tree just seems broken.
Looks like a bad merge maybe. There's a changeset dated from back in October
allegedly which references vcpu_ioreq which has never been part of the Xen
3.4 interfaces.
Ian will have to sort it and then I guess we will have to do a 3.4.3-rc6.
Thanks,
Keir
next prev parent reply other threads:[~2010-04-22 21:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 8:51 New release candidate for Xen 3.4.3 Keir Fraser
2010-04-22 20:24 ` Bryan D. Payne
2010-04-22 20:34 ` Keir Fraser
2010-04-22 20:50 ` Bryan D. Payne
2010-04-22 21:11 ` Keir Fraser [this message]
2010-04-28 9:37 ` Ian Jackson
2010-04-28 10:28 ` Ian Jackson
2010-04-28 3:51 ` Keir Fraser
2010-04-28 13:32 ` Ian Jackson
2010-04-22 21:40 ` M A Young
2010-04-23 7:05 ` Keir Fraser
2010-04-28 1:46 ` KUWAMURA Shin'ya
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=C7F67A00.BFF%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=bryan@thepaynes.cc \
--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).