So @Smithx10 -> you are aware of /zones/$UUID/logs/console.log --> right?

It's bunyan output, but you could tail -f /zones/170e57f0-4ffe-4fad-af11-c235d04ee16d/logs/console.log | bunyan

(Obvs. your UUID may vary, term and conditions apply....)

It's VERBOSE, but you can parse bunyan output with a little effort...

only gotcha is that logs don't get written until a newline.

so my `ubuntu login: ` prompt isn't there until I hit return or enter a username.

Make sense @Smithx10 ?

Yeah, the packer-plugin-bhyve is actually spawning the bhyve process so I'll just capture stdout / err from there and write it to a file

was hoping to get an easy win and just be able to have bhyve do it vs the packer plugin. thanks

Sorry.

are you not running bhyve in a zone then?

Hmmm... the man page is off (at least in SmartOS) compared with what it's doing.

jbk: github.com/TritonDataCenter/packer-…b/main/builder/bhyve/driver.go#L102 we have the builder zone

Yeah... and what you're working on is the sort of application it was built (no pun intended) for.

@Smithx10 we could always add some logging to the plugin too, might be useful to attach to the builds anyhow.. Can you describe what's your doing and why you need the output? I can see the need for it too.. just curious if we have different ideas.

Mostly to see if the VNC is hung and capture the logs from anaconda. TritonDataCenter/packer-plugin-bhyve #11

yeh if we need to add support for extra logging to the code then we should just do that

ah nice.. I missed that issue notice somehow.. that makes sense to me

I was working on it, Was exploring the options and seeing what works in the UX. I had it all in to stdout and it wasn't great, so I was gonna just dump it to a file