Re: libvirt, bhyve, and Jenkins configuration problems

Craig Rodrigues wrote: > On Wed, Jun 25, 2014 at 11:08 AM, Roman Bogorodskiy > wrote: > > > > Does that mean that I need to configure my VM, so that it comes up with a > > > known IP, so that > > > it can be entered on this configuration page? > > > > Correct. > > > > Though, normally you don'

Re: jenkins bhyve vms crashing and burning after several days of use

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

Re: jenkins bhyve vms crashing and burning after several days of use

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

Re: jenkins bhyve vms crashing and burning after several days of use

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

Re: jenkins bhyve vms crashing and burning after several days of use

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

jenkins bhyve vms crashing and burning after several days of use

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

Re: py-libvirt problems with bhyve

On Wed, Jun 25, 2014 at 11:01 AM, Roman Bogorodskiy wrote: > Craig Rodrigues wrote: > > > > > conn = libvirt.openReadOnly(None) > ^^^ > > I think here the URI should be 'bhyve:///system'. > Or you could tweak libvirt.conf and assign the bhyve url value to the > '

Re: Request for Testers: libvirt and bhyve

Hi, I've updated the patch to use /var as localstatedir instead of /usr/local/var Without this patch, I can't connect to a Linux box with virt-manager because I need the ?socket=/var/run/libvirt/libvirt-sock parameter in libvirt uri Index: Makefile ===