Tag Info

New answers tagged

1

In Ubuntu - you may need to install the virtualbox-guest-x11 (sudo apt-get install virtualbox-guest-x11) and then start virutal box client (VBoxClient -all)


0

Had the same problem - I tried to uncheck the entire usb (1.1 and 2.0) before starting the guest. Then XP recognized the usb When XP booted and completed USB Driver install, you have to put the usb device through by selecting it in the "devices" tab in the machine menu which can be integrated when in the C View mode or center-down when Full view.


2

VBox_StopRestoreStart.sh #!/bin/bash if [ -z "$1" ]; then echo "Usage: $0 VMNAME_or_UUID" exit 1 fi set -x VBoxManage controlvm "$1" poweroff #enforce turnoff VBoxManage snapshot "$1" restorecurrent #retore state VBoxManage showvminfo "$1" | grep State #display state to ensure VBoxHeadless -s "$1" #run in headless mode in ...


1

I searched the same too as had the same issue sometime back. I could not find anything reliable (for free) but VirtualBox. You may use VMware workstation 10.0.3. But it is not free. You have to buy it. However you may download and test it free for 30 days. Link: Download VMware Workstation 10.0.3 for Linux On the same page, at right hand side, you may ...


0

It should be enough to run sudo gedit /etc/group then find vboxusers line and add to it's end Yours user name. After this reboot is suggested, but logging out or kill -9 -1 and logging in should be enough.


1

Found that Hyper-V needs to be disabled/uninstalled. You can disable Hyper-V without uninstalling it. Start a command prompt with administrator rights and execute the following command: // to disable hyper-v bcdedit /set hypervisorlaunchtype off // to enable hyper-v bcdedit /set hypervisorlaunchtype auto Both Operations require restarting your computer. ...


0

VirtualBox supports 64-bit guest operating systems, even on 32-bit host operating systems, provided that the following conditions are met: You need a 64-bit processor with hardware virtualization support (see Section 10.3, “Hardware vs. software virtualization”). You must enable hardware virtualization for the particular VM for which you want 64-bit ...


0

Guest Additions itself may have been causing an additional uninvited issue you were unaware of. The ticket for the issue can be found here https://www.virtualbox.org/ticket/12879 and has been resolved in Guest Additions 4.3.12 Guest Additions 4.3.10 has an incorrect symlink for which the workaround is to create a new symlink: sudo ln -s ...


0

Create a new virtual disk and attach it to the VM. You may then want to move "/home" onto that new virtual disk. If you choose to do that, you will obviously have to mount the new disk at /home. HTH!


3

Yes just click erase disk and then follow the instructions. If you're running on a Virtual machine then it is always going to install to the virtual disk.


9

Assuming you are installing on a virtual machine that is running on your host OSX system, the VM has no access to your host's hardware. It is running on a virtual drive that you created for it. So no, it will not affect your host and the Ubuntu installer has absolutely no knowledge of the host system. It is safe to answer OK.


0

I solved my problem . 1- shut down both VMs and recreate virtual network adapter . first for internet(NAT) second for internal network . 2- turn on VMs . delete both connection in network manager . 3-open /etc/network/interfaces 4-add these lines : auto eth0 iface eth0 inet static address 192.168.0.1 netmask 255.255.255.0 auto eth1 iface eth1 inet ...


0

Firstly, ensure that you haven't mounted the USB stick in Ubuntu itself. Also, just in case, the latest version of VirtualBox is actually 4.3.14, which you might consider upgrading to. But more likely, if you only enabled USB 2.0 after having installed Windows, you might have to remove and re-add the USB controller from the Windows Device Manager, as it ...


1

This answer to a related question explains that the difference between these disk images is that the "64-bit Mac (AMD64)" version forces BIOS-mode (rather than UEFI) booting to avoid lack of support for multi-catalog CDs in the EFI boot mode of Mac machines. So it sounds like I should be able to use either version, since the boot-time pseudo-firmware is ...


0

VirtualBox has very limited support for Mac guests, so I would suggest the AMD-64 version to prevent the possibility that some odd hardware emulation causes problems.


0

You are installing in virtual box so any of the above version is fine.but i suggest 64-bit mac because you are using mavericks.have fun with ubuntu


0

I ran into the same issue. You can try my solution : after increasing both the guest and video memory, my VM booted to the desktop.


1

If I run lspci on a LiveCD booted in VirtualBox I see a couple of devices which give it away: 00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest Service I haven't installed the Guest additions. If this is scripted, you could do something as ...


1

There are several modes in which you can connect to internet inside from a virtual machine. Easiest is using NAT. Select your Ubuntu virtual machine in virtual box manager and go to settings. Navigate to Network and select NAT as shown in the screenshot. When you open Ubuntu go to Network Connection and go to Wired tab and select your connection and ...


1

Take a snapshot From the Virtual Box GUI (Virtualbox Manager) we can easily take a snaphot from a running virtual machine by selecting Take Snapshot or pressing HOST+T: This will open a dialog to give in a sensible name and optionally a description of this snapshot: The snapshot will then be saved in the machine's directory (depending on the size of ...


0

Try to install the following packages in your VM: sudo apt-get install virtualbox-guest-dkms virtualbox-guest-utils virtualbox-guest-x11 Restart the VM and you should avoid the black screen.


1

The fix for 14.04 is indeed different, but not that different: sudo apt-get install linux-headers-generic build-essential dkms sudo apt-get remove --purge virtualbox-dkms sudo apt-get install virtualbox-dkms The install virtualbox-dkms command was actually failing applying the 13.10 fix. By fully purging the package things got back to normal.


0

id That will give you uid=1000([username]) gid=1000([username]) groups=1000([username]),10(wheel),18(dialout),497(plugdev) if vboxusers is missing in that then add usermod -a -G vboxusers [username] This should resolve


1

The VirtualBox guest additions provide clipboard integration between the host and a X11 GUI running in the guest. They don't provide clipboard integration with a Linux console guest (there is a feature request for this, but it's understandably very low priority, because very few people use that feature). If you want a comfortable interface inside the guest, ...


0

If your Ubuntu uses Unity, then it is natural Ubuntu runs very slow in Virtualbox. Ubuntu and Unity is very heavy, especially on low RAM. So the solution is vary, one of them is changing your Unity into another lightweigth user interface such as XFCE, LXDE, or even Openbox. How To Install XFCE How can i install XFCE along side unity? How To Install LXDE ...


0

Could you explain the situation better? Here is what I understand from your write-up. You have a Windows machine. You have installed some virtualization software on your Windows machine. You have created two "identical" virtual machines, each running some version of Ubuntu. Within each VM you have 3 interfaces: lo0 (obviously), eth0 and eth1. One of the ...


0

If there is not packet loss to the first hope (your router) that means that it's out of your PCs hands and the problem is somewhere up stream from your router. Not much you can do on a PC to effect how the packet will be handled after your router


2

Virtual Box guest additions are installed as kernel modules. To see whether guest additions are installed, and to get information on the version we can issue: modinfo vboxguest This will give an output similar to this: filename: /lib/modules/3.13.0-24-generic/updates/dkms/vboxguest.ko version: 4.3.10 license: GPL description: ...


1

Using a virtual machine, you will not be using a "wireless interface". Your host machine uses the wireless interface and the virtual machine accesses the internet through the virtual machine's virtual ethernet connection and so you should most likely focusing on the device "eth0". During installation, the network should automatically configure itself as ...


0

I think you may extend the permissions of /var/log/samba/: #chgrp "DOMAIN+domain users" /var/log/samba #chmod 770 /var/log/samba Look in /var/log/samba to see the log files. and total 16 is say that there are total 16 log files related to this in log/samba/... And one more thing..try to run below code testparm -s Hope this help full to you.. Best ...


1

The reason of the problem is that you have booted the 3.11 kernel while the dpkg-reconfigure expects a 3.13 kernel. That's why you get the message 'no suitable module for the running kernel'. Be sure to update your bootloader. In my case the bootloader is updated from another OS (Debian) and booting to that and do an 'update-grub' solved the problem.


1

You need to install the Guest Additions go to devices menu > select "install guest additions" after installation restart virtual system now select view menu and click "switch to full screen"


0

grep managed /etc/NetworkManager/NetworkManager.conf to see if network manager trying to DHCP an address and fails. On top of the whole wireless confusion sudo ifconfig eth0 192.168.1.1 only sets ip temporary (until you reboot or restart the service) you need to set static IPs in /etc/network/interfaces like this: auto lo iface lo inet loopback auto eth0 ...


0

MY SETUP Oracle Virtualbox v4.2.8 r83876 for Windows on a Toshiba laptop running Windows 7. Guest OS within Virtualbox is Lubuntu 13.10 (32-bit). SOLUTION I'm simply going to list the commands I ran that eventually resolved the issues (Screen resolution not using entire display, mouse roller not working, bidirectional copy and paste (clipboard) not ...


0

It seems, this deflect in guest additions is popular. There are plenty of threads/tickets filled for the issue. Closed & reopened again because same version may work for some but not for others. One related ticket: #12941 3D not working on Ubuntu 14.04. What worked for me: Upgraded VirtualBox to last stable release 4.3.12-93733 from: deb ...


0

Try with installing common grapics driver package: sudo apt-get install xserver-xorg-video-all


1

For those who want the NetworkManager approach, I just went through this, taking the tack mss suggested. There's a touch of information on the Debian wiki and full documentation of the options at the GNOME developer site. (From the RHEL7 docs, it does look like their version of nmcli has add support, so hopefully that'll make it in.) The dynamic IP is ...


1

man bash ... i.e. try to adapt your code to bash -c 'echo Hello!' Need to know more about bash? http://tldp.org has at least two guides om bash - they will take you from a novice to an advanced level.


0

Virtualbox.org has a very long answer to this question - it is not always easy, because your existing installation in dependant upon hardware which will not be present in the virtual machine. The hardware is not missing, but the concept of a virtual machine means that the hardware will be replace with emulations of hardware, probably different than what you ...


0

Run Oracle VB Select your VM on the LHS Settings -> Display - > Video tab, "Enable Features:" and check the Enable 3D Acceleration box Click OK


2

You have a list of VirtualBox networking modes in its Documentation. The one you need on both systems is Internal networking. You have to give it a name, you can create several networks in this mode. VirtualBox will connect all guests in the same internal network, so names must match on both virtual machines. The default should work right out-of-the-box. ...


0

Tf2 and steam are now on Linux, don't use Wine. I tried it and Tf2 works awesome on linux (on a laptop).


0

As mentioned in this question's answers: You should update to the latest VirtualBox and extension pack, and reinstall vbox addition. Everything works fine after it, tested minute ago. This is the correct way to fix this problem without losing functionality, although sometimes, disabling mouse integration is the only way to go.


0

You can try to find a suspected big file/folder by running this, it will tell you all files/folders sizes: du ~ -h|sort -r -n|less it will also sort so the biggest file/folder will go first at the top of your screen. And don't forget to clean the Trash/Rubbish Bin anyway.


0

On my guest I only ever did the sudo adduser myguestuser vboxsf, installed guest additions, installed the extension pack and then added a shared folder via the VirtualBox GUI with automount and full access. Never needed to do a mount. The host is then available via /media/sf_myguestuser (or similar path).


0

If you're having display troubles in the Virtual Machine, the first step should always be to try installing Guest Additions. See How do I install Guest Additions in a VirtualBox VM?


1

To install/configure SSH you should check out one of many guides you can find browsing the internet, this one for example. You can connect to your viritual machiene via SSH using the following command: ssh user@ip You will thereafter be prompted to enter your password. To be able to connect you need, as said, an IP. When connecting locally you have a ...


0

in Virtual Machine Settings/Audio I changed Host Audio Driver from ALSA Audio Driver -> to PulseAudio and sound became fine. No other changes to configuration (VirtualBox Guest Additions 4.3.12 (CentOS 6.5), by the way)


1

As @Takkat suggests, reinstall guest addtions after the kernel update sudo /etc/init.d/vboxadd setup sudo shutdown -r now .. then restart the VM. Now after running the script, the mount point succeeds. Ensure that you have dkms installed. sudo apt-get install dkms


0

As an aside, I'd recommend putting your swap on your HDD rather than your SSD - this is for two main reasons: 4 GB of a 24 GB drive is a large percentage. SSDs run best when you're using below a certain percentage of their storage (I think the number is around 80%) Lots of writes from the swap, which will likely lead to degradation of the hard drive faster ...



Top 50 recent answers are included