A set of "standard" virtual devices?

On the subject of virtualization; there are a number of devices which keep being invented and reinvented by just about every virtualization vendor for no really good reason.

I personally recently pointed out that a proper virtualization solution should handle entropy collection at the lowest level (where the physical hardware drivers are) and present a hw_rng interface to the guests. Unfortunately, none of the hardware-based hw_rng interfaces is sane enough to do that with, which calls for a virtual driver.

It would be nice if there was one, and not a dozen, such drivers.

I would therefore like to propose that the Linux Foundation register a PCI ID for use by LANANA ($3000/year), and we set up a LANANA registry for these device IDs, together with a description of the device interface each of them expect. Similarly, a Subsystem ID registry can be used (for virtualization vendors which don't have their own VID already) to distinguish different implementations.

Obviously, anyone who adheres to the published interface can use one of these VID:DIDs -- as far as I'm concerned, even hardware vendors; we'll use the SID to distinguish between implementations.

-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: [PATCH 0/1] IPN: Inter Process Networking
    ... you can add them to bridges, route between them, filter traffic between them, use multicast, etc as you would any real interface. ... if, however, you are talking about non-network communications, and want multiple processes to receive them, this sounds like exactly the thing that splice was designed to do, distribute data to multiple recipiants simultaniously and efficiantly. ... You can implement ptrace over utrace, ... use utrace also for virtualization in a cleaner, ...
    (Linux-Kernel)
  • Re: Registering ActiveX control on Vista
    ... meant to say that Vista does not have the fallback to HKCU\Software\Classes ... They normally extract the registry keys when creating the ... this is not related to Registry Virtualization. ...
    (microsoft.public.win32.programmer.ole)
  • Re: arch/xen is a bad idea
    ... >> work it is long term to keep an Linux architecture uptodate. ... > We're actually very well setup to handle this, ... > interface that gives good performance. ... > virtualization. ...
    (Linux-Kernel)
  • Re: Ini File vs Registry
    ... The registry is a good place to store app data only to the ... the U3 Flash drive but to make it appear to be part of the registry ... ... in Windows itself, and as a result, U3 was no more. ... virtualization of the Registry is quite a good solution ... ...
    (microsoft.public.vc.mfc)
  • Re: Detect when in 64bit OS
    ... For example, if you write to the registry from a 32 bit app, then try to read back the same key in a 64 bit app, you'll get totally different data. ... Disabling "virtualization" will be done by default when using the Orcas csharp compiler, pre-Orcas CSC buids should include a manifest by running mt.exe in order to disable "virtualization". ... static extern bool GetTokenInformationNative( ... int TokenInformationClass, ...
    (microsoft.public.dotnet.languages.csharp)