Search results

Yes, it is. It is pretty stable right now with the older kernel. Will boot the hv with new kernel if netcup updates his host kernel.

So after a long while... I finally made the VMs boot. What did I do? I've booted the pve server with an older kernel - that fixed the issue for now. Hopefully I'll remember this workaround ;D I've checked every logfile for errors with the newest kernel and there was NOTHING... but thanks for the...

Nabend, hier dasselbe Problem. Update von 6.4 auf 7.1 verlief in katastrophalem Zustand. Alle möglichen SCSI Änderungen, HW-Anpassungen in der PVE Config für die VMs etc. haben keine Besserung gebracht. Mit dem älteren Kernel bootet wieder alles normal.

I cannot start a simple rescue disc in a new vm either. EDIT: it is possible, but only if I boot in UEFI mode. My VMs running in SeaBIOS, so this would not be an option. EDIT2: UEFI is not working in every scenario - only a fresh configured vm without anything will boot a rescue disc, nothing...

I'm running my system on a 6-Core nested AMD Epyc. Is it possible that AMD is a problem?

My VMs are freezing. I don't get it. No errors shown. I experimented a bit with hardware settings for vm's but no luck at all. Is there a logfile / log folder for vm's?

So after a bit of time I wasn't able to get network working... I'm very clueless right now. I will screenshot the bootlog and attach it. EDIT: the workaround with hardcoded MAC works very well. At least I can continue my research right now and I'm able to ssh into it again :D journal attached.

Ok... now it is not possible anymore to get on it via ssh... Right now I have to deal with that. networking.service is marked as active (exited). And a reboot is resulting in timeout from watchdog and rebooting.

From what I see right now is, that the SCSI controller is corrupted on all machines. The "Start" task finishes fine. No errors to see in GUI. The problem is, that my VMs won't boot up. They freeze during startup. If I set up another controller, they will be "stable" but won't boot into system...

root@proxmox:~# pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve) pve-manager: 6.3-2 (running version: 6.3-2/22f57405) pve-kernel-5.13: 7.1-4 pve-kernel-helper: 7.1-4 pve-kernel-5.4: 6.3-1 pve-kernel-5.13.19-1-pve: 5.13.19-2 pve-kernel-5.4.73-1-pve: 5.4.73-1 ceph-fuse...

Hi, got the same problem. But I don't know where to put aio=threads? Via GUI not possible? nvm... but my VMs won't start :(

Little update from my system - after an upgrade from netcup - i do not know what they did - suddenly my system seems to be stable. And after a while, netcup did a kvm upgrade and all out of a sudden nothing happened anymore. System is stable for about 20 days without any issues or problems...

Nope, no physical machine. Netcup will not tell me any configuration regarding the host system. I think that it must be a debian host, using qemu for virtualization - but configwise there is no information I can get from them... A little update: since I ran just three machines with debian at the...

A little feedback from here... I upgraded proxmox to pve-manager/6.3-3/eee5f901 (running kernel: 5.4.73-1-pve). I still got freezes, my rServer hangs unreproducably after indefinable days of runtime. There is no reproducable error to find in the logs. I try to run proxmox without any windows...

Hi there, I've got the same problem on 6.3-2 just tonight. Web GUI ist reachable, two VMs are not (out of 6). Just the error TASK ERROR: timeout waiting on systemd is coming up. I cannot guess how this is coming up, because there is no info there nor a log. Right now I added the...