All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Haigh <netwiz@crc.id.au>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Inplace upgrading 4.4.x -> 4.5.0
Date: Mon, 09 Feb 2015 19:40:09 +1100	[thread overview]
Message-ID: <54D87269.9050006@crc.id.au> (raw)
In-Reply-To: <alpine.DEB.2.02.1502090834190.29696@kaball.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1264 bytes --]

Thanks Stefano,

I wanted to make sure I was correct with this belief before I posted all
the info.

I'll gather as much info as I can in the next day or so and see what we
can do.

On 9/02/2015 7:35 PM, Stefano Stabellini wrote:
> Hello Steven,
> upgrades from Xen 4.4 to 4.5 are supposed to work out of the box.
> 
> Please post more details and we'll try to help you figure out what's
> wrong.
> 
> Cheers,
> 
> Stefano
> 
> On Sun, 8 Feb 2015, Steven Haigh wrote:
>> Hi all,
>>
>> I was under the impression that you should be able to do in-place
>> upgrades from Xen 4.4 to 4.5 on a system without losing the ability to
>> manage DomUs...
>>
>> This would support upgrades from running systems from Xen 4.4.x to 4.5.0
>> - only requiring a reboot to boot into the 4.5.0 hypervisor.
>>
>> When I try this in practice, I get a whole heap of permission denied
>> errors and lose control of any running DomUs.
>>
>> Is there some secret sauce that will allow this to work?
>>
>> -- 
>> Steven Haigh
>>
>> Email: netwiz@crc.id.au
>> Web: http://www.crc.id.au
>> Phone: (03) 9001 6090 - 0412 935 897
>>
>>


-- 
Steven Haigh

Email: netwiz@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-02-09  8:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08  7:59 Inplace upgrading 4.4.x -> 4.5.0 Steven Haigh
2015-02-09  8:35 ` Stefano Stabellini
2015-02-09  8:40   ` Steven Haigh [this message]
2015-02-09  8:59   ` Sander Eikelenboom
2015-02-09  9:09     ` Steven Haigh
2015-02-09  9:15       ` Andrew Cooper
2015-02-09  9:16       ` Ian Campbell
2015-02-09  9:36         ` Steven Haigh
2015-02-18 12:38           ` Ian Campbell
2015-02-18 23:09             ` Steven Haigh

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=54D87269.9050006@crc.id.au \
    --to=netwiz@crc.id.au \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.