Recent content by sshaikh

Yes - hd-idle/standby seems to work fine in proxmox... as long as the VM the disk is being passthrough'd to is off. Once on it doesn't seem to standby at all, even if the VM guest isn't using it. I suspect QEMU keeps a hold on the disk or something.

Have you tried setting up manually? The script doesn't do that much and is pretty self explanatory.

That wasn't my own issue, and I'm a bit reluctant to share a patch file since I wouldn't recommend it myself. All the script does is add the bit to the corosync config and restart qdevice on each node. If I need to do this again I'll just do those two steps. Otherwise it's a bit obvious which...

I had to build my own version of qnetd for an platform that it hasn't been built by others for, and had to disable tls to get it to build. As such I don't want/need certificates to be used for this and suspect therefore a manual set up would be best. Do we have instructions available for such a...

I threw caution to the wind and used the following thread to rename the node: https://forum.proxmox.com/threads/proxmox-node-name-change.14327/ Very hacky and the cluster is no more but since it's temporary it'll work for in this case.

It doesn't I'm afraid: It's exactly the empty node requirement that makes this non trivial. Cluster vs standalone doesn't seem to be relevant. Looks like deleting and restoring the VMs is the best way forward. Do I have to backup the storage too or will that survive a rename?

Ok I suspect I'm being dim or unclear (or probably both). My current node is called "frodo". I want to build a new node with new hardware, migrate my VMs over and decommission the old node. There will be a period where both nodes will be running as machines are migrated. Eventually I want...

I naively assumed nodes in a cluster have to have unique names. Is this not the case? The complication here is a) wanting to keep (or reuse) the node name and b) have both old and new nodes up as I migrate the (offline) VMs.

I am trying to figure out a strategy to move my existing PVE installation to a new server. The new host will have new disks etc, so data will need to be migrated (as opposed to just physically moving the disk). I am also taking this opportunity to install Proxmox fresh. Quite significantly, I...

One of my Proxmox hosts randomly loses network for 5-6 seconds at what appears to be random points throughout the day. I am usually using VMs via RDP, and they either pause or disconnect. While investigating the issue I've noticed both pings to and from the host also stop, so it seems to be a...

I figured it was a long shot, but always worth documenting these data points. If I see the same hostwide performance again, what's the best way to quantify what's going on? I didn't see anything unusual using top on the host for example.

I usually run a couple of desktops on a Proxmox host running on a Haswell Xeon with 32GB ram. Hardware capabilities aside, the setup has been running well for me. The host is part of a two box cluster (which I use for the datacentre UI and not resilience). For the last three days or so my...

For anyone else who finds this, don't do what I did and replace everything vmbr0 with the above. You'll lose network access. Make sure you keep the bridge lines, so perhaps something like: auto vmbr0 iface vmbr0 inet dhcp bridge_ports eth0 bridge_stp off bridge_fd 0...

It's worth noting that any kind of GPU passthrough will disable the proxmox SPICE setup. I've gone the other way and set up "bespoke" remoting per VM. That's essentially RDP for Windows (although sometimes VNC for GPU/game streaming) and still tossing up between NoMachine and xRDP for Linux...

As we are now in the future, any sign of this functionality coming soon? ;) I notice that the usage can be found in lvs say, so although I appreciate the guest-agent is the right way to do it, perhaps in the short term for LVM disks it can be picked up directly?