Windows Server 2019: Driver Signature Enforcement
Hello, I’m running oVirt 4.3.0 and installing Windows Server 2019 with UEFI Secure Boot is impossible with the bundled VirtIO drivers. Windows complains about invalid signatures on vioscsi.sys. The only way to boot the system is halting the process with F8 and them selecting: Disable Driver Signature Enforcement. So, what’s the recommended way to solve this? There’s no signed drivers? Thanks,
I'm running server 2012R2, 2016, and 2019 with no issue using the Redhat signed drivers from RHEV.
RHV drivers works. oVirt drivers does not. Checked this now. I’m not sure if this is intended or not. But oVirt drivers aren’t signed for Windows.
On 29 May 2019, at 21:41, michael@wanderingmad.com wrote:
I'm running server 2012R2, 2016, and 2019 with no issue using the Redhat signed drivers from RHEV. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GBQEMLOW5DCSW7...
On Mon, Jun 10, 2019 at 10:54 PM Vinícius Ferrão <ferrao@versatushpc.com.br> wrote:
RHV drivers works. oVirt drivers does not.
Checked this now.
I’m not sure if this is intended or not. But oVirt drivers aren’t signed for Windows.
oVirt's drivers are simply copied from virtio-win repositories. Adding Vadim from virtio-win team. Best regards,
On 29 May 2019, at 21:41, michael@wanderingmad.com wrote:
I'm running server 2012R2, 2016, and 2019 with no issue using the Redhat signed drivers from RHEV. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GBQEMLOW5DCSW7...
Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PNZWHYEWW23N4G...
-- Didi
Hi, I think that it's expected behaviour. In secure mode only WHQL'd drivers are allowed to be loaded into the OS kernel, and while RHEV/RHV provides WHQL'd drivers, oVirt users receive RH signed ones, which from the OS standpoint are basically not certified. Thanks in advance, On Thu, Jun 13, 2019 at 1:12 PM Yedidyah Bar David <didi@redhat.com> wrote:
On Mon, Jun 10, 2019 at 10:54 PM Vinícius Ferrão < ferrao@versatushpc.com.br> wrote:
RHV drivers works. oVirt drivers does not.
Checked this now.
I’m not sure if this is intended or not. But oVirt drivers aren’t signed for Windows.
oVirt's drivers are simply copied from virtio-win repositories.
Adding Vadim from virtio-win team.
Best regards,
On 29 May 2019, at 21:41, michael@wanderingmad.com wrote:
I'm running server 2012R2, 2016, and 2019 with no issue using the Redhat signed drivers from RHEV. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GBQEMLOW5DCSW7...
Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PNZWHYEWW23N4G...
-- Didi _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OIBSOZEBGSF65J...
-- Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev@redhat.com | lveyde@redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
Lev, thanks for the reply. So basically Windows on Secureboot UEFI is simply “broken” within oVirt? Will Red Hat reconsider this? Since one of the “selling points” of oVirt 4.3 was UEFI support. Can the RH WHQL drivers be shipped with oVirt? Thanks,
On 13 Jun 2019, at 07:25, Lev Veyde <lveyde@redhat.com> wrote:
Hi,
I think that it's expected behaviour.
In secure mode only WHQL'd drivers are allowed to be loaded into the OS kernel, and while RHEV/RHV provides WHQL'd drivers, oVirt users receive RH signed ones, which from the OS standpoint are basically not certified.
Thanks in advance,
On Thu, Jun 13, 2019 at 1:12 PM Yedidyah Bar David <didi@redhat.com <mailto:didi@redhat.com>> wrote: On Mon, Jun 10, 2019 at 10:54 PM Vinícius Ferrão <ferrao@versatushpc.com.br <mailto:ferrao@versatushpc.com.br>> wrote: RHV drivers works. oVirt drivers does not.
Checked this now.
I’m not sure if this is intended or not. But oVirt drivers aren’t signed for Windows.
oVirt's drivers are simply copied from virtio-win repositories.
Adding Vadim from virtio-win team.
Best regards,
On 29 May 2019, at 21:41, michael@wanderingmad.com <mailto:michael@wanderingmad.com> wrote:
I'm running server 2012R2, 2016, and 2019 with no issue using the Redhat signed drivers from RHEV. _______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GBQEMLOW5DCSW7... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/GBQEMLOW5DCSW7XSLNZKNX532BQHRFUB/>
Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PNZWHYEWW23N4G... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/PNZWHYEWW23N4GQKHMJ2RUSQR363NSYH/>
-- Didi _______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OIBSOZEBGSF65J... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/OIBSOZEBGSF65JEVMNMPOCAB6ICTVKIU/>
--
LEV VEYDE SOFTWARE ENGINEER, RHCE | RHCVA | MCITP Red Hat Israel
<https://www.redhat.com/> lev@redhat.com <mailto:lev@redhat.com> | lveyde@redhat.com <mailto:lveyde@redhat.com> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
On Thu, 2019-06-13 at 15:24 -0300, Vinícius Ferrão wrote:
Lev, thanks for the reply. So basically Windows on Secureboot UEFI is simply “broken” within oVirt?
Will Red Hat reconsider this? Since one of the “selling points” of oVirt 4.3 was UEFI support. Can the RH WHQL drivers be shipped with oVirt?
Technically, WHQL-signing is not required to satisfy secure boot requirements. UEFI signing should be enough. But it might be some license issues.https://techcommunity.microsoft.com/t5/Windows-Hardware- Certification/Microsoft-UEFI-CA-Signing-policy-updates/ba-p/364828
Thanks,
On 13 Jun 2019, at 07:25, Lev Veyde <lveyde@redhat.com> wrote: Hi,
I think that it's expected behaviour.
In secure mode only WHQL'd drivers are allowed to be loaded into the OS kernel, and while RHEV/RHV provides WHQL'd drivers, oVirt users receive RH signed ones, which from the OS standpoint are basically not certified.
Thanks in advance,
On Thu, Jun 13, 2019 at 1:12 PM Yedidyah Bar David <didi@redhat.com
wrote: On Mon, Jun 10, 2019 at 10:54 PM Vinícius Ferrão <ferrao@versatus hpc.com.br> wrote:
RHV drivers works.
oVirt drivers does not.
Checked this now.
I’m not sure if this is intended or not. But oVirt drivers aren’t signed for Windows.
oVirt's drivers are simply copied from virtio-win repositories. Adding Vadim from virtio-win team. Best regards,
On 29 May 2019, at 21:41, michael@wanderingmad.com wrote:
I'm running server 2012R2, 2016, and 2019 with no issue using the Redhat signed drivers from RHEV.
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/ community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ov irt.org/message/GBQEMLOW5DCSW7XSLNZKNX532BQHRFUB/
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/co mmunity-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovir t.org/message/PNZWHYEWW23N4GQKHMJ2RUSQR363NSYH/
-- Didi
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/comm unity-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt. org/message/OIBSOZEBGSF65JEVMNMPOCAB6ICTVKIU/
--
Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel
lev@redhat.com | lveyde@redhat.com
TRIED. TESTED. TRUSTED.
+Amnon & Martin On Fri, 2019-06-14 at 17:52 +1000, Vadim Rozenfeld wrote: On Thu, 2019-06-13 at 15:24 -0300, Vinícius Ferrão wrote: Lev, thanks for the reply. So basically Windows on Secureboot UEFI is simply “broken” within oVirt? Will Red Hat reconsider this? Since one of the “selling points” of oVirt 4.3 was UEFI support. Can the RH WHQL drivers be shipped with oVirt? Technically, WHQL-signing is not required to satisfy secure boot requirements. UEFI signing should be enough. But it might be some license issues. https://techcommunity.microsoft.com/t5/Windows-Hardware-Certification/Micros... Thanks, On 13 Jun 2019, at 07:25, Lev Veyde <lveyde@redhat.com<mailto:lveyde@redhat.com>> wrote: Hi, I think that it's expected behaviour. In secure mode only WHQL'd drivers are allowed to be loaded into the OS kernel, and while RHEV/RHV provides WHQL'd drivers, oVirt users receive RH signed ones, which from the OS standpoint are basically not certified. Thanks in advance, On Thu, Jun 13, 2019 at 1:12 PM Yedidyah Bar David <didi@redhat.com<mailto:didi@redhat.com>> wrote: On Mon, Jun 10, 2019 at 10:54 PM Vinícius Ferrão <ferrao@versatushpc.com.br<mailto:ferrao@versatushpc.com.br>> wrote: RHV drivers works. oVirt drivers does not. Checked this now. I’m not sure if this is intended or not. But oVirt drivers aren’t signed for Windows. oVirt's drivers are simply copied from virtio-win repositories. Adding Vadim from virtio-win team. Best regards,
On 29 May 2019, at 21:41, michael@wanderingmad.com<mailto:michael@wanderingmad.com> wrote:
I'm running server 2012R2, 2016, and 2019 with no issue using the Redhat signed drivers from RHEV. _______________________________________________ Users mailing list -- users@ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GBQEMLOW5DCSW7...
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PNZWHYEWW23N4G... -- Didi _______________________________________________ Users mailing list -- users@ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OIBSOZEBGSF65J... -- Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com/> lev@redhat.com<mailto:lev@redhat.com> | lveyde@redhat.com<mailto:lveyde@redhat.com> [https://www.redhat.com/profiles/rh/themes/redhatdotcom/img/logo-red-hat-black.png]<https://red.ht/sig> TRIED. TESTED. TRUSTED.<https://redhat.com/trusted>
Vadim, its OVMF. I think it is. Just selected UEFI with Secure Boot on the VM properties on oVirt. I’m not aware of SeaBIOS with UEFI support. Thanks. Sent from my iPhone
On 18 Jun 2019, at 08:26, Vadim Rozenfeld <vadimrosenfeld@hotmail.com> wrote:
+Amnon & Martin
On Fri, 2019-06-14 at 17:52 +1000, Vadim Rozenfeld wrote:
On Thu, 2019-06-13 at 15:24 -0300, Vinícius Ferrão wrote: Lev, thanks for the reply.
So basically Windows on Secureboot UEFI is simply “broken” within oVirt?
Will Red Hat reconsider this? Since one of the “selling points” of oVirt 4.3 was UEFI support. Can the RH WHQL drivers be shipped with oVirt?
Technically, WHQL-signing is not required to satisfy secure boot requirements. UEFI signing should be enough. But it might be some license issues. https://techcommunity.microsoft.com/t5/Windows-Hardware-Certification/Micros...
Thanks,
On 13 Jun 2019, at 07:25, Lev Veyde <lveyde@redhat.com> wrote: Hi,
I think that it's expected behaviour.
In secure mode only WHQL'd drivers are allowed to be loaded into the OS kernel, and while RHEV/RHV provides WHQL'd drivers, oVirt users receive RH signed ones, which from the OS standpoint are basically not certified.
Thanks in advance,
On Thu, Jun 13, 2019 at 1:12 PM Yedidyah Bar David <didi@redhat.com> wrote:
On Mon, Jun 10, 2019 at 10:54 PM Vinícius Ferrão <ferrao@versatushpc.com.br> wrote: RHV drivers works. oVirt drivers does not.
Checked this now.
I’m not sure if this is intended or not. But oVirt drivers aren’t signed for Windows.
oVirt's drivers are simply copied from virtio-win repositories.
Adding Vadim from virtio-win team.
Best regards,
> On 29 May 2019, at 21:41, michael@wanderingmad.com wrote: > > I'm running server 2012R2, 2016, and 2019 with no issue using the Redhat signed drivers from RHEV. > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-leave@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GBQEMLOW5DCSW7... _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PNZWHYEWW23N4G...
-- Didi _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OIBSOZEBGSF65J...
--
LEV VEYDE SOFTWARE ENGINEER, RHCE | RHCVA | MCITP Red Hat Israel
lev@redhat.com | lveyde@redhat.com
TRIED. TESTED. TRUSTED.
On Thu, 2019-06-13 at 11:36 +0300, Yedidyah Bar David wrote:
On Mon, Jun 10, 2019 at 10:54 PM Vinícius Ferrão <ferrao@versatushpc. com.br> wrote:
RHV drivers works.
oVirt drivers does not.
Checked this now.
I’m not sure if this is intended or not. But oVirt drivers aren’t signed for Windows.
oVirt's drivers are simply copied from virtio-win repositories.
Adding Vadim from virtio-win team.
Best regards,
Hi guys, Can you please help us to reproduce the problem? It will be great if you can provide me with the followinginformation: - qemu and host kernel versions,- qemu command line,- RHV and oVirt drivers versions. Cheers,Vadim.
On 29 May 2019, at 21:41, michael@wanderingmad.com wrote:
I'm running server 2012R2, 2016, and 2019 with no issue using the Redhat signed drivers from RHEV.
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/comm unity-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt. org/message/GBQEMLOW5DCSW7XSLNZKNX532BQHRFUB/
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/commun ity-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.or g/message/PNZWHYEWW23N4GQKHMJ2RUSQR363NSYH/
Hello Vadim, I got the working drivers from RHEL8: eecdff62b5d148f02dc92d7115631175 virtio-win-1.9.7-rhel8.iso Non working ones directly from the Hosted Engine: c55e2815bc7090f077cf82aed5c90423 virtio-win-0.1.171.iso Thanks,
On 13 Jun 2019, at 23:33, Vadim Rozenfeld <vrozenfe@redhat.com> wrote:
On Thu, 2019-06-13 at 11:36 +0300, Yedidyah Bar David wrote:
On Mon, Jun 10, 2019 at 10:54 PM Vinícius Ferrão <ferrao@versatushpc.com.br <mailto:ferrao@versatushpc.com.br>> wrote:
RHV drivers works. oVirt drivers does not.
Checked this now.
I’m not sure if this is intended or not. But oVirt drivers aren’t signed for Windows.
oVirt's drivers are simply copied from virtio-win repositories.
Adding Vadim from virtio-win team.
Best regards,
Hi guys,
Can you please help us to reproduce the problem?
It will be great if you can provide me with the following information:
- qemu and host kernel versions, - qemu command line, - RHV and oVirt drivers versions.
Cheers, Vadim.
On 29 May 2019, at 21:41, michael@wanderingmad.com <mailto:michael@wanderingmad.com> wrote:
I'm running server 2012R2, 2016, and 2019 with no issue using the Redhat signed drivers from RHEV. _______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GBQEMLOW5DCSW7... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/GBQEMLOW5DCSW7XSLNZKNX532BQHRFUB/>
Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PNZWHYEWW23N4G... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/PNZWHYEWW23N4GQKHMJ2RUSQR363NSYH/>
On Fri, 2019-06-14 at 12:01 -0300, Vinícius Ferrão wrote:
Hello Vadim, I got the working drivers from RHEL8: eecdff62b5d148f02dc92d7115631175 virtio-win-1.9.7-rhel8.iso
Non working ones directly from the Hosted Engine: c55e2815bc7090f077cf82aed5c90423 virtio-win-0.1.171.iso
Thanks,
Hello Vinícius,Do you use OVMF or SeaBios? If it is OVMF then Lev already nailed the problem.Only WHQL or UEFI signed drivers will work with secure boot. Best regards,Vadim.
On 13 Jun 2019, at 23:33, Vadim Rozenfeld <vrozenfe@redhat.com> wrote: On Thu, 2019-06-13 at 11:36 +0300, Yedidyah Bar David wrote:
On Mon, Jun 10, 2019 at 10:54 PM Vinícius Ferrão <ferrao@versatus hpc.com.br> wrote:
RHV drivers works. oVirt drivers does not.
Checked this now.
I’m not sure if this is intended or not. But oVirt drivers aren’t signed for Windows.
oVirt's drivers are simply copied from virtio-win repositories.
Adding Vadim from virtio-win team.
Best regards,
Hi guys,
Can you please help us to reproduce the problem?
It will be great if you can provide me with the following information:
- qemu and host kernel versions, - qemu command line, - RHV and oVirt drivers versions.
Cheers, Vadim.
On 29 May 2019, at 21:41, michael@wanderingmad.com wrote:
I'm running server 2012R2, 2016, and 2019 with no issue using the Redhat signed drivers from RHEV. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/ community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ov irt.org/message/GBQEMLOW5DCSW7XSLNZKNX532BQHRFUB/
Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/co mmunity-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovir t.org/message/PNZWHYEWW23N4GQKHMJ2RUSQR363NSYH/
ul[class*='mb-extra__public-links'], ul[class*='mb-note__public- links'], ul[class*='mb-task__public-links'] { display: none !important; }
participants (6)
-
Lev Veyde -
michael＠wanderingmad.com -
Vadim Rozenfeld -
Vadim Rozenfeld -
Vinícius Ferrão -
Yedidyah Bar David