Search results

I've solved this issue by myself. You have to take care about the nfs version while setting up the storage in Proxmox gui. If you take the default settings, Proxmox will do a nfs mount on version 4 while this is a nfs 3 server. Setting this explicit to version 3 will do the trick. Cheers Knuuut

Nobody? The only way to get rid of it is to cancel the block job, kill the VM and move the disk offline. Again, this is reproduceable. This looks like a bug in qemu...? Cheers Knuuut

Hi, while moving a disk on a running VM on pve 5.4, it got stuck reproduceable when moving from nfs to rbd. This is NOT the case when moving the disk vice versa. If I move the disk from a shutdown VM it works. create full clone of drive scsi2 (bkp-1901:111/vm-111-disk-1.raw) drive mirror is...

Nimm auf jeden Fall 3 striped mirrors im ZFS-Pool. Deine VMs danken es dir mit dreifacher io/s. Cheers Knuuut

Bei langen Antwortzeiten ist oft ein Problem bei DNS zu suchen und finden. Nur so mal als Hinweis. Cheers Knuuut

It has to be, because this nfs share is also mounted on another linux box, on which was no trouble at all. Anyway, after countless mount, umount, create, delete, restarts of nfs service with no(!) change of configurations, this problem disappered and I don't know why. But if it stays like now...

syslog Apr 03 12:30:37 pmve-1901 pvedaemon[2089411]: unable to activate storage 'nfs02' - directory '/mnt/pve/nfs02' does not exist or is unreachable Just setting up a nfs-storage via gui. No problems at all After the mountpoint vanished, i do a umount -f /mnt/pve/nfs02 on every node, then...

nfsstat -m /mnt/pve/nfs01 from x.x.x.101:/data/nfs01 Flags: rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=x.x.x.101,mountvers=3,mountport=20048,mountproto=udp,local_lock=none,addr=x.x.x.101 /mnt/pve/nfs02 from...

Hi, after adding a second nfs-storage to the cluster, this storage fails after exactly 30 minutes. Cause the mountpoint /mnt/pve/nfs2 vanished, but still listed in the output of mount. This is reproduceable. The first nfs storage isn't affected at all. The second nfs server got the same...

IO/s interacts with network latency. Think about a 40/100Gb/s network infrastructure and more OSDs/node. Cheers Knuuut

Already discussed here: https://forum.proxmox.com/threads/dependency-problam-breaks-upgrade-from-5-2-to-5-3.52622/#post-243591 Cheers Knuuut

Ich habe mir so beholfen, dass ich den HA-Status per script bereinige - nach dem Backup. Momentan läuft mein Cluster noch unter 5.1. Mal sehen ob nach dem Upgrade 5.1 -> 5.3 dieses Problem - wie behauptet - behoben sein wird. Cheers Knuuut

Yes, scripting works. Anyway, a downtime for all VMs... Thank you Knuuut

kvm64 works... :eek: All (>200) VMs have got the cpu type set to host. Does this mean, the only option I've got is to alter the CPU type on every machine and do a stop/start cycle?

Same CPUs, but different mainboard manufactors (Intel/Supermicro)...

of corse... bootdisk: scsi0 cores: 4 cpu: host hotplug: disk,network,usb ide2: none,media=cdrom memory: 16384 name: pmm-1801 net0: virtio=DE:AD:0A:1F:1E:0D,bridge=vmbr0 numa: 1 ostype: l26 scsi0: bkp-1901:256/vm-256-disk-0.raw,discard=on,size=40G scsi1...

Hello Community, after upgrading one node from 5.1.to 5.3 in a 5 node cluster, I can't do live migration of VMs. Now I'm stuck and in a bad situation, because I want to do a node by node upgrade of the cluster and I can't get the other nodes free... Here is the migration log of migration from...

Ja https://de.wikipedia.org/wiki/Non-Uniform_Memory_Access https://www.thegeekdiary.com/centos-rhel-how-to-find-if-numa-configuration-is-enabled-or-disabled/ Cheers Knuuut

Dann baue doch mal zum Spaß 1 CPU aus...

Ich lehne mich mal weit aus dem Fenster: Kann es sein, dass die Virtualisierungsfunktion(VT-X) im BIOS vom Host deaktiviert ist? Das kannst du schnell überprüfen mit cat /proc/cpuinfo sollte unter flags vmx aufführen. Wenn nicht dann im BIOS nachsehen. Cheers Knuuut