RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1235771 - Guest should not be booted if we specify the devices we do not plan to support with -M (PCI bridge)
Summary: Guest should not be booted if we specify the devices we do not plan to suppor...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Marcel Apfelbaum
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1175220
TreeView+ depends on / blocked
 
Reported: 2015-06-25 16:53 UTC by Hai Huang
Modified: 2015-09-08 15:43 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1175215
Environment:
Last Closed: 2015-09-08 15:43:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Hai Huang 2015-06-25 16:53:27 UTC 
+++ This bug was initially created as a clone of Bug #1175215 +++

Description of problem:
Guest could be booted if we specify rhel7.1 new feature with -M RHEL7.0/RHEL6.x on rhel7.1 host. Consequences might have 
1. From end user pov, boot successfully means we support it, however, we do not fully support new features under older machine type.

2. https://bugzilla.redhat.com/show_bug.cgi?id=1175099 and Bug 1172643 - migration/pci-bridge: 7.1rhev->7.0 fails

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.1.2-17.el7

How reproducible:
100%

Steps to Reproduce:
1.Boot guest with pci bridge or ovmf with -M rhel6.x on rhel7.1 host
2.
3.

Actual results:
Guest could be booted successfully but migration fail 

Expected results:
Guest should not be booted if we specify the devices we do not plan to support with -M


Additional info:

--- Additional comment from Paolo Bonzini on 2014-12-19 09:00:53 EST ---

PCI bridges were tech preview, so there's no problem in not supporting migration.  AHCI will probably be the same when we start supporting Q35 fully.

For OVMF probably the bug should not be closed, but just deferred to 7.2.  I'm reopening bug 1175099.

In any case, QE is already opening bug when they find new stuff not working on old machine types.  Changing this to a tracker.

----------------------------------------------
Cloning the BZ specifically for PCI bridge
(another BZ will be cloned for OVMF).
Comment 1 Paolo Bonzini 2015-09-08 13:22:00 UTC 
The PCI bridge feature works correctly if you use the old machine type on newer host, right?

If so, this is NOTABUG (and so is the tracker bug 1175220).  When you migrate to 7.0, where the feature was tech preview, it is implied that the VM becomes unsupported.

Since it is possible to migrate 7.1-with-7.0-machine-type to another 7.1-with-7.0-machine-type, blocking migration with the 7.0 machine type would be unnecessary.  The fix (rejecting incoming migration) would have to be applied in 7.0, which is long dead.
Comment 2 Marcel Apfelbaum 2015-09-08 15:43:25 UTC 
(In reply to Paolo Bonzini from comment #1)
> The PCI bridge feature works correctly if you use the old machine type on
> newer host, right?
> 
> If so, this is NOTABUG (and so is the tracker bug 1175220).  When you
> migrate to 7.0, where the feature was tech preview, it is implied that the
> VM becomes unsupported.
> 
> Since it is possible to migrate 7.1-with-7.0-machine-type to another
> 7.1-with-7.0-machine-type, blocking migration with the 7.0 machine type
> would be unnecessary.  The fix (rejecting incoming migration) would have to
> be applied in 7.0, which is long dead.

Yes, there is no reason for bridge to not work properly on older machine types.
Closed it as NOTABUG.

Thanks,
Marcel
Note You need to log in before you can comment on or make changes to this bug.