Search results

Your 3rd node is P"X"E, not P"V"E, so they are correctly sorted alphabetically right now. You'd need to rename the node, but that might be a little of a hassle with SSH keys and stuff (off the top of my head).

32GB of memory might be a little light if you plan on running all those at the same time. I say might because my laptop right now only has 8GB (Win 11) but it always seems to be maxed on usage, but still runs fine. It is going to depend greatly on what you plan to do with the VMs. As Pifouney...

"2 node cluster" Is that screen capture looking at the "Data Center" list or on one of the nodes? Do you have a Pi or something as a qdevice for quorum? Are those with a ? on one node, and the others are on the other node? When you see the ? and they are always on the same node as the other ...

Bind mount from the host to the LXC, then share from there. You'd have a line in your conf something like: mp0: /tank/backups,mp=/mnt/backups,replicate=0 Then inside the LXC, you share /mnt/backups If I remember correctly, bind mounts are not recursive, so you can't just bind mount /tank, you...

Did you ever find out if you could do this @elkemper? I'm curious about giving this a try myself.

I don't know anything about the A100. Does it require different drivers than the A10? https://docs.nvidia.com/grid/16.0/grid-vgpu-release-notes-generic-linux-kvm/index.html Here they explicitly mention support for the A10.

Thanks for this. I just ran thru this without error. Note that 535.161.05.patch is available on PolloLoco's site ./NVIDIA-Linux-x86_64-535.161.05-vgpu-kvm.run --dkms -m=kernel --uninstall proxmox-boot-tool kernel unpin reboot, run uname -r to verify kernel 6.8 was loaded after the reboot...

Edit: Sorry, I didn't mean to post this in the Proxmox Backup Server forum. I don't see any way for me to move it or even delete it. This is probably more of a feature request, however, being new to HA, I didn't know there was a way to put a node in maintenance mode. It would be nice if there...

Unless I'm mistaken, HA via Replication requires local ZFS storage. https://pve.proxmox.com/wiki/Storage_Replication I would recommend, if this is something that the OP really wants, then they should keep an eye on the secondary market for few enterprise level SSD drives. That's what I did.

I think that block_cloning needs to be enabled with zpool upgrade on existing pools which is why you have different results.

I started a thread about this before I thought to check this one. However, Seems someone can repo it even with zfs_dmu_offset_next_sync=0. https://github.com/openzfs/zfs/issues/15526#issuecomment-1826065538 Seems this might be the fix...

I just stumbled over this and I was wondering how it relates to the versions of zfs here in the proxmox kernel? It seems like there is a bug that's been around that seemed a while that was brought to light with the latest block cloning code, or maybe they are 2 different bugs, I don't really...

So far, seems to have resolved my migration issue: https://forum.proxmox.com/threads/opt-in-linux-5-19-kernel-for-proxmox-ve-7-x-available.115090/post-499008

It looks like it has resolved my migration issues to/from an i7-12700K and i7-8700K machine.

5.15.53-1-pve doesn't work for me. Migrating a VM from an i7-12700K to an i7-8700K did the typical 100% cpu thing. Back to 5.15.39-3-pve-guest-fpu

Anyone try 5.15.53-1 yet?

I rolled back both nodes. Edit: Before rolling back, I could migrate from the 8700k to the 12700k w/o issue. So I migrated things off the 8700k and rolled it back. When I attempted to migrate from the 12700k to the 8700k so I could roll it back, they hung, so I don't think you can apply it to...

I'm just a freeloader running on consumer grade hardware (except for my SSD and nic cards) and I also have the same issue. One box has an I7-12700K in it, the other an I7-8700K and migrating a machine from the 12700K to the 8700K would cause it to lock up and I'd have to SSH into the node and...

This may or may not be related, but try installing iperf3 on your openmediavault vm, on the proxmox host, and on one of your client machines. Run iperf3 -s on your vm, then iperf3 -c vm.ip from the client and see if you are getting high retr. Run the iperf3 -s on your proxmox host and see if you...

I just happen to create my first debian 11 container last night and noticed the same thing as well. I normally used ubuntu 20.04 containers and never noticed these issues