Search results

Again after some researches, i discover that first message has to be an auth message, like user@realm:ticket... Let's implement that and see i have more luck.

After some researching, i found that proxmox wraps the messages (https://git.proxmox.com/?p=pve-xtermjs.git;a=blob;f=README;h=1efdc521328a22bd5e36c1a45d3889f9f3d74e75;hb=refs/heads/master), maybe i should do the same thing in case of Xterm ?

Hi there ! I made a webapp that manage my proxmox cluster. I embed the noVNC console and it works great. But now, i wanted to add Xterm, i thought that would be easy, but i was wrong. After requesting a term ticket, i'm using the same websocket server (...

I think i found out : Timed out waiting for device dev-virtio\x2dports-org.qemu.guest_agent.0.device - /dev/virtio-ports/org.qemu.guest_agent.0. I forgot to check Qemu Guest Agent in Options tab :eek: My bad :) Thanks your reply helped me to solve the issue

Hey guys ! Small issue today : emu guest agent refuses to start on a VM deb 12 cloud init. Any reasons ?

Thanks for reply

Hi there I was wondering, is there a way to manage api permissions at cluster or node level ?

Hello I have 3x Windows 2019 Server VMs with the same problem : after windows update and reboot, the network is down. The culprit : Any idea ? The machines is default (i440fx) and latest version. Thanks !

Ok... I re-install the node with promos 7, same configuration (zfs) and he can now join the cluster. i do not dare to make an upgrade to pve8 :(

Hi there I was wondering... I have a 5 nodes pve 7 cluster. I installed a fresh pve 8 and try to add it. It is stuck with the message : 'waiting for quorum'. So what is the solution ? I prefer to mention that the pve8 is working with zfs, but not the others nodes. Maybe it is the problem ? Thx !

Hi there ! I have a small cluster (3 machines) and one node doesn't boot anymore because of a disk failure. I would like to remove the entry in the fstab, so i tried to boot on a usb stick in rescue mode, but i have an error « Invalid Argument » when i want to mount the main disk : mount -t ext4...

Ok thx, very useful. Problem solved.

Hello there ! This morning I ran into a serious issue. Boot failed with this message : I stopped the server yesterday, no updates or something, no hardware replacement... It worked perfectly. Any idea ? Thanks !

I waited one minute (VM has only 2G) After a second try, task was successful after 2 mins. It seems a big too long for a small VM (HD 32 G, RAM 2G), doesn't it ? See the screenshot.

Hi there I recently set up a new Proxmox environnement (7.0.13) on Dell Poweredge T340. Everything is ok except vm snapshot is not working (infinite task). If I does not include RAM, snapshot is ok. So hardware issue or Proxmox bug ? Thank you.

ok, so I just choose ignore...

Hi there, I just installed a new copy of Proxmox 7 on a single node. Main disk is a ssd hdd Samsung 1 To. With parted, I wanted to inspect the config and saw this error : Invalid partition table on /dev/mapper/pve-data_tdata -- wrong signature 0. Hardware problem or something else ? Nicolas

UPDATE. This afternoon i wanted to migrate a vm from node4 to node3, and got this error : Host key verification failed. command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=nsxxxxxx' root@192.168.0.3 pvecm mtunnel -migration_network xxx.xxx.x.x/24 -get_migration_ip' failed: exit...

yes i edited /etc/hosts, i removed public ip and added local ones : #135.125.x.x ______.ip-135-125-x.eu node1 192.168.0.1 nsxxxxxx.ipxx-xxx-xxx.eu node1 192.168.0.2 nsxxxxxx.ipxx-xxx-xxx.eu node2 192.168.0.3 nsxxxxxx.ipxx-xxx-xxx.eu node3 192.168.0.4...

Oh god, after updatecerts i have this error :