Search results

Hey Christoph, thanks for the continuous replies and sticking up with me. You are correct. I haven't done the args part. As soon as I saw it working with my workaround I didn't want to put extra args in the vm that in the future I'll forget about. I've done the full-upgrade as you recommended...

to circumvent this phenomenon I have a local systemd timer that is starting the vms after 10 min :D, I'm sure its not the way it is supposed to work but yeah

So the funny thing is at host boot I can't start the vms, as soon as I log into the webui or the thru the cli at the server I can start them manually. Task viewer: VM 101 - Start swtpm_setup: Not overwriting existing state file. kvm: warning: Spice: reds.c:2620:reds_init_socket...

Hi thanks for the feedback. My error was that for the storage I've misunderstood the docu. I assumed the size will be put in place after the $STORAGE:$SIZE which was not the case, I had to use $STORAGE:0 but yeah it works in the end

The problem still persists. Please check my other post: unable to create vm with qm as soon as I switched to i440fx for the machine type it is working, or I can use q35 with SeaBIOS, but not both q35 and uefi, the funny part is from the WebUI I can. is there a plan fix for the issue @fiona?

you have the disks from your earlier config, if you don't have the /etc/pve/qemu-server/$VMID.conf just recreate the vms to use the same disks as before, your data is there

so after reading on this thread [SOLVED] "Guest has not initialized the display (yet)" on new OVMF VMs after update to 7.0-13 I found out that the problem is not with my config but with ProxmoxVE 7.4. When I change the machine type to i440fx it is working. The strange thing is when I create the...

So I'm unable to create a vm with qm or pvesh. I can create them with the webui no problem. The commands I use are bellow plus their output. root@proxmox:~# pvesm alloc VM-OS-Drives 106 vm-106-disk-0 1M --format raw successfully created 'VM-OS-Drives:vm-106-disk-0' root@proxmox:~# pvesm alloc...

@cheiss is there a way I can add args from the webui or only cli ?

Unfortunately no, I've scrapped that idea and sold my cards and switch

Thanks for the amazing tutorial, it works, is there a way I can add a special name to the pendrive like OEMDRV or something like that. Also how to remove the drive from the VM? Just delete it?

kvm: warning: spice: reds.c:2620:reds_init_socket: getaddrinfo(127.0.0.1,61000): Address family for hostname not supported kvm: warning: spice: reds.c:3516:do_spice_init: Failed to open SPICE socket kvm: failed to initialize spice server start failed: qemu exited with code 1 I'm getting this...

I have changed sshd_config to ssh only using pubkeys. SSHing into root just feels wrong to me. However I didn't know that the useradd command wouldn't create a user home dir by default. What is the preferred (best practice) method then for managing PVE? Thru the web ui?

I want to have a local user other than root to manage the system both thru the cli and thru the web interface. So far I've created the lessfoobar user with pam, I've manually created the user on the nodes, I've given myself admin rights, setup password and totp, I can do everything thru the web...

I'm missing the Infiniband kernel module for my Qlogic IB card. lspci | grep -i infiniband 07:00.0 InfiniBand: QLogic Corp. IBA7322 QDR InfiniBand HCA (rev 02) Are there a prebuild modules to add it in the kernel in proxmox? Do I have to build the kmod myself? dmesg | grep qib [ 12.352184]...