On 28 February 2014 02:05, Alexander Graf <agraf@xxxxxxx> wrote:
> > Am 28.02.2014 um 03:56 schrieb Arnd Bergmann <arnd@xxxxxxxx>
> >> Replace Windows by "Linux with custom drivers" and you're in the same
> >> situation even when you neglect Windows. Reality will be that we will
> >> have fdt and acpi based systems.
> > We will however want to boot all sorts of guests in a standardized
> > virtual environment:
> > * 32 bit Linux (since some distros don't support biarch or multiarch
> > on arm64) for running applications that are either binary-only
> > or not 64-bit safe.
> > * 32-bit Android
> > * big-endian Linux for running applications that are not endian-clean
> > (typically network stuff ported from powerpc or mipseb.
> > * OS/v guests
> > * NOMMU Linux
> > * BSD based OSs
> > * QNX
> > * random other RTOSs
*snip*
> You're forgetting a few pretty important cases here:
>
> * Enterprise grade Linux distribution that only supports ACPI
> * Maybe WinRT if we can convince MS to use it
> * Non-Linux with x86/ia64 heritage and thus ACPI support
I think we need limit the scope of the spec a bit here.
For a this VM system specification, we should describe what is simple to set up and high performance for KVM, Xen and mainline Linux. For everyone else, there is Qemu where we can mangle to provide whatever the guest OS might want.
Re UEFI,
> > Am 28.02.2014 um 03:56 schrieb Arnd Bergmann <arnd@xxxxxxxx>
> >> Replace Windows by "Linux with custom drivers" and you're in the same
> >> situation even when you neglect Windows. Reality will be that we will
> >> have fdt and acpi based systems.
> > We will however want to boot all sorts of guests in a standardized
> > virtual environment:
> > * 32 bit Linux (since some distros don't support biarch or multiarch
> > on arm64) for running applications that are either binary-only
> > or not 64-bit safe.
> > * 32-bit Android
> > * big-endian Linux for running applications that are not endian-clean
> > (typically network stuff ported from powerpc or mipseb.
> > * OS/v guests
> > * NOMMU Linux
> > * BSD based OSs
> > * QNX
> > * random other RTOSs
*snip*
> You're forgetting a few pretty important cases here:
>
> * Enterprise grade Linux distribution that only supports ACPI
> * Maybe WinRT if we can convince MS to use it
> * Non-Linux with x86/ia64 heritage and thus ACPI support
I think we need limit the scope of the spec a bit here.
For a this VM system specification, we should describe what is simple to set up and high performance for KVM, Xen and mainline Linux. For everyone else, there is Qemu where we can mangle to provide whatever the guest OS might want.
Re UEFI,
Riku
_______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm
