The following reply was made to PR kern/186375; it has been noted by GNATS.

From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= <>
To: Kensaku MASUDA <>
Cc: <>
Subject: Re: kern/186375: [xen] FreeBSD 10 is very unstable on Xen 4.1(XCP
Date: Mon, 28 Apr 2014 17:49:03 +0200

 On 28/04/14 14:37, Kensaku MASUDA wrote:
 > Hello, Roger.
 >     In the PR you mention that the VM crashes/panics, could you please
 >     provide the complete logs of the crash and the panics? Without those it
 >     is impossible to diagnose the problem, much less try to fix it.
 > Sorry, It was already deleted with VM. and disassembled Xen 4.1(XCP 1.6)
 > resource pool.
 > Now, my resource pool is upgraded about Xen 4.2(XenServer 6.2 SP1). But
 > I get same situation /w FreeBSD version 10-stable.
 > And successfull collect log.
 >     a FreeBSD VM running on Xen 4.4/4.5, and so far I haven't seen any of
 >     this issues.
 > FreeBSD 10 STABLE on Xen 4.2(XenServer 6.2) are stable than 10 RELEASE
 > on Xen 4.1, But it was randomly stall/panic/crash.
 I'm not sure I understand your last sentence correctly, sorry. Do you
 mean that 10-STABLE works fine on XenServer 6.2 and 10-RELEASE doesn't?
 The dump provided seems to be from 10-STABLE, so I guess both are affected?
 The crash itself doesn't happen on Xen code (it's in geom AFAICT), so
 it's kind of hard for me to figure out what's going on there.
 The following line in ps output seems quite worrying:
   0   999     1   0   20  0 50168 17979214322466816 g_waitfo Ds    -
 0:00.29 [bsnmpd]
 bsnmpd seems to be using a huge amount of memory, have you tried
 disabling it?
 Also, from vmstat -m:
 ip6ndp 18446744073708511156 18014398509416956K       -       41  32,64,128
 Can you provide a little more info about the VM itself, from the logs I
 see it has 4CPUs and 1024MB of RAM. Which kind of workload were you
 running inside of it when the crash happened?
 Could you try installing a vanilla 10-RELEASE VM using the ISOs on, and run the same workload (without xe-guest-utilities,
 bsnmpd or anything not strictly necessary).
_______________________________________________ mailing list
To unsubscribe, send any mail to ""

Reply via email to