Hi! Does anyone have any experience getting RHEL9 based distros (Rocky, specifically) to boot as a bhyve hvm on smartos? Would someone mind looking at this vmadm get and tell me if I'm doing something dumb? (vmadm get: pastebin.com/W7rx6SNc // booting with: vmadm boot 669bfb47-bdc5-6cd3-efa2-c26ac1ff9c96 order=cd,once=d cdrom=/Rocky-9.1-x86_64-minimal.iso,ide)

Over vnc, I get a uefi prompt where it looks like there's only one storage device but I'm really not sure next steps for uefi debugging. :(

Mapping table BLK0: Alias(s) PciRoot(0x0)/Pci(0x4,0x0) ... i'd think with the disk and iso there should be two things?

Oh okay, looks like Pci(0x4,0x0) is the virtio disk 0 and its just not picking up the CD.

Do I have to specify in the vmspec json that the machine has a cdrom drive, maybe?

Same behavior w/ Debian 11 netinstall ... so I think I'm just doing something dumb. :(

justinw: Start with this: github.com/TritonDataCenter/mi-centos-hvm

how many folks are running smartos under modern qemu/kvm/ovmf?

I just updated my (linux) hypervisor, and now a smartos guest is griping about the garbage smbios info it's getting from that qemu/ovmf combo

We've moved our jenkins agents to running in bhyve instead of kvm.

I've never run it under linux kvm.

the fields for the cpu information have some garbage in them, which makes its way through sysinfo to vminfod, which goes into maintenance

How garbage is it?

"CPU Type": "\x01",

Maybe I need to do something like this? TritonDataCenter/smartos-live 27dee23

OS-8428

So back story on that, illumos#13560 changed how smbios expresses non-printable characters.

And sysinfo just mostly tries to take a bare string and put quotes around it, which isn't always valid JSON encoded text.

yeah

So in OS-8248 I JSON.stringify()'d those strings.

Sorry, OS-8248 is not public.

8428, even

So maybe I need to do that in more places?

probably anywhere data is being emitted from smbios?

CPU_Version looks like the one straggler

But yours is hanging up on CPU_Type?

Oh, but that's just CPU_Version

Pardon, CPU_Version is the variable name used in the script

yeah

Yeah, ok.

vendor also

Ok, I'll get to that on Monday.

vendor isn't being emitted as part of the json, though

I don't think

Oh, ok, yeah that's just used to check if it's bhyve.

I don't see vendor referenced anywhere else.

If you're in a hurry, and you want to do a PR, I'll fast track it for you (not to dump work on you...)

But otherwise, we just had a release, so I can get you a build early next week.

Sorry about that. I had wondered about CPU_Vendor at the time. I should have just done it along with the rest of them.

If you want to try hotpatching it, I think this will fix it: gist.github.com/afb15c96135162e1f93d7e29613da268

that function doesn't output the bits directly

it just sets variables for later use

AFAICT

Yeah, but that's all we need.

will it not be also emitted by output_parsable()"

Once it's strigified, it'll be valid later.

?

oh, pardon, you're evaling that

yeah

Yeah.

OK, I have a branch here: TritonDataCenter/smartos-live 3d775ed

If you can verify that works, I'll get that merged in on Monday, and I can cut a build for you if you'd like.

seems to work

OK, cool.

the sysinfo caching means I don't even need the overlayed version

since the "real" sysinfo just uses the cached version, haha

*cached data

Oh, that's right. Yeah, we did that last time I tested it.

I personally don't need a special build

there's been enough drama lately

Also kind of makes testing it a pain in the ass, because when I was running it repeatedly I had to hack up sysinfo so that it *wouldn't* read or write the cache.

yeah

Ok, smartos-live#1068

Can you put a comment there that you tested it and it fixed the issue for you?

bahamat: thanks i'll check that out!

bahamat: added some commentary to the PR

Perfect, thanks!

thanks for looking at it on a saturday

Well, luckily it was one I had remembered from just a few weeks ago.

Having already worked it out then, the fix was simple.

You're just lucky you caught me when I happened to be at my computer.