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/
Home Products Support Community News


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: Tue, 7 Jul 2009 18:05:22 +0300
Cc: "jeremy@xxxxxxxx" <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 07 Jul 2009 08:05:50 -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=ECChjfvA4QnGsO1O68gTpy8+K9PSpVjqZe7/RuwkvoQ=; b=RS6YrqmgyEy0tvSLHK/xbabkM/4H8J+SVJZpE2vYeFxE0OsJZGI6RW3v/qSTamHBPG /KxwLebcqE+dr52Gm7S6CpCoE197VSTRYRgNamat/Y50lvi9rfdsJFcGYxnMHPU2mstZ aoX/f9FBnpWrQBGM0ncmsfKQQ8VxC8k1e+IMw=
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=trRtGv6POm5wsHzZd9Q0+5e/jTidgzA2DS3eNGZAujeImlSIjIvs/jMVRBgBQYSxbA qXt4btJbv9aHvQmWYjjOwMGNDA76LJ3l1xVkeGM7v3tNiJW4cgF1Hmjj+ZqND5LH8ZzS oJF/OwinnhQBVC8QrvyEIi6CNksB8/saiGMf0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5997D0BE578D47409D1EBD41DFD341F4777C7B391B@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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?

On Tue, Jul 7, 2009 at 5:51 PM, Kamala
Narasimhan<Kamala.Narasimhan@xxxxxxxxxx> wrote:
>> What does it mean, that vbetool doesn't use the right emulation
>> library?
> vbetool uses lmri by default to make real mode calls.  You need to build 
> vbetool with libx86 (http://www.codon.org.uk/~mjg59/libx86/) to get around 
> the problem you see.
>> Regarding the XCI tree - are there specific patches for the 'vbetool'
>> and other stuff? will i be able to find them in the XCI kernel
>> patch-queue?
> I can't point to a bulk of code for problems like these.  They mostly pertain 
> to configuration/environment and solved by bringing in the right dependencies 
> and invoking the right tools etc. which the XCI build ensures.
> Kamala

Xen-devel mailing list