Search results

OK, I have played around with things a bit. After a clean install the vm boots as expected. After doing the initial update with adding the latest kernel, the next reboot things break. On a standard bare metal setup using UEFI, installing and running Fedora 33 just works even after several...

After running that, the upgrade is still failing saying that the type is not supported. Even before running the skip, it would not complain about the TPM.

Which one of the two scripts do I run?

Is that on the host or quest side?

VM config file: root@odin:~# cat /etc/pve/nodes/odin/qemu-server/103.conf agent: 1 bios: ovmf boot: order=sata0;ide2;net0 cores: 4 efidisk0: datastore2s:vm-103-disk-1,efitype=4m,pre-enrolled-keys=1,size=1M hostpci0: 0000:04:00.0 ide2...

That is good to know. Looking at the boot order in the GUI, the UEFI does not show up. Is there a command line to add it and make it first?

Hmmm...... I think I see the problem. Looks like the order order change is NOT getting saved. I go 'Boot Maintenance Manager' -> 'Boot Options' -> 'Change Boot Order', make the fedora entry be first, and save at every point backing out of the menu options. Also the 'Boot Next Value'...

Followed those steps, and it still boots to the initial OVMF Menu screen. I added a new 'fedora' option and made that the first entry, but still boots to the OVMF menu. Deleted both fedora entries, added a bootable iso image to the cd, and it still boots to the OVMF menu. Added back a new...

Anyone else got any ideas on what to do so the VM boots as expected?

The boot order is: ide2, scsi0,net0 I tried swapping the order to: scsi0, ide2,net0 and that did not make any difference.

Yes, it was added before I did the guest os install.

Plus with each reboot, it enables the *&@(# secure boot nonsense.....

I am running proxmox 7.1 and I got some behavior with a VM I do not understand. The VM is running Fedora 33 with a passthrough disk controller. Initially I had the BIOS set to SeaBIOS, but the VM would hang on boot with the Machine UUID line. I switched over to OVMF, added an efi disk...

I am trying to get a Windows 10 guest to upgrade to Windows 11 and keeps failing on the stupid CPU check. The host is running pve-manager/7.1-4/ca457116 and has a pair of Xeon E5-2680v3 CPUs. I have tried qemu64 and host, but it doesnt matter. I also modified the Windows 11 ISO as point...

I have a ASMedia Technology ASM2142 USB3.1 card that I am passing through to a linux guest VM. On both the host and guest it shows up in lspci [guest] 00:11.0 USB controller: ASMedia Technology Inc. ASM2142 USB 3.1 Host Controller (prog-if 30 [XHCI]) Subsystem: ASMedia Technology Inc...

I am running version 7.1

Anyone know the CPU type that should be used for Windows 11. The proxmox host has E5-2680v3 cups installed and setting the guest to either host, kvm64, or qemu64 causes the windows 11 cpu check to fail for unsupported cpu type.

Is there any any to do any type of customization on the summary page for the node(s)? It would be awesome to add things like disk statistics/usage, lm_sensor data, ipmi data, etc.

At least with 7.1-4/ca457116 'use physical CD/DVD' might need some more polishing. When using with for a Linux/Fedora guest, the guest is seeing errors with dd, vlc, mplayer, and tar. Now if the host dumps the CD/DVD to an iso file with dd and then presents that iso to the guest, the guest...

A VM guest.