Bug 748466 - [vdsm-bootstrap] Intel host recognized as AMD processor
Summary: [vdsm-bootstrap] Intel host recognized as AMD processor
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: 3.1
Assignee: Dan Kenigsberg
QA Contact:
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-24 14:33 UTC by Kiril Nesenko
Modified: 2014-07-11 00:08 UTC (History)
5 users (show)

Fixed In Version: vdsm-4.9.6-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-09 08:05:56 UTC
oVirt Team: ---


Attachments (Terms of Use)
bootstrap.log (6.24 KB, application/x-bzip)
2011-10-24 14:33 UTC, Kiril Nesenko
no flags Details

Description Kiril Nesenko 2011-10-24 14:33:21 UTC
Created attachment 529886 [details]
bootstrap.log

Description of problem:
While installing host, noticed that Intel host recognized as AMD processor.

Mon, 24 Oct 2011 09:56:29 DEBUG    CPU vendor is GenuineIntel
Mon, 24 Oct 2011 09:56:29 DEBUG    virt support in cpu: True, in bios: True
Mon, 24 Oct 2011 09:56:29 DEBUG    <BSTRAP component='VT_SVM' status='OK' processor='AMD' message='Server supports virtualization'/>


Version-Release number of selected component (if applicable):


How reproducible:
vdsm-bootstrap-4.9-108.el6.x86_64

Steps to Reproduce:
1. Install Intel host and check the bootstrap log.
2.
3.
  
Actual results:
 Intel host recognized as AMD processor

Expected results:
 Intel host should be recognized as Intel processor.

Additional info:

Comment 2 Dan Kenigsberg 2011-10-24 14:52:43 UTC
Gosh, it is a very very old bug, since

commit 46ede4b17f7ba64c1c6f501a4b4aa4bb69845334
Author: Dan Kenigsberg <danken>
Date:   Tue May 25 18:09:51 2010 +0300

    BZ#591846 - vds_bootstrap accepts both rhel 5 & 6


http://gerrit.usersys.redhat.com/1060

Comment 4 Itamar Heim 2012-08-09 08:05:56 UTC
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/


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