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

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210410

John Baldwin  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|New |Closed

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

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

[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 if the virtio backing file has already been created.

  The '-f' check works fine on a regular file but not if the backing file is
  a device (e.g., /dev/md0). In this case it would print a misleading but
  otherwise benign message about the backing file not being present.

  PR:   210410

Changes:
_U  stable/10/
  stable/10/share/examples/bhyve/vmrun.sh

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

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

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210410

John Baldwin  changed:

   What|Removed |Added

 CC||j...@freebsd.org

--- Comment #1 from John Baldwin  ---
This was fixed in HEAD/11 by r273102.  It just needs to be merged to 10.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

RE: Bhyve tests and findings

[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 
>kernel module? It still remains that from 10.3

Definitely sounds like something not right with bhyve; It shouldn't exit like 
that.
You can try building vmm from 11, although I'm not really a kernel dev and 
can't help much with trying to merge 11 code into 10.

Matt

___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve tests and findings

[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: https://svnweb.freebsd.org/base?view=revision=297806

On Wed, 10 Aug 2016 20:36:34 +0700
Victor Sudakov  wrote:

> 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 4:0,ahci-hd,/d02/vm/win/disk0.img \
> > >-s 5:0,virtio-net,tap5,mac=58:9c:fc:03:77:3b -s 
> > > 6:0,fbuf,tcp=0.0.0.0:5900,wait \
> > >-l com1,stdio \
> > >   -s 3:0,ahci-cd,/d02/vm/.iso/bhyve_win7_x64.iso
> > 
> > > But bhyve just spits out the "usage" help (that's why it exits 
> > > immediately). But I cannot find out what's incorrect with the options.
> > 
> > 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 kernel module? It still remains that from 10.3
> 
> -- 
> Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> sip:suda...@sibptus.tomsk.ru
> ___
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"


-- 
Homepage:  www.yamagi.org
XMPP:  yam...@yamagi.org
GnuPG/GPG: 0xEFBCCBCB
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve tests and findings

[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 4:0,ahci-hd,/d02/vm/win/disk0.img \
> >-s 5:0,virtio-net,tap5,mac=58:9c:fc:03:77:3b -s 
> > 6:0,fbuf,tcp=0.0.0.0:5900,wait \
> >-l com1,stdio \
> >   -s 3:0,ahci-cd,/d02/vm/.iso/bhyve_win7_x64.iso
> 
> > But bhyve just spits out the "usage" help (that's why it exits 
> > immediately). But I cannot find out what's incorrect with the options.
> 
> 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 kernel module? It still remains that from 10.3

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

bhyve in KVM

[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 (2294.49-MHz K8-class CPU)
 Origin="GenuineIntel"  Id=0x306d4  Family=0x6  Model=0x3d  Stepping=4
 
Features=0xf83fbff
 
Features2=0xfffa3223

 AMD Features=0x2c100800
 AMD Features2=0x121
 Structured Extended 
Features=0x1c0f3a

 XSAVE Features=0x1
 VT-x: (disabled in BIOS) PAT,HLT,PAUSE,EPT,UG
Hypervisor: Origin = "KVMKVMKVM"

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?

Thanks,

Gábor Zahemszky
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: bhyve in KVM

[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 have to be relaxed (and some slight 
rework). See the thread starting at 
http://lists.freebsd.org/pipermail/freebsd-virtualization/2015-October/003870.html, 
and also PR 203994.


later,

Peter.

___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: Bhyve tests and findings

[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 with FreeBSD 11 for
UEFI-GOP testing. 

Matt and others, thanks for the effort.


-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

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

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211746

Dexuan Cui  changed:

   What|Removed |Added

 CC||delp...@freebsd.org,
   ||ema...@freebsd.org,
   ||freebsd-virtualization@Free
   ||BSD.org,
   ||gerard_seib...@outlook.com,
   ||honz...@microsoft.com,
   ||kyl...@microsoft.com,
   ||labmonke...@gmail.com,
   ||mar...@freebsd.org,
   ||m...@trettin.org,
   ||rze...@o2.pl,
   ||se...@freebsd.org,
   ||zhangx...@hotmail.com

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

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

[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 was merged into 10.3, stable/11 and 12.-CURRENT.

but unluckily today I found the I couldn't boot UEFI VM (i.e. Hyper-V
Generation-2 VM) with the 10.3 uefi iso  and 11-beta1  iso. :-(

The symptom is the same (it looks the kernel crashes at the very early point
where the uefi fb driver fails to load?). I'll report a new bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

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

[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 11-alpha/beta fail to load the kernel.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"