bkingsolver

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

bkingsolver's Achievements

Noob

Noob (1/14)

4

Reputation

  1. That fixed it. Following that guide way back in the past will break the upgrade to 6.11.1. It is a custom script and not a problem with 6.11.1. Here are the steps I followed to successfully upgrade to 6.11.1, for those that followed this guide to add TPM support: https://www.linkedin.com/pulse/swtpm-unraid-zoltan-repasi/ In an unraid shell, delete these files on the unraid server /boot/extra/libseccomp.txz /boot/extra/libtpms.txz /boot/extra/swtpm_final.txz Next, in the unraid webpage, go to Settings/User Scripts Click on the gear for the startup_script (mine was called swtpm startup_script) and click Delete Script Then, head over to Tools and upgrade to 6.11.1.
  2. https://www.linkedin.com/pulse/swtpm-unraid-zoltan-repasi/ via this thread: I'm backing up my system, going back through the guide backing out changes, then will upgrade to 6.11.1 and report back.
  3. No joy. Here's what I did. Renamed that VM from Darth-Eleven to DarthEleven Upgraded to 6.11.1 On reboot, none of my OVMF TPM VMs booted (tried all of Darth [Win10], DarthEleven [Win11], and rhel9). My OVMF VM (fedora) booted fine. I tried to create a new Windows 11 VM backed by OVMF TPM, and got the error about it lacking TPM 2.0 support when I hit the Create button on the VM creation screen. I reverted to 6.11.0 and things are working well again. @20051231 might be on to something. I followed instructions in the forums to add TPM support before it was officially supported by unraid. I'm tracking down the instructions on what I did to see if I can undo it. However, I'm guessing others followed this procedure as well and are surprised that 6.11.0 works but 6.11.1 doesn't in this configuration. I attached updated diagnostics if it's helpful. I appreciate your help with tracking this down! tower-diagnostics-20221013-2000.zip
  4. A correction on this: the OVMF TPM VMs work fine on 6.11.0 and broke on 6.11.1. I'm not sure why I entered 6.10.0 in the bug report. @Paulo Vieira - I reverted from 6.11.1 to 6.11.0 and the VMs worked fine for me.
  5. Thank you, let me know if I can provide any other information. I have VMCustom icons. I wonder if it didn't run on startup like it normally does.
  6. After upgrading from 6.10.0 to 6.11.1, VMs with OVMF TPM fail to start. Even a new VM with OVMF TPM fails with to start this same error. VMs start normally after reverting to 6.10.0. I attached the diagnostics file generated before reverting. tower-diagnostics-20221006-1928.zip
  7. One other issue after upgrading to 6.11.1: This affects both my Windows 10 and Windows 11 (both using OVFM TPM). I tried to create a new VM from scratch with OVMF TPM and it failed with the same error on first start. I saved diagnostics, reverted, and things are fine. Should I file a bug report on this?