[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xen 4.18/ARM64 on Raspberry Pi 4B: VLAN traffic crashing Dom0


  • To: xen-users@xxxxxxxxxxxxxxxxxxxx
  • From: Paul Leiber <paul@xxxxxxxxxxxxxxxx>
  • Date: Fri, 13 Oct 2023 20:01:11 +0200
  • Arc-authentication-results: i=1; strato.com; arc=none; dkim=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; t=1697220078; s=strato-dkim-0002; d=strato.com; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=CDi7FeJ4m1kqoYWzHBVsKXsrQTj0ydul0iaoScrT/Eo=; b=hun4wkUB/pWvNM7MuTLQ76xR/ztzD1Rm5pCQgF4OSdVtZt1Q7LFAHvHwCRMjLvlfbF kz2CxpCsvvp2+NMFV7CZV29DUzMLpl0HvtS3Vk3H0xFP7NV8PpFRYFwv+ShBX9lHBLaz cnYToKEs49ps6IehLUB+KcmH6Tu6A0UHJAhRtijwIjdWHj5AJnbPnflVao2QOBdML7Fr YMlMDUcuVqqyqAhNSiQ8mAK/TVrBx08B6eF//CWoBvbJYwRShAfQQfeBcKI8wqpLwXfm Lcj/5U5Lf2xS2g8OIhmBZF1KnMNb8RYoSIFYwzZ0UHnldd6ua7NUPRZUODwoKhq5h7ai 2iNg==
  • Arc-seal: i=1; a=rsa-sha256; t=1697220078; cv=none; d=strato.com; s=strato-dkim-0002; b=Z47WwADma+p/L4wB+U4QhWaHF6NBhxYtToEjrOD+zsl7EIYceaFNW58W8bK2O4VFDB FsVGiotVZBJGPQeKTiEl0Uua7g9ZJGZp6QdEkB7Kr9YGNCcq2UdfrX6gBSSRJ92lBmkp NIRXRBHk+uC87oE4LMEXWOGWs/QM5wv7yzLdQQ6JyGtXWvOkSN1Y7dyhxE+dQRuAuwVD zmqKXiT9wYa+mFgrTBqmtleYo8vWqR708nOWHx7Xs9qyMLIuGYzqiR7RATKcicpfhcgR rzv+0EKje/WD4S+ebHBbhBsE5egIj/dYzpL3m3zk3Ixv7e0KY8SWcMPA1hAcMsbK8Wlb qKUw==
  • Delivery-date: Fri, 13 Oct 2023 18:02:08 +0000
  • List-id: Xen user discussion <xen-users.lists.xenproject.org>

Am 11.10.2023 um 10:55 schrieb Paul Leiber:
On 16.09.2023 13:26, reijo.korhonen@xxxxxxxxx wrote:
On Thu, 2023-09-07 at 18:41 +0200, Paul Leiber wrote:
However, as soon as I remotely access the zabbix web interface, the

complete system (DomUs and Dom0) becomes unresponsive and reboots
after

a couple of seconds. This is reliably reproducable.



I didn't see any error message in any log (zabbix, DomU syslog, Dom0

syslog) except for the following lines immediately before the system

reboots on the Xen serial console:



(XEN) Watchdog timer fired for domain 0

(XEN) Hardware Dom0 shutdown: watchdog rebooting machine
Hmm.. Here you have a hint, how to study this issue. Seems, that this
is not Xe, issue, but it is watchdog issue. Your should set watchdog to
log, why it is rebooting machine.

You can also set or edit watchdog to do something else than rebooting
machine, because rebooting does not help your study.

I tried to dig deeper into the cause for the watchdog triggering. However, I didn't find any useful documentation on the web on how the watchdog works or how to enable logging. Can anybody direct me to useful information on the Xen watchdog, please?

Maybe it could also be helpful set your system to pure VLAN system
without Xen at all, but set system somehow to run same kind apps your
run with Xen and zabbix web interface. Maybe running Web server is
enough to study your VLAN1 and VLAN2. When your are sure, that VLAN1
and VLAN2 settings are OK and VLAN itself work with Raspberry OK, it is
much easier to continue with Xen and zabbix.

I booted the system without Xen and set it up to use the VLAN 20 bridge (the same that leads to a reboot when using it in the DomU) as primary network interface. Everything seems to be working, I could download large files from the internet without any problem. Next step is then to follow your advice reproduce the Zabbix setup (sigh).

Setting up Zabbix on the base debian system (which in Xen setup would be Dom0) showed that the same setup (VLANs 10 and 20, bridges 1 and 2, using bridge 2 as interface for Zabbix) without Xen is working reliably, no reboots. This points to some Xen component being the root cause.

I'm out of ideas, I'm taking this to xen-devel now.

Paul



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.