Date: Sat, 19 Feb 2011 00:25:25 +0100 From: Ivan Voras <ivoras@freebsd.org> To: Hugo Silva <hugo@barafranca.com> Cc: freebsd-xen@freebsd.org Subject: Re: XenServer? Message-ID: <AANLkTim3BwmioJiLjCzFPHu_YGUb-2%2B33Mk7Dn-i9jBO@mail.gmail.com> In-Reply-To: <4D5E92F3.6050709@barafranca.com> References: <AANLkTiktYkyrJ9Kzo7E9EAMBC9n9JzAD5-spYAzUnQnX@mail.gmail.com> <4D5E7CF7.8020209@barafranca.com> <AANLkTin5tUG2EWB0CrD2cWqbH_8XVyjJeh2huijuj01k@mail.gmail.com> <4D5E92F3.6050709@barafranca.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18 February 2011 16:40, Hugo Silva <hugo@barafranca.com> wrote: > I haven't tested with high vcpu counts, but in this particular VM, it's b= een > running happily with 2 VCPUs and no noticeable problems. No panics, =C2= =A0 no > noticeable performance problems (after the tso fix) and certainly not the > famous 'time went backwards' problem. No such luck here; I've just tried an amd64 machine (8-STABLE from today) in a new installation of XenServer 5.6 and while the GENERIC kernel works stable enough, the XENHVM kernel produces all kinds of timer-related problems, accompanied by messages like: Feb 18 23:20:03 xbsd kernel: calcru: runtime went backwards from 28669021884109 usec to 22622950 usec for pid 11 (idle) The difference between 28669021884109 and 22622950 is huge! It almost looks like a memory corruption.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTim3BwmioJiLjCzFPHu_YGUb-2%2B33Mk7Dn-i9jBO>