VMware Communities
continuum
Immortal
Immortal

@ VMware engineers and documentation authors

In the Workstation forum the top 1 question is: why does Workstation XY fails to install on Ubuntu YZ.

Can we please get an announcement or a sticky posts that explains this in some depth.
Do you really want us volunteers to repeat this rant over and over again:

VMware does not care wether the latest Workstation installs on latest Ubuntu.
Instead monitor the Ubuntu scene - sooner or later some freak from the Ubuntu scene will post a script that fixes the defects of the official installer.

This is advertisement of the worst kind - do you think we are enjoying posting "VMware just does not care ...." over and over again ?

Regards Ulli


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

28 Replies
scott28tt
VMware Employee
VMware Employee

@Mikero 

 


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
Mikero
Community Manager
Community Manager

Thanks Ulli,

We should have responded on this sooner, I agree. I honestly don't spend as much time in the Workstation forums as I should, but we do see the trending issues and put together plans to fix what we're hearing/seeing.

We care, and I care... Kind of painfully too much for me sometimes, ngl. Please don't think that us not posting here as often as we should means that we don't!

I want us to be 10 steps further ahead than we are now, so I get pretty sad when it doesn't look like we're moving fast enough. We've had some really tough challenges the past couple of years, so it's been hard for us and our tiny little team against the background of everything else that's going on at VMW. We're just... strapped. 

What's tricky is that WS 16 was never intended to support Ubuntu 22.04, that came out much later than WS16 did. So until it was put in scope, not a lot of testing goes into it.

That said, we recognize this issue and have been heads down internally getting this resolved in addition to everything else we have going on (multiple TP's coming up, lots of backend work due to Windows, Linux and macOS changes, etc).  

We do have a fix internally for this issue, and we'll be shipping it next week via Workstation 16.2.4.

Ulli, I thank you for what you do here and what you've been doing over the years. I'm sorry that we let this and other issues linger for too long. I hope to not put you or anyone else in a position to think that we don't care. Our products are supposed to show the best of what VMware has to offer, and we value when the community lets us know when we're missing that mark. 

 

-
Michael Roy - PM/PMM: Fusion & Workstation
RDPetruska
Leadership
Leadership

Michael,

Thanks for the update, and at least the intent/desire to commit to better products.  When are you going to fix the regressed issues between 16.1.2 and 16.2.x?  As of 16.2.3 there are multiple items STILL not fixed!  The most egregious one for me is the disk mounting/drive mapping...  Any build after 16.1.2, either will not let me mount my DOS vmdks to my host without crashing, or else allows me to mount them but then as soon as I attempt to navigate the mounted disk, or copy a file to/from it, crashes.

rick2600
Contributor
Contributor

Hi @Mikero, thank you for the infos.

As many others I can't launch Workstation Pro due the compilation problem of vmmon and vmnet.

The setup is:

Software: VMware Workstation 16.2.3 build-19376536
OS: Ubuntu 20.04
Kernel: 5.15.0-41-generic

You mentioned that a fix to address this issue is comming.
Is there a deadline?
If not... Is there a temporary official workaround until we wait for the patch?

Thank you.

Reply
0 Kudos
wila
Immortal
Immortal

Hi,


@rick2600 wrote:

Hi @Mikero, thank you for the infos.

As many others I can't launch Workstation Pro due the compilation problem of vmmon and vmnet.

The setup is:

Software: VMware Workstation 16.2.3 build-19376536
OS: Ubuntu 20.04
Kernel: 5.15.0-41-generic

You mentioned that a fix to address this issue is comming.
Is there a deadline?
If not... Is there a temporary official workaround until we wait for the patch?

Thank you.


https://communities.vmware.com/t5/VMware-Workstation-Player/VMWare-Kernel-Module-Updater-failed/td-p...

--
Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
rick2600
Contributor
Contributor

Thank you @wila .

I had seen this workaround, but I wanted to hear from VMware if they have a date scheduled for an official patch.

Depending on it I could wait or apply the third-party patch.
As I didn't get an official reply until now I suspect I'll have to go for option 2.

Anyway thank you.

Reply
0 Kudos
scott28tt
VMware Employee
VMware Employee

Perhaps you missed the bit about 16.2.4 and it releasing this week.

 


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
RDPetruska
Leadership
Leadership

Well, big surprise... 16.2.4 STILL has mounting virtual disks broken!!  Come on, QA department - start paying better attention to regression testing!  I'm tired of having to keep rolling back to 16.1.2 in order to do my job.

continuum
Immortal
Immortal

Can someone please try wether non-persistant vmdks are still broken ?
Thank you

Ulli


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
Kinnison
Expert
Expert

Hi,


AFAIK, "the independent non-persistent disk feature" still does not work.


Regards,
FERdinando

Reply
0 Kudos
Mikero
Community Manager
Community Manager

On the disk mounting...

With my head in my hands, I'm just going to go ahead and say it... but that feature is being pulled in the next major.

Folks should notice that in next week's Tech Preview.

Sadly, the folks who intimately knew how it works have been long gone.
It's also always broken because Windows continues to enhance its security posture, and the driver was not designed with security in mind originally.

I don't like it at all, but I don't want folks to have the expectation that it will work again.

I wish I had a better answer, but our focus has been on making Windows 11 work.

Note that we never expected to do a Windows 11, but MS decided to change their playbook raised the requirements bar putting a ton of engineering work for us to do just to make Win11 VMs boot on Workstation for Windows and Linux as well as Fusion for Intel and Apple Silicon.

I'll take the slings and arrows, and let the team as well as leadership know the pain the community is feeling over this.


-
Michael Roy - PM/PMM: Fusion & Workstation
RDPetruska
Leadership
Leadership

Yeah, well, until you write a VMware Tools to make shared folders work for DOS (which I know will NEVER happen), then the ONLY way to get large files in/out of DOS VMs is to mount the drive.  And it has consistently worked without flaws up to 16.1.2.  And as I've written elsewhere, I'm not touching Win11 with a 20' pole... it seems to be worse debacle than Vista was.  I could care less about modern OS's... the ENTIRE reason I use VMware is to run older outdated ones!

Thanks for the heads-up at least... I guess there's no reason for me to renew my Support subscription, which expires in September, then.

Reply
0 Kudos
continuum
Immortal
Immortal

> Sadly, the folks who intimately knew how it works have been long gone.

Yes - we were here when they were fired and remember the discussions ...
IMHO Workstation was fastest with 4.5, was most feature rich and wellbuild with WS 7 and the ACE addons.
Since then we see a slow and gradual regression until the layoff at the time of 12.5
That regression added momentum after 12.5 and nowadays we dont count new features when seeing a new version.
We count the numbers of features that once worked as advertised and now are slowly disappearing and get buggier.

Sometimes I am actually impressed that you made it to a version 16.2 at all - well done given the circumstances.
It is a pity that we dont talk about what Workstation could be - your message is a highly welcome exception.
Thank you

Ulli


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Kinnison
Expert
Expert

Comment removed...

Reply
0 Kudos
Hvergelmir
Enthusiast
Enthusiast

@Mikerowhat's the issue with Windows 11? It's not even that different from the latest Windows 10 release (21H2) at the time of this writing. I have done quite a bit of Windows kernel development in my professional career (even in the file system realm) and dabble in Windows internals almost on a daily basis and the biggest changes I am aware of were during the Windows 10 era but not so much at the divide between Windows 10 and 11. Also, technically Windows 11 still keeps reporting as 10.0 (with manifest or RtlGetVersion, which are the two ways to avoid Windows lying and returning 6.2), despite its marketing name. The SDK and WDK are also called 10.0 (referring to the Windows 11 build number 22000, though).

Does this have to do with the fact that Windows (since 10, though) often runs atop Hyper-V to enable features like the Virtualization-based Security (VBS), which also necessitates installing Windows Hypervisor Platform? Is MSFT seriously refusing to work with VMware on this? I'd be surprised, since they are a competitor with Hyper-V and therefore I imagine they'd literally hand you arguments for a potential legal case.

MSFT has literally raised the bar year after year for anti-malware products, too. Performance requirements and other stuff in order to be able to participate at different levels in their private "programs". So I can relate to the pain you describe. However, it does depend a lot on how much technical debt was accrued before their respective deadlines (and I've seen them pushing deadlines due to vendors not being able to make them). And also you definitely can't put a user mode dev on a driver and expect anything good to come off of it.

Regarding Windows 11 (guest) support. Thanks, I was pleasantly surprised to see that go so smoothly initially. But after I ran into the issue with the VM being reported as encrypted and no way to access it anymore (several times), I ended up resorting to the trick where during setup you add a few registry values to have the setup skip the relevant checks. Sure, this could also break at the mercy of MSFT, but a VM suddenly no longer being accessible without any way to recover, just because this vTPM thingamy acts up, isn't an option either.

I recall how disappointed I was when time travel debugging was culled from VMware Workstation. I think you called it replay debugging or so. Regardless, that feature was so much ahead of its time. It was a pity to see it go. It indeed looks a bit like the product is in decline. My main beef with alternatives on the Linux side is currently the lack of agreeable (guest) multi-monitor support as well as the lack of accelerated graphics for the guest. Hope these don't also go the way of the dodo :winking_face:

Reply
0 Kudos
Mongo424242
Enthusiast
Enthusiast

Hi all,

So, can I assume that is safe to "upgrade" to 16.2.4 (i.e. nothing new is broken, and it will compile under kernel 5.15)?  I am another of those who use Workstation for older OS's on a Linux backbone (I have no care for anything beyond Windows 7), and I have always thought of VMWare as the "top-o-the-line" desktop hypervisor.  I continue to hope that VMWare does not have the intention of abandoning the desktop crowd (type 2) for the server people (type 1).  A big "thank you" to Mikero for his attention and participation here!

Mongo

Reply
0 Kudos
continuum
Immortal
Immortal

> So, can I assume that is safe to "upgrade" to 16.2.4 (i.e. nothing new is broken, and it will compile under kernel 5.15)?

I have not seen someone reporting a successful build on newer kernels yet.
In case you use VMs for productive work I would stick to a working earlier version.
Its also a reasonable strategy to test a new build inside a VM first.

> Noting new is broken ...
I am not sure wether the developers are aware of what we long time users assume to work ...
Have not seen any
makewsgreatagain-1.png
demos these days

Ulli

 


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

RDPetruska
Leadership
Leadership

Ulli,

LOVE the hat idea!  I think it needs the old 'boxes' logo, though, from back in the time when WS really *was* great.  :winking_face: 

Reply
0 Kudos
Mongo424242
Enthusiast
Enthusiast

Well, I guess I am the guinea pig.  I found another post where the user had upgraded from 16.2.3 to 16.2.4 with no issues, and nothing (that I could find) saying that it broke anything, so I took a chance.  I allowed Workstation to upgrade to 16.2.4 from the upgrade prompt, tested it under kernel 5.13 (it worked), then allowed the OS to upgrade the kernel to 5.15.  I rebooted, and then tried workstation.  It compiled everything successfully, and all of my VMs are behaving nominally.  As usual, like an idiot I neglected to check if the other user was running a Windows host or a Linux host (he was running Windows, judging from the path to the vmci driver).  I guess I dodged a bullet here.  Your suggestion that I test future installers in a VM is well taken, so thank you for that.

One thing I did notice from the other user's post is that the vmci module in the 16.2.4 install was an old version (9.8.16), and that they had to manually upgrade it to current (9.8.18).  Now I realize that they were on a Windows host, but I did dome digging, and in the vmxf file for each of my VMs I found the vmci versions to be as follows: WindowsXP: v9.5.10.0 and Windows 7: v9.8.16.1.  I cannot find anything that tells me if these are current, and I have no idea how to upgrade them if they are not.  Thanks!

Reply
0 Kudos