mirror of
https://github.com/virt-manager/virt-manager.git
synced 2024-12-22 13:34:07 +03:00
ec434948a8
When shim in the guest sees unpopulated EFI NVRAM, like when we create a new UEFI VM, it invokes fallback.efi to populate initial NVRAM boot entries. When the guest also has a TPM device, shim will do a one time VM reset. This reset throws off the reboot detection that is central to virt-install's install process. The main install case that this will usually be relevant is the combo of UEFI and --cloud-init. The latter usually implies use of a distro cloud image, which will be using shim, and the --cloud-init process requires a multi stage install compared to just a plain import install. For that case, we disable the default TPM device for the first boot. https://bugzilla.redhat.com/show_bug.cgi?id=2133525 Signed-off-by: Cole Robinson <crobinso@redhat.com> |
||
|---|---|---|
| .. | ||
| devices | ||
| domain | ||
| install | ||
| __init__.py | ||
| _progresspriv.py | ||
| buildconfig.py | ||
| capabilities.py | ||
| cli.py | ||
| cloner.py | ||
| connection.py | ||
| diskbackend.py | ||
| domcapabilities.py | ||
| generatename.py | ||
| guest.py | ||
| logger.py | ||
| network.py | ||
| nodedev.py | ||
| osdict.py | ||
| pollhelpers.py | ||
| progress.py | ||
| snapshot.py | ||
| storage.py | ||
| support.py | ||
| uri.py | ||
| virtclone.py | ||
| virtinstall.py | ||
| virtxml.py | ||
| xmlapi.py | ||
| xmlbuilder.py | ||
| xmlutil.py | ||