[Pkg-xen-devel] Re: [Pkg-xen-changes] r55 - trunk/debian [u]

[Guido Trotter]

On Sat, Feb 25, 2006 at 01:54:13PM +0100, Ralph Passgang wrote:

Hi,

> >
> > Then we need for the new package to have a "Replaces:" on the first one...
> 
> yes, probablly that fixes that, but I cannot test an upgrade anymore. I don't 
> have xen2 machines anymore...
> 

Do you remember which packages cause that error, so we can do it properly?

> If I am not totally wrong adams packages call "xend stop" and then "xendomains 
> stop". By doing this the domUs will NOT be stopped, because xend was stopped 
> first and xendomains will fail because it cannot contact xend anymore.
> 

I see... Then it's a bug in the older packages... We can probably ignore it, and
put in the NEWS not to upgrade with VMs running... A fix would be to upload a
transitory xen 2, but it seems like an overkill!

> This probably means that after a upgrade from 2.0.6 -> our 3.0.1 packages 
> there will still some domUs running, but the user cannot shut the domus down 
> anymore (unless he is not ssh'ing into every domU). the userspace tools will 
> not be able to communicate with a 2.x hypervisor.
> 

Understandable...

> absolutly an overkill. How do you want to keep old files, even if the xen 
> packages gets updated?
> 

Yeah, you're right... :)

> Maybe we should just include a BIG warning before upgrading that it's better 
> not to try a upgrade within a running xen system at all. It's the best to 
> start a normal kernel (and having no domUs running then) and update xen and 
> reboot the new hypervisor + kernel then.
> 

Well... if you have no VMs running it's already ok, I think... there's no need
to actually boot inside a linux only system! Let's not scare the users! ;)

Thanks,

Guido