[prev in list] [next in list] [prev in thread] [next in thread] 

List:       libvirt-users
Subject:    Re: [libvirt-users] live migration
From:       Thomas Stein <himbeere () meine-oma ! de>
Date:       2015-02-24 17:15:26
Message-ID: 1860422.rBJD87cZq9 () rather
[Download RAW message or body]

On Tuesday 24 February 2015 17:47:11 you wrote:
> On Tuesday 24 February 2015 16:58:22 you wrote:
> > On 24.02.2015 16:10, Thomas Stein wrote:
> > > On Tuesday 24 February 2015 14:56:10 Michal Privoznik wrote:
> > >> On 24.02.2015 14:29, Thomas Stein wrote:
> > >>> Hola.
> > >>> 
> > >>> Just tried a live migration after fixing the pc-q35-2.1 error. Now i
> > >>> have new problem. It seems during live migration only the ram gets
> > >>> migrated. I use the following command.
> > >>> 
> > >>>  # virsh migrate --live domain qemu+ssh://newhost/system
> > >>> 
> > >>> --copy-storage-all --verbose --persistent
> > >>> 
> > >>> It works without problems. Apart from beeing way to fast.
> > >>> 
> > >>>  # virsh migrate --live domain qemu+ssh://newhost/system
> > >>> 
> > >>> --copy-storage-all --verbose --persistent
> > >>> Migration: [100 %]
> > >>> 
> > >>> On the destination i can enter the VM but thats it. There is no
> > >>> filesystem and so on.
> > >>> 
> > >>> Did the migration syntax change?
> > >>> 
> > >>> I use libvirt 1.2.12 and qemu 2.2.0. Thanks for any hints.
> > >> 
> > >> Only RW disks are copied. You have to copy RO, sourceless or shared
> > >> disks yourself.
> > > 
> > > Thanks for your answer. But what do you mean by "rw disks"? I chmod(ed)
> > > a+rw all images but the issue still exists.
> > 
> > Those are two separate things. One is the Linux permissions over a file,
> > the other is disk (which doesn't have to be necessary a regular file)
> > and set of actions guest is allowed to do over it. RO disk contains
> > 'readonly="yes"' in its XML definition in domain XML. If there's none,
> > disk is RW. A sourceless disk contains no <source/>, shared disk
> > contains 'shared="yes"' and so on.
> 
> Okay. Thanks for this information. But i don't think it applies to my case.
> I think i'll try a downgrade.

Wow. Downgrading to qemu-2.1.3 solves the problem.

cheers
t.

> cheers
> t.
> 
> > Michal

[prev in list] [next in list] [prev in thread] [next in thread]