Comment # 35 on bug 1204162 from Kirk Allan

(In reply to Lin Ma from comment #34)
> (In reply to ulfbart from comment #33)
> > (In reply to Lin Ma from comment #32)
> > > First of all, Virtio-net doesn't work in your windows vm, It's unbelievable
> > > to me because it was well tested.
> > > It seems that only one reason can explain why it doesn't work: you forgot to
> > > install vmdp-win drivers in your win vms. Please verify it. It you did
> > > install it, Then please let me know the vmdp-win version you installed.(I
> > > used VMDP-WIN-2.5.2, virtio-net works well in my win10,win11 vms)
> > 
> > Nope, if this is not part of the Windows installation it wouldn't installed.
> > I use my VM sessions like the most only out of the box.
> > 
> > I find only a download at SUSE which you need to register according my
> > understanding only for professionals (not hobby users like me). There is
> > VMDP-WIN-2.5.3.exe provided:
> > https://www.suse.com/download/suse-vmdp/
> > Or is there a different precompiled version based on the GitHub w/o
> > registration available (e.g. vie MS Store)?
> > https://github.com/SUSE/vmdp
> 
> @Kirk, Do we have such plan to MS Store or easier way to get binaries
> without registration?

We do build binaries from https://github.com/SUSE/vmdp to produce a community
version of vmdp e.g. VMDP-WIN-2.5.3-Community.exe.  The difference between
VMDP-WIN-2.5.3-Community.exe and VMDP-WIN-2.5.3.exe are the signatures on the
drivers.  The community version drivers are SUSE signed and the Win10 and newer
drivers are SUSE signed and Microsoft attestation signed.  The drivers in
VMDP-WIN-2.5.3.exe are WHQL signed.

We are currently working on a plan to make the community vmdp package easily
available.  I will attach it to the bug for now.