What happened to hw.vmm.topology.cores_per_package?

[Patrick M. Hausen]

Hi all,

I am using bhyve mainly in the context of FreeNAS.

Recently a major version upgrade and re-branding took place from FreeNAS 11.3 
to TrueNAS CORE 12.0.
This implies the underlying FreeBSD changing from RELENG_11_3 to RELENG_12.


FreeNAS/FreeBSD 11.3:

root@freenas01[~]# uname -r
11.3-RELEASE-p14
root@freenas01[~]# sysctl hw.vmm.topology
hw.vmm.topology.cpuid_leaf_b: 1
hw.vmm.topology.cores_per_package: 16
hw.vmm.topology.threads_per_core: 1
root@freenas01[~]#


TrueNAS CORE 12.0/FreeBSD 12.2:

root@freenas[~]# uname -r
12.2-RELEASE-p3
root@freenas[~]# sysctl hw.vmm.topology
hw.vmm.topology.cpuid_leaf_b: 1
root@freenas[~]#


What happened to those tunables?

Thanks,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP

Re: When is a switch not a switch?

[Patrick M. Hausen]

Hi!

> Am 22.10.2020 um 04:47 schrieb D'Arcy Cain :
> public: flags=8843 metric 0 mtu 1500
>ether 02:9d:b2:b8:78:00
>inet 98.158.139.65 netmask 0xffe0 broadcast 98.158.139.95
>id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
>maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
>root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
>member: eth0 flags=143
>ifmaxaddr 0 port 1 priority 128 path cost 55
>groups: bridge
>nd6 options=9
> tap0: [...]

tap0 is not a member of your bridge. With the VM running you can try

ifconfig public addm tap0

and check if that changes things.

Then go back to the drawing board and probably let vm-bhyve manage
all that stuff. Just make sure to configure your physical interface with
the hardware acceleration features disabled.

You *can* put the IP address on the physical interface and have
vm-bhyve create the bridge. I honestly don't know why the documentation
explicitly states that you should not. FreeNAS has been running like this
for years and only supports the "correct" configuration since 11.3 or so.

On the other hand coming from Cisco and friends putting the address on
the topmost layer 3 interface does make perfect sense to me - so e.g.
on a Cisco switch you have physical ports that are members of a VLAN
and if you run anything layer 3 on that box, of course the address goes
on the VLAN, not the port ...

But give vm-bhyve a spin with the address on the physical. Or use two
different physical interfaces - one for the host, one for the "public" bridge.

HTH,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP

Re: When is a switch not a switch?

[Patrick M. Hausen]

Hi!

> Am 20.10.2020 um 14:10 schrieb D'Arcy Cain :
> 
> On 10/20/20 7:39 AM, Patrick M. Hausen wrote:
>>> When I started I thought of a switch as analogous to a physical switch.  If 
>>> I am in an office with one ethernet jack but I have multiple devices I 
>>> might connect a switch (or hub) to the jack and plug my devices into the 
>>> switch. I don't need to create a separate network for my office.  All of my 
>>> devices are on the company network.
>> OK, the "switch" interface in FreeBSD is bridge(4).
> 
> Understood.
> 
>> Or to cite Radia Perlman:
>> A bridge is a network device making forwarding decisions based on layer 2 
>> addresses.
>> A router is a network device making forwarding decisions based on layer 3 
>> addresses.
>> "Switch" is a marketing term meaning "faster or cheaper than the 
>> competition".
> 
> I always thought that a switch was a hub with packet switching to avoid 
> collisions.

That is a bridge. A switch simply is a multiport bridge. And a layer 3 switch 
is a router.

> Or else rename the bridges to "public" and "private".

Yep, probably.

>> ifconfig_inet0="addm igb0 up"
> ifconfig_public="addm bge0 up"
> ifconfig_private="addm bge1 up"
> 
>> ifconfig_inet0_alias0="inet 1.2.3.4/24"
> ifconfig_public_alias0="inet 1.2.3.4/24"
> ifconfig_private_alias0="192.168.151.4/14"
> 
> So why alias?  Wouldn't "ifconfig_public=" work?

We already have

ifconfig_public="addm bge0 up"

Adding

ifconfig_public="inet 1.2.3.4/24"

on another line would overwrite the first one. These are just
variable assignments not executable code. You cannot have
more than one

ifconfig_public

line. If you need more than one they have to be named

ifconfig_public
ifconfig_public_alias0
ifconfig_public_alias1
...

Execution stops at the first undefined one, so no gaps, either.

> Not sure I need this as long as arp works as it should.  Do I really care 
> what the MAC is?

Well, the ARP timeouts specifically of Cisco gear can be enervatingly long so 
hosts
are not reachable after reboot for minutes ... these settings fix that.

HTH,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP

Re: When is a switch not a switch?

[Patrick M. Hausen]

A short P.S.

I just looked shortly into vm-bhyve. Whatever this tool does with respect to 
the "switches",
possibly just turning off all the hardware acceleration features for your 
network card can
solve your problems without further messing around with bridge(4) and friends.

What you need to configure depends on your hardware.
I made a table for the various interfaces we use at our place:

em: -rxcsum -txcsum -lro -vlanmtu -vlanhwcsum -vlanhwfilter 
-vlanhwtag up
igb:-rxcsum -rxcsum6 -txcsum -txcsum6 -tso -vlanhwtag -vlanhwtso up
ix: -rxcsum -rxcsum6 -txcsum -txcsum6 -tso -lro -vlanhwtag 
-vlanhwtso up
ixl:-rxcsum -rxcsum6 -txcsum -txcsum6 -tso -lro -vlanhwtag 
-vlanhwtso up
bnxt:   -rxcsum -rxcsum6 -txcsum -txcsum6 -tso -lro -vlanhwtag -vlanhwtso 
-vlanhwfilter up

HTH,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP

Re: When is a switch not a switch?

[Patrick M. Hausen]

Hi all,

> Am 20.10.2020 um 12:50 schrieb D'Arcy Cain :
> 
> On 10/20/20 5:36 AM, Patrick M. Hausen wrote:
>>> I did see that.  Does that mean that I don't even need to create switches 
>>> at all?
>> What is a switch in this context? I use bridge interfaces to connect jails 
>> via epair
>> and VMs via tap.
> 
> When I started I thought of a switch as analogous to a physical switch.  If I 
> am in an office with one ethernet jack but I have multiple devices I might 
> connect a switch (or hub) to the jack and plug my devices into the switch. I 
> don't need to create a separate network for my office.  All of my devices are 
> on the company network.

OK, the "switch" interface in FreeBSD is bridge(4).

Or to cite Radia Perlman:

A bridge is a network device making forwarding decisions based on layer 2 
addresses.
A router is a network device making forwarding decisions based on layer 3 
addresses.
"Switch" is a marketing term meaning "faster or cheaper than the competition".

> cloned_interfaces="bridge0"
> ifconfig_bridge0="a.b.c.d.1 addm bge0 addm switch0 up"

> Except that switch0 doesn't get created until vm-bhyve starts so it probably 
> doesn't exist at that time.

What is "switch0"? I suspect it is just a bridge interface that gets renamed by
your VM management software. In that case manually creating bridge0
and all the things we discussed will not get you anywhere.

>> If em0 does not have an IP address on the host and should be used
>> exclusively for VMs, then the bridge does not need an IP address, either.
>> Still you need to configure em0 "up".
> 
> I can't imagine a scenario like that.  You probably always need access to the 
> host for maintenance.

Well, there could be a second hardware interface for host communication ...
And if one of the two is member of the bridge and the other one isn't it is
perfectly valid to plug them into the same broadcast domain and get
e.g. 1Gbit/s for the host and 1Gbit/s for all the jails or VMs.

>> And additionally ...
>> - you should disable all hardware acceleration features on the physical 
>> interface
> 
> Like ASF?

Real life example from our environment:

ifconfig_igb0="-rxcsum -rxcsum6 -txcsum -txcsum6 -tso -vlanhwtag -vlanhwtso up"
cloned_interfaces="bridge0"
ifconfig_bridge0_name="inet0"
ifconfig_inet0="addm igb0 up"
ifconfig_inet0_alias0="inet 1.2.3.4/24"

Then we configure iocage to attach the jails to bridge0.

In your case you would have to tell your VM management tool to attach the
VM tap interfaces to bridge0 instead of creating its own "switch0" - which I
suspect is a bridge interface in disguise. As you can see above we rename
all our Internet facing interfaces to "inet0" on all hosts. Then there are more
like "mgmt0", "priv0", ... like that. So probably the bridge is renamed to 
"switch0".

Tell the tool not to do that and use the preconfigured bridge0 instead.

Another useful sysctl to get reproduceable static MAC addresses for the bridge
itself accross reboots is:

loader.conf: if_bridge_load="YES"
sysctl.conf: net.link.bridge.inherit_mac=1


HTH,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein


signature.asc
Description: Message signed with OpenPGP

Re: When is a switch not a switch?

[Patrick M. Hausen]

Hi all,

> Am 20.10.2020 um 11:28 schrieb D'Arcy Cain :
> 
> On 10/20/20 4:36 AM, Patrick M. Hausen wrote:
>> It's officially documented here:
>> https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bridging.html
> 
> I did see that.  Does that mean that I don't even need to create switches at 
> all?

What is a switch in this context? I use bridge interfaces to connect jails via 
epair
and VMs via tap.

>> "If the bridge host needs an IP address, set it on the bridge interface, not 
>> on the member interfaces."
> 
> But I don't necessarily need an IP on the bridge itself, right?

Depends ;-)

If the host has got e.g. em0 with an IP address and you want to make
that physical interface part of e.g. bridge0 as well as all the VMs so they
can communicate on the wire ...

you *must* move the IP address config from em0 to bridge0 and
configure em0 "up".

If em0 does not have an IP address on the host and should be used
exclusively for VMs, then the bridge does not need an IP address, either.
Still you need to configure em0 "up".

And additionally ...

- you should disable all hardware acceleration features on the physical 
interface
- if you are using pf you should move the rule processing from the members to 
the bridge like so:

sysctl net.link.bridge.pfil_member=0
sysctl net.link.bridge.pfil_bridge=1


HTH,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein


signature.asc
Description: Message signed with OpenPGP

Re: When is a switch not a switch?

[Patrick M. Hausen]

Hi all,

> Am 20.10.2020 um 08:56 schrieb John-Mark Gurney :
> I have heard (and that is the way I do that), that you have to put the
> host IPs on the bridge0 interface, and not the em0 interface.

It's officially documented here:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bridging.html

"If the bridge host needs an IP address, set it on the bridge interface, not on 
the member interfaces."


Kind regards,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein


signature.asc
Description: Message signed with OpenPGP

Re: FreeBSD a server and bhyve

[Patrick M. Hausen]

Hi Mario,

> Are you still using freeNAS or have you switched to TrueNAS?

They are one and the same product.

Version 11.3 is named FreeNAS
Version 12.0 is named TrueNAS Core

TrueNAS Core is currently in beta testing. I use it at home but have not
yet updated our company production systems.

I will as soon as there is an official release.

> Do you favor the switch or stick with FreeNAS?

As I said, there is no switch.

> Are they both ZFS only?

Yes, of course. They are the same thing.

> I haven't used either of them but I want to experiment with it.

If you are just starting, IMHO don’t shy away from the beta version.
I run it in power-user/semi-professional production: file sharing,
5 VMs, 6 jails, most with Internet facing applications, simply great.

The main advantage is that FreeNAS <=11.3 has always had issues when
FreeBSD versions reached their EOL due to the development model.

FN 11.3 is based on FreeBSD RELENG_11_3. As soon as that reaches end
of support, so will parts of FN 11.3. While iXsystems will still publish
patches, you will e.g. have a hard time to install packages inside of
FreeBSD 11.3 jails. FreeBSD 11.4 jails OTOH are not guaranteed to
run on the older kernel. Our experience has been that they do run OK
but things like „ps“ or „netstat“ might not work properly inside the
newer jail on the old kernel.

TN Core 12.0 despite the „12.0“ tracks FreeBSD RELENG_12. So it will
continue to get updates of FreeBSD unless the complete 12.x branch
will reach its EOL. So TN Core 12.0 is on FreeBSD 12.1, currently and
will be on 12.2, eventually. If you run web facing applications in jails you
get TLS 1.3 - yay! :-)

Confusing? Not so much if you are familiar with the FreeBSD development
and release model. I appreciate the move to RELENG_X instead of RELENG_X_Y.
Very much so.

HTH,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP

Re: FreeBSD a server and bhyve

[Patrick M. Hausen]

Hi!

> Am 12.08.2020 um 15:54 schrieb Odhiambo Washington :
> Do you mind sharing the tools you use (scripts) for creating/managing VMs?

I use FreeNAS aka TrueNAS Core as a hypervisor system. That may be a bit much.
Specifically it provides a rather large attack surface if hosted on the 
Internet.

Inside a private network it is one of my favourite FreeBSD based products.
File sharing, replication, jails, VMs … all in one nice box and UI.

> 1. https://www.davd.io/install-ubuntu-on-freebsd-with-bhyve/
> 2. https://www.daemon-security.com/blog/bhyve-simple-0713/

iohyve and chyves seem to be two possible choices:

https://github.com/pr1ntf/iohyve
http://chyves.org

Kind regards,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP

Re: FreeBSD a server and bhyve

[Patrick M. Hausen]

Hi all,

> Am 11.08.2020 um 22:15 schrieb Pete Wright :
> this should be pretty straight forward - the first step would be to setup the 
> additional public IP's as virtual addresses on your NIC similar to this:
> https://www.freebsd.org/doc/handbook/configtuning-virtual-hosts.html
> 
> then setting up your firewall (pf or ipfw) to forward requests coming in on 
> one of those public IP's to the specific bhyve VM which is listening on a 
> private IP.  this would be identical to hosting multiple services on a single 
> IP.
> 
> here's an example pf config that does the forwarding of SMTP on port 25 to a 
> VM using a private IP to give you an idea of what the syntax would look like:
> rdr pass on $ext_if inet proto tcp from any to 1.2.3.4 port = 25 -> 10.1.0.10 
> port 25

Why so complicated? Why not just bridge the bhyve VM to the physical NIC
and assign that additional IP address in the guest OS?

At least that is what I do all the time ;-)

Kind regards,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP

Re: Need X-server to run in bhyve guest

[Patrick M. Hausen]

Hi all,

> Am 03.12.2019 um 16:27 schrieb Rodney W. Grimes 
> :
> I am not sure you actuall need an EFI partition in that situation, but
> you may want one, and that is a missing feature of bsdinstall.

Are you possibly missing the point that Victor is talking about
FreeBSD *in* bhyve which mandates UEFI boot?

Or am I not aware that bhyve can do legacy boot, too?

Kind regards,
Patrick
-- 
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein

___
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: Need X-server to run in bhyve guest

[Patrick M. Hausen]

Hi all,

> Am 03.12.2019 um 09:45 schrieb Victor Sudakov :
> 
> Paul Webster wrote:
>>   Use dummy video driver and tightvnc, launch the vnc server as a normal
>>   user then connect with a VNC client from the outside, 
> 
> Connect to what?

Xvnc ;-)

At least that's what I figure he suggests. Start a virtual frame buffer server
like Xvnc and connect to that via VNC.

Patrick
-- 
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein

___
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: Virtualbox on Linux in bhyve?

[Patrick M. Hausen]

Hi,


> Am 04.07.2019 um 11:33 schrieb Patrick M. Hausen :
> is it possible to run Ubuntu 18.04 inside a bhyve VM
> and use Vagrant with Virtialbox?

I just found out - yes, you can. As long as you stickt to
32 bit Virtualbox guests.

You need nested virtualization for 64 bit guests.

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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"

Virtualbox on Linux in bhyve?

[Patrick M. Hausen]

Hi all,

is it possible to run Ubuntu 18.04 inside a bhyve VM
and use Vagrant with Virtialbox?

Currently we have this show stopper:

Stderr: VBoxManage: error: AMD-V is not
 available (VERR_SVM_NO_SVM)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component 
ConsoleWrap,
 interface IConsole

I’m not quite sure how AMD-V relates to VT-x. Any hints welcome.

Thanks,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: [vm-bhyve] shutting down VMs and kern.init_shutdown_timeout

[Patrick M. Hausen]

Hi all,

> Am 28.04.2019 um 06:41 schrieb Victor Sudakov :
> "if the /etc/rc.shutdown does not terminate within 120 seconds, init will
> terminate it.  The timeout can be configured via the sysctl variable
> kern.init_shutdown_timeout.“

What’s keeping you from increasing that timeout for your
particular requirements? IMHO 2 minutes are a reasonable
default for a system that does not run hypervisor VMs -
which is probably the vast majority.

Anyone with the knowledge to implement a virtualized
environment can simply set that to a more suitable value,
can’t he/she?

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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, sparse disk image and trim support?

[Patrick M. Hausen]

Hi!

> Am 21.04.2019 um 19:01 schrieb Bjoern A. Zeeb 
> :
> Do we support this?  Has anyone worked on this?  How do people deal with 
> these problems?

I’m actually surprised this is supported for some configurations - thanks
for starting the thread. As for how others deal with this - e.g. VMware files
never shrink, but there is a „vacuuming“ function that compresses the
virtual disk while the VM is offline in the workstation products. For ESXi
I think the only way is to actually copy the image file to a new one with
vmkfstools.

Used to use defrag and sdelete a lot in Windows VMs in the past, then
ran the compaction …

Kind regards
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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 and vfs.zfs.arc_max, and zfs tuning for a hypervisor

[Patrick M. Hausen]

Hi all,

> Am 21.03.2019 um 11:24 schrieb Matt Churchyard via freebsd-virtualization 
> :
> I'd also be intrigued to know what the logic in FreeNAS is for it. It is 
> simply a case of "(arc = total_ram - guest_allocated)"?
> Is there a lower limit based on a percentage or total RAM, and/or a hard 
> lower limit?

The relevant code can be found here:
https://github.com/freenas/freenas/blob/master/src/middlewared/middlewared/plugins/vm.py

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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 and vfs.zfs.arc_max, and zfs tuning for a hypervisor

[Patrick M. Hausen]

Hi Matt,

> Am 20.03.2019 um 10:34 schrieb Matt Churchyard :
>>> 2. If ARC does cache volumes, does this cache make sense on a 
>>> hypervisor, because guest OSes will probably have their own disk cache 
>>> anyway.
>> 
>> IMHO not much, because the guest OS is relying on the fact that when 
>> it writes it’s own cached data out to „disk“, it will be committed to 
>> stable storage.
> 
> Maybe I've missed something but I don't quite get the link between read cache 
> (ARC) and guest writes here?

You are correct - I confused ARC and ZIL. I still recommend to
set sync=always for hypervisor „disk“ ZVOLs.

Kind regards
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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 and vfs.zfs.arc_max, and zfs tuning for a hypervisor

[Patrick M. Hausen]

Hi!

> Am 20.03.2019 um 02:52 schrieb Victor Sudakov :
> Is SLOG also used by zfs volumes?

Yes, but for synchronous writes only, if I’m not mistaken.
So fundamentally yes, but in most cases no.

Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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 and vfs.zfs.arc_max, and zfs tuning for a hypervisor

[Patrick M. Hausen]

Hi!

> Am 19.03.2019 um 03:46 schrieb Victor Sudakov :
> 1. Does ARC actually cache zfs volumes (not files/datasets)?

Yes it does.

> 2. If ARC does cache volumes, does this cache make sense on a hypervisor,
> because guest OSes will probably have their own disk cache anyway.

IMHO not much, because the guest OS is relying on the fact that when
it writes it’s own cached data out to „disk“, it will be committed to
stable storage.

> 3. Would it make sense to limit vfs.zfs.arc_max to 1/8 or even less of
> total RAM, so that most RAM is available to guest machines?

Yes if you build your own solution on plain FreeBSD. No if you are running
FreeNAS which already tries to autotune the ARC size according to the
memory committed to VMs.

> 4. What other zfs tuning measures can you suggest for a bhyve
> hypervisor?

e.g.
zfs set sync=always zfs/vm

if zfs/vm is the dataset under which you create the ZVOLs for your emulated
disks.

I’m using this for all my VM „disks“ and have added a 16 GB SLOG device
to my spinning disk pool - seems to work great. This is on a home system.

Our new data centre systems feature all NVME SSDs and no spinning rust.
So no need for a separate SLOG.

HTH,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: Detecting that a guest kernel has booted

[Patrick M. Hausen]

Hi all,

> Am 11.03.2019 um 19:09 schrieb Rodney W. Grimes 
> :
> I have no love for them either, but until we get our UEFI updated
> it is a rather sad state of affairs.

I routinely boot FreeBSD, Ubuntu and Windows 10 with
UEFI, so I don’t see much that I would consider broken.

Missing persistence of boot variables (correct term?) is
the only thing that I know of - what else makes it a
sad state, currently?

Kind regards
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: Detecting that a guest kernel has booted

[Patrick M. Hausen]

Hi all,

> Am 11.03.2019 um 18:04 schrieb Mark Raynsford via freebsd-virtualization 
> :
> Leaving aside userland monitoring tools such as Prometheus[0], is there
> any way to detect on the host that a guest kernel running in bhyve has
> booted? I'm assuming "booted" in this sense to mean "PID 1 has probably
> started". I'm guessing that there probably isn't, but I thought I'd
> better ask anyway. "Not booted" would mean something like "Is sitting
> at the Grub prompt doing nothing“.

The abandoned FreeNAS Corral release did have guest additions
that served as a simple health monitor for FreeBSD and Linux
guests.

They used virtio_console(4) and the last state of the project can
be found here:
https://github.com/freenas/freenas-vm-tools

They compile cleanly on FreeBSD 12 and I even made a port that
I submitted to iX Systems, but we all know what happened to
Corral, unfortunately.

Possibly they can serve as a starting point for a new project.

And then there seems to be a newer version, again from FreeNAS,
written in Go:
https://github.com/freenas/bhyve-vm-goagent

HTH,
Patrick

--
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling



signature.asc
Description: Message signed with OpenPGP

Re: The status of docker

[Patrick M. Hausen]

Good morning,

> Am 28.01.2019 um 03:53 schrieb Paul Kraus :
> (Open)Solaris already had Linux Brand zones, which I’m sure helped get there 
> much faster.
> They could already run Linux (user space) in a Zone.


Yes, but how did they get there? Is there some technical reason
why Linux branded zones are „so far ahead“ of FreeBSD’s Linux
ABI that they can run native Docker images while FreeBSD can’t?

Or is it just a matter of money and manpower invested?

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: The status of docker

[Patrick M. Hausen]

Hi!

> Am 22.01.2019 um 21:09 schrieb Grzegorz Junka :
> BTW is Joyent is any way related to Oracle? Why would they want to support 
> zones? Is the support they implemented open sourced?

Sorry, I don’t know many details. Their cloud is built on Open Solaris,
hence the connection. IIRC the company was founded by some
bright people who left Sun after the acquisition by Oracle.

Bryan Cantrill is sort of a net.personality. Sean Chittenden presented
at EuroBSDCon 2018:
https://2018.eurobsdcon.org/talks-speakers/#SeanChittenden 


Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: The status of docker

[Patrick M. Hausen]

Hi all,

> Am 22.01.2019 um 20:48 schrieb Grzegorz Junka :
> 2. A docker container in a jail with no native linux kernel, docker is 
> running completely in FreeBSD environment
> 
> 2 would be most convenient but also most difficult as all smallest docker 
> features would need to be ported natively to FreeBSD


IIRC the Joyent approach was to port the Linux system call API to an
extent that made it possible to „simply“ run Linux Docker in zones without
a Linux kernel …

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: The status of docker

[Patrick M. Hausen]

Good morning,

> Am 22.01.2019 um 03:57 schrieb Craig Rodrigues :
> I hope I am wrong, but unfortunately I think getting Docker to work on
> natively on FreeBSD is ultimately a losing battle,
> unless you can get a team of several developers to work on it full time.

I have the same gut feeling, but unless somebody actually tries, we can’t
tell for sure, can we? ;-)

Thanks for making the effort.

Now what I wanted to throw in: possibly getting in touch with some of the
people at Joyent who implemented Docker support for Illumos/Solaris
zones might help:

https://www.joyent.com/blog/triton-docker-and-the-best-of-all-worlds 


Kind regards
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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 Guest Network Troubles

[Patrick M. Hausen]

Hi,

> Am 10.08.2018 um 11:29 schrieb David Powers via freebsd-virtualization 
> :
> I have a test vm running in Bhyve that is able to reach all interfaces on its 
> host via icmp.
> However, the guest is unable to reach the default route of the host, and thus 
> no Internet.
> I was hoping that someone might be able to help take a look at my config and 
> spot the potential issue(s), but not sure what information would be most 
> helpful.

What OS is the guest running?

Please provide

ifconfig -a
netstat -rn

of both host and guest.

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: Why can't I dtrace processes running in a jail from the host?

[Patrick M. Hausen]

Hi!

> Am 09.08.2018 um 16:52 schrieb Mark Johnston :
> For userland static probes to be globally visible, the process needs to
> register them with the kernel when it starts.  This is done
> automatically using a constructor which issues ioctls to
> /dev/dtrace/helper, hence the requirement for /dev/dtrace/* in the jail.

I figured as much. Enabling /dev/dtrace/* in the jail and restarting
the jail made the probes visible in the host system

I'm still somewhat stuck. What I'm trying to do is track down some
performance problems in a large complex PHP web application.
I have done this in the past on "regular" setups without jails
and with PHP 5.6 compiled with dtrace support using
/usr/local/share/dtrace-toolkit/Php/* ...

This setup is jailed with PHP 7.2, dtrace support seems to be the
default for the port.

I'm specifically after

php-fpm dtrace_execute_ex function-entry
php-fpm dtrace_execute_ex function-return

of course, to see where the application spends it's CPU cycles.

But regardless if I'm doing this on the host or in the jail, I only get
these results:

dtrace -m php\*
ZEND_CATCH_SPEC_CONST_CV_HANDLER:exception-caught
php_request_shutdown:request-shutdown
php_request_startup:request-startup
zend_error:error
zend_throw_exception_internal:exception-thrown

Nothing else. Still `dtrace -m php\* -l` does show all the probes.

Any ideas?

Thanks
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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"

Why can't I dtrace processes running in a jail from the host?

[Patrick M. Hausen]

Hi all,

I'm wondering why on a busy hosting server with hundreds of PHP-FPM
workers running in jails "dtrace -l" on the host does not show any
PHP specific probes. PHP *is* compiled with dtrace support for all the
jails.

Enabling /dev/dtrace/* via devfs.rules for a specific jail and then repeating
the process *inside* the jail works as expected.

Shouldn't jailed processes be transparently visible from the host system
but not vice versa?

Thanks,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: Centos7 uefi boot problem with bhyve after update

[Patrick M. Hausen]

Hi all,

> Am 04.05.2018 um 15:41 schrieb Peter Grehan :
> 
> Hi Mike,
> 
>> the fault here could be that of bootrom not reading the files it should
> 
> That is exactly the issue. The current UEFI code does not save non-volatile 
> variables to persistent storage. Guest o/s's are increasingly writing their 
> efi loaders to non-standard locations and using nv vars to direct UEFI to 
> boot from these locations.

I recommend installing rEFInd to the default location /EFI/BOOT/bootx64.efi.
It will call the Centos boot loader automatically if this is the only other one 
installed.

http://www.rodsbooks.com/refind/

HTH,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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 networking

[Patrick M. Hausen]

Hi!

> Am 26.04.2018 um 15:32 schrieb Paul Esson :
> I'd really like to try and use the switch approach if possible and had 
> thought that creating the switch and adding the igb1 interface would have 
> brought igb1 up automatically.  Is that the expected behaviour?

You have to "ifconfig igb1 up" manually for any of the bridging technologies in 
FreeBSD
as far as I know. Definitely with if_bridge. It is not sufficient to "ifconfig 
addm" the physical
interface.

But of course one just puts

ifconfig_igb1="up"

into rc.conf and forgets about it on a production system ...

HTH,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: Migrate from real server to virtual

[Patrick M. Hausen]

Hi all,

> Am 28.02.2018 um 15:31 schrieb Rodney W. Grimes 
> :
> Yes, I do believe that is the correct conclusion to your current situation.
> The other part that could be at issue here is if this is a 32bit or 64bit
> version of windows.  As Peter stated only 64 bit windows in UEFI mode.
> 
> It might be possible to create a shim drive that has the Windows UEFI boot
> code on it, and set that shim drive up to load the copy of windows from
> your image file.

rEFInd might be worth a try:
http://www.rodsbooks.com/refind/features.html

Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: Running dual boot windows inside of bhyve

[Patrick M. Hausen]

Hi all,

> Am 27.12.2017 um 18:15 schrieb Alan Somers 
> I fear that you may be out of luck.  Windows deliberately frustrates this
> use case by profiling its hardware at installation time and at every boot
> thereafter.  If the hardware changes too much, then Windows demands a new
> license fee.  Moving from physical hardware to a VM would probably trip
> every one of its alarms.

Correct. But we are talking Windows 7 here. It will lose it's activation for
sure, but as far as my experience goes you can always reactivate Windows 7
with the same keycode (unless it was a counterfeit one and is intentionally 
blocked).
As a last resort MS offers a phone dialog system that has always worked for me.

> For this reason, I would recommend using a
> separate instance for your VM.  However, if you do use a shared instance,
> then make sure that your PC is booting in UEFI mode.  BHyve can only  boot
> Windows in that mode.  If you do that, then BHyve will probably be able to
> boot it just fine.

This is actually the bigger of the two obstacles. If the original installation 
is
MBR booting, I don't know of a way to convert it to EFI.

If you happen to have some genuine not "OEM" Windows 7 install medium
*and* your original key, you should be able to do a fresh installation and
complete activation - via phone if necessary.

HTH,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: Storage overhead on zvols

[Patrick M. Hausen]

Hi all,

> Am 05.12.2017 um 16:41 schrieb Paul Vixie :
> in some bsd related meeting this year i asked allan jude for a bhyve level 
> null mount,
> so that we could access at / inside the guest some subtree of the host, and 
> avoid block
> devices and file systems altogether. right now i have to use nfs for that, 
> which is irritating.

I'm not an FS developer but from experience as an admin that
feature - nullfs mounts into a hypervisor - while greatly desired,
looks quite nontrivial to implement.

Jordan went to 9Pfs for the now discontinued FreeNAS Corral
at iX. If it was easy to do at the VFS layer, I doubt they would have
gone that way.

Kind regards,
Patrick
-- 
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling

___
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: Vagrantboxen stblassitude/freebsd-11 and stblassitude/freebsd-10 with workaround for sudo

[Patrick M. Hausen]

Hey, guys,

> Am 08.11.2017 um 23:18 schrieb Stefan Bethke :
> 
> I’ve just updated my Vagrant boxes with a workaround for sudo segfaulting 
> when no hostname is set (by setting a default hostname in the box).

So did we - I did not think this was honoring a mention ;)

https://app.vagrantup.com/punktde

Patrick
--
punkt.de GmbH   Internet - Dienstleistungen - Beratung
Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100
76133 Karlsruhe i...@punkt.de   http://punkt.de
AG Mannheim 108285  Gf: Juergen Egeling



signature.asc
Description: Message signed with OpenPGP

Re: Ubuntu guest in bhyve - startup.nsh

[Patrick M. Hausen]

Hi!

> Am 02.08.2017 um 15:15 schrieb Christian Stærk :
> After installing refind I had to move it to the default boot location in 
> order to have it boot automatically:

Yes, of course. That's the idea ;-)

> Now it works. Thank you.

You are most welcome.
Patrick


signature.asc
Description: Message signed with OpenPGP

Re: Ubuntu guest in bhyve - startup.nsh

[Patrick M. Hausen]

Hi!

> Am 02.08.2017 um 14:34 schrieb Christian Stærk :
> I was trying to work around bhyve not saving the EFI nvvars by creating a 
> startup.nsh file inside the EFI partition.
> None of my attempts seemed to make any kind of difference when trying to boot 
> so I am still stuck waiting a few minutes and then selecting grub manually.
> 
> Has anyone had any success crafting such a workaround?

Sorry - cannot help with your question proper. But to just get
the job done of booting various guests via EFI in bhyve I had
good success with rEFInd:

http://rodsbooks.com/refind/

HTH,
Patrick


signature.asc
Description: Message signed with OpenPGP

Re: UEFI and othere Unixes

[Patrick M. Hausen]

Hello

> Am 23.05.2017 um 03:45 schrieb The Doctor :
> 
> All right, I am using UEFI for all my virtualisation.
> 
> I was wondering using UEFI  how to install
> 
> netBSD
> OpenBSD
> Gentoo
> Mandrake
> Mandriva
> et al
> 
> I see an entry for ArchLinux

I had good results with rEFInd:
http://www.rodsbooks.com/refind/

whenever I needed to get some Linux to boot in FreeNAS/bhyve
via EFI. Never tried one of the other BSDs, though.

> Just wondering if we can start this and abandon non-UEFI practices.

That would be great, IMHO ;-)

Kind regards,
Patrick


signature.asc
Description: Message signed with OpenPGP

Re: What is the recommended version of virtio-win for bhyve

[Patrick M. Hausen]

Hi!

> Am 07.04.2017 um 13:15 schrieb Christian Stærk :
> Can anoyone here recommend a version, that works with bhyve and windows 10?

According ti the FreeBSD wiki 0.1.96 is the recommended version.
https://wiki.freebsd.org/bhyve/Windows

I'm running Windows 7 with 0.1.134 but can't speak for Windows 10 (yet).

HTH,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

___
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: virtio_console in bhyve? (FreeBSD host and guest)

[Patrick M. Hausen]

Hi, Jakub,

nice to meet you here.

> virtio_console(4) driver in 10.3 and in 11.0 doesn't support named ports 
> feature,
> which is used by bhyve in FreeNAS 10. I'll look into backporting FreeBSD 12 
> fixes
> to stable/10 and stable/11.

May I suggest (as a first step) to document that simple fact
("requires at least FreeBSD 12 for the guest") here:

https://github.com/freenas/freenas-vm-tools

:-))

Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

Wir schaffen Lösungen für Ihre digitale Herausforderung.
Am 23.02.2017 sind wir auf der IT & Media in Frankfurt vertreten.
Wir freuen uns auf Ihren Besuch am Stand B7

___
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: virtio_console in bhyve? (FreeBSD host and guest)

[Patrick M. Hausen]

Some more information:

> I'm trying to get guest-additions to work for FreeBSD guests in FreeNAS 10.
> FreeNAS 10 is built on top of RELENG_11 and uses the bhyve hypervisor.
> 
> Each VM is started with one virtio_console device like this:
> 
> bhyve [...] -s 
> '30,virtio-console,org.freenas.vm-tools=/var/run/containerd/dfdbb716-789f-44c3-9653-2157bdb3e76e.vmtools.sock'
> 
> Yet, inside the VM guest (I tried RELENG_10_3 and RELENG_11_0):
> 
> root@icescrum:~ # kldload virtio_console  
>
> vtcon0:  on virtio_pci1   
> 
> vtcon0: vtcon_ctrl_process_event: invalid port ID 779313518   
>   
> vtcon0: vtcon_ctrl_port_open_event: open port 0, but does not exist

When I deploy a Linux guest virtual machine on that FreeNAS system,
bhyve is invoked in exactly the same way:

bhyve [...] -s 
'30,virtio-console,org.freenas.vm-tools=/var/run/containerd/b5652839-4765-4384-8cd0-90964d4b1b4f.vmtools.sock'

(different UUID, of course).

Yet, in Linux the virtio_console is probed correctly, a device named
'/dev/virtio-ports/org.freenas.vm-tools' is created in the guest and the
guest and the host can communicate.

So the problems seems to lie not with FreeNAS but with the FreeBSD
implementation of virtio_console(4).

Anyone? Is this even the correct mailing list or should I address
freebsd-emulation or something entirely different like -stable?

Thanks,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

Wir schaffen Lösungen für Ihre digitale Herausforderung.
Am 23.02.2017 sind wir auf der IT & Media in Frankfurt vertreten.
Wir freuen uns auf Ihren Besuch am Stand B7

___
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"

virtio_console in bhyve? (FreeBSD host and guest)

[Patrick M. Hausen]

Hi, all,

I'm trying to get guest-additions to work for FreeBSD guests in FreeNAS 10.
FreeNAS 10 is built on top of RELENG_11 and uses the bhyve hypervisor.

Each VM is started with one virtio_console device like this:

bhyve [...] -s 
'30,virtio-console,org.freenas.vm-tools=/var/run/containerd/dfdbb716-789f-44c3-9653-2157bdb3e76e.vmtools.sock'

Yet, inside the VM guest (I tried RELENG_10_3 and RELENG_11_0):

root@icescrum:~ # kldload virtio_console
 
vtcon0:  on virtio_pci1 
  
vtcon0: vtcon_ctrl_process_event: invalid port ID 779313518 

vtcon0: vtcon_ctrl_port_open_event: open port 0, but does not exist

Unfortunately the byhve(8) manpage does not mention virtio_console
at all and I did not find anything detailled in the wiki or with Internet
search.

So I simply don't know if this is a bug in the way FreeNAS uses/starts
byhve or if there is a deeper problem with the implementation in FreeBSD.

Any hints greatly appreciated,
Patrick
-- 
punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe
Tel. 0721 9109 0 * Fax 0721 9109 100
i...@punkt.de   http://www.punkt.de
Gf: Jürgen Egeling  AG Mannheim 108285

Wir schaffen Lösungen für Ihre digitale Herausforderung.
Am 23.02.2017 sind wir auf der IT & Media in Frankfurt vertreten.
Wir freuen uns auf Ihren Besuch am Stand B7

___
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"