mirror of
https://github.com/virt-manager/virt-manager.git
synced 2025-01-11 05:17:59 +03:00
26ecf8a5e3
This was previously discussed here: https://listman.redhat.com/archives/virt-tools-list/2020-September/msg00017.html For the x86 + hvm case, failure to specify an --osinfo/--os-variant OS, and failure to detect an OS from install media, will now throw a big error: ``` --os-variant/--osinfo OS name is required, but no value was set or detected. This is now a fatal error. Specifying an OS name is required for modern, performant, and secure virtual machine defaults. If you expected virt-install to detect an OS name from the install media, you can set a fallback OS name with: --osinfo detect=on,name=OSNAME You can see a full list of possible OS name values with: virt-install --osinfo list If your Linux distro is not listed, try one of generic values such as: linux2020, linux2018, linux2016 If you just need to get the old behavior back, you can use: --osinfo detect=on,require=off Or export VIRTINSTALL_OSINFO_DISABLE_REQUIRE=1 ``` The thread goes into more detail, but basically, for x86 VMs at least, it's unlikely you will _ever_ want the default 'generic' behavior, which gives gives no virtio, no PCIe, no usb3, IDE disks, slow network devices, etc. Many people use virt-install in scripts and CI, and this may now cause breakage. The environment variable is there to help them get things back to normal as quick as possible, but it will still noisy up their logs with the warning to hopefully get them to make a useful change to their virt-install invocations. This is limited to x86, since that's where most of our defaults historically differ, and where we can depend on libosinfo to give the most accurate device info. This may be relevant to change for other KVM architectures in the future. Signed-off-by: Cole Robinson <crobinso@redhat.com> |
||
|---|---|---|
| .. | ||
| virt-clone.rst | ||
| virt-install.rst | ||
| virt-manager.rst | ||
| virt-xml.rst | ||