Bug 784570 - imvirt fails to detect it's running under QEMU/KVM
Summary: imvirt fails to detect it's running under QEMU/KVM
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: imvirt
Version: 19
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-25 12:06 UTC by Lars Seipel
Modified: 2013-08-19 13:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-19 13:15:10 UTC
Type: ---


Attachments (Terms of Use)

Description Lars Seipel 2012-01-25 12:06:59 UTC
Description of problem:
When running imvirt inside a virtualized Rawhide system it fails to detect this and reports it's running on physical hardware. The host runs F16 and its virtualization stack.

Version-Release number of selected component (if applicable):
imvirt-0.9.0-6.fc17.x86_64

How reproducible:
100%

Steps to Reproduce:
1. make sure you are logged in with appropriate privileges (i.e. root)
2. run imvirt
  
Actual results:
[root@rawhidevm ~]# imvirt
Physical

Expected results:
The system is correctly reported as virtualized.

Additional info:
There is a new upstream version (0.9.1) which, according to the upstream changelog, improves detection of guests running under QEMU/KVM with virtio devices.

The similar program virt-what (also in Fedora) correctly identifies it is running on KVM.

Comment 1 Miroslav Suchý 2012-02-06 10:27:39 UTC
Can you please try new imvirt:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3765373

If it still fail, can you please provide output of "imvirt -d"?

Comment 2 Lars Seipel 2012-02-06 15:32:10 UTC
The new version from koji properly detects the system as running on KVM. Thanks.

Comment 3 Fedora End Of Life 2013-04-03 16:26:23 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 4 Miroslav Suchý 2013-08-19 13:15:10 UTC
Closing per #2


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