Re: Xen2/NetBSD 3.1 DomU running slowly

●To: Stephen Borrill <netbsd%precedence.co.uk@localhost> ●Subject: Re: Xen2/NetBSD 3.1 DomU running slowly ●From: Johan Ihren <johani%autonomica.se@localhost> ●Date: Thu, 31 May 2007 10:51:25 +0200

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Every now and then I get reports of a customer's DomU running slowly and, sure enough, when I connect it takes ages to login. However, it's running at 100% idle and the other DomU on the same box is fine. A reboot of the DomU fixes it. When it happened today, I saw the following on the Dom0 console (which is running quickly and responsively):


xen_shm_map: ENOMEM
xen_shm_map: ENOMEM1
xvif3.0: can't map packet page

The first two are debugging, I believe, but the third looks suspicious...

The kernels are 3.1_STABLE from 20th Nov 2006. Have there been pullups that fix this, i.e. should I be updating? I'm not in a position to upgrade to NetBSD 4.0/Xen3 at the moment.

I've seen the same console messages, repeatedly, in a Xen2/NetBSD 4.0beta2 environment (both DOM0 and DOMU) from Dec'06/Jan'07.

I've not noticed the extreme slowness of the DOMUs though, but have not looked for it either.


Johan


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGXoyNKJmr+nqSTbYRAs0pAJkBWjTPwevhHZukOJok8NheVIq7gwCdHzAg
/0UPsqGrYRzA/zjNjTvnG6E=
=eQU5
-----END PGP SIGNATURE-----

●References: ●Xen2/NetBSD 3.1 DomU running slowly ●From: Stephen Borrill

●Prev by Date: Xen2/NetBSD 3.1 DomU running slowly ●Next by Date: Re: xennetback_ifstart: no mcl_pages crashes XEN2-dom0 ●Previous by Thread: Xen2/NetBSD 3.1 DomU running slowly ●Next by Thread: Re: Xen2/NetBSD 3.1 DomU running slowly ●Indexes: ● reverse Date ● reverse Thread ● Old Index Home | Main Index | Thread Index | Old Index