Howto close BHyVe console

2012-04-03 Thread Takuya ASADA
o idea to close bhyve console. Is there any shortcut-key or commands to shutdown it? I also tried vmmctl --vm= --destroy, but it suddenly causes panic. kill && vmmctl --vm= --destroy had worked, so I guess the panic reason is because /usr/sbin/bhyve still holding /

suspend/resume on BHyVe

2013-03-27 Thread Takuya ASADA
Hi, I had some discussion with Iori about the project since last year, and now I'm suggesting him to apply Google Summer of Code'13 with the project. (GSoC'13 will start next month) > For this, I think those below must be implemented. > > > > - virtual machine state command interface > > - s

Re: suspend/resume on BHyVe

2013-03-27 Thread Takuya ASADA
Hi, > A brute force way of figuring out all the state must be saved is to > look at all the initialization functions that are called when a vm and > a vcpu are created. So, this would be vm_create() and vcpu_init() in > the kernel module. I think these things are need to dump by resume action: -

Re: suspend/resume on BHyVe

2013-04-02 Thread Takuya ASADA
You can dump whole struct just a binary array(don't look into it in your program), and get sizeof(vmxctx) via ioctl return. It should enough to suspend/resume. Then if AMD SVM mode will have different values on the structure, your implementation won't break. Does it make sense? > Peter, Neel And,

Standalone binary loader for BHyVe

2013-08-04 Thread Takuya ASADA
Hi, I implemented standalone binary loader for BHyVe. This allows to load custom program on guest memory area, and run it from specified entry point address. I wrote this for test code of BHyVe suspend/resume project(Yoneji Iori's work), but it might be useful for some other purposes. This is a p

Linux on BHyVe in 10.0-RELEASE

2014-01-21 Thread Takuya ASADA
Hi, I want to know which Linux distribution is supported on BHyVe (+grub2-bhyve) in 10.0-RELEASE. I tried to these distributions, but I haven't succeeded to install any choice. On these tests, I used modified vmrun.sh script for all test, source code is here: https://gist.github.com/syuu1228/85524

Re: Linux on BHyVe in 10.0-RELEASE

2014-01-21 Thread Takuya ASADA
Hmm, looks like neel@ adding ignoring unimplemented MSR access patch on -CURRENT. Does it means we can't use (some version of) Linux on 10.0-RELEASE? https://github.com/freebsd/freebsd/commit/5dab6f9ed3816204ff73fd075abfaba1ed5c7673 2014/1/22 Takuya ASADA > Hi, > > I want to kn

Re: Linux on BHyVe in 10.0-RELEASE

2014-01-21 Thread Takuya ASADA
Oh, I didn't know bhyve-script.tar is still on bhyve.org (I didn't notice there's "Tools" tab on the page). I'll try it. 2014/1/22 Matt Donovan > Hello > > On Jan 21, 2014 8:38 PM, "Takuya ASADA" wrote: > > > > Hmm, looks

Re: Linux on BHyVe in 10.0-RELEASE

2014-01-21 Thread Takuya ASADA
Looks like CentOS 6.5 with bhyve-script fails on same place: Unknown WRMSR code 391, val 200f, cpu 0 Did you succeeded with 10.0-RELEASE? not -CURRENT? 2014/1/22 Matt Donovan > > I have gotten Centos 6.5 to boot however I used the bhyve scripts which > can be gotten at bhyve.org. haven't tr

Re: Linux on BHyVe in 10.0-RELEASE

2014-01-21 Thread Takuya ASADA
2014/1/22 Peter Grehan > On 1/21/14 9:20 PM, Takuya ASADA wrote: > >> Looks like CentOS 6.5 with bhyve-script fails on same place: >> Unknown WRMSR code 391, val 200f, cpu 0 >> >> Did you succeeded with 10.0-RELEASE? not -CURRENT? >> > > The MSR

Re: Linux on BHyVe in 10.0-RELEASE

2014-01-21 Thread Takuya ASADA
lun 0: SCSI3 0/direct fixed sd0: 10240MB, 512 bytes/sector, 20971520 sectors virtio0: couldn't map interrupt So, only Debian had worked on my environment for now. 2014/1/22 Takuya ASADA > Hi, > > I want to know which Linux distribution is supported on BHyVe > (+grub2-bhyve) in

Re: Linux on BHyVe in 10.0-RELEASE

2014-01-21 Thread Takuya ASADA
> > > * Ubuntu 13.10 with bhyve-scripts > Dies at same place: (initramfs) > Anyway I'll test with ahci-cd, which is point-outed by Peter. > > No this was wrong, bhyve-scripts already uses ahci-cd, I could install&boot Ubuntu 13.10 without problem. ___ fre

Re: Linux on BHyVe in 10.0-RELEASE

2014-01-21 Thread Takuya ASADA
2014/1/22 Takuya ASADA > Append results using bhyyve-scripts. > > * CentOS 6.5 with bhyve-scripts > Dies at same place: Unknown WRMSR code 391, val 200f, cpu 0 > > This issue was resolved by back-porting -CURRENT patch: svn co svn://svn.freebsd.org/base/head cd head

Re: Linux on BHyVe in 10.0-RELEASE

2014-01-21 Thread Takuya ASADA
Thanks, I'll test your image. 2014/1/22 Peter Grehan > Hi Takuya, > > > * Debian 7.3 with bhyve-scripts >> Able to install, bootup! >> But serial console sometimes outputs "AT+GCAP" or something, looks like AT >> command? >> Maybe I mis-configured Debian during installation? >> > > I think I

Re: CFT: vmrc Virtual Machine rc script

2014-02-27 Thread Takuya ASADA
Hi Michael, I tried openbsd6, ubuntu7, centos9 by remove comment out on install.sh, and did provision command like this: $ sudo /usr/local/etc/rc.d/vm provision openbsd6 Then I get an error: vm: provisioning VM openbsd6 /usr/local/vm//openbsd6/openbsd6.conf: 21: Syntax error: "(" unexpected Same

Re: CFT: vmrc Virtual Machine rc script

2014-02-27 Thread Takuya ASADA
2014-02-27 16:25 GMT+02:00 Matt Donovan : > The error is coming from the openbsd.conf line 21 > The error is due to a syntax errror in your openbs.conf. Can you post your > configuration as it appears you have an extra ). > It's true, but I even never changes it. Which means the configuration fil

Re: CFT: vmrc Virtual Machine rc script

2014-02-28 Thread Takuya ASADA
2014-02-28 10:00 GMT+02:00 Michael Dexter : > On 2/27/14 6:13 AM, Takuya ASADA wrote: > > Then I get an error: > > vm: provisioning VM openbsd6 > > /usr/local/vm//openbsd6/openbsd6.conf: 21: Syntax error: "(" unexpected > > Note that because the OpenBSD VM is

Re: bhyve VM crashed

2014-04-08 Thread Takuya ASADA
Did you execute bhyveload before bhyve? 2014-04-09 4:26 GMT+09:00 Steve Wills : > On Tue, Apr 08, 2014 at 11:43:27AM -0700, Peter Grehan wrote: > > Hi Steve, > > > > > I experienced a bhyve VM crash with this message: > > > > > > vm exit[1] > > > reason VMX > > > rip