From: Amit Shah <amit.shah@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Alex Bligh <alex@alex.org.uk>
Subject: Re: [Qemu-devel] Live migrate, inconsistent machine types - new machine type to fix?
Date: Tue, 22 Jul 2014 15:52:58 +0530 [thread overview]
Message-ID: <20140722102258.GA18209@grmbl.mre> (raw)
In-Reply-To: <53CE3511.3000402@redhat.com>
On (Tue) 22 Jul 2014 [11:55:29], Paolo Bonzini wrote:
> Il 22/07/2014 11:50, Amit Shah ha scritto:
> > These are the ones that remain after fixing up the rest:
> >
> > Section "xio3130-downstream" Description "xio3130-express-downstream-port": version error: 2 > 0
> > Section "usb-host" Section "usb-host" Description "usb-host": minimum version error: 0 < 1
> > Section "ich9-usb-ehci1" Section "ich9-usb-ehci1" Description "ehci": minimum version error: 0 < 1
> > Section "x3130-upstream" Description "xio3130-express-upstream-port": version error: 2 > 0
> > Section "usb-ehci" Section "usb-ehci" Description "ehci": minimum version error: 0 < 1
> > Section "ioh3420" Description "ioh-3240-express-root-port": version error: 2 > 0
> > Section "isa-pit", Description "i8254": expected field "channels", got "channels[0].irq_disabled"; skipping rest
> > Section "PIIX4_PM" Section "PIIX4_PM" Description "piix4_pm": minimum version error: 2 < 3
>
> What about qemu-kvm 1.0 vs qemu 2.1?
Just one extra failure:
Section "pci-assign" does not exist in dest
Also interesting is qemu 1.0 -> qemu-kvm-1.0:
Section "i6300esb" Section "i6300esb" Description "i6300esb_wdt": minimum version error: 1336 < 1368
Section "isa-pit", Description "i8254": expected field "channels", got "flags"; skipping rest
And qemu-kvm-1.0 to qemu-1.0:
Section "kvmclock" does not exist in dest
Section "i6300esb" version error: 1368 > 1336
Section "i6300esb" Description "i6300esb_wdt": version error: 1368 > 1336
Section "isa-pit", Description "i8254": expected field "flags", got "channels"; skipping rest
Section "pci-assign" does not exist in dest
Amit
next prev parent reply other threads:[~2014-07-22 10:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 23:33 [Qemu-devel] Live migrate, inconsistent machine types - new machine type to fix? Alex Bligh
2014-07-19 5:51 ` Paolo Bonzini
2014-07-19 7:10 ` Alex Bligh
2014-07-19 7:30 ` Paolo Bonzini
2014-07-19 8:43 ` Alex Bligh
2014-07-19 8:54 ` Peter Maydell
2014-07-19 8:59 ` Alex Bligh
2014-07-19 10:53 ` Paolo Bonzini
2014-07-19 11:37 ` Alex Bligh
2014-07-21 10:22 ` Paolo Bonzini
2014-07-21 13:59 ` Alex Bligh
2014-07-21 14:11 ` Paolo Bonzini
2014-07-21 14:35 ` Alex Bligh
2014-07-21 14:14 ` Paolo Bonzini
2014-07-22 7:11 ` Amit Shah
2014-07-22 9:50 ` Amit Shah
2014-07-22 9:55 ` Paolo Bonzini
2014-07-22 10:22 ` Amit Shah [this message]
2014-07-22 10:32 ` Alex Bligh
2014-07-22 10:54 ` Amit Shah
2014-07-22 11:38 ` Alex Bligh
2014-07-22 11:54 ` Amit Shah
2014-07-22 12:12 ` Paolo Bonzini
2014-07-22 12:19 ` Alex Bligh
2014-07-22 12:47 ` Amit Shah
2014-07-22 12:40 ` Amit Shah
2014-07-22 12:15 ` Alex Bligh
2014-07-22 12:44 ` Amit Shah
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=20140722102258.GA18209@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=alex@alex.org.uk \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).