[fedora-atomic] PR #114: add a few modules to initramfs to enable vmw/hyperv

[Dusty Mabe]

dustymabe opened a new pull-request against the project: `fedora-atomic` that you are
following:
``
add a few modules to initramfs to enable vmw/hyperv
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/114

[Dusty Mabe]

dustymabe commented on the pull-request: `add a few modules to initramfs to enable
vmw/hyperv` that you are following:
``
Please review, but don't merge as I'm still doing some testing. Thanks!
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/114

[Peter Robinson]

pbrobinson commented on the pull-request: `add a few modules to initramfs to enable
vmw/hyperv` that you are following:
``
Please do no merge this, it's likely not the right location to fix this, and will
possibly break multiarch.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/114

[Dusty Mabe]

dustymabe commented on the pull-request: `add a few modules to initramfs to enable
vmw/hyperv` that you are following:
``
>  Please do no merge this, it's likely not the right location to
> fix this, and will possibly break multiarch.
>  
k. is that because those modules don't exist for non x86_64 ? 
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/114

[Nicolas Chauvet]

kwizart commented on the pull-request: `add a few modules to initramfs to enable
vmw/hyperv` that you are following:
``
As pbrobinson said, this is not the right place to fix. The module should be added
automatically by dracut in no "host-only" mode.
/me reads anything related to atomic and kmod...
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/114

[Dusty Mabe]

dustymabe commented on the pull-request: `add a few modules to initramfs to enable
vmw/hyperv` that you are following:
``
>  As pbrobinson said, this is not the right place to fix. The module
> should be added automatically by dracut in no "host-only" mode.
>  /me reads anything related to atomic and kmod...
>  
@kwizart, yes. I'll cancel this pull request. but would like to follow an issue
somewhere where progress is being made on having this done in dracut itself?? Do you know
where I can do that? 
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/114

[Dusty Mabe]

dustymabe commented on the pull-request: `add a few modules to initramfs to enable
vmw/hyperv` that you are following:
``
where can we follow up on this? 
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/114

[Dusty Mabe]

dustymabe commented on the pull-request: `add a few modules to initramfs to enable
vmw/hyperv` that you are following:
``
@kwizart ?? 
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/114

[Dusty Mabe]

dustymabe canceled a pull-request against the project: `fedora-atomic` that you are
following.

Cancelled pull-request:

``
add a few modules to initramfs to enable vmw/hyperv
``

https://pagure.io/fedora-atomic/pull-request/114

[Nicolas Chauvet]

kwizart commented on the pull-request: `add a few modules to initramfs to enable
vmw/hyperv` that you are following:
``
Please verify to have the dracut-config-generic package installed in your install set.
Then it's just a matter to have the dracut initramfs generated normally.

Usually "regular" livemedia images have the  dracut-config-generic package
installed, then removed in %post after the initramfs is generated. So end-users will
default to a generic host agnostic image on first boot. But will have a lighter
host-specific initramfs on later kernel updates.

If vmware/hyperv kernel modules aren't present on generic initramfs, then it's a
matter to patch dracut upstream. 
You can start looking at:
https://github.com/dracutdevs/dracut/tree/master/modules.d/90kernel-modules




``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/114

[Nicolas Chauvet]

kwizart commented on the pull-request: `add a few modules to initramfs to enable
vmw/hyperv` that you are following:
``
That been said, you should be already have the --no-hostonly option from your json file
So it could also be an issue with theses kernel modules to have the appropriate alias or
use the function so that dracut can autodetect them as disk drivers...
Probably Fixing dracut is the way forward
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/114

[Dusty Mabe]

dustymabe commented on the pull-request: `add a few modules to initramfs to enable
vmw/hyperv` that you are following:
``

>  As pbrobinson said, this is not the right place to fix. The module
> should be added automatically by dracut in no "host-only" mode.
>  

you are right, at least on f29 i verified that both "vmw_pvscsi",
"hv_storvsc" are present when providing `--no-hostonly`. We're good here. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/114