[Bug 210410] /usr/share/examples/bhyve/vmrun.sh assumes virtio_diskdev must be a regular file

2016-08-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210410 John Baldwin changed: What|Removed |Added Resolution|--- |FIXED

[Bug 210410] /usr/share/examples/bhyve/vmrun.sh assumes virtio_diskdev must be a regular file

2016-08-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210410 --- Comment #2 from commit-h...@freebsd.org --- A commit references this bug: Author: jhb Date: Wed Aug 10 16:31:15 UTC 2016 New revision: 303925 URL: https://svnweb.freebsd.org/changeset/base/303925 Log: MFC 273102: Use '-e' to check

[Bug 210410] /usr/share/examples/bhyve/vmrun.sh assumes virtio_diskdev must be a regular file

2016-08-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210410 John Baldwin changed: What|Removed |Added CC||j...@freebsd.org

RE: Bhyve tests and findings

2016-08-10 Thread Matt Churchyard via freebsd-virtualization
> [..] > > You just need the vm name (win) on the end: > > # bhyve [options] vm-name > >Sorry, I was being stupid. With the vm name on the end, it just exits with >error code 1 and without printing anytning. >I have recompiled bhyve itself and the libvmmapi, maybe it's not enough? The

Re: Bhyve tests and findings

2016-08-10 Thread Yamagi Burmeister
Hi, to be able to use the GOP instructions on FreeBSD 10.3 you'll need to merge r296103 [0]. If it's an AMD system it's a good idea to merge r297806 [1], too. Otherwise most Linux distros will panic at startup. Regards, Yamagi 0: https://svnweb.freebsd.org/base?view=revision=296103 1:

Re: Bhyve tests and findings

2016-08-10 Thread Victor Sudakov
Matt Churchyard wrote: > > >I have tried replicating manually all the options vm is passing to bhyve, > >like > > >bhyve -c 1 -m 1G -Hwl bootrom,/d02/vm/.config/BHYVE_UEFI.fd \ > >-U 093f9134-5e18-11e6-9502-5404a6b49a66 \ > >>-s 0,hostbridge -s 31,lpc -s

bhyve in KVM

2016-08-10 Thread gabor
Hi! I tried the 11-beta4 in a KVM (qemu) virtual machine. In Linux, the nested KVM functionality is enabled. I started the VM with: qemu-system-x86_64 -enable-kvm -cpu host,+vmx -m 512 FBSD.qcow2 And here is processor info in the FreeBSD VM: CPU: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz

Re: bhyve in KVM

2016-08-10 Thread Peter Grehan
Hi Gábor, First of all, what is this Disabled in BIOS? Second, what needs to use bhyve, az kldloading vmm I got: vmx_init: processor does not support desired basic capabilities module_register_init: MOD_LOAD (vmm, 0x8221c4e0, 0) error 22 What's missing? There are some checks that

Re: Bhyve tests and findings

2016-08-10 Thread Victor Sudakov
Yamagi Burmeister wrote: > Hi, > to be able to use the GOP instructions on FreeBSD 10.3 you'll need to > merge r296103 [0]. If it's an AMD system it's a good idea to merge > r297806 [1], too. Otherwise most Linux distros will panic at startup. I'd rather abandon the idea and get a separate box

[Bug 211746] [Hyper-V] UEFI VM can't boot from the iso installation disk

2016-08-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211746 Dexuan Cui changed: What|Removed |Added CC|

[Bug 195819] TSC calibration can hang FreeBSD in Hyper-V Generation 2 VM

2016-08-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195819 --- Comment #24 from Dexuan Cui --- (In reply to Dexuan Cui from comment #22) The TSC calibration issue was fixed in Apr: https://github.com/freebsd/freebsd/commit/cff47489671a6ec6470f706f530df99c158511b0 and the fix

[Bug 195819] TSC calibration can hang FreeBSD in Hyper-V Generation 2 VM

2016-08-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195819 --- Comment #25 from Dexuan Cui --- (In reply to Dexuan Cui from comment #24) I reported a new bug: Bug 211746 - [Hyper-V] UEFI VM can't boot from the iso installation disk It looks the uefi loaders in 10.3 and