WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: Xen pv kernel (2.6.30) causes s2ram to crash with se

To: Kamala Narasimhan <Kamala.Narasimhan@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Xen pv kernel (2.6.30) causes s2ram to crash with segmentation fault
From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
Date: Wed, 8 Jul 2009 17:45:30 +0300
Cc: "jeremy@xxxxxxxx" <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 08 Jul 2009 07:45:56 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=yxo2rPdikb6eFjwO91hiCA63cmUYxzA5dhosOGw5Vf8=; b=tuNqJZw7t/N8SY33Lds/A7woFWqpmY+4HF2C9XLKNrYJDyqztatuN2BaaoU9+Yb2PG C2mt7cBcv6wRfJhMHYOWHYmHJLhDvhlFkyMMxml+mwDYvpiVG8BnWi2fHZYp5Y28MyjX oAgawmS8wXpBz/DYoSFIBLowoqfjXJ9B44hSg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xExzlMqPC5lhOjDjRlheNPnkLcy440Soc8w3P1DbIt49kL0WM/NIjJAzzLkSEf/WKt VgV645RE9U+aYCegjU7IvnwEiD28bylMYOBgOhns9N7Btss094+GGJrwggWjPFy0Zq7k CSK5zbGt/meJKVKPVgy68h8uMY4/4caQU8hS4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5997D0BE578D47409D1EBD41DFD341F4777C7B391F@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <8686c3cd0907060804n2f2427b7vebc326878ba6e34d@xxxxxxxxxxxxxx> <8686c3cd0907060857h399c7846m336e3d2133e39b52@xxxxxxxxxxxxxx> <5997D0BE578D47409D1EBD41DFD341F4777C7B3917@xxxxxxxxxxxxxxxxxxxxxxxxx> <8686c3cd0907060913y7747ab1fr87b0ebc7e015866d@xxxxxxxxxxxxxx> <5997D0BE578D47409D1EBD41DFD341F4777C7B391B@xxxxxxxxxxxxxxxxxxxxxxxxx> <8686c3cd0907070805x81aca50pe05a8fc68a9653c2@xxxxxxxxxxxxxx> <5997D0BE578D47409D1EBD41DFD341F4777C7B391F@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
OK.

I saw in the vbetool makefile,of XCI build, that you replace the
'-lx86' lines in the Makefile, to be linked against:
'/usr/lib/libx86.so'.
What's the difference between the two libs??

Tom

On Wed, Jul 8, 2009 at 4:52 PM, Kamala
Narasimhan<Kamala.Narasimhan@xxxxxxxxxx> wrote:
>> Ok, i'll try the XCI tree (although, i am experiencing some
>> difficulties in building it - but i think i saw a previous thread
>> which talked about the same issue i have).
>>
>> Just last question: what's the problem of lrmi above dom0? why can't
>> it work like that, and it needs to be built with libx86?
>>
>
> vm86 mode used by the default lrmi library is not available with 64 bit 
> hypervisor ...
>
> Kamala
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel