From d7d8461f7b38765cde327aba43e421416f16b425 Mon Sep 17 00:00:00 2001 From: Mike Degatano Date: Mon, 8 Apr 2024 12:42:55 -0400 Subject: [PATCH] Document unsupported reason 'virtualized image' (#31971) * Document unsupported reason 'virtualized image' * Apply suggestions from code review Co-authored-by: Stefan Agner * Fix title * Use the unsupported reason in description --------- Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Co-authored-by: Stefan Agner --- .../unsupported/virtualization_image.markdown | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 source/more-info/unsupported/virtualization_image.markdown diff --git a/source/more-info/unsupported/virtualization_image.markdown b/source/more-info/unsupported/virtualization_image.markdown new file mode 100644 index 00000000000..8a88c2cb81f --- /dev/null +++ b/source/more-info/unsupported/virtualization_image.markdown @@ -0,0 +1,18 @@ +--- +title: "Incorrect image for virtualization" +description: "More information on why virtualization image marks the installation as unsupported." +--- + +## The issue + +Your Home Assistant OS installation appears to run in a virtualized environment using +a disk image which is not meant to run in a virtualized environment. + +Home Assistant OS publishes specific images which support being run on a virtualized +system. These are optimized to run in virtual environments, e.g. have guest tools installed +and para-virtualization drivers enabled. + +## The solution + +You need to reinstall Home Assistant OS using an image which supports being run +on a virtualized system, [see instructions here](/installation/alternative).