VMware woes

[Sherman Grunewagen]

Hello all.

Does anyone have VMware Workstation Pro 17.5.0 running with any of the
later 6.6.X kernels?

I'm having a hard time getting it to run with a Fedora 38
installation.  I'm fully updated as of 2 days ago, including the 6.6.9
kernel.  When I try to start Workstation directly after VMware
installation I get a popup saying that the kernel-headers package for
kernel-6.6.9 is missing and so it can't build some modules. the problem is that
the kernel-headers package for 6.6.9 is missing from Updates. The latest package is
for 6.6.3.

I'm guessing those modules are vmmon and vmnet, which usually have to be rebuilt for
new kernels and so I also tried build the modules following the instructions here:

  https://github.com/mkubecek/vmware-host-modules/blob/workstation-17.5.0/I...

but it failed also and I don't know how to debug the problems.

Would appreciate any help!

-- Sherman

[GMX]

Sorry to hear. The kernel-headers are mandatory, so you will have to
wait for them or use another distribution which have them availlable.
Thanks to mkubecek , VM Workstation is running well with all kernels
6.6 and 6.7.

-------- Ursprüngliche Nachricht --------
Van: Sherman Grunewagen via users <users(a)lists.fedoraproject.org&gt;
Antwoord-naar: Community support for Fedora users
<users(a)lists.fedoraproject.org&gt;
Aan: fedora users <users(a)lists.fedoraproject.org&gt;
Cc: Sherman Grunewagen <sugarwagon(a)gmx.com&gt;
Onderwerp: VMware woes
Datum: 11.01.2024 00:36:32

Hello all.

Does anyone have VMware Workstation Pro 17.5.0 running with any of the
later 6.6.X kernels?

I'm having a hard time getting it to run with a Fedora 38
installation.  I'm fully updated as of 2 days ago, including the 6.6.9
kernel.  When I try to start Workstation directly after VMware
installation I get a popup saying that the kernel-headers package for
kernel-6.6.9 is missing and so it can't build some modules. the problem
is that
the kernel-headers package for 6.6.9 is missing from Updates. The
latest package is
for 6.6.3.

I'm guessing those modules are vmmon and vmnet, which usually have to
be rebuilt for
new kernels and so I also tried build the modules following the
instructions here:

 
https://github.com/mkubecek/vmware-host-modules/blob/workstation-17.5.0/I...

but it failed also and I don't know how to debug the problems.

Would appreciate any help!

-- Sherman

--
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue

[Sherman Grunewagen]

Thanks very much!  I still have 6.6.7 on the machine. I'll try booting on that kernel
and see if I can get VMware to work.

On 10/01/2024 15.45, GMX wrote:
>  Sorry to hear. The kernel-headers are mandatory, so you will have to
> wait for them or use another distribution which have them availlable. Thanks to mkubecek ,
> VM Workstation is running well with all kernels 6.6 and 6.7.
>
>  -------- Ursprüngliche Nachricht --------
>  *Van*: Sherman Grunewagen via users <users(a)lists.fedoraproject.org
> <mailto:[e-mail]%3e>>
>  *Antwoord-naar*: Community support for Fedora users <users(a)lists.fedoraproject.org
> <mailto:[e-mail]%3e>>
>  *Aan*: fedora users <users(a)lists.fedoraproject.org
> <mailto:[e-mail]%3e>>
>  *Cc*: Sherman Grunewagen <sugarwagon(a)gmx.com
> <mailto:[e-mail]%3e>>
>  *Onderwerp*: VMware woes
>  *Datum*: 11.01.2024 00:36:32
>
>  Hello all.
>
>  Does anyone have VMware Workstation Pro 17.5.0 running with any of the
>  later 6.6.X kernels?
>
>  I'm having a hard time getting it to run with a Fedora 38
>  installation.  I'm fully updated as of 2 days ago, including the 6.6.9
>  kernel.  When I try to start Workstation directly after VMware
>  installation I get a popup saying that the kernel-headers package for
>  kernel-6.6.9 is missing and so it can't build some modules. the problem is that
>  the kernel-headers package for 6.6.9 is missing from Updates. The latest package is
>  for 6.6.3.
>
>  I'm guessing those modules are vmmon and vmnet, which usually have to be rebuilt for
>  new kernels and so I also tried build the modules following the instructions here:
>
>  https://github.com/mkubecek/vmware-host-modules/blob/workstation-17.5.0/I...
> <https://github.com/mkubecek/vmware-host-modules/blob/workstation-17.5.0/I...
>
>  but it failed also and I don't know how to debug the problems.
>
>  Would appreciate any help!
>
>  -- Sherman
>
>  --
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
> <mailto:[e-mail]>
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> <mailto:[e-mail]>
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> <https://fedoraproject.org/wiki/Mailing_list_guidelines>
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
> <https://lists.fedoraproject.org/archives/list/[e-mail].o...
>  Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> <https://pagure.io/fedora-infrastructure/new_issue>
>

[Samuel Sieb]

On 1/10/24 15:36, Sherman Grunewagen via users wrote:
>  Does anyone have VMware Workstation Pro 17.5.0 running with any of
> the
>  later 6.6.X kernels?
>  
>  I'm having a hard time getting it to run with a Fedora 38
>  installation.  I'm fully updated as of 2 days ago, including the 6.6.9
>  kernel.  When I try to start Workstation directly after VMware
>  installation I get a popup saying that the kernel-headers package for
>  kernel-6.6.9 is missing and so it can't build some modules. the problem 
>  is that
>  the kernel-headers package for 6.6.9 is missing from Updates. The latest 
>  package is
>  for 6.6.3. 
That sounds like a broken build system.  The kernel-headers package 
doesn't get updated for every kernel if they haven't changed.

Have you tried using qemu/kvm instead?

[Sherman Grunewagen]

On 10/01/2024 16.06, Samuel Sieb wrote:
>  On 1/10/24 15:36, Sherman Grunewagen via users wrote:
> > Does anyone have VMware Workstation Pro 17.5.0 running with any of the
> > later 6.6.X kernels?
> >
> > I'm having a hard time getting it to run with a Fedora 38
> > installation.  I'm fully updated as of 2 days ago, including the 6.6.9
> > kernel.  When I try to start Workstation directly after VMware
> > installation I get a popup saying that the kernel-headers package for
> > kernel-6.6.9 is missing and so it can't build some modules. the problem is that
> > the kernel-headers package for 6.6.9 is missing from Updates. The latest package is
> > for 6.6.3.
>
>  That sounds like a broken build system.  The kernel-headers package doesn't get
> updated for every kernel if they haven't changed.
>
>  Have you tried using qemu/kvm instead?
>  -- 
I haven't.

I've been living in a certain closed country for the past several
years and sadly haven't been able to update either my Fedora system
or my Linux "praxis".  I'm very rusty.

Having returned to America, I did a fresh install of Fedora 38 from
Fedora 30 (don't laugh :-)) on which VMware 15 worked flawlessly.
Tweaking the system to get things the way I ran F30 has taken all my
meagre brain cycles. :-) Lots has changed since F30!

Now I'm trying to get the newest VMware to work.  Changing to qemu/kvm
(I barely know what they are) seems daunting, especially as I need for
the Windows 7 guest to run as it did under VMware.  I no longer have
the installation disks for Windows or Office 2013 (both "pro"
editions), nor the mathematics macros I installed in PowerPoint.  So
re-installation isn't possible.  Staying with VMware seems the right
road for now.

-- Sherman

[Frank Bures]

On 2024-01-10 21:03, Sherman Grunewagen via users wrote:
>  On 10/01/2024 16.06, Samuel Sieb wrote:
> > On 1/10/24 15:36, Sherman Grunewagen via users wrote:
> >> Does anyone have VMware Workstation Pro 17.5.0 running with any of the
> >> later 6.6.X kernels?
> >>
> >> I'm having a hard time getting it to run with a Fedora 38
> >> installation.  I'm fully updated as of 2 days ago, including the 6.6.9
> >> kernel.  When I try to start Workstation directly after VMware
> >> installation I get a popup saying that the kernel-headers package for
> >> kernel-6.6.9 is missing and so it can't build some modules. the problem 
> >> is that
> >> the kernel-headers package for 6.6.9 is missing from Updates. The latest 
> >> package is
> >> for 6.6.3.
> >
> > That sounds like a broken build system.  The kernel-headers package 
> > doesn't get updated for every kernel if they haven't changed.
> >
> > Have you tried using qemu/kvm instead?
> > -- 
>  
>  I haven't.
>  
>  I've been living in a certain closed country for the past several
>  years and sadly haven't been able to update either my Fedora system
>  or my Linux "praxis".  I'm very rusty.
>  
>  Having returned to America, I did a fresh install of Fedora 38 from
>  Fedora 30 (don't laugh :-)) on which VMware 15 worked flawlessly.
>  Tweaking the system to get things the way I ran F30 has taken all my
>  meagre brain cycles. :-) Lots has changed since F30!
>  
>  Now I'm trying to get the newest VMware to work.  Changing to qemu/kvm
>  (I barely know what they are) seems daunting, especially as I need for
>  the Windows 7 guest to run as it did under VMware.  I no longer have
>  the installation disks for Windows or Office 2013 (both "pro"
>  editions), nor the mathematics macros I installed in PowerPoint.  So
>  re-installation isn't possible.  Staying with VMware seems the right
>  road for now.
>  
>  -- Sherman 
You would not have to reinstall.  Once you convert your VMWare disks to 
QEMU disk and configure the QEMU virtual machine, it just boots the same 
way as it used to in VMWare.  That's the beauty of it.

Cheers
Frank


-- 

<listfrank1(a)gmail.com&gt;

[Barry]

>  On 11 Jan 2024, at 02:43, Frank Bures <buresf(a)gmail.com&gt;
> wrote:
>  
>  You would not have to reinstall.  Once you convert your VMWare disks to QEMU disk and
> configure the QEMU virtual machine, it just boots the same way as it used to in VMWare. 
> That's the beauty of it. 
Yes this works well. I converted a windows 10 successfully.
Just remember that you also need to copy the Ethernet address from the vmware xml config
file into the qemu config. Easy to do with libvirt manager.

Last few days I managed to upgrade the windows 10 image to windows 11.
A little tricky to convert from MBR to GPT then boot under UEFI and secure boot, but
doable.

Barry

[Sbob]

I am running Fedora 39 (Kernel 6.6.9-200) and VMWare workstation Pro 17.5.0


Here is what I do every time there is a new kernel:

1) run the dnf update and get the new kernel installed


2) reboot


3) open a terminal as root and run this script:

#!/bin/bash

VMWARE_VERSION=workstation-17.5.0
TMP_FOLDER=/tmp/patch-vmware
rm -fdr $TMP_FOLDER
mkdir -p $TMP_FOLDER
cd $TMP_FOLDER
git clone https://github.com/mkubecek/vmware-host-modules.git
cd $TMP_FOLDER/vmware-host-modules
git checkout $VMWARE_VERSION
git fetch
make
sudo make install
sudo rm /usr/lib/vmware/lib/libz.so.1/libz.so.1
sudo ln -s /lib/x86_64-linux-gnu/libz.so.1
/usr/lib/vmware/lib/libz.so.1/libz.so.1
sudo /etc/init.d/vmware restart


There are always a couple of not found errors but the compile succeeds


4) I start VMWare as root by running this script:


#!/bin/bash

/etc/init.d/vmware restart

vmware&



At this point VMWare should start but it will not actually start a VM 
throwing an error about vmmon if I remember correctly


5) Stop VMWare


6) reboot once again


7) log in again and as root start VMWare with the start script again 
(step 4) and presto, everything works as expected


Note: as you upgrade VMWare versions make sure you set the 
"VMWARE_VERSION=workstation-17.5.0" in the patch script (step3) to match 
your version




On 1/11/24 16:39, Barry wrote:
>
>> On 11 Jan 2024, at 02:43, Frank Bures <buresf(a)gmail.com&gt; wrote:
>>
>> You would not have to reinstall.  Once you convert your VMWare disks to QEMU disk
and configure the QEMU virtual machine, it just boots the same way as it used to in
VMWare.  That's the beauty of it.
> Yes this works well. I converted a windows 10 successfully.
> Just remember that you also need to copy the Ethernet address from the vmware xml
config file into the qemu config. Easy to do with libvirt manager.
>
> Last few days I managed to upgrade the windows 10 image to windows 11.
> A little tricky to convert from MBR to GPT then boot under UEFI and secure boot, but
doable.
>
> Barry
>
>
> --
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Frank Bures]

On 2024-01-12 11:28, Sbob wrote:
>  I am running Fedora 39 (Kernel 6.6.9-200) and VMWare workstation Pro
> 17.5.0
>  
>  
>  Here is what I do every time there is a new kernel:
>  
>  1) run the dnf update and get the new kernel installed
>  
>  
>  2) reboot
>  
>  
>  3) open a terminal as root and run this script:
>  
>  #!/bin/bash
>  
>  VMWARE_VERSION=workstation-17.5.0
>  TMP_FOLDER=/tmp/patch-vmware
>  rm -fdr $TMP_FOLDER
>  mkdir -p $TMP_FOLDER
>  cd $TMP_FOLDER
>  git clone https://github.com/mkubecek/vmware-host-modules.git
>  cd $TMP_FOLDER/vmware-host-modules
>  git checkout $VMWARE_VERSION
>  git fetch
>  make
>  sudo make install
>  sudo rm /usr/lib/vmware/lib/libz.so.1/libz.so.1
>  sudo ln -s /lib/x86_64-linux-gnu/libz.so.1
>  /usr/lib/vmware/lib/libz.so.1/libz.so.1
>  sudo /etc/init.d/vmware restart
>  
>  
>  There are always a couple of not found errors but the compile succeeds
>  
>  
>  4) I start VMWare as root by running this script:
>  
>  
>  #!/bin/bash
>  
>  /etc/init.d/vmware restart
>  
>  vmware&
>  
>  
>  
>  At this point VMWare should start but it will not actually start a VM 
>  throwing an error about vmmon if I remember correctly
>  
>  
>  5) Stop VMWare
>  
>  
>  6) reboot once again
>  
>  
>  7) log in again and as root start VMWare with the start script again (step 
>  4) and presto, everything works as expected
>  
>  
>  Note: as you upgrade VMWare versions make sure you set the 
>  "VMWARE_VERSION=workstation-17.5.0" in the patch script (step3) to match 
>  your version
>  
>  
>  
>  
>  On 1/11/24 16:39, Barry wrote:
> >
> >> On 11 Jan 2024, at 02:43, Frank Bures <buresf(a)gmail.com&gt; wrote:
> >>
> >> You would not have to reinstall.  Once you convert your VMWare disks to 
> >> QEMU disk and configure the QEMU virtual machine, it just boots the same 
> >> way as it used to in VMWare.  That's the beauty of it.
> > Yes this works well. I converted a windows 10 successfully.
> > Just remember that you also need to copy the Ethernet address from the 
> > vmware xml config file into the qemu config. Easy to do with libvirt 
> > manager.
> >
> > Last few days I managed to upgrade the windows 10 image to windows 11.
> > A little tricky to convert from MBR to GPT then boot under UEFI and 
> > secure boot, but doable. 
IMHO, it's too many hoops to jump through.  Give me QEMU any day :-)

Cheers
Frank



-- 

<listfrank1(a)gmail.com&gt;

[Frank Bures]

On 2024-01-10 19:06, Samuel Sieb wrote:
>  On 1/10/24 15:36, Sherman Grunewagen via users wrote:
> > Does anyone have VMware Workstation Pro 17.5.0 running with any of the
> > later 6.6.X kernels?
> >
> > I'm having a hard time getting it to run with a Fedora 38
> > installation.  I'm fully updated as of 2 days ago, including the 6.6.9
> > kernel.  When I try to start Workstation directly after VMware
> > installation I get a popup saying that the kernel-headers package for
> > kernel-6.6.9 is missing and so it can't build some modules. the problem 
> > is that
> > the kernel-headers package for 6.6.9 is missing from Updates. The latest 
> > package is
> > for 6.6.3.
>  
>  That sounds like a broken build system.  The kernel-headers package doesn't 
>  get updated for every kernel if they haven't changed.
>  
>  Have you tried using qemu/kvm instead? 
I have had a bad experience with F39 and VMWare Player.  I've made it work 
initially using above mentioned modules, but it was highly unstable.  The 
machine would randomly stop crucial services, announce CPU core errors and 
eventually the only way out would be a hard reset, just to have to whole 
thing repeated in a day or two.

I converted my VMWare disks into QEMU disk and I've been running QEMU every 
since.  Rock solid, no problems with kernel modules and frequent kernel 
updates.

I'd highly recommend to go this way.  The choice is yours, of course.

Cheers
Frank

-- 

<listfrank1(a)gmail.com&gt;

[ja]

On Wed, 2024-01-10 at 21:40 -0500, Frank Bures wrote:
>  On 2024-01-10 19:06, Samuel Sieb wrote:
>  > On 1/10/24 15:36, Sherman Grunewagen via users wrote:
>  > > Does anyone have VMware Workstation Pro 17.5.0 running with any of the
>  > > later 6.6.X kernels?
>  > > 
>  > > I'm having a hard time getting it to run with a Fedora 38
>  > > installation.  I'm fully updated as of 2 days ago, including the 6.6.9
>  > > kernel.  When I try to start Workstation directly after VMware
>  > > installation I get a popup saying that the kernel-headers package for
>  > > kernel-6.6.9 is missing and so it can't build some modules. the problem 
>  > > is that
>  > > the kernel-headers package for 6.6.9 is missing from Updates. The latest 
>  > > package is
>  > > for 6.6.3.
>  > 
>  > That sounds like a broken build system.  The kernel-headers package doesn't 
>  > get updated for every kernel if they haven't changed.
>  > 
>  > Have you tried using qemu/kvm instead?
>  
>  I have had a bad experience with F39 and VMWare Player.  I've made it work 
>  initially using above mentioned modules, but it was highly unstable.  The 
>  machine would randomly stop crucial services, announce CPU core errors and 
>  eventually the only way out would be a hard reset, just to have to whole 
>  thing repeated in a day or two.
>  
>  I converted my VMWare disks into QEMU disk and I've been running QEMU every 
>  since.  Rock solid, no problems with kernel modules and frequent kernel 
>  updates.
>  
>  I'd highly recommend to go this way.  The choice is yours, of course.
>  
>  Cheers
>  Frank 
I had host crashes with some kernels and just stayed with an older kernel.
The latest kernels are now working fine with WS 17.5.0
It was really a kernel problem not a VMware problem.
See
https://github.com/mkubecek/vmware-host-modules/tree/master

ja@meon ~ 1$ uname -a                                                                     
            
Linux meon.jaa.org.uk 6.6.9-200.fc39.x86_64

From my notes
2023_12_26-12.38
Must run mkubecek vmmon & vmnet scripts after every kernel update
DO NOT rely on vmware script even if it returns no errors!
Must download the matching mkubecek code after every new WorkStation release.
From INSTALL file:

As ja
Just Once for WS17.5.0 say
cd /global/db/sw/VMware_17/mkubeck_17.5.0
wget https://github.com/mkubecek/vmware-host-modules/archive/workstation-17.5....
tar -xzf workstation-17.5.0.tar.gz

For Every New kernel
cd /global/db/sw/VMware_17/mkubeck_17.5.0/vmware-host-modules-workstation-17.5.0
make clean
make
su
make install
systemctl restart vmware.service

John

[Roger Heflin]

On Thu, Jan 11, 2024 at 4:06 AM ja <ja(a)jaa.org.uk&gt; wrote:
>  I had host crashes with some kernels and just stayed with an older kernel.
>  The latest kernels are now working fine with WS 17.5.0
>  It was really a kernel problem not a VMware problem.
>  See
>  https://github.com/mkubecek/vmware-host-modules/tree/master
>  
That is not a kernel problem.  That is a problem with a 3rd party
module not working right with a new kernel.   Note that 3rd party
modules break all of the time because of kernel changes and as such
are best to avoid unless absolutely necessary.

And since vmware needs this 3rd party module to work I am going to
suspect that vmware is somehow funding the module (since no one else
would likely care), and since VMware needs this module to work then it
is a VMWare problem.

If there is any other way (KVM/QEMU) to work without a 3rd party
module I will take it.  3rd party modules are typically a few weeks
behind the current kernels (and sometimes never updated reliably) and
as such will break with new kernels.

[Jonathan Billings]

On Wed, Jan 10, 2024 at 03:36:32PM -0800, Sherman Grunewagen via users wrote:
>  Hello all.
>  
>  Does anyone have VMware Workstation Pro 17.5.0 running with any of the
>  later 6.6.X kernels?
>  
>  I'm having a hard time getting it to run with a Fedora 38
>  installation.  I'm fully updated as of 2 days ago, including the 6.6.9
>  kernel.  When I try to start Workstation directly after VMware
>  installation I get a popup saying that the kernel-headers package for
>  kernel-6.6.9 is missing and so it can't build some modules. the problem is that
>  the kernel-headers package for 6.6.9 is missing from Updates. The latest package is
>  for 6.6.3. 
Does the popup actually say that you need a newer kernel-headers
package?  Because we should provide feedback to VMWare that what
they're really asking for is a kernel-devel package for the running
kernel.  The kernel-headers package is just for compiling userspace
programs, and only is updated when there's an API change that affects
userspace.

I suspect that the "headers" part is coming from the Debian/Ubuntu
world, because I think their kernel source is in a linux-headers
package. 

-- 
Jonathan Billings <billings(a)negate.org&gt;

[Sherman Grunewagen]

On 11/01/2024 13.48, Jonathan Billings wrote:
>  On Wed, Jan 10, 2024 at 03:36:32PM -0800, Sherman Grunewagen via
> users wrote:
> > Hello all.
> >
> > Does anyone have VMware Workstation Pro 17.5.0 running with any of the
> > later 6.6.X kernels?
> >
> > I'm having a hard time getting it to run with a Fedora 38
> > installation.  I'm fully updated as of 2 days ago, including the 6.6.9
> > kernel.  When I try to start Workstation directly after VMware
> > installation I get a popup saying that the kernel-headers package for
> > kernel-6.6.9 is missing and so it can't build some modules. the problem is that
> > the kernel-headers package for 6.6.9 is missing from Updates. The latest package is
> > for 6.6.3.
>
>  Does the popup actually say that you need a newer kernel-headers
>  package?  Because we should provide feedback to VMWare that what
>  they're really asking for is a kernel-devel package for the running
>  kernel.  The kernel-headers package is just for compiling userspace
>  programs, and only is updated when there's an API change that affects
>  userspace.
>
>  I suspect that the "headers" part is coming from the Debian/Ubuntu
>  world, because I think their kernel source is in a linux-headers
>  package.
>  
Yes, the popup explicitly says that the 6.6.9 headers are needed (as I'm running
kernel-6.6.9).
Here's a screenshot of the popup:  <http://tinyurl.com/VMwarePop>;. (I don't
know how to make
hot links. :-))

-- Sherman

[Sherman Grunewagen]

On 12/01/2024 17.58, Sherman Grunewagen via users wrote:
>  On 11/01/2024 13.48, Jonathan Billings wrote:
> > On Wed, Jan 10, 2024 at 03:36:32PM -0800, Sherman Grunewagen via users wrote:
> >> Hello all.
> >>
> >> Does anyone have VMware Workstation Pro 17.5.0 running with any of the
> >> later 6.6.X kernels?
> >>
> >> I'm having a hard time getting it to run with a Fedora 38
> >> installation.  I'm fully updated as of 2 days ago, including the 6.6.9
> >> kernel.  When I try to start Workstation directly after VMware
> >> installation I get a popup saying that the kernel-headers package for
> >> kernel-6.6.9 is missing and so it can't build some modules. the problem is
> that
> >> the kernel-headers package for 6.6.9 is missing from Updates. The latest package
> is
> >> for 6.6.3.
> >
> > Does the popup actually say that you need a newer kernel-headers
> > package?  Because we should provide feedback to VMWare that what
> > they're really asking for is a kernel-devel package for the running
> > kernel.  The kernel-headers package is just for compiling userspace
> > programs, and only is updated when there's an API change that affects
> > userspace.
> >
> > I suspect that the "headers" part is coming from the Debian/Ubuntu
> > world, because I think their kernel source is in a linux-headers
> > package.
> >
>
>  Yes, the popup explicitly says that the 6.6.9 headers are needed (as I'm running
> kernel-6.6.9).
>  Here's a screenshot of the popup:  <http://tinyurl.com/VMwarePop>;. (I don't
> know how to make
>  hot links. :-))
>
>  -- Sherman 
Ha! To my surprise, the link text became a hot link.  I lucked out.  Nice list feature!

[Samuel Sieb]

On 1/12/24 18:00, Sherman Grunewagen via users wrote:
>  On 12/01/2024 17.58, Sherman Grunewagen via users wrote:
> > Yes, the popup explicitly says that the 6.6.9 headers are needed (as 
> > I'm running kernel-6.6.9).
> > Here's a screenshot of the popup:  <http://tinyurl.com/VMwarePop>;. (I 
> > don't know how to make
> > hot links. :-))
> >
> > -- Sherman
>  
>  Ha! To my surprise, the link text became a hot link.  I lucked out.  
>  Nice list feature! 
Nothing to do with the list.  That's your email client converting it.

[Dave Close]

Samuel Sieb wrote:

> Nothing to do with the list.  That's your email client converting
> it. 
Speaking of email clients modifying received messages ...

{This message was not written in HTML. If you are reading it as such,
 the presentation is dishonest and not what the author intended.}
-- 
         Dave Close, Compata, Irvine CA       [phone]
       dave(a)compata.com              dhclose(a)alumni.caltech.edu
     "Resentment is like drinking poison and then hoping it will
      kill your enemies." -- Nelson Mandela

[Tim]

On Fri, 2024-01-12 at 21:33 -0800, Dave Close wrote:
>  Speaking of email clients modifying received messages ...
>  
>  {This message was not written in HTML. If you are reading it as such,
>   the presentation is dishonest and not what the author intended.} 
Which I received base64 encoded, for reasons unfathomable.

-- 
 
NB:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the list.
 
The following system info data is generated fresh for each post:
 
uname -rsvp
Linux 6.2.15-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 16:51:53
UTC 2023 x86_64

[Patrick O'Callaghan]

On Sun, 2024-01-14 at 08:29 +1030, Tim via users wrote:
>  On Fri, 2024-01-12 at 21:33 -0800, Dave Close wrote:
>  > Speaking of email clients modifying received messages ...
>  > 
>  > {This message was not written in HTML. If you are reading it as
>  > such,
>  >  the presentation is dishonest and not what the author intended.}
>  
>  Which I received base64 encoded, for reasons unfathomable. 
AFAIK there's nothing wrong with that. It's plaintext in UTF-8, so
Base64 would be a reasonable encoding.

poc

[Dave Close]

Tim via users wrote:

> I wrote:
> > Speaking of email clients modifying received messages ...
> > 
> > {This message was not written in HTML. If you are reading it as such,
> >  the presentation is dishonest and not what the author intended.} 
> Which I received base64 encoded, for reasons unfathomable. 
I wonder what did that. It wasn't sent that way:
  Content-type: text/plain; charset="utf-8"
  Content-transfer-encoding: 8bit
-- 
         Dave Close, Compata, Irvine CA       [phone]
       dave(a)compata.com              dhclose(a)alumni.caltech.edu
    "Politics have no relation to morals." --  Niccolo Machiavelli

[Tim]

Tim:
> > Which I received base64 encoded, for reasons unfathomable.
Dave Close:
>  I wonder what did that. It wasn't sent that way:
>    Content-type: text/plain; charset="utf-8"
>    Content-transfer-encoding: 8bit 
These days, 8-bit mail ought to be able to traverse the internet
unscathed (not need encoding), but so many things decide that they
better re-encode it for reasons best known only to themselves.  The
SMTP server you posted through, a list mail server it went into, any
other servers before you received it...

But I didn't notice anything in that message that wasn't 7-bit, so even
less need to encode it.

-- 
 
uname -rsvp
Linux 3.10.0-1160.105.1.el7.x86_64 #1 SMP Thu Dec 7 15:39:45 UTC 2023 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.

[Patrick O'Callaghan]

On Sun, 2024-01-14 at 17:17 +1030, Tim via users wrote:
>  Tim:
>  > > Which I received base64 encoded, for reasons unfathomable.
>  
>  Dave Close:
>  > I wonder what did that. It wasn't sent that way:
>  >   Content-type: text/plain; charset="utf-8"
>  >   Content-transfer-encoding: 8bit
>  
>  These days, 8-bit mail ought to be able to traverse the internet
>  unscathed (not need encoding), but so many things decide that they
>  better re-encode it for reasons best known only to themselves.  The
>  SMTP server you posted through, a list mail server it went into, any
>  other servers before you received it...
>  
>  But I didn't notice anything in that message that wasn't 7-bit, so
>  even
>  less need to encode it. 
I suspect that saying it's UTF-8 would be enough. I doubt that any mail
server would bother scanning the content to see if it really needed
encoding.

poc

[Sherman Grunewagen]

On 12/01/2024 18.34, Samuel Sieb wrote:
>  On 1/12/24 18:00, Sherman Grunewagen via users wrote:
> > On 12/01/2024 17.58, Sherman Grunewagen via users wrote:
> >> Yes, the popup explicitly says that the 6.6.9 headers are needed (as I'm
> running kernel-6.6.9).
> >> Here's a screenshot of the popup:  <http://tinyurl.com/VMwarePop>;. (I
> don't know how to make
> >> hot links. :-))
> >>
> >> -- Sherman
> >
> > Ha! To my surprise, the link text became a hot link.  I lucked out. Nice list
> feature!
>
>  Nothing to do with the list.  That's your email client converting it. 
Ok, thanks. That would be Thunderbird 115.6.0.
E-mail is, like so many things, a mystery to me. :-)

[Jonathan Billings]

>  On Jan 12, 2024, at 20:59, Sherman Grunewagen via users
> <users(a)lists.fedoraproject.org&gt; wrote:
>  
>  On 11/01/2024 13.48, Jonathan Billings wrote:
> >> On Wed, Jan 10, 2024 at 03:36:32PM -0800, Sherman Grunewagen via users wrote:
> >> Hello all.
> >> 
> >> Does anyone have VMware Workstation Pro 17.5.0 running with any of the
> >> later 6.6.X kernels?
> >> 
> >> I'm having a hard time getting it to run with a Fedora 38
> >> installation.  I'm fully updated as of 2 days ago, including the 6.6.9
> >> kernel.  When I try to start Workstation directly after VMware
> >> installation I get a popup saying that the kernel-headers package for
> >> kernel-6.6.9 is missing and so it can't build some modules. the problem is
> that
> >> the kernel-headers package for 6.6.9 is missing from Updates. The latest package
> is
> >> for 6.6.3.
> > 
> > Does the popup actually say that you need a newer kernel-headers
> > package?  Because we should provide feedback to VMWare that what
> > they're really asking for is a kernel-devel package for the running
> > kernel.  The kernel-headers package is just for compiling userspace
> > programs, and only is updated when there's an API change that affects
> > userspace.
> > 
> > I suspect that the "headers" part is coming from the Debian/Ubuntu
> > world, because I think their kernel source is in a linux-headers
> > package.
> > 
>  
>  Yes, the popup explicitly says that the 6.6.9 headers are needed (as I'm running
> kernel-6.6.9).
>  Here's a screenshot of the popup:  <http://tinyurl.com/VMwarePop>;. (I don't
> know how to make
>  hot links. :-)) 
Ah, it doesn’t explicitly say “kernel-headers”. 

I realize it’s confusing, but the headers for any librarypackage in Fedora is called
$name-devel, so to maintain consistency, it’s a kernel-devel package. 

The kernel-headers are a subset of kernel headers that are used by glibc and related
packages to compile userland executables, not kernel modules. 

-- 
Jonathan Billings