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 1191617 - numa-enabled domain with rhel6.5.0 machine type fails to start
Summary: numa-enabled domain with rhel6.5.0 machine type fails to start
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Eduardo Habkost
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1191567
Blocks: 1190580
TreeView+ depends on / blocked
 
Reported: 2015-02-11 15:35 UTC by Michal Privoznik
Modified: 2015-03-05 23:24 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1191567
Environment:
Last Closed: 2015-03-05 23:24:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Eduardo Habkost 2015-02-26 18:59:01 UTC 
So, just to confirm everything is covered and I understood everything correctly:

Michal, is the fix for bug 1191567 going to make the QEMU-side fix unnecessary, or do we still have any existing regressions?

I am planning to close this as WONTFIX because that would require touching the BIOS shadowing fix we added for RHEL-6 migration support, and I assume that the libvirt patches for bug 1191567 and bug 1175397 are going to be enough for not making this bug reproducible on valid use cases (i.e. use cases where it would be a regression).

Note that this bug would be still reproducible on invalid use cases (e.g. enabling NUMA binding on rhel6 machine-types). But those cases were never supported anyway.
Comment 2 Michal Privoznik 2015-02-27 08:27:00 UTC 
(In reply to Eduardo Habkost from comment #1)
> So, just to confirm everything is covered and I understood everything
> correctly:
> 
> Michal, is the fix for bug 1191567 going to make the QEMU-side fix
> unnecessary, or do we still have any existing regressions?
> 
> I am planning to close this as WONTFIX because that would require touching
> the BIOS shadowing fix we added for RHEL-6 migration support, and I assume
> that the libvirt patches for bug 1191567 and bug 1175397 are going to be
> enough for not making this bug reproducible on valid use cases (i.e. use
> cases where it would be a regression).
> 
> Note that this bug would be still reproducible on invalid use cases (e.g.
> enabling NUMA binding on rhel6 machine-types). But those cases were never
> supported anyway.

Correct. Libvirt workaround is just enough. This can be closed. But lets have an upstream discussion about the whole capabilities problem. I mean (as you've probably read in one of my emails), there are two problem here:

1) libvirt checks qemu capabilities with '-M none', but starts domains with machine type configured in domain XML. This is a libvirt bug.

2) Even if 1) was fixed, we need qemu to report the correct capabilities for machine type. That is, if we start qemu with '-M rhel6.5.0' for instance, and query supported objects, we can't find memory_backend_ram, as it's clearly unsupported.

But as far as this BZ goes, its okay to close this (sorry for the noise) and have the design discussion upstream.
Comment 3 Jiri Denemark 2015-02-27 10:17:17 UTC 
(In reply to Michal Privoznik from comment #2)
> 1) libvirt checks qemu capabilities with '-M none', but starts domains with
> machine type configured in domain XML. This is a libvirt bug.

Not really, it's actually a feature. We don't want to start QEMU with every possible machine type when probing for supported features. If there are features which depend on machine type, we need to have a way to probe for them with -M none.
Comment 4 Eduardo Habkost 2015-03-05 23:24:43 UTC 
This is a QEMU limitation that libvirt is now able to workaround, and is specific for the RHEL-6 migration compatibility code in RHEL-7. Closing as DEFERRED.
Note You need to log in before you can comment on or make changes to this bug.