Page MenuHomeFreeBSD

Use ahci-hd device instead of virtio-blk device in vmrun.sh
AbandonedPublic

Authored by rodrigc on Sep 21 2014, 1:56 AM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 30 2023, 1:28 AM
Unknown Object (File)
Dec 14 2023, 1:50 PM
Unknown Object (File)
Sep 23 2023, 9:56 PM
Unknown Object (File)
Jul 14 2023, 5:25 AM
Unknown Object (File)
Apr 9 2023, 6:21 AM
Unknown Object (File)
Mar 23 2023, 4:05 PM
Unknown Object (File)
Jan 4 2023, 10:29 AM
Unknown Object (File)
Apr 23 2017, 6:41 AM
Subscribers
None

Details

Reviewers
grehan
neel
Summary

Use the ahci-hd device for disks. When bhyve boots, the disk devices
will be /dev/ada because they will be going through the SATA driver and CAM. This is how disks in other virtualization systems like
QEMU, VirtualBox, etc. appear.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

rodrigc retitled this revision from to Use ahci-hd device instead of virtio-blk device in vmrun.sh.
rodrigc updated this object.
rodrigc edited the test plan for this revision. (Show Details)
rodrigc added reviewers: neel, grehan.

I'll defer to Peter on this one.

I'd actually prefer that this remain as virtio-blk. Any decent virtualization system would prefer to use that over a h/w emulation (see Google Compute Engine, the VM configurations for Specvirt runs). Plus, having this for the disk device gets better coverage for bhyve at what I think is a negligible cost of not having the ATA-style disk name during installation.

If you have scripts that you would like to keep the same for all hypervisors, then perhaps a better way to solve this is an option to vmrun.sh that requests an AHCI emulation for the hard drive.

OK, will look at another approach.