qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Thomas Treutner <thomas@scripty.at>,
	qemu-devel <qemu-devel@nongnu.org>,
	KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [ANNOUNCE] qemu-kvm-0.12.1.1
Date: Mon, 04 Jan 2010 16:22:25 +0100	[thread overview]
Message-ID: <4B4207B1.9050100@redhat.com> (raw)
In-Reply-To: <4B320116.3030505@redhat.com>

On 12/23/09 12:37, Avi Kivity wrote:
> On 12/23/2009 12:58 PM, Thomas Treutner wrote:
>> On Wednesday 23 December 2009 11:24:04 Avi Kivity wrote:
>>> Please post a full log, after 'make clean'.
>> http://pastebin.com/f404c8648
>>
>
> Oh, I missed it at first - looks like libxenguest and libxenctrl conflict.

Indeed, there are (un)lock_pages functions in both libraries.  It is 
fixed in xen 3.3+, where libxenguest doesn't has these functions any more.

/me also wonders why Debian seems to have only static xen libraries.
I think when linking against the shared libraries avoids this too as the 
functions are supposed to be library-internal.

> Copying Gerd for an opinion.

I think there isn't much we can do about this, it is clearly a xen bug.

Uhm, well, while thinking about it:  The test app compiled and linked by 
configure should have failed in a simliar way, thereby automatically 
disabling xen support.  I have no idea why it didn't ...

cheers,
   Gerd

       reply	other threads:[~2010-01-04 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4B30C07B.2090009@redhat.com>
     [not found] ` <200912231115.24380.thomas@scripty.at>
     [not found]   ` <4B31EFC4.30903@redhat.com>
     [not found]     ` <200912231158.20614.thomas@scripty.at>
     [not found]       ` <4B320116.3030505@redhat.com>
2010-01-04 15:22         ` Gerd Hoffmann [this message]
2010-01-04 15:52           ` [Qemu-devel] Re: [ANNOUNCE] qemu-kvm-0.12.1.1 Michael S. Tsirkin

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=4B4207B1.9050100@redhat.com \
    --to=kraxel@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thomas@scripty.at \
    /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).