#417 Add HyperV and VMWare pv storage modules to the default initrd for Atomic host
Opened 2 years ago by imcleod. Modified 2 years ago

In order for Atomic Host to work (or work well) on VMWare and HyperV, we need the PV storage drivers for these platforms in the initrd. These two modules are:

vmw_pvscsi
hv_storvsc

Together they are less than 20 kb of additional file content.

Can we add these to the default ostree configuration and, once this is done, enable the creation of HyperV and VMWare fusion vagrant boxes for Atomic Host?


At a whopping 20kb I don't have an issue with including these (assuming the licenses meet requirements).

Can we add these to the default ostree configuration and, once this is done, enable the creation of HyperV and VMWare fusion vagrant boxes for Atomic Host?

Do we truly need different vagrant boxes or could these modules be used from the main one?

Do we truly need different vagrant boxes or could these modules be used from the main one?

It's probably because these are a different disk format or something.

Metadata Update from @dustymabe:
- Issue tagged with: host, vagrant

2 years ago

Do we truly need different vagrant boxes or could these modules be used from the main one?

It's probably because these are a different disk format or something.

Yeah. The disk image and metadata formats are different. It's all supported in koji and, I believe, pungi. The non-atomic C7 images are available for virtualbox, kvm, hyperv and VMWare Fusion/Workstation, all of which have to be built as distinct output files (alongside, for example, the qcow2). I can certainly help sort out the details.

In any case, getting the modules in is the first step. After that, we can run some scratch Vagrant box builds.

At a whopping 20kb I don't have an issue with including these (assuming the licenses meet requirements).

Credit is due to VMWare and Microsoft for getting them both into the official upstream kernel. Licensing should not be an issue.

Login to comment on this ticket.

Metadata