Bug 1286778 - [RFE] Downstream appliance proposes as default just one core
Summary: [RFE] Downstream appliance proposes as default just one core
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhevm-appliance
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-3.6.1
: 3.6.0
Assignee: Anatoly Litovsky
QA Contact: Gonza
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-30 17:33 UTC by Simone Tiraboschi
Modified: 2016-03-09 21:44 UTC (History)
5 users (show)

Fixed In Version: rhevm-appliance-20151209.0-1
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-09 21:44:45 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0385 0 normal SHIPPED_LIVE rhevm-appliance bug fix and enhancement update 2016-03-10 02:43:23 UTC

Description Simone Tiraboschi 2015-11-30 17:33:57 UTC 
Description of problem:
Downstream appliance proposes as default just one core which makes it quite slow.

Version-Release number of selected component (if applicable):
rhevm-appliance-20151119.0-1.x86_64.rhevm.ova

How reproducible:
100%

Steps to Reproduce:
1. check the file
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Gonza 2015-12-14 10:08:30 UTC 
Verified with:
rhevm-appliance-20151209.0-1.x86_64.rhevm.ova

# cat master/vms/9059c326-bbdc-4442-b35b-d674e84d75ca/9059c326-bbdc-4442-b35b-d674e84d75ca.ovf | xmllint --format -
...
      <Item>
        <rasd:Caption>2 virtual CPU</rasd:Caption>
        <rasd:Description>Number of virtual CPU</rasd:Description>
        <rasd:InstanceId>1</rasd:InstanceId>
        <rasd:ResourceType>3</rasd:ResourceType>
        <rasd:num_of_sockets>1</rasd:num_of_sockets>
        <rasd:cpu_per_socket>2</rasd:cpu_per_socket>
      </Item>
...
Comment 5 errata-xmlrpc 2016-03-09 21:44:45 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:0385
Note You need to log in before you can comment on or make changes to this bug.