Bugs item #1831806, was opened at 2007-11-14 08:40 Message generated for change (Settings changed) made by iggy_cav You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1831806&group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Technologov (technologov) Assigned to: Nobody/Anonymous (nobody) Summary: [Feature Request] See KVM version from userspace Initial Comment: It would be very helpful, if I would be able to see several things from Qemu/KVM userspace: 1.KVM user space version 2.KVM kernel space version 3.If KVM kernel space loaded, the userspace must show current CPU capabilities has: VT-x, VT-d, FlexPriority, SVM, ... ============================================= Explanation: 1. KVM userspace has no ID at all. Having several versions installed makes it confusing. 2. modinfo kvm is not always good, because it shows which module installed on the hard disk in standard location, not which module is loaded into RAM. (which may be loaded manually from non-standard location) 3. Currently /proc/cpuinfo doesn't shows those advanced CPU capabilities :( This will make debugging/testing easier. -Alexey. 14.11.2007. ---------------------------------------------------------------------- Comment By: Anthony Liguori (aliguori) Date: 2008-05-26 12:18 Message: Logged In: YES user_id=120449 Originator: NO KVM now reports the userspace version in the QEMU help output. ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2007-11-25 08:07 Message: Logged In: YES user_id=1839746 Originator: YES >Since the kvm will print the module version when it is loaded, do we still need the first two working items? Well, that would help debugging/beta-testing mostly. As I have many versions installed at once. >For the third one, could you give me an example about the "advanced CPU capabilities"? Intel: VT, FlexPriority, FlexMigration, Extended Page Tables, VT-d... AMD: SVM, Nested Page Tables, ... ---------------------------------------------------------------------- Comment By: Neo Jia (chenghuan_jia) Date: 2007-11-25 03:47 Message: Logged In: YES user_id=446034 Originator: NO Could you provide any suggestions on the module version implementation? So, I can give a try. And for the "advanced CPU capabilities", I am looking into it now. Thanks, Neo ---------------------------------------------------------------------- Comment By: Technologov (technologov) Date: 2007-11-25 02:32 Message: Logged In: YES user_id=1839746 Originator: YES >Since the kvm will print the module version when it is loaded, do we still need the first two working items? Well, that would help debugging/beta-testing mostly. As I have many versions installed at once. >For the third one, could you give me an example about the "advanced CPU capabilities"? Intel: VT, FlexPriority, FlexMigration, Extended Page Tables, VT-d... AMD: SVM, Nested Page Tables, ... ---------------------------------------------------------------------- Comment By: Neo Jia (chenghuan_jia) Date: 2007-11-24 16:23 Message: Logged In: YES user_id=446034 Originator: NO Since the kvm will print the module version when it is loaded, do we still need the first two working items? For the third one, could you give me an example about the "advanced CPU capabilities"? Thanks, Neo ---------------------------------------------------------------------- Comment By: Avi Kivity (avik) Date: 2007-11-20 04:31 Message: Logged In: YES user_id=539971 Originator: NO kvm will now print the module version into the kernel log when loaded. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1831806&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
