F25 was running fine; after upgrade to F26 my VMware was broken, now I have a VMware running with F26, which brings this:
"This host does not support "Intel EPT" hardware assisted MMU virtualization. This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor. Module 'CPUIDEarly' power on failed. Failed to start the virtual machine."
and the same machine runs the latest Win10 without problems(!)
this machine is an old HP wkst xw4600 with a Core2 Quad Q9300 CPU and 4 GByte RAM
Greetings, Walter
On 09/30/2017 11:38 AM, Walter H. wrote:
F25 was running fine; after upgrade to F26 my VMware was broken, now I have a VMware running with F26, which brings this:
"This host does not support "Intel EPT" hardware assisted MMU virtualization. This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor. Module 'CPUIDEarly' power on failed. Failed to start the virtual machine."
and the same machine runs the latest Win10 without problems(!)
this machine is an old HP wkst xw4600 with a Core2 Quad Q9300 CPU and 4 GByte RAM
Greetings, Walter
But you can still revert to installing vmware which was compiled for f25. Just uninstall vmware-f26 and install vmware-f25 and try it.
On 30.09.2017 19:48, JD wrote:
On 09/30/2017 11:38 AM, Walter H. wrote:
F25 was running fine; after upgrade to F26 my VMware was broken, now I have a VMware running with F26, which brings this:
"This host does not support "Intel EPT" hardware assisted MMU virtualization. This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor. Module 'CPUIDEarly' power on failed. Failed to start the virtual machine."
and the same machine runs the latest Win10 without problems(!)
this machine is an old HP wkst xw4600 with a Core2 Quad Q9300 CPU and 4 GByte RAM
Greetings, Walter
But you can still revert to installing vmware which was compiled for f25. Just uninstall vmware-f26 and install vmware-f25 and try it.
I tell you a secret, guest which vmware was installed before? and guess what it means "compiled for f25" ... and then guess how it was running ...
I wonder what a complete "purge" of VMWare and a complete fresh install from their site would do?...just curious...
EGO II
On Sat, Sep 30, 2017 at 2:42 PM, Walter H. Walter.H@mathemainzel.info wrote:
On 30.09.2017 19:48, JD wrote:
On 09/30/2017 11:38 AM, Walter H. wrote:
F25 was running fine; after upgrade to F26 my VMware was broken, now I have a VMware running with F26, which brings this:
"This host does not support "Intel EPT" hardware assisted MMU virtualization. This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor. Module 'CPUIDEarly' power on failed. Failed to start the virtual machine."
and the same machine runs the latest Win10 without problems(!)
this machine is an old HP wkst xw4600 with a Core2 Quad Q9300 CPU and 4 GByte RAM
Greetings, Walter
But you can still revert to installing vmware which was compiled for f25. Just uninstall vmware-f26 and install vmware-f25 and try it.
I tell you a secret, guest which vmware was installed before? and guess what it means "compiled for f25" ... and then guess how it was running ...
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 09/30/2017 10:38 AM, Walter H. wrote:
F25 was running fine; after upgrade to F26 my VMware was broken, now I have a VMware running with F26, which brings this:
"This host does not support "Intel EPT" hardware assisted MMU virtualization. This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor. Module 'CPUIDEarly' power on failed. Failed to start the virtual machine."
Did you change the version of VMware you are running? This looks like a change in VMware requiring certain features. There's a small possibility that it's a change in the Linux kernel, but that's not going to be specific to Fedora. Any distribution with a recent kernel would have the same problem.
and the same machine runs the latest Win10 without problems(!)
How is this relevant at all? Fedora is running fine on it too.
Do you have to use VMware? Have you tried using KVM/qemu?
HI there, I know the frustration and people around keep suggesting KVM/qemu and virtualbox. It like XY solution. Dont be mad with thus people. They just don't know that some people like me, need to use specific tools (vmware) for getting job done and don't use another alternative because I need to get my existing image running.
Maybe some people like me can help you? My last attempt are resulted failure with kernel module, even I posted here https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/...
I saw, the thread inside VMware official forum about the problems too, which fault come from VMware it self.
But recently with new update, it worked flawless for VMware Player 14.0.0 build-6661328 and VMware Workstation 14.0.0 build-6661328 Here a tweet about my success achievement https://twitter.com/RobbiNespu/status/914081821557583872 ,it just few hour ago.
There is automated tool by hhemied - https://github.com/hhemied/FixVMware for VMware workstation, plus here some changes if you need for VMplayer https://github.com/hhemied/FixVMware/issues/1#issuecomment-333295703
Get newer version of VMware (uninstall older version first, reboot, install new ones, reboot, check new VM working or not) and get new kernel. It should be work fine for now. If you still having problem, share you details from terminal output such kernel version, vmware version, journalctl -xe , output when run vm via terminal and any useful logs to help you in future.
On Sun, Oct 1, 2017 at 3:31 AM, JD jd1008@gmail.com wrote:
On 09/30/2017 01:20 PM, Samuel Sieb wrote:
How is this relevant at all? Fedora is running fine on it too.
Do you have to use VMware? Have you tried using KVM/qemu?
Not to mention VirtualBox.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 30.09.2017 22:57, Robbi Nespu wrote:
I saw, the thread inside VMware official forum about the problems too, which fault come from VMware it self.
But recently with new update, it worked flawless for VMware Player 14.0.0 build-6661328 and VMware Workstation 14.0.0 build-6661328
exact this release claimed for non existing CPU features ...
Here a tweet about my success achievement https://twitter.com/RobbiNespu/status/914081821557583872 ,it just few hour ago.
There is automated tool by hhemied - https://github.com/hhemied/FixVMware for VMware workstation, plus here some changes if you need for VMplayer https://github.com/hhemied/FixVMware/issues/1#issuecomment-333295703
this did the application part complete and the thing with vmmon.ko and vmnet.ko has to be adjusted with chcon ...
Get newer version of VMware (uninstall older version first, reboot, install new ones, reboot, check new VM working or not) and get new kernel.
exact this is the problem ..., 12.5.7 doesn't run without above's hack, and 14.0.0 doesn't run at all ...
On 10/01/17 01:38, Walter H. wrote:
F25 was running fine; after upgrade to F26 my VMware was broken, now I have a VMware running with F26, which brings this:
"This host does not support "Intel EPT" hardware assisted MMU virtualization. This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor. Module 'CPUIDEarly' power on failed. Failed to start the virtual machine."
and the same machine runs the latest Win10 without problems(!)
this machine is an old HP wkst xw4600 with a Core2 Quad Q9300 CPU and 4 GByte RAM
Greetings, Walter
Are you trying to use Fedora 26 as the Host O/S for VMware?
If so, did you note the list of Host O/S's that VMware supports?
Host Operating Systems Ubuntu 14.04 and above Red Hat Enterprise Linux 6 & above CentOS 6.0 and above Oracle Linux 6.0 and above openSUSE Leap 42.2 and above SUSE Linux 12 and above
So, why would you be upset with Fedora Project and not VMware?
On 01.10.2017 11:48, Ed Greshko wrote:
On 10/01/17 01:38, Walter H. wrote:
F25 was running fine; after upgrade to F26 my VMware was broken, now I have a VMware running with F26, which brings this:
"This host does not support "Intel EPT" hardware assisted MMU virtualization. This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor. Module 'CPUIDEarly' power on failed. Failed to start the virtual machine."
and the same machine runs the latest Win10 without problems(!)
this machine is an old HP wkst xw4600 with a Core2 Quad Q9300 CPU and 4 GByte RAM
Greetings, Walter
Are you trying to use Fedora 26 as the Host O/S for VMware?
yes ...
If so, did you note the list of Host O/S's that VMware supports?
Host Operating Systems Ubuntu 14.04 and above Red Hat Enterprise Linux 6& above CentOS 6.0 and above Oracle Linux 6.0 and above openSUSE Leap 42.2 and above SUSE Linux 12 and above
seems you're talking about the previous VMware release ... v14.0.0.0 is for F26 or up
So, why would you be upset with Fedora Project and not VMware?
what do you mean by that?
On 10/01/17 20:17, Walter H. wrote:
On 01.10.2017 11:48, Ed Greshko wrote:
On 10/01/17 01:38, Walter H. wrote:
F25 was running fine; after upgrade to F26 my VMware was broken, now I have a VMware running with F26, which brings this:
"This host does not support "Intel EPT" hardware assisted MMU virtualization. This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor. Module 'CPUIDEarly' power on failed. Failed to start the virtual machine."
and the same machine runs the latest Win10 without problems(!)
this machine is an old HP wkst xw4600 with a Core2 Quad Q9300 CPU and 4 GByte RAM
Greetings, Walter
Are you trying to use Fedora 26 as the Host O/S for VMware?
yes ...
If so, did you note the list of Host O/S's that VMware supports?
Host Operating Systems Ubuntu 14.04 and above Red Hat Enterprise Linux 6& above CentOS 6.0 and above Oracle Linux 6.0 and above openSUSE Leap 42.2 and above SUSE Linux 12 and above
seems you're talking about the previous VMware release ... v14.0.0.0 is for F26 or up
I looked here....
https://www.vmware.com/products/workstation-pro.html
Also, http://store.vmware.com/store?SiteID=vmware&Action=DisplayProductDetails...
VMware Workstation Pro runs on most 64-bit* Windows or Linux host operating systems:
Windows 10Windows Server 2016Windows Server 2012Windows Server 2008Windows 8Windows 7UbuntuRed Hat Enterprise LinuxCentOSOracle LinuxopenSUSESUSE Linux Enterprise Server
I do not see any mention of Fedora.
Where is your information from Vmware that they support F26 as a Host O/S?
So, why would you be upset with Fedora Project and not VMware?
what do you mean by that?
Simple. As far as I can tell, see the above link, F26 isn't supported as a Host O/S platform And even if they were you're talking about an application that isn't connected with the Fedora Project. So, Fedora Project has nothing to do with making sure a 3rd party app. works.
Now, since Vmware Workstation, that is what you have right, is a purchased product you should be opening a trouble ticket with them. I'm retired now, but the company I worked for used VMware products and we had trouble with them back in the RH5.0 days (we also bought and paid for Red Hat Support). We found them very responsible.
Like I said, please tell me where VMware lists Fedora as a supported platform.
On 10/01/17 21:34, Ed Greshko wrote:
Like I said, please tell me where VMware lists Fedora as a supported platform.
OK.... I finally found it....
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cm...
Well, they say they support it.... But it doesn't work for you. So, seems they should be the one to fix it. Don't you think?
Ed Greshko:
Like I said, please tell me where VMware lists Fedora as a supported platform.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cm...
about halfway down the page
On 10/01/17 21:55, katnip wrote:
Ed Greshko:
Like I said, please tell me where VMware lists Fedora as a supported platform.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cm...
about halfway down the page
Yes, I had indicated in a later reply that I finally found it. VMware didn't make it "easy".
Still, it is *their* product and if it fails to work they are the ones responsible for it.
If you buy a car and then purchase a sound system for it from a 3rd party you don't take the car to your dealership when it goes silent.
On 10/01/17 01:38, Walter H. wrote:
this machine is an old HP wkst xw4600 with a Core2 Quad Q9300 CPU and 4 GByte RAM
By any chance did you also note that according to the requirements of VMware....
CPU Requirements
64- Intel "Sandy Bridge" generation or greater
And,
Intel "Nahalem" and earlier based CPU's are not supported in this release.
I think your old CPU may fall into that category.