mgerdts

This is has the OmniOS variables from Building Illumos at the end.

# -----------------------------------------------------------------------------
# Parameters you are likely to want to change
# -----------------------------------------------------------------------------

#       DEBUG build only (-D, -F)
#       do not bringover from the parent (-n)
#       runs 'make check' (-C)

mgerdts

This is for the initial round of review of link-local route support for LX ....

$ bldenv illumos.sh "cstyle /tmp/lxinit.c"
Build type   is  non-DEBUG
RELEASE      is
VERSION      is joyent_20190713T171701Z
RELEASE_DATE is July 2019

The top-level 'setup' target is available to build headers and tools.

mgerdts

Overview

This fixes

9318 vol_volsize_to_reservation does not account for raidz skip blocks

$ git whatchanged -v master..
commit 969a6b100f3e67c3a623d898c3825506f1a40b49
Author: Mike Gerdts <mike.gerdts@joyent.com>

mgerdts

In general, the instructions at https://illumos.org/docs/developers/build/ are pretty good but could use some help.

cups.h

ln -s ../../opt/ooce/include/cups /usr/include

Things that require java fail.

mgerdts

commit 2d1a8a4a97fe44c06e3fedddbb32f89fc2755a3e
Author: Hans Rosenfeld <hans.rosenfeld@joyent.com>
Date:   Tue Jan 15 16:29:40 2019 +0100

    OS-7508 mdb: assertion tripped in libvmm when bhyve VM halts while mdb is attached
    OS-7519 mdb: bhyve target can attach before the first vCPU is configured

commit 2a78db82bec123064d30d051995cb4d577ca04ba
Author: Hans Rosenfeld <hans.rosenfeld@joyent.com>
Date:   Wed Feb 13 16:08:32 2019 +0000

mgerdts

The panic is seen on Linux. Screenshots of the panic: 1 2 3

I built ZoL on xubuntu 18.04 with this commit at the tip.

I suspect the clones difference between @7 and @8 is due to the interrupted receive.

root@xubuntu:~# zfs get -o property,value all rpool/crypto/vol0@7  > /tmp/7
root@xubuntu:~# zfs get -o property,value all rpool/crypto/vol0@8  > /tmp/8
root@xubuntu:~# sdiff  /tmp/7 /tmp/8

mgerdts

Bhyve Machine Images

Each bhyve virtual machine (guest) uses a machine image. A machine image is sometimes called a guest image. Bhyve machine images are quite similar to KVM machine images. In fact, it is sometimes possible to create hybrid images that work with bhyve or KVM.

Bhyve is different from KVM in a few ways that are quite relevant to machine images. In particular:

• Bhyve supports UEFI and emulates legacy BIOS via a Compatibility Support Module (CSM). The CSM is not as full-featured as SeaBIOS used with KVM.
• Network configuration via a per-instance DHCP server is not supported.

The following sections describe the relevance of these differences and how to overcome them in many cases.

mgerdts

This shows how to upgrade cloud-init from the one found in the early CentOS 6 bhyve images and create a new image from that.

Create a source instance

First, we will install an instance using image 11891f44-a374-11e8-9c35-c7bfcc724881.

The vmadm payload

{

mgerdts

mget /Joyent_Dev/public/SmartDataCenter/release-20170316-20170315T223833Z/headnode/coal-release-20170316-20170315T223833Z-gc64b017-4gb.tgz | tar xvzf -

Follow first boot instructions at

https://github.com/joyent/triton/blob/master/docs/developer-guide/coal-setup.md

Then using sdc-docker/README.md as a guide,

Copy keys

mgerdts

Redirect Ubuntu Console to First Serial Port

The cloud images that Canonical provides has the grub and linux console on the VGA port. This doesn't work so well for bhyve, where the graphical console only works with uefi. This document describes how to fix that using SmartOS.

Select a source image

The source image needs to include cloud-init 18.3 or later. Any Ubuntu 16.04 or later image produced by Canonical starting in July, 2018 should fit this criteria. The image in this example is described as Ubuntu 18.04.1 LTS (20180808 64-bit). Certified Ubuntu Server Cloud Image from Canonical..

src_uuid=96768413-88a7-43d6-867b-d74284d616d6