GNOME Bugzilla – Bug 688759
support key to tell desktop whether or not to behave differently if virtualization is detected
Last modified: 2013-01-14 14:22:01 UTC
+++ This bug was initially created as a clone of Bug #684801 +++ 1) I plan to use VMs as a testing tool, and having the system behave differently makes it more likely that bugs will make it to people who actually run GNOME on bare metal. Especially bugs in subsystems like this. 2) Some people want to deploy GNOME in VMs by default, where the host is just a thin hypervisor. In this scenario, they often want behaviors that make the system feel like a "real" host. Anyways, If we go this way, I'd really like a GNOME-global switch to disable any special behaviors when run as a VM. Maybe gnome-settings-daemon should have a gsettings key "enable-virtualization-customization"? It could default to true.
What do you consider customization ? Is showing 'running kvm' in the info panel already out ?
(In reply to comment #1) > What do you consider customization ? > Is showing 'running kvm' in the info panel already out ? That's fine - it's not a functional change.
I would implement this through a kernel command-line option (as we do to override the fallback mode for example). It survives session changes and can be changed globally with minimum fuss.
I'll close this as we don't want a key in GSettings. This should get documented in the sysadmin guide (and/or the release notes) along with the kernel command-line options used by gnome-session.
Created attachment 233423 [details] [review] power: Allow overriding the VM detection In some cases we want the power plugin running in a virtual machine to behave as it would on bare metal. The gnome.is_vm=[01] kernel command-line argument allows us to override the detection that would be done through systemd.
Attachment 233423 [details] pushed as 6dde03d - power: Allow overriding the VM detection