![]() ![]() The slider bar represents all of the memory installed in the host machine. Say "64-bit" and only see "32-bit", come talk to me.) Indicates your intended use so you can easily identify it later.)įor Version, select "Arch Linux (64-bit)". (Doesn't matter, but might be helpful to pick something that Probably work on other versions, though there may be slight differences.)ĭownload VirtualBox from the vendor website and The problem still persists.(The following instructions were written using VirtualBox 6.0.0 (Screenshots are from VirtualBox 6.0.18 r136238 on a Mac). Updated the wired adapter drivers (there are no updated version for the wireless one), disable the "offload" settings, I even disabled all network adapters (including VMware virtual ones), removed the network adapters from the VM, completetly disabled the network in the guest machine this time at another reinstall (didn't see the "starting network" message at boot). ![]() Should I try disable them and see if it helps? Regarding the "offload" settings I see 2: But, should I be looking drivers for both the wired and wireless adapters? I'm currently connected by wireless (the problem did occur when I was using the wired connection too). I'm going to look for driver updates in the NIC manufacturer website though. I never saw one single driver (update or current) for the laptop BIOS. LG sucks on that end, not ever they released driver updates, specially BIOS updates. But I can alwaus use qemu to convert the. I'm running VirtualBox at the moment but I would really prefer to use VMware, though I'm already in the middle of installing software and configuring the whole system. I'm not a VMware expert but I think this means that everything that was outputed to the log file was BEFORE the crash, and I'm not sure if that information is relevant to my problem.īut I don't mind creating the image again and post the necessary log file if you think it's useful. I rebooted, opened the log file and the last line was still 1701. I noticed that the last line was 1701, then I type "reboot" and the host crashed. I was kinda in a hurry to have Arch running because I need it for university and couldn't wait for someone to help out and risk myself missing the projects deadline.īut I don't the log would help, I mean, I opened the log when I was at the console, logged in, waiting for any command. ![]() Reason: removed the emoticon from the subject Please, somone, help me out fix this issue in VMware, I can't understand why it crashes the host system, there's no reason for that to happen. I installed VirtualBox just to test if the same thing happened and it didn't, it works fine on VirtualBox, but due to other issues, I can't swap to VirtualBox at the moment. I've been searching google for the past hours and couldn't find the cause and/or solution for the problem, this is driving me nuts. ", and after a few seconds, boom, host freezes.īy freezes I mean I have to press the power off button for a few seconds to turn off the computer and reboot (laptop, no reset button). Other times, I could type other things, like "ls", or "cd
" and then "cd.
Most of the times, I just type "reboot" and it freezes the host machine. I'm just there, in the console and it freezes everything without me doing nothing. ![]() I just installed Arch Linux in VMware Workstation 6.5 and after the first boot just right after the installation (meaning, nothing else but the base system was installed/configured) I can barely use the virtual machien without having the host freezing. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |