On Fri, 2014-06-27 at 14:23 -0700, Neel Natu wrote:
> Hi,
>
> On Thu, Jun 26, 2014 at 3:43 PM, Neel Natu wrote:
> > Hi Sean,
> >
> > On Thu, Jun 26, 2014 at 3:23 PM, Sean Bruno wrote:
> >> On Thu, 2014-06-26 at 15:00 -0700, Neel Natu wrote:
> >>> Hi Sean,
> >>>
> >>> On Thu, Jun 26, 2014 at 2:46
Hi,
On Thu, Jun 26, 2014 at 3:43 PM, Neel Natu wrote:
> Hi Sean,
>
> On Thu, Jun 26, 2014 at 3:23 PM, Sean Bruno wrote:
>> On Thu, 2014-06-26 at 15:00 -0700, Neel Natu wrote:
>>> Hi Sean,
>>>
>>> On Thu, Jun 26, 2014 at 2:46 PM, Sean Bruno wrote:
>>> > On Thu, 2014-06-26 at 14:42 -0700, Sean Br
Hi Sean,
On Thu, Jun 26, 2014 at 3:23 PM, Sean Bruno wrote:
> On Thu, 2014-06-26 at 15:00 -0700, Neel Natu wrote:
>> Hi Sean,
>>
>> On Thu, Jun 26, 2014 at 2:46 PM, Sean Bruno wrote:
>> > On Thu, 2014-06-26 at 14:42 -0700, Sean Bruno wrote:
>> >> so, we're seeing the bhyve vms running in the fre
On Thu, 2014-06-26 at 15:00 -0700, Neel Natu wrote:
> Hi Sean,
>
> On Thu, Jun 26, 2014 at 2:46 PM, Sean Bruno wrote:
> > On Thu, 2014-06-26 at 14:42 -0700, Sean Bruno wrote:
> >> so, we're seeing the bhyve vms running in the freebsd cluster for
> >> jenkins crashing and burning after a couple of
Hi Sean,
On Thu, Jun 26, 2014 at 2:46 PM, Sean Bruno wrote:
> On Thu, 2014-06-26 at 14:42 -0700, Sean Bruno wrote:
>> so, we're seeing the bhyve vms running in the freebsd cluster for
>> jenkins crashing and burning after a couple of days of use.
>>
>> vm exit[9]
>> reason VMX
>> rip
On Thu, 2014-06-26 at 14:42 -0700, Sean Bruno wrote:
> so, we're seeing the bhyve vms running in the freebsd cluster for
> jenkins crashing and burning after a couple of days of use.
>
> vm exit[9]
> reason VMX
> rip 0x29286336
> inst_length 3
> status 0
so, we're seeing the bhyve vms running in the freebsd cluster for
jenkins crashing and burning after a couple of days of use.
vm exit[9]
reason VMX
rip 0x29286336
inst_length 3
status 0
exit_reason 49
qualification 0x
inst_type
