Description of problem: I've got a nested VM setup: RHEL 6 bare-metal => RHEL 5 xen kernel ====> F13 paravirt guest Running virt-what inside the nested guest is displaying nothing (with the initial virt-what proposal for Fedora) or just 'kvm' (after applying the patch from bug 647862). Version-Release number of selected component (if applicable): 64-bit bare-metal host: qemu-kvm-0.12.1.2-2.113.el6.x86_64 32-bit xen intermediary: kernel-xen-2.6.18-228.el5 xen-3.0.3-117.el5 libvirt-0.8.2-9.el5 32-bit F13 paravirt guest: dmidecode-2.10-1.39.fc12.i686 virt-what-1.3-3.fc13.i686 How reproducible: Steps to Reproduce: 1. setup a nested paravirt guest inside a xen kernel KVM guest 2. try virt-what, or its constituent commands 3. Actual results: In the nested F13 guest as root: $ virt-what # unpatched $ virt-what.647862 # patched for '-cpu qemu32' issue kvm $ /usr/libexec/virt-what-cpuid-helper KVMKVMKVM $ dmidecode # dmidecode 2.10 # No SMBIOS nor DMI entry point found, sorry. $ ls -a /proc/xen/ . .. $ ls /dev/xvda /dev/xvda $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 3 model name : Pentium II (Klamath) stepping : 3 cpu MHz : 2666.758 cache size : 4096 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 4 wp : yes flags : fpu tsc msr pae cx8 cmov mmx fxsr sse sse2 up pni popcnt hypervisor bogomips : 5333.51 clflush size : 32 cache_alignment : 32 address sizes : 36 bits physical, 32 bits virtual power management: From the xen intermediary: $ virsh dumpxml fedora_13-xen <domain type='xen' id='3'> <name>fedora_13-xen</name> <uuid>305644c6-60c5-ed3d-747e-afbb10d5be5b</uuid> <memory>524288</memory> <currentMemory>524288</currentMemory> <vcpu current='1'>2</vcpu> <bootloader>/usr/bin/pygrub</bootloader> <os> <type>linux</type> <kernel>/var/lib/xen/boot_kernel.KR8hBL</kernel> <initrd>/var/lib/xen/boot_ramdisk.9fC3i1</initrd> <cmdline>ro root=/dev/mapper/vg_fedora13xen-lv_root rd_LVM_LV=vg_fedora13xen/lv_root rd_LVM_LV=vg_fedora13xen/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet</cmdline> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <disk type='block' device='disk'> <driver name='phy'/> <source dev='/dev/hdb'/> <target dev='xvda' bus='xen'/> </disk> <interface type='bridge'> <mac address='00:16:36:0b:49:87'/> <source bridge='virbr0'/> <script path='vif-bridge'/> <target dev='vif3.0'/> </interface> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target port='0'/> </console> <input type='mouse' bus='xen'/> <graphics type='vnc' port='5902' autoport='yes' listen='127.0.0.1' keymap='en-us'/> </devices> </domain> Expected results: virt-what is probably okay printing kvm, seeing as how the guest is running nested inside a xen host which itself is a kvm guest. But it should _also_ be printing some form of xen Additional info: Let me know if you can think of anything else useful to check. Is it reasonable to assume that the existence of /dev/xvda is a good indicator of a virtual disk provided by xen?
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
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.