Karel Zak <kzak@xxxxxxxxxx> writes: > On Mon, Sep 29, 2008 at 11:01:05PM +0200, Karel Zak wrote: >> On Mon, Sep 29, 2008 at 03:17:28PM +0200, Matthias Koenig wrote: >> > The tool has been written by Ky Srinivasan <ksrinivasan@xxxxxxxxxx>. >> >> Do we really need a new tool? IMHO the hypervisor Vendor ID should >> be exported by kernel in /sys or /proc -- or we can add this info to >> lscpu(1) or so. > > The (untested) patch below introduces a new fields "Hypervisor vendor > ID:" and "Para-Virtualized:" in lscpu(1). > > The "Hypervisor vendor ID:" field reports the raw ID, it means it works > for all hypervisors (the same logic like CPU "Vendor ID:"). > > I think this solution is a good compromise to avoid a new tool. Yeah, Ok. Avoiding a new tool seems to be the better approach in this case. I gave this patch a short try, but only running on bare metal, where it outputs: Hypervisor vendor ID: @ Para-Virtualized: Not Hmm, I think Para-Virtualized should read either Yes or No. 'Not' looks a bit strange. I guess '@' as Hypervisor vendor ID is not intentional. Matthias -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
