First of all, download the Kali Linux ARM64 installer ISO image. Create Kali Linux Virtual Machine. Here is the error message Igot each time I tried to copy a file: "There was an error getting information about …"Once you’ve successfully installed the Parallels Desktop application on your Mac M1 computer, then follow the below steps to install Kali Linux on Apple Mac M1. Immediately after that, I found an annoying issue when tryingto drag and drop files from the host into the VM. The first thing I did (and I guess everybodydoes) was run an "apt-get update & apt-get dist-upgrade" toupgrade the system. Downloads: 0 This Week Last Update: See Project.So I downloaded the VMware image from the Kali Linux download page and ran it using VMware Fusion.Virtual Machines DocumentationTo install theVMware Tools, I selected "Reinstall VMware Tools" from the "Virtual Machine" menu (Iam using VMware Fusion 5.0.3 on Mac OS X, but the same procedure should apply on otherplatforms and versions).This automatically mounted a virtual CD containing the installation software.My next step would be tocopy the compressed file, untar it and run the installer (the version at thetime of writing was 9.2.2-893683). These images have the default credentials 'kali/kali'. VmwareTools InstallationKali Linux VMware & VirtualBox images are available for users who prefer, or whose specific needs require a virtual machine installation. Apparently, the VMwareTools needed to be upgraded and, believe me, it was not an easy task.
![]() ![]() Kali Linux Vmware Image Download The KaliI suspected that missing files mighthave been the issue.Tracing the system calls with strace I found the following: # apt-get install strace# strace '/usr/lib/vmware-tools/sbin32/vmware-modconfig-console' -validate-kernel-headers -k 3.7-trunk-686-pae "" -l "/usr/lib/vmware-tools".access("/lib/modules/3.7-trunk-686-pae/build/include/linux/version.h", F_OK) = -1 ENOENT (No such file or directory).With that, I'd discovered the issue: the file/lib/modules/3.7-trunk-686-pae/build/include/linux/version.h was missing.To fix it, I used this: # cd /lib/modules/3.7-trunk-686-pae/build/include/# ln -s /usr/src/linux-headers-3.7-trunk-686-pae/include/generated/uapi/linux/version.h linux/version.hAnd I was presented with the following after running vmware-config-tools.pl again:"Excellent," I thought, "it's fixed." In actuality, there was more work to do:Some of the services reported an error, and one in particular didnot start. I had to plunge further and find out which files the tool was calling. The first parameter of the getValidKernelHeadersPath()function is $kh_path and upon further review I found the code responsible for settingits value (line 6192): $gKernelHeaders = `$modconfig -get-kernel-headers $mcKverOpt $appLoaderArgs` I just added this code right after the line6192 in vmware-config-tools.pl to find out what the command actually is: print("$modconfig -get-kernel-headers $mcKverOpt $appLoaderArgs") As I expected, nothing happened. Looking at vmware-config-tools.plWhen I opened the file /usr/bin/vmware-config-tools.pl with my favorite editor and searched for the string "is not a valid path to," I found this at line 6152:Apparently, $kh_path was empty (""), and I needed to find outwhy. /vmware-install.plAfter answeringsome questions with the default options, I ended up with the following:I needed to dig deeper into the vmware-config-tools.pl code to understand what was going on. # tar xzvf VMwareTools-9.2.2-893683.tar.gz# cd vmware-tools-distrib/#. In that case, you would need to modifythe file vmware-tools-distrib/installer/services.sh in the VMware Toolsinstallation directory because it will overwrite/etc/init.d/vmware-tools. If you wantto re-run the whole installation with vmware-install.pl, the file/etc/init.d/vmware-tools will be overwritten. For more details, I opened the /etc/init.d/vmware-tools file to see whatlies at line 1088: local run_kver=`get_version_integer`The get_version_integer() function is defined as follows:As you can see above, the script gets the kernel versionnumber by running the "uname –r" command and parsing the resultstring.Running the command gave me this: # uname –r3.7-trunk-686-paeThe issue here is that the script is expecting a set of three numbers (kernel version, major revision and minor revision), but here theuname command only returns two numbers: the kernel version and the majorrevision (3.7).When the script called the kernel_version_integer() function,the calling parameter values were wrong: v1="3"v2="7-trunk-686-pae"v3=""Here is the kernel_version_integer() function definition: kernel_version_integer() Perfect! The services started successfully.Keep in mind that I ran vmware-config-tools.pl. Fixing /etc/init.d/vmware-toolsIt seems that the service initialization script also needed to be fixed. Load word for mac without add insI haven't tried the VMware Fusion 6.0 yet and don't know if these issues are still there, but I'm sure you will have to adapt the fixes according to the errors you may find.I hope this post will be useful and will save you some time.But remember, debugging basics are important, and you may have to repeat the process for the next kernel or VMware upgrade.
0 Comments
Leave a Reply. |
AuthorRhonda ArchivesCategories |