I'd expect you should be able to remove the blacklisting after the vmware install to restore kvm support if you wish If you can successfully blacklist the kvm modules, then you should be able to run your vmware installer. Instead of unloading, you might be able to blacklist the kvm module(s) and then reboot (After which you can test for the modules if you wish). You'll have to reload it after your vmware install if you want KVM support So, the following describes unloading the module altogether. The installer is likely detecting that the KVM module is although it's saying that the module is which aren't the same. Based on what has been described, it seems that the vmware installer is throwing a misleading error. UnsatisfiedDependency: Component vmware-vmrc-app 10.0.1 has unsatisfied dependency: vmware-usbarbitrator>=17.0.0Įach is a different approach to addressing the same issue about the mysterious KVM module enabled. ResolveResults = Resolve(,, , db.database)įile "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/dependency.py", line 1416, in Resolveįile "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/dependency.py", line 383, in constructLinks IntegrityError: UNIQUE constraint failed: files.pathįile "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/transaction.py", line 478, in RunThreadedTransaction Top level exception handlerįile "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/transaction.py", line 430, in RunThreadedTransactionįile "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/transaction.py", line 78, in Runįile "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/common.py", line 138, in Showįile "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/core/install.py", line 385, in Executeĭb.files.Add(filePath, fileMtime,, uid)įile "/tmp/vmis.hgFT7G/install/vmware-installer/vmis/db.py", line 33, in decorator Installation failed, rolling back installation. Integrity Error: Adding file /usr/lib/vmware/setup/vmware-config with mtime 1508586231, fileType 0, and uid 8. destination /usr/lib/vmware/setup/vmware-config already exists, overwriting. Ignored execution error: No such file or directory when running command: Cannot use vmware-app-control to shut down open VMs, defaulting to fallback message.
destination /tmp/tmpENlohR/.installer/14.0.0/include/versions.py already exists, overwriting. destination /tmp/tmpENlohR/.installer/14.0.0/include/update.py already exists, overwriting. destination /tmp/tmpENlohR/.installer/14.0.0/include/initscript.py already exists, overwriting. destination /tmp/tmpENlohR/.installer/14.0.0/include/systemType.py already exists, overwriting. destination /tmp/tmpENlohR/.installer/14.0.0/_init_.py already exists, overwriting. Opening database file /etc/vmware-installer/database ['/tmp/vmis.hgFT7G/install/vmware-installer/vmware-installer.py', '-set-setting', 'vmware-installer', 'libconf', '/tmp/vmis.hgFT7G/install/vmwarĮ-installer/lib/libconf', '-install-component', '/tmp/vmis.hgFT7G/install/vmware-installer', '-install-bundle', '/home/hardy/Downloads/./VMware-Player-14.0.0-6661328.x86
Saying this, I have to confess that I have no idea what kind of integrity check this could be and why it fails.
The installation always did create a new usr/lib/vmware/setup/ vmware-config file successfully, but then fails with the next step, when the integrity is tested/checked. With respect to your rename/move suggestion: I did move all files in folder usr/lib/vmware/setup/ into some folder in my /home area (again and again). I was referred to that URL by my "VMware ESXi Embedded Host Client" - which is a VMware Flings tool, a browser-based alternative to the (Windows-only) vSphere client.īut to answer your question: No, I don't have vSphere Client nor vRealize Automation installed on my openSuse 42.3 Leap machine. Leaving a renamed file in the same directory is not a sure-fire way to disable the file. that file to another temporary location altogether, like /Documents. Have you, or do you still have either of these two other VMware products installed?Īlso, up a ways, all you did was to rename the file that was to be overwritten. Normally it's part of, and is invoked using either VSphere client or vRealize Automation. According to the vmrc documentation, it's unusual to install it by itself.
0 kommentar(er)
