Tag Info

New answers tagged

0

Virtual box needs an extension pack for USB 2.0. The extension packs are located at https://www.virtualbox.org/wiki/Downloads My iPod was successfully recognized after I installed the extension pack. However, it still crashes when iTunes tries to talk to the iPod. Good luck!


2

I know, it is out date, but will be useful for anyone in the future. I have the same problem. It looks like VirtualBox can't provide such information without GuestAdditions installed inside guest VM. So, after installing GuestAdditions inside your guest RHEL, you can run VBoxManage list runningvms VBoxManage guestproperty get "dev-006" ...


1

Ideally dhclient-eth0 should work but as you don't have network connection its not possible to obtain ip address via dhcp you have few work work around if you just want internet on kali make network adapter on NAT this will give you internet access You can use BRIDGE MODE and gnome-network-manager to configure it via GUI by right clicking on network ...


0

Turns out I resized the base image vdi of my virtual hard drive. However, I was using a snapshot. I found the right vdi corresponding to the snapshot and resized that instead.


0

I got VGA passthrough working with an NVIDIA GTX 760 using KVM as a hypervisor with vfio-vga; I have never tried it with Virtualbox. It was a pain, but works well after getting the configuration right. KVM is just as convenient as Virtualbox for quick VMs from your desktop and you might consider it as another option. This thread has tons of information on ...


0

There is a great ArchWiki article for this: https://wiki.archlinux.org/index.php/Remastering_the_Install_ISO If you have a running linux system (preferrably arch) you can follow this guide straight, because of the use of chroot. On Windows I would recommend booting the Arch-Live-CD, and work from there. You might need 2 copys of the Live-CD, one for ...


0

Making a bootable ISO (live CD/DVD) is a different process from installing that distribution in a VirtualMachine (VM). If your host is non-arch (Windows, other Linux distribution), then first installing Arch in a VM and then using that VM to modify an existing live CD/DVD is a good way to work, as you can use the tools from the arch in VM to update the ...


0

Extract the installed windows and keep it safe somewhere as the size of exported machine is too small as compare to original, Even once you had installed windows yuo can take snapshot also of it and store it with snapshot


0

I would recommend you to use virtual machine. First, you get full Windows installation so you don't have to worry about compatibility issues. Second, you can backup you machine by just copying .vdi ot .vmdk or whatever format you'll use. Third, you can export your virtual machine and even upload to some cloud platforms like AWS and your machine won't ...


0

This is not going to work, as the new install will not have the license key automatically available. It used to be possible to convert an existing hardware based windows installation to a VMware┬╣ or VirtualBox VM, but Windows licensing seems to have gotten more restrictive over time (with hardware change tests). This explains how to do things, but it ...


0

This appears to work: # VBoxManage hostonlyif remove vboxnet0 This removes the host-only network. Then restarting VirtualBox brought the interface back and it works. For now. Honestly, I don't know if I've actually found the solution or if it's just dumb luck and it will stop working in a few minutes.


0

Hopefully you have found the solution by now. In case someone else stumbles across this, perhaps this will help: # yum install kernel-devel kernel-headers perl There are other dependencies for building the kernel modules, but those should be well documented. My specific problem (due to using the minimal install) was not having perl.


0

The upstream VirtualBox packages contain an init script that tries to detect your distribution. It isn't doing a good job on your system: it's looking for /etc/init.d/functions, which should be a Red Hat thing, on a Debian-based system. Since you're purging the package, rather than try to fix the script, it's simpler to work around it. Add the following ...


1

There is a typo in your config: auto eht1 It should be instead: auto eth1 So the interface just is not autoenabled. You can still see it with ifconfig eth1 and bring it up with ifconfig eth1 up


0

Sometimes if you reboot your computer, the computer don't see the new settings of interfaces. (I don't know why.) But if you "reboot" the eth1 with ifdown eth1 and after that ifup eth1.


-2

You need to install the required packages and reboot the system: apt-get install linux-headers-$(dpkg --print-architecture) virtualbox-dkms


1

The error message is clear. You have to install 2 packages : # apt-get update; apt-get install virtualbox-dkms linux-headers-amd64


0

Did it. $ vboxmanage registervm ~/VirtualBox\ VMs/origClone/origClone.vbox


1

Yes, it is possible. Use: $ vboxmanage showvminfo testvm | grep VRDE: VRDE: enabled (Address 0.0.0.0, Ports 3398, MultiConn: off, ReuseSingleConn: off, Authentication type: null)


1

What you describe as your "actual" IP address isn't, it is the IP address of your router, or anything else that got an IP address from your provider and acts as an intermediary for your computer to the internet. That is why your (windows) hosts provides an internal address as well. Your VirtualBox host gives out IP addresses in the range 10.x.x.x by default ...



Top 50 recent answers are included