VM doesn't start Proxmox 6 - timeout waiting on systemd

I have the same problem. One VM keeps freezing the entire system. It seems I can log in via noVNC, but when I shutdown, it stops before killing the process. Stopping the process on Proxmox does not work either.
This is only on my home server: My CPU is an Intel i7-7700T on a GIGABYTE GA-Z270N-WIFI Mainboard with 16 GB DDR4-2400 RAM and Samsung Pro 256 GB SSD. Did not happen on PVE 5.4 before the upgrade. I already had no-cache active, not writeback. Did not help.
I had exactly the same behaviour on different proxmox version. For me disabling the experimental zcopytx features solves the issue.
Create a file called vhost-net.conf in /etc/modprobe.d with the following content:
Code:
options vhost_net  experimental_zcopytx=0

I took the solution from the redhat bugtracker: I am not allowed to post the link...but it is Bug 1494974

Best Chris
 
  • Like
Reactions: Mrt12
I had exactly the same behaviour on different proxmox version. For me disabling the experimental zcopytx features solves the issue.
Create a file called vhost-net.conf in /etc/modprobe.d with the following content:
Code:
options vhost_net  experimental_zcopytx=0

I took the solution from the redhat bugtracker: I am not allowed to post the link...but it is Bug 1494974

Best Chris

Thanks. Just disabled zcopytx. Will report back.

EDIT:
For anyone else trying this, don’t forget to run the following command after adding the config file to /etc/modprobe.d

Code:
update-initramfs -u

EDIT 2: Fix works. Issue seem to be resolved.
 
Last edited:
  • Like
Reactions: Mrt12
I also had the same issue. Besides that, it was not possible to open the "Console" view in the browser.
It appears that using
Code:
options vhost_net  experimental_zcopytx=0
in
Code:
/etc/modprobe.d/vhost-net.conf
and
Code:
update-initramfs -u
fixed the problem.
 
I have check on my proxmox5 node,
vhost_net experimental_zcopytx was already at 1.

Not sure if it's a regression in kernel or ovs ....

but a recent patch is going to set it again to 0 by default
https://lkml.org/lkml/2019/6/17/202

Edit:
this patch has been applied in kernel 5.1
 
Last edited:
I have a updated to 6.0 proxmox from 5.4 (without any issues) and Debian 9 (updated before with normal reboot) to Debian 10
(same on my 2 serveur node - same time - same result)
Following the procedure at https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
When i reboot server the default kernel 5.0 stay frozen (picture) :
upload_2019-8-20_10-59-17.png

But if manualy take grub option for Kernel 4.15.18-20-pve (last before upgrade), the reboot go to the end and i can going on web interface and shell for using my serveur.

But if i reboot this serveur again without change grub option (auto boot), the server freeze again (kernel 5.0)

Can you say me that can i do ?
(Sorry for my poor English :) )
 
I also had the same issue. Besides that, it was not possible to open the "Console" view in the browser.
It appears that using
Code:
options vhost_net experimental_zcopytx=0
in
Code:
/etc/modprobe.d/vhost-net.conf
and
Code:
update-initramfs -u
fixed the problem.

I can confirm this, was also using Open vSwitch by the way and setting this kernel option, update initramfs, reboot, the server is running for four days already without any hang up! Works like charm, but why :rolleyes::)
 
Hmm, it appears that it worked just fine for a few days and the problem now appears again?!
Same error message, "timeout waiting on systemd".
 
I'm also still getting TASK ERROR: timeout waiting on systemd, I've made the above changes to /etc/modprobe.d/vhost-net.conf about 2 weeks ago
 
I have disabled zercopy in vhost-net by doing the following

Creating
/etc/modprobe.d/vhost-net.conf
with
then running
update-initramfs -u

I've still experienced the issue with the above fix applied.
 
I'm still not seeing that kernel version

cat sources.list


deb http://ftp.uk.debian.org/debian buster main contrib





deb http://ftp.uk.debian.org/debian buster-updates main contrib





# security updates


deb http://security.debian.org buster/updates main contrib


root@pve10:/etc/apt# dpkg -l|grep pve-kernel


ii pve-firmware 3.0-2 all Binary firmware code for the pve-kernel


ii pve-kernel-5.0 6.0-5 all Latest Proxmox VE Kernel Image


ii pve-kernel-5.0.15-1-pve 5.0.15-1 amd64 The Proxmox PVE Kernel Image


ii pve-kernel-helper 6.0-5 all Function for various kernel maintenance tasks.


root@pve10:/etc/apt#
 
you currently don't have a PVE-repository configured in your 'sources.list' - do you have any files in '/etc/apt/sources.list.d'? If yes paste them in code tags. Additionally please paste the output of `apt update` (also in code tags)

The correct configuration of all PVE repositories is explained quite well in https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_package_repositories

I hope this helps!
 
Code:
ls -lrt
total 1
-rw-r--r-- 1 root root 68 Sep  3 21:56 pve-enterprise.list

Code:
cat pve-enterprise.list
deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise

Code:
apt update
Hit:1 http://ftp.uk.debian.org/debian buster InRelease
Hit:2 http://ftp.uk.debian.org/debian buster-updates InRelease                                     
Hit:3 http://security.debian.org buster/updates InRelease                                                           
Err:4 https://enterprise.proxmox.com/debian/pve buster InRelease                                                     
  401  Unauthorized [IP: 212.224.123.70 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  401  Unauthorized [IP: 212.224.123.70 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve buster InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


There's is a sources.list in the /etc/apt directory and that contains

Code:
root@pve10:/etc/apt# cat sources.list
deb http://ftp.uk.debian.org/debian buster main contrib

deb http://ftp.uk.debian.org/debian buster-updates main contrib

# security updates
deb http://security.debian.org buster/updates main contrib
 
Can anyone confirm that this indeed works? We too are using ZFS for OS and VM storage, with BIOS boot.

It should, I do not recall any issues here, and this thread got quiet, what most of the time means "no news is good news".

We came to work this morning with a whole host down with about 10 production VMs offline :/

What kernel is running there?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!