--On 17 February 2014 16:56:14 +0100 Roger Pau Monné
wrote:
In order to provide more debug info, could you apply the following patch:
http://xenbits.xen.org/people/royger/0001-xen-debug-Xen-PV-timer.patch
It will expand the panic message a little bit. Also, after applying the
patch you can
--On 17 February 2014 16:56 +0100 Roger Pau Monné
wrote:
How many guests are you running on this host, and how many vCPUs has
each one assigned?
Only 1 active guest (the FreeBSD one) - there are others on there, but
they're not running (so I'm hoping they don't count? :)
I don't think
On 14/02/14 18:51, John Baldwin wrote:
> On Thursday, February 13, 2014 8:49:24 pm Andrew Cooper wrote:
>> On 08/02/2014 21:42, John Baldwin wrote:
>>> On Tuesday, December 24, 2013 12:20:58 PM Roger Pau Monne wrote:
Lower the quality of the MADT ACPI enumerator, so on Xen Dom0 we can
for
On 17/02/14 15:44, Karl Pielorz wrote:
>
> Hi,
>
> I've got a FreeBSD 10-R amd64 DomU guest I'm using under XenServer 6.2
> (SP1) - this was working fine (i.e. had been restarted many times -
> while I look at things like HAST).
>
> I noticed the other day it was only set to use 4 vCPU's - so I
Hi,
I've got a FreeBSD 10-R amd64 DomU guest I'm using under XenServer 6.2
(SP1) - this was working fine (i.e. had been restarted many times - while I
look at things like HAST).
I noticed the other day it was only set to use 4 vCPU's - so I increased
this to 8 (the machine has an 4 Core, 8
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
--On 11 February 2014 18:20 +0100 Roger Pau Monné
wrote:
You could try to disable the following:
ifconfig xnX -rxcsum -txcsum -tso4 -lro
As a follow-up to this, using:
ifconfig xnX -rxcsum -txcsum
Does actually fix the problem. I finally got a block of time to go through
all this stuf
