This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 499685

Summary: RFE - include virt type in virt-manager Guest->Details tab
Product: [Fedora] Fedora Reporter: James Laska <jlaska>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: berrange, crobinso, hbrock, jturner, markmc, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: virt-manager-0.8.0-2.fc12.noarch Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-15 06:30:53 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 498969    
Description Flags
Screenshot none

Description James Laska 2009-05-07 12:38:47 EDT
Created attachment 342877 [details]

Description of problem:

Presently, there is no indicator for the guest virt type (xenpv, xenfs, qemu, kvm, etc...) when looking at the virtual machine window for a guest (see screenshot attached).  

The only method I'm aware of is to run:
 # virsh dumpxml <guest> | grep qemu

Having this information present in the UI would be great.

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

How reproducible:

Steps to Reproduce:
1. Run virt-manager
2. Double click on a guest
3. Select the "Details" tab
4. Select the "Overview" section
Actual results:

See screenshot

Expected results:

Perhaps more verbose information about the type of virtualization used for the guest.

Additional info:
Comment 1 Mark McLoughlin 2009-05-07 13:06:55 EDT
Yeah, anything has got to be better than:
Comment 2 Cole Robinson 2009-05-12 13:34:13 EDT
I've pushed this upstream:

Details->Overview now lists HV Type, VM Arch, and Emulator path.

There is still the issue of the emulator being unable to open /dev/kvm, and continuing on it's merry way. My feeling is that if VM is of type='kvm', libvirt should look for that error message, and bomb out accordingly. Silently falling back to plain emulation is pretty sucky.
Comment 3 Mark McLoughlin 2009-05-21 16:34:52 EDT
Cool stuff, this will be fixed for F-12 with the next virt-manager release

(In reply to comment #2)
> Silently falling back to plain emulation is pretty sucky.  

Indeed. It's been discussed upstream and think the conclusion is that this behaviour won't be merged from qemu-kvm.git into qemu.git - i.e. expect this falling back to go away eventually
Comment 4 Mark McLoughlin 2009-09-15 06:30:53 EDT
This is in rawhide now