New answers tagged

0

Change the permissions in fstab back to the default. As a normal user: sudo apt-get update && sudo apt-get upgrade && sudo apt-get install build-essential module-assistant sudo m-a prepare Mount the Guest Additions CD using the VirtualBox Menu (sudo mount /media/cdrom) sudo sh /media/cdrom/VBoxLinuxAdditions.run If the error you noted ...


2

PLEASE NOTE If you already have the Debian 8 version of VirtualBox installed this may not work. If you need VirtualBox installed and working for other virtual images this may break that. You can manually install the wheezy versions of the required packages. Download the following .debs for your architecture: libgsoap2 virtualbox virtualbox-fuse Use ...


1

You are not booted in EFI-mode. Can you disable Secure Boot -- it could be falling back to "Legacy" mode in the absence of a correctly signed kernel image and bootloader. And if you have already disabled Secure Boot, this means that you motherboard do not allow UEFI. The reason why this step is vital is that Legacy boot use MBR and UEFI mostly use ESP. So, ...


0

Check the filesystem that hosts your sf_my_share directory. Seem like ls can't stat this directory, may be because of the the filesystem's mount options


1

The problem is caused by VBoxGuestAdditions_5.0.18, I believe the graphics driver is broken in it. Try to install VBoxGuestAdditions_5.0.16, that works just fine.


1

How I did this in Vagrantfile. For people searching ... ubuntu.vm.provider "virtualbox" do |virtualbox| virtualbox.name = "Ubuntu_1510_#{Time.now.getutc.to_i}" virtualbox.customize [ "storagectl", :id, "--name", "SATAController", "--controller", "IntelAHCI", "--portcount", "1", "--hostiocache", "on" ] ...


0

We are facing two issue in one question so I will address them one by one: Virtual Machine As this superuser question suggests, try to solve the problem with VirtualBox not recognizing your 64bit CPU. After you are able to create a 64bit VM Kali should install without problems. Hardware Installation To answer this question we need further information. I ...


2

You could boot it into single user mode (if you don't know how to do it, just Google it) then enter this command: mount -uw / (In some cases, this command varies from system to system, so you may have to try some other command to make the filesystem writeable.) Then type 'passwd' then type what you want 'the root password' to be (just make sure it's a ...


1

On Arch Linux, you could boot a live image of the OS, arch-chroot and then run passwd. Maybe you could do something similar on Linux Mint.


0

VirtualBox Guest Extensions Follow that link, find your version of VirtualBox and I normally use the ISO and manually mount the CDROM drive under Linux and perform the install. Never had luck installing from the EPEL


0

Check the permissions of your sf_my_share directory. If you have read but not execute permissions on this directory, then you have enough rights to list the files in that directory, but you can't actually use these files or get more detailed information about them.


0

I needed to install the following: yum install gcc kernel-devel The gcc is important too. After that I simply ran ./VBoxLinuxAdditions.run And after a reboot the whole functionality was there.


0

If bridged mode doesn't work due to it not being an open wi-fi access point then go with NAT and create a forwarding rule in the main virtualbox interface for the virtual machine


0

When booting tails i think there is option "more" where you can choose a root password for the session. Try to get a console and run dmesg.


0

My first thought is that it shouldnt take 30hrs to install and it might be a corrupt ISO. Have you tried downloading a new ISO and reinstall? If not, here are 3 conversations on the black screen issue that may help- http://www.linuxquestions.org/questions/debian-26/debian-wheezy-black-screen-on-launch-after-successful-install-4175475144/ and ...


1

Try running VBoxClient --clipboard and see if you can copy and paste from the client to the host and vv. If that works you might want to just add that command as a line to your ~/.bashrc. It doesn't hurt to be invoked multiple times, and I have not been able to convince Solus to use it from ~/.xinitrc as the log indicates. The video here, shows a clean ...


1

To make the console mode permanent, add a line to /etc/rc.conf: allscreens_flags="MODE_332" (substitute your desired mode number for 332 of course.)


-1

bash -x ./filename.filetype should work. It worked for me when I got permission denied as a root user.


0

Open gparted and create a new ext2 Primary partition labelled live-rw Boot from the usb Flash drive From the boot-menu press ESC to see the boot prompt and type live persistent All the changes that you make will be saved in the partition live-rw



Top 50 recent answers are included