Dear all,
My name is Olivier, I've been lurking on this forum for some weeks now, reading a lot. I'm an amateur sysadmin for my local server. I'm dipping my toe in this community with the hope of getting to know proxmox a little better.
I'm planning to migrate from an Ivy Bridge-era xeon E3-1240v2 running Debian/KVM/libvirt to a Ryzen 7 5800X running Proxmox 7.x. (because RAM limitations are an issue, some CPU-bound tasks also).
The old host has 2x 250Gb SSDs in mirror raid as root file system + with lvm for the VMs root filesystems. + 3 large-ish (8-10 To each) spinning drives passed directly to the VMs with data. (all btrfs or ext4).
This host runs 2 VMs with libvirt.
1) one for NFS share on the LAN + the occasional Minecraft or Satisfactory server
2) the second with lots of online services (a mail stack, nextcloud, mastodon, jitsi, xmpp ....).
Each VM gets 1 spinning drive passed through for its big data (the NFS server gets 1 drive, the Nextcloud data folder gets the other, sort of)
Now for the PVE part:
- Ryzen 7 5800X, 2x 1To commercial PCIe NVMes for system + VMs
- I intend to use LVM-thin on the PVE host for the VMs root fs because it's LVM on the previous host so migration should be easy AND because I hear ZFS is a bad idea for commercial NVMe. (wear, data safety, etc...)
Am I correct ?
- I'm not sure how the spinning drives will be named and presented to the VMs. the services will not work properly on first start but that may not be a big issue, so that I can sort out which drive goes where. I've read this and it helps a lot
** Should I comment the fstab lines in the VMs before first start ? (so that the VM starts properly first).
** Is it a good idea to "prepare" the vms before shutting them down on the old server (comment their /dev/vdX lines in fstab, add the /dev/disk/by-id lines) since ?
** is there a best practice for disk passthrough (performance-wise) ? ... to prevent stutter?
- Should I study other solution instead of complete disk passthrough ? I don't have 2 or 3 spare spinning drives to create a raid5 or something and didn't intend to do that.
Thanks for reading all of this. I hope I didn't forget anything major. As it's a home thing I don't have a deadline or a project milestone to reach. i just want to do this right. I'm also studiying Proxmox for a non-profit, but that's another story.
Kind regards,
Aqua
My name is Olivier, I've been lurking on this forum for some weeks now, reading a lot. I'm an amateur sysadmin for my local server. I'm dipping my toe in this community with the hope of getting to know proxmox a little better.
I'm planning to migrate from an Ivy Bridge-era xeon E3-1240v2 running Debian/KVM/libvirt to a Ryzen 7 5800X running Proxmox 7.x. (because RAM limitations are an issue, some CPU-bound tasks also).
The old host has 2x 250Gb SSDs in mirror raid as root file system + with lvm for the VMs root filesystems. + 3 large-ish (8-10 To each) spinning drives passed directly to the VMs with data. (all btrfs or ext4).
This host runs 2 VMs with libvirt.
1) one for NFS share on the LAN + the occasional Minecraft or Satisfactory server
2) the second with lots of online services (a mail stack, nextcloud, mastodon, jitsi, xmpp ....).
Each VM gets 1 spinning drive passed through for its big data (the NFS server gets 1 drive, the Nextcloud data folder gets the other, sort of)
Now for the PVE part:
- Ryzen 7 5800X, 2x 1To commercial PCIe NVMes for system + VMs
- I intend to use LVM-thin on the PVE host for the VMs root fs because it's LVM on the previous host so migration should be easy AND because I hear ZFS is a bad idea for commercial NVMe. (wear, data safety, etc...)
Am I correct ?
- I'm not sure how the spinning drives will be named and presented to the VMs. the services will not work properly on first start but that may not be a big issue, so that I can sort out which drive goes where. I've read this and it helps a lot
** Should I comment the fstab lines in the VMs before first start ? (so that the VM starts properly first).
** Is it a good idea to "prepare" the vms before shutting them down on the old server (comment their /dev/vdX lines in fstab, add the /dev/disk/by-id lines) since ?
** is there a best practice for disk passthrough (performance-wise) ? ... to prevent stutter?
- Should I study other solution instead of complete disk passthrough ? I don't have 2 or 3 spare spinning drives to create a raid5 or something and didn't intend to do that.
Thanks for reading all of this. I hope I didn't forget anything major. As it's a home thing I don't have a deadline or a project milestone to reach. i just want to do this right. I'm also studiying Proxmox for a non-profit, but that's another story.
Kind regards,
Aqua