qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Marc Hartmayer <mhartmay@linux.vnet.ibm.com>,
	libvir-list@redhat.com, qemu-devel@nongnu.org
Cc: Jiri Denemark <jdenemar@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Boris Fiuczynski <fiuczy@linux.vnet.ibm.com>,
	"Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
	Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>Christian
	Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [Qemu-devel] [libvirt] Question about the host-model CPU mode
Date: Fri, 20 Oct 2017 15:16:07 +0200	[thread overview]
Message-ID: <0aab6dae-a926-c106-9bc5-68561a9bef5c@redhat.com> (raw)
In-Reply-To: <87mv4m6pp5.fsf@marc-ibm.boeblingen.de.ibm.com>


> Hi all,
> 
> we recently encountered the problem that the 'host-model' [1] has to be
> related to the machine type of a domain. We have following problem:
> 
>    Let's assume we've a z13 system with a QEMU 2.9 and we define a
>    domain using the default s390-virtio-ccw machine together with the
>    host-model CPU mode [1]. The definition will have the machine
>    expanded to s390-virtio-ccw-2.9 but retain the host-model CPU mode
>    in the domain definition. In a next step we upgrade to QEMU 2.10
>    (first version to recognize z14). Everything is still fine, even
>    though the machine runs in 2.9 compatibility mode. Finally we
>    upgrade to a z14. As a consequence it is not possible to start the
>    domain anymore as the machine type doesn't support our CPU host
>    model (which is expanded at start time of the domain).

Actually, what is the cause of that problem? I assume it is the gs
feature (gs_allowed)?

We should really avoid such things (..._allowed) for CPU model features
in the future and clue all new such stuff to cpumodel_allowed.

-- 

Thanks,

David

  parent reply	other threads:[~2017-10-20 13:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y3oqugm7.fsf@marc-ibm.boeblingen.de.ibm.com>
     [not found] ` <20171005121115.GD3946746@orkuz.home>
     [not found]   ` <87y3ok7n2n.fsf@marc-ibm.boeblingen.de.ibm.com>
     [not found]     ` <20171012120714.GA314661@orkuz.home>
2017-10-20 11:09       ` [Qemu-devel] [libvirt] Question about the host-model CPU mode Marc Hartmayer
2017-10-20 11:37         ` David Hildenbrand
2017-10-20 12:50           ` Jiri Denemark
2017-10-20 13:04             ` David Hildenbrand
2017-10-23  7:25               ` Jiri Denemark
2017-10-20 12:43         ` Jiri Denemark
2017-10-20 13:16         ` David Hildenbrand [this message]
2017-10-20 13:36           ` Christian Borntraeger
2017-10-20 13:43             ` David Hildenbrand
2017-10-20 13:49               ` Christian Borntraeger
2017-10-20 13:51                 ` David Hildenbrand
2017-10-20 14:02                   ` Christian Borntraeger
2017-10-20 14:06                     ` David Hildenbrand
2017-10-20 14:12                       ` Christian Borntraeger
2017-10-20 14:58                         ` Halil Pasic
2017-10-20 15:14                           ` David Hildenbrand

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=0aab6dae-a926-c106-9bc5-68561a9bef5c@redhat.com \
    --to=david@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=fiuczy@linux.vnet.ibm.com \
    --cc=jdenemar@redhat.com \
    --cc=jjherne@linux.vnet.ibm.com \
    --cc=libvir-list@redhat.com \
    --cc=mhartmay@linux.vnet.ibm.com \
    --cc=mihajlov@linux.vnet.ibm.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).