Pined guide: https://forums.unraid.net/topic/29679-guide-virtualizing-unraid-on-proxmox-31/

PVE INSTALL guide: https://forums.unraid.net/topic/179219-guide-proxmox-virtualize-unraid-experimental-with-v7/

NEW Internal HD ISO Boot disk

https://forums.unraid.net/topic/197992-new-iso-installer-for-testing/

So yet another Virtualize Unriad guide post.

Step 1 setup PVE VM for unraid:

Some Recommend PVE Options.

First lets create a VM:

It Is Important to Note THE internal Boot needs TPM and Potentaly Secure boot key...

Pleas Note YOU MUST TURN OFF BALLONNING AND ALLOW KSM! Unraid exists in RAM even after boot.

This is a bare min PVE configuration on lattest PVE version 9.1.6 as of writing.

Some recommended side options for the web UI PVE and edits.

One of the first things I do is keep the connections SATA at creation teh HD is sata 0 So let's remove the disk drive and readd it as sata 1.

Now that the cd rom is removed, we need to recreate it.

We alos want to add a VirtIO RNG

and edit the display options to asist GUIi based installs via ISO

With that done we now need to fix boot options and set the disk drive to boot.

Now it time to start the console and enter BIOS by clicking in the console and hitting "esc" multiple times to get to the boot menu:
The goal is to disable secureboot and enable custom Secure Boot keys.

This should get you into PVE boot menu

Go to Device Manger > Secure Boot Configuration
arrow keys to the X and hit space bar
and change standard to Custom Mode
DON"T FORGET TO HIT f10 and y to SAVE!

Then hit "esc" multiple times and hit continue to boot You have successfully set up Unraid for Generic Default Linux Secure Boot and Stable VM Boot

Edited April 1Apr 1 by bmartino1
Data

ISO installer boot Unraid internal boot setup

The ISO lads and the initial Boot Process begin.

We must first download the Uriad Zip file:

We then select option 2 with the current ISO pointing at the beta zip file.

By Default the Option is NO

But lets see the Log and what it did:

Thats it We now need to power off and tell boot options to boot to the HD first. It is better to Power off

And now enjoy unriad booting form a HDD:

Edited April 1Apr 1 by bmartino1
data - typo

Let's take a look around



Yes, this installation makes the boot partition a ZFS Partition:

I've noticed a small PVE QEMU virtualized unraid issues where its format doesn't allocate or read the VM disk even when set to raw. I ofter after in have to add 10 GB-ish more to the Virtual disk to help with disk size and format allocation.

In my case, this is VM 101 and the disk is sata0 the PVE command to assign more data to the VM disk as I only gave 80 GB but as you can see per the web UI its reading 85...

qm resize 101 sata0 +10G

Note adding size doesn't change the partition. Usually, other disk commands are needed when you add storage to expand and use the added space...

Power off and power on and lets take another look...

(as this is/ was more for testing... ) I'm not ready to move a paid key over and boot mode requires a paid key can't do a trial at boot on beta instance for test... Given Virtualized HD is being read as "Invalid".)
Unraid OS No Boot Device

tower-diagnostics-20260401-1646.zip

Outside of that, there side things I would recommend to a virtualized Unraid
1 set the pve qemu to run qemu guest tools as seen here:
https://forums.unraid.net/topic/179219-guide-proxmox-virtualize-unraid-experimental-with-v7/#findComment-1484536

Thanks simon.

we do this by editing the go file in boot

cd /boot/config/
nano go

as seen here:

root@Tower:/boot/config# cat go 
#!/bin/bash

# Start the Management Utility
/usr/local/sbin/emhttp

#Guest Tools
/usr/bin/qemu-ga -l /var/log/qemu-ga.log -d

Edited April 1Apr 1 by bmartino1

Following information per the iso post and support. Thanks Limetech and SimonF!
https://docs.unraid.net/unraid-os/troubleshooting/tpm-licensing-faq/

VM unirad will still need a USB passed.
https://unraid.net/blog/unraid-7-3-beta.1?srsltid=AfmBOopz_zT7WWOn5GDbJLneiqE988kR3ZRhxluxK-NZxTAXfleeHs7K

Internal Boot and Licensing: Connected, But Not the Same Thing

Internal Boot determines where Unraid boots from. Licensing determines what hardware your license is tied to. These are separate choices, and that distinction matters:

• Boot internally + and keep your flash drive for licensing

• Boot internally + and use TPM for licensing, if your hardware supports it

As another has said you could pass a USB formatted fat and Labled UNRIAD to act as the license only.
This will act as a GUID license. to still use internal boot. but it would be easier to just use the USB for unraid. and pass the USB at that point...

Edited April 7Apr 7 by bmartino1
License info

see also