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] HVM resumable with -c flag?

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] HVM resumable with -c flag?
From: "Mike Sun" <msun@xxxxxxxxxx>
Date: Thu, 18 Sep 2008 19:12:43 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, John Levon <levon@xxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 18 Sep 2008 16:13:07 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=/CsKgDt3+UNRy/pDsc1LrI3EHLSPAP3gex533Lv9HZ4=; b=u4W8UhljBYhoiaLNJ7atjLeAc1ObXA9Qstho4k2lxG/3ISvNrZbC7VfeIC3gxM10sM UaMet+B+joqWQ/BpPF3yWoEJYFp678dCWAtMiu/w78XMHAdFqF7GHwEcciDTkqG2LhgA yLl/QrEaSSFzKnbHYwDZECGakEm7TWfUHkzG0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=fZY97BNskIs1r1Pcuz25Yi5xTaucQug3K1YZNB2poea5vVY4asnlr7YpF+sjWwpY3C uLhgpKg0D88Hjni3BWtYQAF57HdV/ByPL8gUL86e5TiSVgAqiwWaZCTEZWo1oL1SqjNV TkSL+m4x9I0jgF05tGIjDxuMy5rT/kb0jvgfg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C4F5DE22.1D44D%keir.fraser@xxxxxxxxxxxxx>
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: <e4e579070809161230x2856621ld6f20f829c20d8fa@xxxxxxxxxxxxxx> <C4F5DE22.1D44D%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hmm...  I attempted to replace the tools/ioemu source in 3.1.4 with
that from 3.2.1... and find this call in cirrus_vga.c is not supported
in 3.1.x:

        xc_handle, domid,
        begin >> TARGET_PAGE_BITS,
        end >> TARGET_PAGE_BITS,

I looked into patching 3.1.x with the code necessary to support that
function call, but found myself down a long list of dependencies that
required updating things like mtrr and mm.c which seemed a bit

I figured I'd just remove that memory cache pin call in cirrus_vga.c
and see how that went.  (The only other slight change I had to make
was to remove the z position stuff from xenfb.c).  Everything build,
but I can't create HVM domains without them getting wedged in a
"weird" state (i.e. -----), so it looks like qemu-dm is bugging out.

Any ideas on how I can port the 0.90 version of QEMU in Xen 3.2.x into
Xen 3.1.x easily?


On Tue, Sep 16, 2008 at 5:05 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> qemu-dm should be quite portable.
>  -- Keir
> On 16/9/08 20:30, "Mike Sun" <msun@xxxxxxxxxx> wrote:
>> Thanks Keir.  It is the qemu-dm.  Hmm, not my dilemma is whether it'd
>> be a fairly easy thing to incorporate the newer qemu-dm into a 3.1.x
>> branch...  I've made some major changes to the shadow page table code
>> for my work and would rather not try and merge them into 3.2.x if I
>> don't have to at this point.
>> Mike
>> On Sat, Sep 13, 2008 at 3:09 AM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
>> wrote:
>>> On 13/9/08 03:52, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:
>>>> On Fri, Sep 12, 2008 at 04:42:22PM +0100, Keir Fraser wrote:
>>>>> On 12/9/08 16:33, "Mike Sun" <msun@xxxxxxxxxx> wrote:
>>>>>> Sorry if this is a stupid question, but are you saying that all HVM
>>>>>> guests are now resumable and there no longer needs to be any check for
>>>>>> that as was done by Brendan Cully's earlier patch requests?
>>>>> Correct. All HVM PV drivers must support suspend cancellation (i.e.,
>>>>> resume). And without PV drivers, resume is as simple as just continuing
>>>>> execution of the guest from where it left off!
>>>> Uh, when was this requirement introduced?
>>> Since guest resume was supported by hypervisor and tools. We've never
>>> supported resume of HVM guests with 'uncooperative' PV drivers installed.
>>>  -- Keir

Xen-devel mailing list