qemu/kvm win10 client cannot upgrade to win11

Here is windows health check screen 2.

Hi,

Thanks for reporting this bug.

How are you setting up the windows VM? Would you mind providing its configuration and/or a short reproducer so we can verify the issue?

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

Setup is done by clicking on "Create a new virtual machine" in Virtual Machine Manager and filling in the requested info.

You will find attached 7 screenshots of configuration details.

As best as I can recall, you only need to input CPU (8), RAM (8192 MiB), and disk (50 GiB).

The windows ISO file is read as is.

Hello,

Since Windows 11 requires TPM 2.0 to run, you will need a TPM emulator. To do this, make sure you have swtpm installed. In the terminal run:

sudo apt install swtpm swtpm-tools

With those installed, enter your virtual machine settings, click Add Hardware, select TPM, then choose:

Type: emulated
Model: TIS
Version: 2.0

You will also need secure boot. To do this you will have to edit the xml for your vm.

Start by going to Edit > Preferences > General in the main virt-manager window. Select Enable XML editing.

Now in your vm settings window, select Overview then the XML tab. in the <os> section add the following two lines:

<loader readonly="yes" secure="yes" type="pflash">/usr/share/OVMF/OVMF_CODE_4M.secboot.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/win10-2_VARS.fd</nvram>

and in the <features> section add the following line:

<smm state="on"/>

Click Apply then secure boot should be good to go

I get the following Windows boot error.

Note the extra line in the <os> section that cannot be deleted.

<boot dev="hd"/>

Here is the xml screenshot.

I implemented your 2 code additions separately.

First, TPM code was added to the xml. It worked fine.

Second, Secure Boot was added to the xml. It caused the windows boot error.

Hope this help.

To clarify the previous comment:

First, TPM settings were added to the windows VM. They worked fine.

Second, Secure Boot code was added to the xml. It caused the windows boot error.

@peterzay did you try to boot the system when you got to the screen you attached in comment #16? This is the UEFI interactive shell, it does not look like a boot error. You might try to change to the UEFI directory, maybe /EFI/BOOT, and execute the *.efi file in there. This might be a matter of boot order.

The "boot error" is reproducible.

1. start Virtual Machine Manager
2. click on Open
3. this opens a window called win10 on QEMU/KVM
4. in this window (3.), click on Power on the virtual machine (black triangle pointing right)
5. you get the "boot error" in window (3.)

As for executing *.efi, which one would you suggest from the attached screenshot?

Hi peterzay,

It seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: https://ubuntu.com/support/community-support

I'm marking this report as Incomplete for now. If you believe that this is really a bug, we'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. Thanks!

>provide a more complete description of the problem

What is missing from the description of the problem?

You have the precise steps required to reproduce this problem. It occurs on every attempt.

Whether "bug" or "configuration", the product does not work.

Please provide a fix.

Hello peterzay,

The secure boot failure may indicate you don't have it installed on your system. Try running:

sudo apt install ovmf

If it is not already installed try running your vm again.
Also it may help to enable SATA CDROM 1 in your boot options. Not having it has caused some issues for me in the past. See the screenshot for how to enable this.

Otherwise, if both fail, you may want to create a new vm and install Windows 11 from there with TPM2.0, secure boot, and SATA CDROM enabled from the start.

Hi Lena,

Package ovmf is already installed. It was probably installed by virt-manager.

You will find attached 2 screenshots of ovmf and OVMF folders in the system.

I added SATA CDROM 1 to the boot options as suggested.

I still get the win10 boot error (see attached).

Please bear in mind that I do not have win11. I have win10 that cannot upgrade to win11.

Are you suggesting I create a new VM, install win10 with TPM2.0, secure boot, and SATA CDROM enabled from the start to test for successful boot?

OVMF system folder

win10 boot error with SATA CDROM 1 boot option selected

Package ovmf is version 2022.02-3

I created a new VM; installed win10 with TPM2.0, secure boot, and SATA CDROM enabled from the start.

I got the same boot error.

Any suggestions?

P.S. The ISO file was downloaded from Microsoft and verified for SHA sum.

Does your boot screen show the "Press any key" screen before showing the error? If so press a key quickly during that time and it should boot into windows

Pressing any key quickly enough starts the boot process successfully.

In win10, PC Health Check now qualifies the OS as ok to upgrade to win11.

Please close this case.

Glad that worked, thanks! Marking as invalid since no new code was released.