* William Dauchy (will...@gandi.net) wrote:
> On Dec11 14:34, Dr. David Alan Gilbert wrote:
> > > I dont get your last statement;
> > > my common use case is to live migrate an old userland to a new one
> > > (so 2.1 to 2.2 here); so if I guarantee same HW, it should work, right?
> >
> > I wouldn'
On Dec11 14:34, Dr. David Alan Gilbert wrote:
> > I dont get your last statement;
> > my common use case is to live migrate an old userland to a new one
> > (so 2.1 to 2.2 here); so if I guarantee same HW, it should work, right?
>
> I wouldn't trust -host cpu to be the same on the same HW between
* William Dauchy (will...@gandi.net) wrote:
> On Dec11 14:05, Dr. David Alan Gilbert wrote:
> > Hmm, it might even do it on the same hardware between different qemus;
>
> I dont get your last statement;
> my common use case is to live migrate an old userland to a new one
> (so 2.1 to 2.2 here); so
On Dec11 14:05, Dr. David Alan Gilbert wrote:
> Hmm, it might even do it on the same hardware between different qemus;
I dont get your last statement;
my common use case is to live migrate an old userland to a new one
(so 2.1 to 2.2 here); so if I guarantee same HW, it should work, right?
--
Will
* William Dauchy (will...@gandi.net) wrote:
> On Dec10 18:21, Dr. David Alan Gilbert wrote:
> > Can you try stripping your config down to the bare minimum and see if
> > it goes away? e.g. balloon, rng-pci, network I guess you can probably
> > test without easily enough. If you can also try with
On 11/12/2014 14:44, William Dauchy wrote:
> harder to reproduce now (I have less and less VM running on 2.1 and
> cant reproduce on my dev platform wiath fresh VM on 2.1->2.2
> scenario) anyway I was wondering if the option `-cpu host` could be
> the cause of the issues since the HW is not alway
On Dec10 18:21, Dr. David Alan Gilbert wrote:
> Can you try stripping your config down to the bare minimum and see if
> it goes away? e.g. balloon, rng-pci, network I guess you can probably
> test without easily enough. If you can also try with a normal boot off
> disk rather than kernel that wo
* William Dauchy (will...@gandi.net) wrote:
> On Dec10 17:31, Dr. David Alan Gilbert wrote:
> > OK, and just checking, 2.2->2.2 and 2.1->2.1 works for you?
> > It's just 2.1->2.2 that's breaking?
>
> yes
OK - that shouldn't happen.
Can you try stripping your config down to the bare minimum and s
On Dec10 17:31, Dr. David Alan Gilbert wrote:
> OK, and just checking, 2.2->2.2 and 2.1->2.1 works for you?
> It's just 2.1->2.2 that's breaking?
yes
--
William
signature.asc
Description: Digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/12/2014 18:28, William Dauchy wrote:
> + maybe the last patch from Paulo "kvm/apic: fix 2.2->2.1 migration" is
> related?
No, it's only for 2.2->2.1.
The error it fixes was reported by Igor Mammedov:
source:
qemu-system-x86_64-2.2 -enable-k
* William Dauchy (will...@gandi.net) wrote:
> + maybe the last patch from Paulo "kvm/apic: fix 2.2->2.1 migration" is
> related?
It's worth a go - but I did want to check which direction you were
having the problem with.
Dave
> --
> William
--
Dr. David Alan Gilbert / dgilb...@redhat.com / Man
* William Dauchy (will...@gandi.net) wrote:
> On Dec10 17:10, Dr. David Alan Gilbert wrote:
> > As previously requested, please show your full command line.
>
> qemu-system-x86_64 -m 2048 -cpu host -nodefconfig -nodefaults -nographic
> -readconfig /var/lib/qemu/X/config -pidfile /var/lib/qemu/X/p
+ maybe the last patch from Paulo "kvm/apic: fix 2.2->2.1 migration" is
related?
--
William
signature.asc
Description: Digital signature
On Dec10 17:10, Dr. David Alan Gilbert wrote:
> As previously requested, please show your full command line.
qemu-system-x86_64 -m 2048 -cpu host -nodefconfig -nodefaults -nographic
-readconfig /var/lib/qemu/X/config -pidfile /var/lib/qemu/X/pid -M
pc-i440fx-2.1 -serial pty -d unimp,guest_errors
* William Dauchy (will...@gandi.net) wrote:
> On Dec10 08:58, Dr. David Alan Gilbert wrote:
> > Yes, you've got to keep the same machine type to do a live migration;
> > think of it like keeping the same motherboard/cpu combination in a real
> > machine - we can't squash the state from one shape ma
On Dec10 08:58, Dr. David Alan Gilbert wrote:
> Yes, you've got to keep the same machine type to do a live migration;
> think of it like keeping the same motherboard/cpu combination in a real
> machine - we can't squash the state from one shape machine into
> a different shape machine without the g
* William Dauchy (will...@gandi.net) wrote:
> Hi David,
>
> Thank you for the quick answer.
>
> On Dec09 18:55, Dr. David Alan Gilbert wrote:
> > You don't tell us what that command line is!
> > If you're using -M pc or -M q35 that's expected; if you're not
> > it's probably a bug - please show
Hi David,
Thank you for the quick answer.
On Dec09 18:55, Dr. David Alan Gilbert wrote:
> You don't tell us what that command line is!
> If you're using -M pc or -M q35 that's expected; if you're not
> it's probably a bug - please show us the command line.
sorry it's indeed with `-M pc`. So I m
* William Dauchy (will...@gandi.net) wrote:
> Hello,
>
> I have been testing live migration from qemu2.1.2 to qemu2.2.0 under
> kvm - with same config and same command line.
>
> the process crashes with:
>
> Unknown combination of migration flags: 0
> qemu: warning: error while loading state sec
19 matches
Mail list logo
