On Tue, Jul 15, 2025 at 09:35:02AM +0200, Hans Rosenfeld wrote: > On Tue, Jul 15, 2025 at 08:06:29AM +0200, Marcel Telka wrote: > > > Your error message may be raising because youve left the 'old' test > > > running, > > > be shure to destroy it with bhavectl. > > > > I've no bhyve process running. I'll post some more info shortly... > > The kernel VM state may still be around even if there is no bhyve > process around anymore to control it. You can destroy it with bhyvectl > and then try again: > > # bhyvectl --vm=XXX --destroy
Thank you for the clarification. This really helped. Such an information is desperately missing from the bhyve(8) man page. It turned out that without something like: -l bootrom,/usr/share/bhyve/firmware/BHYVE.fd the machine cannot boot (which is obvious). Thanks all for suggestions and help. -- +-------------------------------------------+ | Marcel Telka e-mail: mar...@telka.sk | | homepage: http://telka.sk/ | +-------------------------------------------+ ------------------------------------------ illumos: illumos-discuss Permalink: https://illumos.topicbox.com/groups/discuss/T0a2ef97770149180-M5d141c31ec9fb33ca87552f1 Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
