public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, Thomas Treutner <thomas@scripty.at>,
	KVM list <kvm@vger.kernel.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [ANNOUNCE] qemu-kvm-0.12.1.1
Date: Mon, 4 Jan 2010 17:52:17 +0200	[thread overview]
Message-ID: <20100104155217.GA13833@redhat.com> (raw)
In-Reply-To: <4B4207B1.9050100@redhat.com>

On Mon, Jan 04, 2010 at 04:22:25PM +0100, Gerd Hoffmann wrote:
> 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 ...

"static library" is in fact just an archive of objects.
If you happen not to pull in the conflicting objects,
you won't see the conflict.
So test file would have to call lock_pages/unlock_pages
for config to detect the issue.

> cheers,
>   Gerd
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 12:50 [ANNOUNCE] qemu-kvm-0.12.1.1 Avi Kivity
2009-12-22 13:35 ` Nikola Ciprich
2009-12-22 13:43   ` Avi Kivity
2009-12-22 14:07     ` Nikola Ciprich
2009-12-22 14:09       ` Avi Kivity
     [not found]       ` <20091224162511.GA14150@amt.cnet>
2009-12-25 12:46         ` Nikola Ciprich
2009-12-23  8:16 ` Thomas Treutner
2009-12-23  8:52   ` Avi Kivity
2009-12-23 10:15     ` Thomas Treutner
2009-12-23 10:24       ` Avi Kivity
2009-12-23 10:58         ` Thomas Treutner
2009-12-23 11:37           ` Avi Kivity
2010-01-04 15:22             ` Gerd Hoffmann
2010-01-04 15:52               ` Michael S. Tsirkin [this message]

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=20100104155217.GA13833@redhat.com \
    --to=mst@redhat.com \
    --cc=avi@redhat.com \
    --cc=kraxel@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