All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua West <jwest@brandeis.edu>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Kurt Hackel <kurt.hackel@oracle.com>, xen-devel@lists.xensource.com
Subject: Re: Migrate/Save of 32-bit domU Broken on Xen 3.1.2 64-bit dom0
Date: Fri, 18 Jan 2008 18:05:57 -0500	[thread overview]
Message-ID: <479130D5.1060009@brandeis.edu> (raw)
In-Reply-To: <C3B6D5FA.12813%Keir.Fraser@cl.cam.ac.uk>

Dang, doesn't work in Xen 3.1.3-rc1 (like you said/expected), with or 
without Kurt's patches.

Hmm... I thought 32-bit paravirtualized domU's on 64-bit dom0's were 
supported in Xen 3.1.x?  Or am I mistaken?

Perhaps standard features such as start/shutdown/pause of 32-bit PV 
domU's on 64-bit dom0's are supported, but not the more advanced 
management features like save and migrate - and I was just unclear from 
the beginning?

And of course... the final question that all developers hate... when 
s/could one _hope_ (not expect!) to see save/migrate functionality of 
32-bit PV domU's on 64-bit dom0's? :-D

Our whole reason for moving to 64-bit dom0's was to utilize 32GB of 
memory, instead of the 16GB limitation on 32-bit PAE dom0's.  We can't 
convert all of our virtual machines (100+) to 64-bit linux as its too 
much work and some actually have to be 32-bit due to vendor supplied 
software (Oracle, Zimbra, etc).  I suppose we'll wait to move to 64-bit 
until [live] migration is available, as its used quite frequently in our 
machine rooms.

Thanks for all of your help Keir and Kurt.

Keir Fraser wrote:
> Looking at the issues that need to be handled to support this, it cannot be
> expected to work.
>
>  -- Keir
>
> On 18/1/08 22:13, "Joshua West" <jwest@brandeis.edu> wrote:
>
>   
>> Ahh.  Well, I'm building xen-3.1.3-rc1 right now and I'll see how that goes.
>>
>> Keir, have you seen this issue before?  Where one cannot xm save/migrate
>> a 32-bit domU on a 64-bit dom0?  Or is this expected to work and just
>> doesn't go well for me?
>>
>> Keir Fraser wrote:
>>     
>>> On 18/1/08 22:05, "Joshua West" <jwest@brandeis.edu> wrote:
>>>
>>>   
>>>       
>>>> Just to make sure the patches aren't the cause of this new error
>>>> message, I'm going to see what happens with Xen 3.1.3-rc1 w/o patches.
>>>>
>>>> Kurt, Keir, everybody else... any ideas as to why "xm save" (and thus
>>>> "xm migrate") of 32-bit domU's does not work on 64-bit dom0's?  Has
>>>> anybody found this to be successful in the past?
>>>>     
>>>>         
>>> The extent of the patches that Kurt posted indicate its pretty unlikely to
>>> work without considerable code modification. I guess those patches aren't
>>> quite fully baked yet, unfortunately, or haven't been written with your
>>> precise case in mind.
>>>
>>>  -- Keir
>>>
>>>
>>>   
>>>       
>
>
>   


-- 
Joshua West
Systems Engineer
Brandeis University
http://www.brandeis.edu

  reply	other threads:[~2008-01-18 23:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18  2:21 Migrate/Save of 32-bit domU Broken on Xen 3.1.2 64-bit dom0 Joshua West
2008-01-18  6:01 ` Kurt Hackel
2008-01-18 19:36   ` Joshua West
2008-01-18 22:05   ` Joshua West
2008-01-18 22:10     ` Keir Fraser
2008-01-18 22:13       ` Joshua West
2008-01-18 22:17         ` Keir Fraser
2008-01-18 23:05           ` Joshua West [this message]
2008-01-18 23:15             ` Keir Fraser
2008-01-18 23:21               ` Joshua West
2008-01-18 23:17             ` Dan Magenheimer
2008-01-18 23:24               ` Keir Fraser
2008-01-19  0:12                 ` Kurt Hackel
2008-01-20 21:28                   ` Joshua West
2008-01-21  7:59                     ` Keir Fraser
2008-02-04 21:08                   ` Migrate/Save of 32-bit domU Broken on Xen 3.1.264-bit dom0 Bruce Rogers
2008-01-18 23:29               ` Migrate/Save of 32-bit domU Broken on Xen 3.1.2 64-bit dom0 Joshua West
2008-01-18 23:32                 ` Joshua West
2008-01-19  8:04                 ` Keir Fraser

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=479130D5.1060009@brandeis.edu \
    --to=jwest@brandeis.edu \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=kurt.hackel@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.