Search results

Can’t you spin up another machine (or a raspberry pi or something) on the same network or is it a single remote server you have access to? Personally, I just spun up a VM (on another server of course) to act as the netconsole logger...

@lhorace: Not sure what you mean by this? The wiki is out of date yes but are you saying there is more up to date info in the actual Proxmox server help files? Regardless, I’ve documented and got netconsole working now so will just wait and see whether I get another freeze/crash and what the...

I haven’t had a crash since enabling the netconsole so will have to wait until one occurs (if at all!) again. My server is Intel i5 based so not sure whether the c state bios fix proposed would be of any use for Intel?

In my home lab, I have 2 Intel NUCs (both only allow 1 * SSD and 1 * NVMe) and I’m currently booting them (UEFI) from the internal SSD. The 2 NUCs are setup in a cluster with an external qdevice for corosync quorum votes. I would like to use these internal SSDs as VM storage to maximise...

Hi There, Posting this more out of interest than an actual issue... I’m getting the following error in the Proxmox host syslog when starting a VM with IGP passthrough: Jun 8 16:08:51 pve-host1.local kernel: [309988.432878] vfio-pci 0000:00:02.0: Invalid PCI ROM header signature: expecting...

Not a production environment, but in my home lab I use NUT. Synology NAS is connected via USB to an APC BackUPS and acts as the UPS “server”. Proxmox nodes are connected power-wise to the same UPS and have NUT installed on them in netclient mode listening for power issue/commands from the...

Thanks for the detailed answer! I’ll take a look around for example scripts and give it a shot! Thanks again!

It’s my understanding that HA is not enabled by default just because you have a 2/3+ Node cluster? I had to enable HA for each desired VM in Datacentre -> HA and assign them to HA groups (to control the priority of the nodes and fallback behaviour etc)

Hi there, I currently have some VMs which are hosted on and run from a shared NFS share by the Proxmox hosts. I currently use Proxmox to backup (snapshot) these VMs back to the NFS share but this seems inefficient with the reads from NFS -> PVE host and writes back from PVE -> NFS host...

@Semmo - No further crashes as yet on my server but I've now eventually managed to get the netconsole method working to catch test Kernel Panic logs on a remote (target) server. I've written up what I did below so hopefully, if you can also get this logging, we have double the chance of...

I didn't try the pvecm "--use_ssh" command but, I've found the cause of the issue... The reason for the error is seemingly because 2FA was turned on for root on both NODE1 and NODE2. As soon as I disabled 2FA (on both nodes) and repasted the Join Information into NODE2, NODE2 was added to the...

Thanks for the reply! Here is /etc/pve/corosync.conf from NODE1 (where I created the cluster) logging { debug: off to_syslog: yes } nodelist { node { name: pve-host1 nodeid: 1 quorum_votes: 1 ring0_addr: 192.168.2.201 } } quorum { provider: corosync_votequorum }...

Can anyone help with the following error I'm getting after creating a cluster on a single node and attempting to add a second node to the cluster? I've created a cluster on the first PVE Node (call it NODE1) which has the following networks configured: DefaultLAN - 192.168.1.NODE1 ClusterHB...

It’s worth noting though that there appears to be multiple posts on the forums recently about PVE nodes hanging/freezing and only a reboot solves the issue so hoping someone can replicate the issue and grab the kernel crash logs for this.

I managed to get it working by rebooting both PVE nodes - When they came back up, it appears they were then successfully receiving a vote from the qdevice: root@pve-node1:~# pvecm status Quorum information ------------------ Date: Mon Jun 3 11:21:30 2019 Quorum provider...

Hi There, Can someone please clarify which corosync packages need to be installed and started on which PVE nodes / qdevice? The wiki (https://pve.proxmox.com/wiki/Cluster_Manager ) states that: First install the corosync-qnetd package on your external server and the corosync-qdevice package...

Hi there, I currently have 2 standalone PVE nodes (pointing to the same NFS storage) and am thinking of clustering them with a 3rd qdevice node for HA. Both standalone nodes are (different versions of) Intel NUC, both with Intel IGP GPU which appears to Proxmox as the same ID. Currenty I run...

@Semmo - Unfortunately not... I haven’t had a chance to try alternatives after the kdump method didn’t seem to work as expected (and detailed above)... did you manage to try to capture logs with the Netconsole method using a second PVE host to log the logs to? I havent tried that as yet but that...

Yes, I'm seeing the same thing trying to enable kdump-tools... I did the following on the host that is experiencing the freezing / crash issue and the service reports it "failed to load kdump kernel ... failed!" 1) apt-get install kdump-tools 2) Create current kernel symlink: cd / ln -s...

I see you set the machine type as Q35. I just use the default for my setup so perhaps you could take a look at changing that?