Skip to content

bhyve: set diskif to nvme by default#154

Merged
citrus-it merged 2 commits into
omniosorg:masterfrom
hadfl:blkdef
Nov 24, 2025
Merged

bhyve: set diskif to nvme by default#154
citrus-it merged 2 commits into
omniosorg:masterfrom
hadfl:blkdef

Conversation

@hadfl

@hadfl hadfl commented Nov 21, 2025

Copy link
Copy Markdown
Member

No description provided.

@MarkProminic

Copy link
Copy Markdown

Before this is the default, could someone tell us what we may be doing wrong here with using NVME as the diskif?

https://illumos.topicbox.com/groups/omnios-discuss/Ta71a6eb8b82b9664/bhyve-problems-with-the-nvme-diskif-on-windows-on-r54

@citrus-it

Copy link
Copy Markdown
Member

Before this is the default, could someone tell us what we may be doing wrong here with using NVME as the diskif?

https://illumos.topicbox.com/groups/omnios-discuss/Ta71a6eb8b82b9664/bhyve-problems-with-the-nvme-diskif-on-windows-on-r54

In case it matters, this is changing the default that zadm uses when creating VMs. The zone default, i.e. what you get if you don't set the diskif property in the zone config, will remain virtio.

The instability you're seeing on Windows is very odd. It should be a standards-compliant emulation (it's actually been tested for this in FreeBSD where it originates). Is there any more information in the event log entry that preceded the reset? (I'll reply on the list).

@citrus-it citrus-it merged commit f40e859 into omniosorg:master Nov 24, 2025
3 checks passed
@hadfl hadfl deleted the blkdef branch November 26, 2025 06:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants