New answers tagged

0

VirtualBox - convert RAW image to VDI dd if=/dev/sdb of=./sdb.raw To use it with VirtualBox we need to convert it to the VDI format: $ VBoxManage convertdd sdb.raw sdb.vdi --format VDI OR $ VBoxManage convertdd sdb.raw sdb.vmdk --format VMDK


1

Haven't tested this myself but this is how I have understood it to be possible. Live boot to server and mount big enough external hard drive where you can store image. Image server's hard drive: dd if=/dev/sdX bs=4k conv=noerror,sync of=/mount_point_of_extHDD/serverIMG.dd Then let's zero out unused blocks: file /path/to/serverIMG.dd Check startsector ...


1

Depending on the distribution, you might have to add your username to the VirtualBox group. usermod -a -G vboxusers myusername Additionally, according a similar Q&A on askubunt, you might have a corrupt ISO. In your case, I would guess it means a botched conversion to raw disk. Try searching on how to correctly do that procedure and repeat it, in ...


2

Check the permission on all the files involved, including the directories: ~/VirtualBox VMs, ~/VirtualBox VMs/MyTinyLinux, ~/VirtualBox VMs/MyTinyLinux/rawdiskonusb.vmdk, /dev/disk2. The directories need to be readable and traversable by your user (chmod +rx) and the image file and the raw disk need to be readable and writable (chmod +rw). You'll need to ...


0

Use kali 2016.1 rolling.It's far morebetter. You may go to settings>>display>>monitor>>choose your desktop size>>done need more??It's enough.


1

Did you check your /etc/network/interfaces config files ? Maybe you have several gateways as pointed here https://askubuntu.com/questions/304898/trying-to-configure-eth0-and-eth1-but-failed-to-bring-up-eth1. Anyway, tweaking that file a bit and playing with ifconfig can help you drag the problem out. Check the permissions also, I doubt it comes from there ...


1

A workaround to the situation appears to be to toggle the link state of the VM right after starting it, i.e. on the command line do: $ VBoxManage startvm <vmid> $ VBoxManage controlvm <vmid> setlinkstate1 off $ VBoxManage controlvm <vmid> setlinkstate1 on


1

open-vmware-tool is for running linux under VWMare. As you are using VirtualBox then you don't need it. If you remove it, then it cannot use the CPU. However, if you simply uninstall it with yum there is the possibility of it still running as it has already loaded. It might be worth rebooting the guest (CentOS) after you uninstall it, or alternatively ...


1

1) Disable the secure boot on your BIOS settings : Secure boot prevent unsigned modules to be loaded. 2) According to Virtualbox-wiki you need to install dkms module: Ubuntu/Debian users might want to install the dkms package to ensure that the VirtualBox host kernel modules (vboxdrv, vboxnetflt and vboxnetadp) are properly updated if the linux kernel ...


1

OpenBSD Requires hardware virtualization to be enabled. Versions 3.7 and later are supported. Guest Additions are not available yet. https://www.virtualbox.org/manual/ch03.html#guestossupport Shared clipboard With the Guest Additions installed, the clipboard of the guest operating system can optionally be shared ...


2

So you want to host a wordpress website, on kali linux, inside a virtualbox virtual machine, under a windows host? How many bad decisions does a man need to do to arrive in this situation? If you want an answer, http://www.howtogeek.com/122641/how-to-forward-ports-to-a-virtual-machine-and-use-it-as-a-server/ But if you want a real answer, I highly suggest ...


1

This configuration works but it's a bit messed up. The output of parted shows that you have just 2 usable partitions: 1 1049kB 256MB 255MB primary ext2 boot This is the boot partition. 2 257MB 107GB 107GB extended 5 257MB 107GB 107GB logical lvm This is the main (root) partition, using LVM, ...


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" ] ...



Top 50 recent answers are included