I assume you are refering to the VM, as on Proxmox itself you need to change “real” hardware!
The Machine Type can be changed - without issues. But do it when the VM is turned off, a reboot will not suffice, on Proxmox the VM actually needs to be turned off before a change is recognized and used.
As your only HD is using IDE (ide0) changing the SCSI controller will not affect anything. You would also need to install the stuff on a VirtIO SCSI disk. But you can do it, no probs will arise.
You can change the network device, but you may need to reallocate it in Rocky. Using the qemu-guest-agent is strongly advised, this gives you stable and fast shutdowns from the Proxmox console (Also if using a UPS…). But the best part is it will show you all IPs (IPv4 and IPv6) used by the VM!
Here is a Win10 “Admin-PC” running as VM in Proxmox. Note the Network NIC speed!
This also uses the VirtIO network drivers - the ones from RedHat on a ISO, best installed directly when installing Windows!
And also use VirtIO SCSI drivers (And the serial driver needed for the Qemu guest agent…).
Proxmox ZFS Memory Limits
Follow the instructions here under " Limit ZFS Memory Usage" from this official doc:
https://pve.proxmox.com/wiki/ZFS_on_Linux#sysadmin_zfs_limit_memory_usage
and ZFS also this:
https://pve.proxmox.com/wiki/ZFS:_Tips_and_Tricks#Snapshot_of_LXC_on_ZFS
A very important note on ZFS booting:
When installing Proxmox with ZFS for booting it is important to note that you will NOT have any working Swap!
The trick is to install Proxmox on the disk (or mirror, which you are not using…) and in the advanced options of the disk settings, reduce the disk size by 16 GB. This can be formatted as a swap partition later on, after the install, with normal Debian commands, as Proxmox is based on Debian! I can help with this if needed.
For those who still think swap is not needed on Linux or Proxmox, I’ll show this:
This box still has ample 20% of 128 GB RAM unused - so why is swap maxed out?
And this box is NOT underpowered: 40 CPU cores…
ZFS RAM settings:
Show contents of nano /etc/modprobe.d/zfs.conf
If I missed out anything, just ask!
I strongly suggest to follow / read this:
and install your VM and Proxmox exactly the way you want it, so that it can and will run the next 5 years or longer, hardware defects aside!
As you run Proxmox, do things step by step, make backups (not snapshots) in between!
A backup is independant, a snapshot still needs the original disk. As changing the disks might be an option, a snapshot restore might present issues…
Good luck!
My 2 cents
Andy