Musings on virtualization and other stuff
So far, most of my use of bhyve has been with kvm images that have been customize to work better with bhyve. For Ubuntu images, those customizations have generally been:
If two hypervisors are not able to coordinate with each other, they must not
both use hardware viritualization. Within SmartOS, there is a pair of
hvm_excl_rele(), described by this
I had a very pleasant surprise today. I have some work that I need to contribute to illumos and figured that a little dogfooding would be good for me. It seems as though two excellent distros for building illumos are OpenIndiana and OmniOS. Since I don’t really need a desktop and I’ve not used OmniOS before, OmniOS seemed like a great choice for the day.
I was looking at ACPI tables in a bhyve guest and stumbled across this:
There have been a few changes in this blog:
While debugging a bug in SmartOS bhyve seen on Ubuntu guests, I needed to debug two areas that most people avoid:
grub is not so bad, as you can at least add print statements and they appear on the console.
uefi was not quite as cooperative at first.
I have a process that will be started later in a special context that I need to
truss(1M). An easy way to do this is with a little help from
It is often times handy to get a stack trace to help you understand how a program got to an error condition. Unfortunately, shell scripting languages tend to not provide an easy mechanism to get a stacktrace. The following examines how it can be accomplished with ksh93.