Kernel 6.5-rc - vmmon fails.. #202
Comments
|
confirmed |
|
Yes, I'm aware of this. My research so far indicates the whole function using |
|
there's a discussion I found http://rglinuxtech.com/?p=3157 but the proposed patch seems not complete .... |
|
Well, |
|
What I am humbly proposing is ... can you prettypleasewithacherryontop temporarily patch the code the way that the discussion is suggesting while searching for a better way ? Thank you for your time and effort :) |
|
vmmon.patch.txt – pte = pte_offset_map(pmd, addr);
#ifdef CONFIG_NET_RADIO include` |
|
vmmon.tar.zip I have applied the patch manually and it works |
|
First crude attempt: commit b049eda. Note that I still have only vague idea what the returned PFNs are used for so the get_user_pages flags are quite likely wrong. On the hand, I was able to build and load the module and run a quick test with a VM on top of a 6.5-rc7 kernel so I may be on the right track after all. TL;DR: use on your risk. :-) |
|
can confirm this on kernel 6.5.0-1. |
|
I got it working with your latest b049eda git no risk involved. latest mainline 6.5.0 no rc kernel compiled with make -j16 bindeb-pkg It was a bit of a hassle to get the latest vmmon-only and vmnet-only workstation-17.0.2-k6.5 |
|
FWIW, I just updated one of my opensuse TW test machines to TW build 20230911 and it is using kernel 6.5.2.1 and I'm seeing the same issue. Here's the compile log in case it has other info that will help: AppLoader] GLib does not have GSettings support. |
|
I had also posted this issue on the VMware Forum for the Tech Preview (W/S 18), and just received the following suggested fix, from comphilip: In vmmon-only/include/pgtbl.h, replace pte_offset_map with pte_offset_kernel I have tested this briefly with kernel 6.5 and the Tech Preview, and also with 6.5.3 and 6.6-rc1 and the standard 17.0.2 patchset (not the tmp version) and this compiles OK and seems to work.. |
|
I really don't like the trick with |
This workaround appears to work for me as well running OpenSUSE Tumbleweed with kernel 6.5.3-1. |
|
is it working Python def download_patch(): subprocess.run(["wget", "https://raw.githubusercontent.com/vmware/open-vm-tools/main/patches/vmmon-only/include/pgtbl.h.patch"]) def unzip_patch(): subprocess.run(["unzip", "patch_file.patch"]) def apply_patch(): subprocess.run(["patch", "-p1", "<", "patch_file.patch"], cwd="/lib/modules/6.5.0-kali1-amd64/build/") def compile_kernel(): subprocess.run(["make", "-j", str(subprocess.check_output(["nproc"]).decode("utf-8"))], cwd="/lib/modules/6.5.0-kali1-amd64/build/") def install_kernel(): subprocess.run(["sudo", "make", "modules_install"], cwd="/lib/modules/6.5.0-kali1-amd64/build/") if name == "main": |
This works for me: Workstation pro 15.5.7 build-17171714 Thanks! |
|
This is very good Workstation pro: 17.0.2 Thanks |
|
Wow lots of recent traffic here, just shows how in demand this repo is. Also using the patch at b049eda I got it working.... Debian 12 with kernel 6.5.0-1-amd64 using vmplayer 17.0.2 Thanks a lot for maintaining this repository. It would be terrifying to update kernels otherwise. |
|
This works on 6.5.0-kali1-amd64 / Debian 6.5.3-1kali1 |
|
Pushed to all active branches, together with some minor hacks for 15.5.7, 14.1.7 and 12.5.9. Everything should build and work up to kernel 6.6-rc3 now. Closing. |
|
Confirmed working on physical machine with Linux fedora 6.5.5-200.fc38.x86_64 |
So what exactly do I have to do? I follow the normal procedure below, I get the latest from Kube's repo and it didn't work. Could I be getting a wrong version somehow. It seems it would be incorporated into the repo? I am afraid to re-install the 6.5.4 kernel as I have to be able to run VMware...Am I missing something stupid?
tar -cf vmmon.tar vmmon-only |
you wanna be sure you are not using the previous folder. Basically before to issue the sequence of commands, be sure that the tar you are downloading is the one you are executing, in my case initially i had a previous patch saved as tar, and the one i downloaded called out a "-1" at the end. So verify that in the folder (would be in home) you don't have a previous copy, and after run the command |
|
Sometimes you hope to be wrong... this is how VMware addressed the |
|
Fixes based on the comment: cd /tmp
git clone https://github.com/mkubecek/vmware-host-modules
cd vmware-host-modules
git checkout 'tmp/workstation-17.0.2-k6.5' # change the branch name according to your version
make
sudo make installUsing vmware-modconfig tar -cf vmnet.tar vmnet-only
tar -cf vmmon.tar vmmon-only
sudo mv vmnet.tar /usr/lib/vmware/modules/source/
sudo mv vmmon.tar /usr/lib/vmware/modules/source/
sudo vmware-modconfig --console --install-allRestart vmware service just in case sudo /etc/init.d/vmware restartNow open vmware and it should open normally: vmware |
|
@xevilstar You are a life saver These zip files saved me! Thank you so much. I would like to ask you how you did this but I can't contact you via github. If you read this can you email me guitarnut at yahoo dot com I really appreciate this. I don't know why it isn't posted with the original downloads. I downloaded the latest from Kubecek and it still doesn't work. I saw your zip files and downloaded them instead and magically I am back up and running in VMware. I would like to know how I can avoid this in the future... |
Hey dude... This really worked for me... |
|
@mkubecek This now also fails since roughly kernel Just seen, that this had already been reported: issue #244 (duplicate). Update: It builds with the current kernel to: The result still has warnings: Also "Could not open /dev/vmmon" ... |
|
Thank you for the heads up. I will backup my machine and disable updates.
When my VMWare goes down I can't do anything. I wish VMWare was more
committed to the product but thank god Kukecek has our backs!
…On Thu, Jun 6, 2024 at 9:27 AM Martin Zeitler ***@***.***> wrote:
This now also fails with kernel 5.14.0-427.18.1.el9_4.x86_64.
It's just the same, except that it also complains about: CrossPage_CodeEnd():
can't find starting instruction.
make -C vmmon-only
make[1]: Entering directory 'vmware-host-modules/vmmon-only'
Using kernel build system.
make -C /lib/modules/5.14.0-427.18.1.el9_4.x86_64/build/include/.. M=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[2]: Entering directory '/usr/src/kernels/5.14.0-427.18.1.el9_4.x86_64'
CC [M] vmware-host-modules/vmmon-only/linux/driver.o
CC [M] vmware-host-modules/vmmon-only/linux/driverLog.o
CC [M] vmware-host-modules/vmmon-only/linux/hostif.o
CC [M] vmware-host-modules/vmmon-only/common/apic.o
CC [M] vmware-host-modules/vmmon-only/common/comport.o
CC [M] vmware-host-modules/vmmon-only/common/cpuid.o
CC [M] vmware-host-modules/vmmon-only/common/crosspage.o
vmware-host-modules/vmmon-only/common/crosspage.o: warning: objtool: CrossPage_CodeEnd(): can't find starting instruction
CC [M] vmware-host-modules/vmmon-only/common/memtrack.o
CC [M] vmware-host-modules/vmmon-only/common/moduleloop.o
CC [M] vmware-host-modules/vmmon-only/common/phystrack.o
CC [M] vmware-host-modules/vmmon-only/common/sharedAreaVmmon.o
CC [M] vmware-host-modules/vmmon-only/common/statVarsVmmon.o
CC [M] vmware-host-modules/vmmon-only/common/task.o
CC [M] vmware-host-modules/vmmon-only/common/vmx86.o
CC [M] vmware-host-modules/vmmon-only/bootstrap/bootstrap.o
CC [M] vmware-host-modules/vmmon-only/bootstrap/monLoader.o
CC [M] vmware-host-modules/vmmon-only/bootstrap/monLoaderVmmon.o
CC [M] vmware-host-modules/vmmon-only/bootstrap/vmmblob.o
LD [M] vmware-host-modules/vmmon-only/vmmon.o
MODPOST vmware-host-modules/vmmon-only/Module.symvers
ERROR: modpost: "__pte_offset_map" [vmware-host-modules/vmmon-only/vmmon.ko] undefined!
make[3]: *** [scripts/Makefile.modpost:134: vmware-host-modules/vmmon-only/Module.symvers] Error 1
make[3]: *** Deleting file 'vmware-host-modules/vmmon-only/Module.symvers'
make[2]: *** [Makefile:1848: modules] Error 2
make[2]: Leaving directory '/usr/src/kernels/5.14.0-427.18.1.el9_4.x86_64'
make[1]: *** [Makefile:117: vmmon.ko] Error 2
make[1]: Leaving directory 'vmware-host-modules/vmmon-only'
make: *** [Makefile:21: vmmon-only] Error 2
—
Reply to this email directly, view it on GitHub
<#202 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKG7EFF7YW46KMCLE57LMDZGBPUZAVCNFSM6AAAAAA222JW3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJSGQ4TEOJZGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
@hwimmer1 Sticking with the currently installed kernel version is probably the least effort, because downgrading all the kernel packages is quite a hassle. The mere problem is, that the RPM repository only holds the last four versions, which means this approach is only temporarily valid: https://unix.stackexchange.com/a/779213/110101 The problem is just, it also happens with |
|
I installed timeshift. Ubuntu forces an update by nagging. In the update I
don't usually see something labeled kernel but after the update I'm screwed
which is why i installed timeshift. I tested time shift in the research lab
but not my production machine. Hopefully i won't have to or kubecek will
have a VMware update. I'm seriously considering my next computer to be
windows based and run Ubuntu in a VM as opposed to the other way around.
Now that VMware made workstation free I'm assuming we'll see even less
support but i don't know what is less than zero and non-negative
hahahahaha.
…On Sat, Jun 29, 2024, 8:14 AM Martin Zeitler ***@***.***> wrote:
@hwimmer1 <https://github.com/hwimmer1> Sticking with the currently
installed kernel version is probably the least effort,
because downgrading all the kernel packages is quite a hassle:
https://unix.stackexchange.com/a/779213/110101
—
Reply to this email directly, view it on GitHub
<#202 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKG7EET3KWNKY7NENIHOJLZJ2QJVAVCNFSM6AAAAAA222JW3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGEZTANJWGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hi Hayden,
Another option you might consider is switching from VMWare to KVM.
I was a long time VMWare user but got tired of the constant issues.
I detailed my journey to switch to KVM in this comment which you might
find useful:
#228 (comment)
Now several months after that reply, I moved my other VM host machine to
KVM and have no plans to go back to vmware even with the new free vmware
pro.
Just my $0.02.
Joe
…On 6/29/24 10:19 AM, Hayden wrote:
I installed timeshift. Ubuntu forces an update by nagging. In the update I
don't usually see something labeled kernel but after the update I'm screwed
which is why i installed timeshift. I tested time shift in the research lab
but not my production machine. Hopefully i won't have to or kubecek will
have a VMware update. I'm seriously considering my next computer to be
windows based and run Ubuntu in a VM as opposed to the other way around.
Now that VMware made workstation free I'm assuming we'll see even less
support but i don't know what is less than zero and non-negative
hahahahaha.
On Sat, Jun 29, 2024, 8:14 AM Martin Zeitler ***@***.***>
wrote:
> @hwimmer1 <https://github.com/hwimmer1> Sticking with the currently
> installed kernel version is probably the least effort,
> because downgrading all the kernel packages is quite a hassle:
> https://unix.stackexchange.com/a/779213/110101
>
> —
> Reply to this email directly, view it on GitHub
>
<#202 (comment)>,
> or unsubscribe
>
<https://github.com/notifications/unsubscribe-auth/ABKG7EET3KWNKY7NENIHOJLZJ2QJVAVCNFSM6AAAAAA222JW3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGEZTANJWGU>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#202 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKAPGF5V7GD4VTBW5JOJDATZJ265RAVCNFSM6AAAAAA222JW3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGIYTANJUGQ>.
You are receiving this because you commented.Message ID:
***@***.***>
--
Regards,
Joe
|
|
Joe,.
I'm looking into this. This fall i may get an intern or student worker in
my lab to test it out. I tried to move to virtual box but it doesn't have
the same networking capabilities as VMware...at least not that I could
find. I currently have 8 different VMNets... can i setup multiple networks
in kvm?
(Virtual box suffers from some similar issues where an update of Ubuntu
breaks it...after an update it was broken and i didn't figure out why).
Thanks for the lead. That is is compatible with VMware (the virtual disk)
is important. With the broadcom thing I'm guessing we'll see less support
from VMware (not that we got any anyway) and wouldn't be surprised to see
the Linux version go away. My next machine will be Windows and I'll VM my
Ubuntu instead of the other way around.
…On Mon, Jul 8, 2024, 10:36 AM JoeSalmeri ***@***.***> wrote:
Hi Hayden,
Another option you might consider is switching from VMWare to KVM.
I was a long time VMWare user but got tired of the constant issues.
I detailed my journey to switch to KVM in this comment which you might
find useful:
#228 (comment)
Now several months after that reply, I moved my other VM host machine to
KVM and have no plans to go back to vmware even with the new free vmware
pro.
Just my $0.02.
Joe
On 6/29/24 10:19 AM, Hayden wrote:
> I installed timeshift. Ubuntu forces an update by nagging. In the update
I
> don't usually see something labeled kernel but after the update I'm
screwed
> which is why i installed timeshift. I tested time shift in the research
lab
> but not my production machine. Hopefully i won't have to or kubecek will
> have a VMware update. I'm seriously considering my next computer to be
> windows based and run Ubuntu in a VM as opposed to the other way around.
>
> Now that VMware made workstation free I'm assuming we'll see even less
> support but i don't know what is less than zero and non-negative
> hahahahaha.
>
> On Sat, Jun 29, 2024, 8:14 AM Martin Zeitler ***@***.***>
> wrote:
>
> > @hwimmer1 <https://github.com/hwimmer1> Sticking with the currently
> > installed kernel version is probably the least effort,
> > because downgrading all the kernel packages is quite a hassle:
> > https://unix.stackexchange.com/a/779213/110101
> >
> > —
> > Reply to this email directly, view it on GitHub
> >
> <
#202 (comment)
>,
> > or unsubscribe
> >
> <
https://github.com/notifications/unsubscribe-auth/ABKG7EET3KWNKY7NENIHOJLZJ2QJVAVCNFSM6AAAAAA222JW3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGEZTANJWGU
>
> > .
> > You are receiving this because you were mentioned.Message ID:
> > ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <
#202 (comment)>,
or unsubscribe <
https://github.com/notifications/unsubscribe-auth/AKAPGF5V7GD4VTBW5JOJDATZJ265RAVCNFSM6AAAAAA222JW3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGIYTANJUGQ
>.
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
--
Regards,
Joe
—
Reply to this email directly, view it on GitHub
<#202 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKG7ECMT3QVOCNDPXBVIYTZLKPWTAVCNFSM6AAAAAA222JW3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJUGI2TINJSHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I also looked at virtual box way back but decided against it. Yes, you can have multiple different types of networks with KVM. When I used VMWare I always used Bridged networking because I wanted all my VMs on the same network as the host and everything else. Out the box, by default KVM uses NAT ( just like VMWare defaults too ). You can use bridged networking with KVM but you have to manually configure it as it is not a selection like it was in VMWare. There are some basic articles out there which talk about how to do that but it is someone environment specific. KVM does offer one network option that doesn't appear in the other products which is to setup an Macvtap device for your VM. Similar to Bridged networking, the vm will appear on the local network and can be accessed by anything there with ONE EXCEPTION. When using macvtap, communication is not possible via the macvtap device between the HOST and the GUEST vm. As previously mentioned communication between the GUEST vm and OTHER GUEST vms and even other physical machines on the same network is fine, it is just communication between the HOST and guests using macvtap. macvtap is a simple configuration similar to the checkbox for bridged networking in vmware vs the more complicated ( but possible ) manual setup of bridged networking on the host. The reason for the limitation between HOST and GUEST using macvtap has to do with how it hooks into the networking stack. There is an article on the libvirt website which talks about that and which also provides a work around. If you use macvtap and need communication between the HOST and GUEST, then add a second network interface to the GUEST vm ( you can make it an isolated network just for the HOST and GUEST communication ) and then make sure that on the HOST the DNS for those guest machines resolves to the 2nd ip address instead of the first one ( which would be used by all the other guests and physical machines on that network ). I tried the manual bridge networking setup sometime last year and it worked but I went with macvtap for the simplicity in setup and just added an extra NIC to the guests where I needed HOST and GUEST communications. If you are cmdline oriented then KVM / QEMU is also nice because you can use the virsh command to do pretty much anything to the guest vm. There is also a service which can be setup which will automatically suspend and resume VMs when the host is shutdown ( which seems to work great ). Unlike VMware where you have an open window whenever a VM is booted, with KVM you can close the GUEST window and the virtual machine manager window ( list of all vms on the host ) so if you were not careful you might reboot / shutdown the host without doing a proper shutdown of the vms. I tended to always leave the guest window minimized for my vms so I didn't make the host reboot / shutdown mistake but it is nice and easy to setup that service to protect yourself. Any vms by default that were running when the host is shutdown / rebooted will be restarted with the host and you can also configure vms to always boot when the host boots. Another really nice feature of Virtual Machine Manager is that you can configure a libvirt connection over SSH to view and/or manage virtual machines which are on a different host machine. I have a headless server that is running KVM and has multiple vms and I manage those vms from my main desktop. When I was using vmware after that server went headless that was another issue I needed a solution for because although I could RDP into the headless server ( running openSUSE Tumbleweed ) if you tried to start a vmware guest there it would fail to start because there was no physical display. KVM does not have that issue and works fine to allow me to remotely connect to and run the VMs located there. My recommendation would be to copy your VMDK file ( like I did in the other post ) and test things out. That way if you have an issue you can easily boot the vmware vm from the original vmdk file. If you decide to switch though, I would recommend converting the vmdk files to qcow2 files ( which is trivial using qemu-img convert ). FWIW, I used Windows since the Windows 3.0 days and spent my working career ( 25 + years ) on very large networks in 1 of 3 main roles, a Database Administrator, Windows Administrator, and software developer ( mainly system / backend programming ). I originally started with a Windows Host but after building my openSUSE Tumbleweed Linux vm and moving my entire workload ( with 1 exception program ) to that VM it made no sense to me for Windows to be the host anymore. I now run that 1 exception workload in a Windows 10 VM and I will never go back to Windows full time. Linux is so much easier to manage and maintain AND some of the decisions MS continues to make with Windows are things that I don't want or desire. Linux leaves you in control. I cannot tell you how many times I was remotely connected to a customer website doing work that needed to run overnight that I was monitoring where Windows decided that it wanted to install updates and that the time was now outside my normal working ours and decided to install and reboot. Linux lets me determine when I want to install updates and when I want to reboot my machine. Just my $0.02 but I'll never go back. Hope that we helpful ! Joe |
|
Thank you for the detailed information. I have done some reading and it
seems a viable solution. I can't believe i never heard of this product
before.
…On Sat, Jul 13, 2024 at 4:39 PM JoeSalmeri ***@***.***> wrote:
@hwimmer1 <https://github.com/hwimmer1>
I also looked at virtual box way back but decided against it.
Yes, you can have multiple different types of networks with KVM.
When I used VMWare I always used Bridged networking because I wanted all
my VMs on the same network as the host and everything else.
Out the box, by default KVM uses NAT ( just like VMWare defaults too ).
You can use bridged networking with KVM but you have to manually configure
it as it is not a selection like it was in VMWare. There are some basic
articles out there which talk about how to do that but it is someone
environment specific.
KVM does offer one network option that doesn't appear in the other
products which is to setup an Macvtap device for your VM.
Similar to Bridged networking, the vm will appear on the local network and
can be accessed by anything there with ONE EXCEPTION.
When using macvtap, communication is not possible via the macvtap device
between the HOST and the GUEST vm. As previously mentioned communication
between the GUEST vm and OTHER GUEST vms and even other physical machines
on the same network is fine, it is just communication between the HOST and
guests using macvtap.
macvtap is a simple configuration similar to the checkbox for bridged
networking in vmware vs the more complicated ( but possible ) manual setup
of bridged networking on the host.
The reason for the limitation between HOST and GUEST using macvtap has to
do with how it hooks into the networking stack. There is an article on the
libvirt website which talks about that and which also provides a work
around.
If you use macvtap and need communication between the HOST and GUEST, then
add a second network interface to the GUEST vm ( you can make it an
isolated network just for the HOST and GUEST communication ) and then make
sure that on the HOST the DNS for those guest machines resolves to the 2nd
ip address instead of the first one ( which would be used by all the other
guests and physical machines on that network ).
I tried the manual bridge networking setup sometime last year and it
worked but I went with macvtap for the simplicity in setup and just added
an extra NIC to the guests where I needed HOST and GUEST communications.
If you are cmdline oriented then KVM / QEMU is also nice because you can
use the virsh command to do pretty much anything to the guest vm. There is
also a service which can be setup which will automatically suspend and
resume VMs when the host is shutdown ( which seems to work great ).
Unlike VMware where you have an open window whenever a VM is booted, with
KVM you can close the GUEST window and the virtual machine manager window (
list of all vms on the host ) so if you were not careful you might reboot /
shutdown the host without doing a proper shutdown of the vms.
I tended to always leave the guest window minimized for my vms so I didn't
make the host reboot / shutdown mistake but it is nice and easy to setup
that service to protect yourself. Any vms by default that were running when
the host is shutdown / rebooted will be restarted with the host and you can
also configure vms to always boot when the host boots.
Another really nice feature of Virtual Machine Manager is that you can
configure a libvirt connection over SSH to view and/or manage virtual
machines which are on a different host machine.
I have a headless server that is running KVM and has multiple vms and I
manage those vms from my main desktop.
When I was using vmware after that server went headless that was another
issue I needed a solution for because although I could RDP into the
headless server ( running openSUSE Tumbleweed ) if you tried to start a
vmware guest there it would fail to start because there was no physical
display.
KVM does not have that issue and works fine to allow me to remotely
connect to and run the VMs located there.
My recommendation would be to copy your VMDK file ( like I did in the
other post ) and test things out. That way if you have an issue you can
easily boot the vmware vm from the original vmdk file.
If you decide to switch though, I would recommend converting the vmdk
files to qcow2 files ( which is trivial using qemu-img convert ).
FWIW, I used Windows since the Windows 3.0 days and spent my working
career ( 25 + years ) on very large networks in 1 of 3 main roles, a
Database Administrator, Windows Administrator, and software developer (
mainly system / backend programming ).
I originally started with a Windows Host but after building my openSUSE
Tumbleweed Linux vm and moving my entire workload ( with 1 exception
program ) to that VM it made no sense to me for Windows to be the host
anymore.
I now run that 1 exception workload in a Windows 10 VM and I will never go
back to Windows full time.
Linux is so much easier to manage and maintain AND some of the decisions
MS continues to make with Windows are things that I don't want or desire.
Linux leaves you in control. I cannot tell you how many times I was
remotely connected to a customer website doing work that needed to run
overnight that I was monitoring where Windows decided that it wanted to
install updates and that the time was now outside my normal working ours
and decided to install and reboot.
Linux lets me determine when I want to install updates and when I want to
reboot my machine.
Just my $0.02 but I'll never go back.
Hope that we helpful !
Joe
—
Reply to this email directly, view it on GitHub
<#202 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKG7EEYOFOD7JARIPP2FG3ZMGF7BAVCNFSM6AAAAAA222JW3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXGA4TQMJRG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Sure no problem, glad it was helpful. Good luck with your evaluation of KVM. |
Tested with kernel.org Kernel 6.5-rc1 to rc3.. reproduced on different systems, and with standard Fedora39 version of 6.5-rc2..
.............................
LD [M] /tmp/modconfig-Dj3fJq/vmmon-only/vmmon.oMODPOST /tmp/modconfig-Dj3fJq/vmmon-only/Module.symvers
ERROR: modpost: "__pte_offset_map" [/tmp/modconfig-Dj3fJq/vmmon-only/vmmon.ko] undefined!
make[3]: *** [scripts/Makefile.modpost:144: /tmp/modconfig-Dj3fJq/vmmon-only/Module.symvers] Error 1
make[2]: *** [/usr/src/linux-6.5-rc3/Makefile:1984: modpost] Error 2
make[1]: *** [Makefile:234: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-6.5-rc3'
make: *** [Makefile:117: vmmon.ko] Error 2
The text was updated successfully, but these errors were encountered: