Re: bhyve: corrupting zfs pools?

2015-06-03 Thread Andriy Gapon
On 04/06/2015 07:37, Neel Natu wrote: > Ok, there are some differences in our systems. The interesting ones > are number of ASIDs (64 versus 65536), flush-by-asid capability, > vmcb-clean capability and the number of cores. > > I was able to mimic all of these on my Opteron but still wasn't able >

Re: bhyve: corrupting zfs pools?

2015-06-03 Thread Neel Natu
Hi Andriy, On Wed, Jun 3, 2015 at 3:01 AM, Andriy Gapon wrote: > On 03/06/2015 00:40, Neel Natu wrote: >> Perhaps, but I wasn't able to repro this. I tried your recipe to repro >> on two systems running -current at r283917. >> >> - Intel Sandybridge server: Xeon E52650 with 8 cores/16 threads an

Re: Where are the VCPU threads created?

2015-06-03 Thread Stefan Andritoiu
On Wed, Jun 3, 2015 at 8:17 PM, Peter Grehan wrote: >> I see that in the main() function of bhyverun.c it adds CPU0 by >> calling fbsdrun_addcpu(ctx, 0, 0, rip). But I can't find where the >> other VCPUs are added. Or if the 'guest_ncpus' variable is ever used >> (except for error checks) > > > H

Re: bhyve: bhyveload, bhyve, bhyvectl --destroy

2015-06-03 Thread Craig Rodrigues
On Wed, Jun 3, 2015 at 9:18 AM, Andriy Gapon wrote: > On 03/06/2015 18:53, John-Mark Gurney wrote: > > JIMO, bhyveload(8) could be just merged into bhyve(8) and the latter should > behave like vmrun.sh does. bhyve(8) should retain an option to run a > preloaded > kernel, so that things like bhyv

Re: Where are the VCPU threads created?

2015-06-03 Thread Peter Grehan
Hi Stefan, I see that in the main() function of bhyverun.c it adds CPU0 by calling fbsdrun_addcpu(ctx, 0, 0, rip). But I can't find where the other VCPUs are added. Or if the 'guest_ncpus' variable is ever used (except for error checks) Have a look at bhyve/spinup_ap.c:spinup_ap() which is ca

Where are the VCPU threads created?

2015-06-03 Thread Stefan Andritoiu
I see that in the main() function of bhyverun.c it adds CPU0 by calling fbsdrun_addcpu(ctx, 0, 0, rip). But I can't find where the other VCPUs are added. Or if the 'guest_ncpus' variable is ever used (except for error checks) ___ freebsd-virtualization@fr

Re: bhyve: bhyveload, bhyve, bhyvectl --destroy

2015-06-03 Thread Andriy Gapon
On 03/06/2015 18:53, John-Mark Gurney wrote: > Andriy Gapon wrote this message on Wed, Jun 03, 2015 at 10:10 +0300: >> On 03/06/2015 02:04, John-Mark Gurney wrote: >>> Andriy Gapon wrote this message on Tue, Jun 02, 2015 at 21:15 +0300: I guess you are running bhyve through the shell script vm

Re: bhyve: bhyveload, bhyve, bhyvectl --destroy

2015-06-03 Thread John-Mark Gurney
Andriy Gapon wrote this message on Wed, Jun 03, 2015 at 10:10 +0300: > On 03/06/2015 02:04, John-Mark Gurney wrote: > > Andriy Gapon wrote this message on Tue, Jun 02, 2015 at 21:15 +0300: > >> I guess you are running bhyve through the shell script vmrun.sh? > >> I am doing everything by hand. > >

Re: bhyve and illumos

2015-06-03 Thread Peter Grehan
Hi Andriy, Has anyone tried to boot an illumos-based OS in bhyve? Any success stories? The Illumos kernel makes some BIOS calls so it can't be booted with grub-bhyve/multiboot - a triple-fault will result on the first BIOS call. It will need the UEFI/CSM firwmare work that's currently being

bhyve and illumos

2015-06-03 Thread Andriy Gapon
Has anyone tried to boot an illumos-based OS in bhyve? Any success stories? Thanks! -- Andriy Gapon ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "

Re: bhyve: corrupting zfs pools?

2015-06-03 Thread Andriy Gapon
On 03/06/2015 00:40, Neel Natu wrote: > Perhaps, but I wasn't able to repro this. I tried your recipe to repro > on two systems running -current at r283917. > > - Intel Sandybridge server: Xeon E52650 with 8 cores/16 threads and 64GB > memory > - hdd1/hdd2 on UFS > - hdd1/hdd2 on ZFS > > -

Re: bhyve: bhyveload, bhyve, bhyvectl --destroy

2015-06-03 Thread Andriy Gapon
On 03/06/2015 02:04, John-Mark Gurney wrote: > Andriy Gapon wrote this message on Tue, Jun 02, 2015 at 21:15 +0300: >> I guess you are running bhyve through the shell script vmrun.sh? >> I am doing everything by hand. > > Correct: > sh /usr/share/examples/bhyve/vmrun.sh -g 6444 -d mach10s.img -t t