Tag Info

New answers tagged

0

Encountered a similar issue and the same fix worked for me. On my pc i get a blank screen and in VirtualMachine i get the force_addr=0xaddr error after upgrading from a workstation. Found the fix at: My computer boots to a black screen, what options do I have to fix it? Just hold Shift when starting to get into GRUB, press E to edit the entry, search for ...


2

First off, make sure you backup everything you've got on the Windows partitions. I would then suggest trying gparted. It might let you remove the existing Windows partitions and expand the Ubuntu partitions without losing any data (depending on how the partitions are laid out).


-1

use sudo cfdisk If you dont know how to use cfdisk this might help


0

check if hyper-v is activate on your windows host and desactivate it


0

So I finally found the answer to my own problem in /etc/bind/named.conf.local i forgot to add "/" in front of "etc". my way: zone "dirks.crtn" { type master; file "etc/bind/zones/dirks.crtn.db"; }; correct way: zone "dirks.crtn" { type master; file "/etc/bind/zones/dirks.crtn.db"; }; I feel kinda stupid, but at least I am able to resolve addresses ...


-1

Use "All distributions - run Installer" (bottommost entry of this list) instead of a deb or rpm package! This fixed the error for me (Ubuntu 14.10 + VirtualBox 4.3.26).


0

I have experienced the same problem Host: Ubuntu 14.10 (64-bit), Guest: Windows 7 (64-bit) Even with the virtualization turned on in host BIOS the CPU load was constantly around 40-50% in guest idle state What helped me was installing Guest Addition with Direct 3D support (you need to do that in safe mode) and turning on the host I/O Cache of the SATA ...


0

I have experienced the same problem. ⠀Host: Ubuntu 14.10 (64-bit) ⠀Guest: Windows 7 (64-bit) Even with the virtualization turned on in host BIOS the CPU load was constantly around 40-50% in guest idle state. What helped me was installing Guest Addition with Direct 3D support (you need to do that in safe mode) and turning on the host I/O Cache of the ...


0

I have experienced the same problem Host: Ubuntu 14.10 (64-bit), Guest: Windows 7 (64-bit) Even with the virtualization turned on in host BIOS the CPU load was constantly around 40-50% in guest idle state What helped me was installing Guest Addition with Direct 3D support (you need to do that in safe mode) and turning on the host I/O Cache of the SATA ...


1

Yes you can install a ssh server on the windows guest. Options range from cygwin and several ssh servers are available. See http://www.windowsnetworking.com/articles-tutorials/windows-server-2008/install-SSH-Server-Windows-Server-2008.html You can download cygwin here - https://www.cygwin.com/ When you run the installer (cygwin.exe) you may choose what to ...


0

So forwarding is working fine. Things in your configuration files do look a little odd to me. Note that I have never been able to make things work with $ORIGIN. I'm sure that somehow it does work, just not for me. For dirks.crtn.db try: $TTL 38400 @ IN SOA filtjener.dirks.crtn. webmaster.dirks.crtn. ( 1263527838 ; serial 10800 ...


2

In the BIOS I had to change the following settings Security > Execute Disable (set to On) Performance > Virtualization (set to On) Performance > VT for Direct I/O Access (set to On) Performance > Trusted Execution (set to Off) In my case first 3 i have already turned on, and what i had to turn off was Performance > Trusted Execution Thanks to ...


0

I think that vagrant is the way to go for a beginner. There's loads of documentation, and loads of 'boxes'(images) to get you started. https://docs.vagrantup.com/v2/getting-started/index.html Just do sudo apt-get install vagrant


1

I just want to share my solution as I just fixed same problem for me. I am using ubuntu 14.04 x64, however native instead of booting in virtualbox. Tl;dr: sudo dpkg --configure -a solved my problem. I tried manually booting using mount /boot/efi but it exited with error 32: mount :wrong fs type, bad option,bad superblock... It asked me to check dmesg | ...


0

I'm using Ubuntu 14.04 and I got the same error. I reduced the memory below 50% of the total memory. And now it works.


0

Boot into a root shell: How do I boot into a root shell? Then change the password for your user (ubuntu) sudo passwd <username> Or create a new user sudo adduser <username>


1

In case other people get to this question: For those using VirtualBox, it already can take care of this, only involves editing a file: # Contents of /etc/default/virtualbox # ... # ... # SHUTDOWN_USERS="foo bar" # check for running VMs of user 'foo' and user 'bar' # 'all' checks for all active users # SHUTDOWN=poweroff # SHUTDOWN=acpibutton # ...


1

Enable Intel (R) Virtualization Technology and Intel (R) VT-d Feature in BIOS settings.


0

After rebooting the system, uname -r yields v3.16.0-34-generic.


0

Running sudo apt-get install p7zip-full 7z x android-ndk-r10c-linux-x86_64.bin will extract the ndk.


0

Unfortunatelly you should turn off 3d acceleration. Don't know why, but just do it. It's solved same problem with my installation.


0

Networking has to be enabled on VirtualBox. Open VirtualBox, then go to: File>Preferences>Networking I didn't have time to fool around, so I just clicked the plus for NAT-networking and for Host-Only networking. After that I ran ./genymotion again and the screen popped up. Don't know what fixed it, but it's fixed, and that's all I did, cause the ...


0

This http://ubuntuforums.org/showthread.php?t=2250037 solution worked for me. Preferences + efi. Some vdi images can also be downloaded, but that bybass the difficulty. http://www.osboxes.org/xubuntu-14-10-images-released-vmware-virtualbox/


0

Before starting the virtual machine: In the VirtualBox main window click on your virtual machine in the left column. Then click Settings at the top of the window. Click Storage in the left hand column. On the Storage page, click on the CD icon in the center column (it should say Empty beside it). An new icon of a CD will appear at the right of the ...


0

After trying many different ISO's, different VM emulated hardware combinations, digging through VirtualBox logs, and addressing the OSX Crash Reporter error logs... I simply installed an older VirtualBox (4.2.x) and restarted my Mac which solved the problem.


0

You might have configured the wrong network interface in Controller's /etc/network/interfaces. Find the correct network interface name and modify /etc/network/interfaces, replacing eth1 with the correct interface name: auto eth1 iface eth1 net dhcp You might also want to remove one of the two stanzas in /etc/network/interfaces, either: auto eth0 iface ...


0

That is generally a non-fatal message as described here. If your virtual machine is not working, the cause is probably elsewhere.


0

Set all VM NIC to Bridge mode then they will communicate through switch only.


1

You can achieve your goal by bridging the virtual NIC of VM1 to eth1 and that of VM2 to eth2. Both settings are to be applied in the properties of the VMs on the host. Both VMs need IP addresses from your home network (easiest through DHCP)


0

Ok the problem could be that you may have installed package for different architecture from you OS architecture. To check which architecture is your OS, write in terminal: uname -a Result for 32-bit Ubuntu: Linux discworld 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 2011 i686 i686 i386 GNU/Linux whereas the 64-bit Ubuntu will show: ...


0

For linux host it can be done as follows. Open the os in virtualbox whose resolution you want to change and follow the following steps. sudo gedit /etc/fstab enter root password Change this line /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 **to** /dev/sr0 /media/cdrom0 udf,iso9660 ...


0

Please install samba in ubuntu for sharing access By typing sudo apt-get install samba And then go to network icon situated in (nautilus)home And add your host network by providing ip, hostname, and password


0

I was having similar problems with virtualbox-guest-utils virtualbox-guest-x11 error messages. Then found this. Did the three steps, restarted and the screen is perfect. I did sudo apt-get remove libcheese-gtk23, then sudo apt-get install xserver-xorg-core and finally sudo apt-get install -f virtualbox-guest-x11 . It solved problems for me.


0

I was having similar problems with virtualbox-guest-utils virtualbox-guest-x11 error messages. Then found this. Did the three steps, restarted and the screen is perfect. I did sudo apt-get remove libcheese-gtk23, then sudo apt-get install xserver-xorg-core and finally sudo apt-get install -f virtualbox-guest-x11. It solved problems for me.


0

It looks to me as a duplicate of Can't resolve windows domains in local network. .local is handled by mDNS (Avahi or Bonjour) before trying with regular DNS server. mDNS should resolve name in the form of machinename.local if it does not get it, it returns NOT FOUND. Where what you are using is anothermachine.mywindowsdomain.local. .local here is part of ...


0

I have a similar problem. I want to attach my USB key to my virtual machine. How do I get the "usbid" to enter in the command?


0

Select a virtual machine by clicking its name in the VirtualBox window Click the Machine menu at the top of the VirtualBox window, and click Settings Click the Storage category in the Settings window Right-click in the storage tree pane, and click Add Floppy Controller Right-click the Floppy Controller device, and click Add Floppy Device Click the Choose ...


1

Make sure you set up the DNS servers too. You can verify if your connection is alive at all by pinging any IP address instead of host name. Try: ping 8.8.8.8 That's an IP address of google DNS servers. If that can be reached it's almost for sure DNS configuration that's bad. To configure your static network you can use many tools that are available in ...


0

Virtualbox can be installed by simple sudo apt-get install virtualbox But before running this command you should sync canonical by software updater on Other option.


0

Jacob Vlijm's python script was very useful. I am sharing a shell script to do this if someone may find it useful. #!/bin/sh ls -d ~/.gconf/desktop/gnome/keybindings/*/ if [[ `echo $?` == 2 ]]; then shortCutNumber=0 else shortCutNumber=$((`ls -d ~/.gconf/desktop/gnome/keybindings/*/ | tail -c 3 | head -c 1`+1)) fi echo -e ...


1

This solution has worked just perfectly for me (Host OS: Ubuntu 14.04; Guest OS: Windows XP SP3): Select "PCnet-PCI II (Am79C970A)" at 'NAT'->'Advanced'->'Adapter Type'.


0

When you make your VirtualBox VM, make sure that the Hard Drive is set to SATA Slot 0, or IDE Slot 0, that may be causing this. Also install using the defaults from the CD, and it should not have a problem. If it says "No Root System", that means you need to go to the partition part of the installer and make a root partition SLASH / For example: / <-- ...


0

well by "erase and use the entire disk" it means the virtual hard disk created before proceeding with the installation xD not the Hos Computer actual HD ! Thanks to http://www.sevenforums.com/tutorials/130922-linux-install-windows-7-virtual-machine-using-virtualbox.html !(http://i.imgur.com/RHIDZb3.png?1)


0

To install virtualbox, download the .deb file from https://www.virtualbox.org/wiki/Linux_Downloads Select the architecture that best fits your machine. Once downloaded, open up terminal and and cd to the directory where you downloaded the file. Then, type sudo dpkg -i virtualbox-* and press ENTER. Let it run through the process. Once it's finished, pass ...


0

somewhere on the internet i found suggestion the issue is related to fused FS . so i reformatted the partition from NTFS to EXT4 then all the issues were gone and no more kernel panic


0

It seems that the program synaptic may help you: synaptic is a graphical package manager. To use synaptic root privileges are required (you will be asked for a password on launch). When launched you can navigate to File->Save Markings As... and select a destination for the package list. (Note: since synaptic is run as root the folder "Desktop" is ...


0

Ubuntu's packages that you download are stored in /var/cache/apt/archives. A thing that might work would be to use scp to copy the files over the internet (via SSH) to your VM machine, and then install them using gdebi using th: mkdir ~/Desktop/old-ubuntu-debs scp -r USERNAME@IP_ADDRESS:/var/cache/apt/archives/ ~/Desktop/old-ubuntu-debs/ cd ...


1

Prepare working environment:: $ mkdir ~/devel/lfs $ VBoxManage createhd --filename ~/devel/lfs/lfs.vdi --size 2000 --format VDI Get required packages:: $ sudo apt-get install qemu-utils $ sudo modprobe nbd max_part=16 Without max_part=16 I get error on Debian for later commands:: $ sudo partprobe /dev/nbd0 ...


1

The headers for the current running kernel were not found. If the following module compilation fails then this could be the reason. Building the shsared folder support module ... fail! That gives a clue. Install the headers for your kernel version: sudo apt-get install linux-headers-`uname -r`


0

I found an hack for this problem, I just took the Guest additions of latest VirtualBox and I installed it.It solved all my problems. :) Thank you



Top 50 recent answers are included