Search results

Thanks. I’ll raise the feature request and post the link back here! Thanks!

If a single bootable ZFS disk (or at least a partition of) is able to run o/s and VMs and replicate VMs to another Node, that would be great! Yes - Id prefer to use a second disk to split local o/s and VMs but with certain NUCs the only option for a second local disk is USB.

Thanks for the update @fabian ! This maybe a little off topic, but related - I’m wondering whether this would enable booting PVE from a single ZFS root disk (using UEFI) and also enabling that single ZFS root disk to hold VMs and act as a replicable ZFS disk? This would be useful for me since...

This would be a good feature to add - The ability to configure a VM to use a Percentage of physical CPUs / vCPUs depending on the total available cores on host that is running the VM... I also have a VM which is configured to use say 8 Cores but this VM cannot automatically start on my failover...

Ive raised this as a bug with Proxmox

If the Proxmox team can confirm it is a bug, then I’m happy to raise it as a bug via the Proxmox bugzilla site

Is this still something that is planned for Proxmox 6?

Nope! I’ve left the c-states as is and haven’t had another crash even though I’ve experimented both with putting the suspect node under load and completely free for prolonged periods of time... still no crash... I suspect the kernel upgrade fixed it...

Glad it’s working well for you!

Yes, there is a standard Debian package for this and it’s fairly simple to setup - Follow the Cluster Manager wiki link above (specifically the “Corosync External Vote Support” section) and take a look at the forum thread I referenced above where I clarified some items from the wiki... I’ve...

Completely agree - As I’m sure it also says in the wiki. I use the qdevice only for homelab cluster - it does work well though...

Yes but PVE does not need to be installed on the 3rd “Node”, indeed the 3rd “Node” appears not as a Node in the Cluster Manager, but as a “qdevice”... Further to the Cluster Manager wiki page above, I also found the following thread useful when I setup my cluster...

You can do HA with 2 PVE nodes and a 3rd “Quorum Device” (qdevice) which provides votes to the 2 main PVE nodes. I have a 2 Node PVE cluster with a 3rd qdevice and it works well - For the qdevice, I simply run a VM (debian9) on my NAS, but the Raspberry Pi should work equally as well since my...

I’ve not used Zabbix myself... My setup is only a small home lab cluster and I use both the inbuilt “External Metric Server” (https://pve.proxmox.com/wiki/External_Metric_Server) to post stats (host, VM, LXC etc) to an InfluxDB database and graph/alert from Grafana but you can also install snmpd...

Thanks for this - I've raised a bug via the URL you provided and have also configured the nofailback for the time being as per your suggestion!

Thanks for the response - Given that the Migrate when stopped doesn't work with the hostpci error, is there anything I have to do to log this as a bug that can be fixed? In terms of the HA failover, I've just tested that and, if Node 1 (Preferred) goes down, it does successfully start the VM on...

Thanks for this - Are you saying that it should work (i.e. its a bug or a new feature that would consider fixing / implementing) to migrate the VM offline? I think it would be very useful and stop a lot of manual steps if I could simply click "Migrate" and then an "Offline option" which would...

Hi There, I've seen this raised a couple of years back (https://forum.proxmox.com/threads/migrate-vm-with-local-devices.17369/#post-88296) and I'm wondering what is the best / recommended method for migrating a VM (with Intel IGP passthrough enabled) from one node to another? Currently, my VM...

Have you tried re-enabling the c-state changes to see whether it still crashes?

I also haven’t had any similar crashes in the last couple of weeks. I haven’t changed anything c-state related in the BIOS but I did move all VMs off the suspect node a couple of days ago (so that it was idle to increase chances of a c-state crash) and still no crash... Possibly the kernel...