Wishing to test F12 final release, tried to install as guest on Virtualbox OSE/ Ubuntu 9.10. F12 installed text only and no X. Using 384Mb main and 16Mb video memory on 8Gb virtual hdd. Installed from tested DVD. F12 or Virtualbox? U9.10 guest install worked perfectly.
View 2 RepliesRunning VirtualBox 3.2.6 under some host OS (should be irrelevant which one, right?), I created a machine, intending to install Fedora 13 on it. Got the Fedora 13 Live CD iso image, and an 8.6 GB virtual hard drive, completely blank. I set the machine to boot off the Live CD image. The Live CD boots nicely and I get to its desktop. I open "Install to Hard Drive"...and nothing happens. No error message, zip, nada. Inspection of the system shows a series of odd file systems, but I have no clue what they are for and whether they're usable or not.
The sticky [URL] mentions that the blank virtual hard disk should be partitioned and formatted beforehand...So I did, using the Live CD's Disk Utility (Applications: System Tools: Disk Utility). Although the sticky states the small /boot partition should be ext2 or ext3, the Live CD installer proposes to reformat it as ext4. Shouldn't we have formatted it as ext4 right away, then? Also, the installer set the /boot partition's size to 524 MB, not 200 MB as recommended by the sticky.
OBSERVATION: This was not easy because VirtualBox sets the display to 800x600 at most, and the Disk Utility spills beyond those confines WITHOUT PROVIDING SLIDERS. It was sheer luck that the required buttons (create partition, format partition) were barely reachable (at the bottom edge of the screen). This is a serious problem, because increasing the VirtualBox display size can only be done *after* installation (see for instance[URL] - since this guest addition requires rebooting the guest OS, it probably won't stick to the Live CD).
Once those two partitions are prepared and the virtual machine rebooted, "Install to Hard Drive" works as expected.
OBSERVATION: It is absolutely inexcusable that the Live CD installer (Anaconda?) does not propose to do this partitioning and formatting for the user. It is even more inexcusable that it should fail without giving any feedback whatsoever to the user.
Aside: VirtualBox's guest additions does not work correctly (for 3.2.6 anyway). The Devices: Install Guest Additions menu merely mounts a CD image VBOXADDITIONS_3.2.6_63112) without any feedback (expected feedback because the menu ends with an ellipsis). The CD, once opened, has an Open Autorun Prompt button...which fails to do anything. Manually running autorun.sh also fails. I had to manually invoke VBoxLinuxAdditions-x86.run from a terminal to get anywhere. Even then I was unable to go higher than 1024x768.
So I decided to build a server using two HDDs and after checking the net I decided to go with Software RAID.Before I mess around and go ahead and buy two 500 GB HDD, I decided to try it out first in virtual box.(my system is F13 64bit with 4GB)
I set up a virtual machine with 2 X 10GB HDD.Mount the live CD (f13 32bit).Run regular install > choose custom layout and do as follows: SDA & SDB will both have Software RAID 500 MB and another software RAID of about 9500 MB I will have md0 /boot (sda1 & sda2 = 500 MB) And another md0 having LVM group loaded with / + SWAP I choose to install boot loader on md0 the first time and I receive the following error when I boot from HDD: FATAL: INT18: BOOT FAILURE I tried installing boot loader on sda same thing.
I am trying to take a look at Fedora for the 1st time and usually like to have a good tryout of a distro in VirtualBox.
Firstly, the live cd image boots up fine and seems to work ok except for a Kernel crash at the beginning of the gnome session, but it does enable basic usage within the live system.
But, when trying to do an actual hd install (still within VBox) Fedora 14 just keeps on crashing the VBox??, every install attempt just aborts, I have given the virtual machine a 20gb virtual hd, 2gb ram, 128mb video ram and have not applied any "unusual" extra settings. All versions of Ubuntu, Mint and PCLinuxOS work flawlessly within VBox.
Has anyone else tried installing into VirtualBox here?? (not just running the live environment)
I've wasted a good few hours with this, is it just that some distros dont like VirtualBox or is this indicative of what Fedora would be like on a real non virtual install??
ps, I have the latest VirtualBox fully updated and a flawless host (Mint 9), and perhaps I should add that I'm not a Linux expert and have only been using Linux for just under a year now.
I'm trying to get a fedora guest running reliable smp under VirtualBox 3.0.6. The VirtualBox manual says "Some Linux distributions, for example Fedora, ship a Linux kernel configured for a timer frequency of 1000Hz. We recommend to recompile the guest kernel and to select a timer frequency of 100Hz." So I tried recompiling the kernel. Being a responsible lad, when it came to setting the kernel specs:
Code:
# Polite request for people who spin their own kernel rpms:
# please modify the "buildid" define in a way that identifies
# that the kernel isn't the stock distribution kernel, for example,
# by setting the define to ".local" or ".bz123456"
#
# % define buildid .local
%define buildid .rim_for_vbox
I've successfully built and installed kernel, headers and firmware:kernel-2.6.30.5-43.rim_for_vbox.fc11.x86_64.rpm
kernel-firmware-2.6.30.5-43.rim_for_vbox.fc11.x86_64.rpm
kernel-headers-2.6.30.5-43.rim_for_vbox.fc11.x86_64.rpm
The system is working fine (well, so far). But trying to install the VirtualBox Guest Additions kernel add-ons still gives me
Please install the build and header files for your current Linux kernel. The current kernel version is 2.6.30.5-43.rim_for_vbox.fc11.x86_64. I'm pretty sure this is because my kernel doesn't match the development packagekernel-devel-2.6.30.5-43.fc11 (x86_64). So the key question is, how on Earth do I create a development package to match the responsibly-renamed kernel?
I have tried a few times already the following procedures: start a new installation (each time, I create a new VBox VM) with the Fedora 12 DVD iso attached to the DVD drive of the VM. I select the default setting, like US english, US keyboard, local time (GMT +8), standard installation ... etc). The installation process had been smooth to the screen the system asking for a reboot after installing something like 1100+ packages. Then I click the reboot button offered. The VM restarted but each and every time, it came up with the following error message:
Booting from local disk...
FATAL: INT18: BOOT FAILURE
There was no other error message durint the installation process. It would be very much appreciated if some one can tell me what went wrong and how to solve it. I believe even I try again the same way, it will end up with same result. Is it a software or hardware problem? In case software problem, is it Fedora or VirtualBox?
I installed VirtualBox (and the virtualbox repo) a few months ago and it works brilliantly. The other day it informed me there was an update available. I downloaded: VirtualBox-3.1-3.1.2_56127_fedora11-1.x86_64.rpm from [URL]
Why doesn't yum update find these new versions of VirtualBox? Is the original repo file out of date? Here it is:
Code:
# cat /etc/yum.repos.d/virtualbox.repo
[virtualbox]
name=Fedora $releasever - $basearch - VirtualBox
baseurl=http://download.virtualbox.org/virtualbox/rpm/fedora/$releasever/$basearch
enabled=1
[Code]....
I have a virtual machine on VirtualBox.I had Fedora 11, all was well.I ran the "preupgrade" tool. It downloaded all successfully, it asked me to reboot.On reboot, it installed everything as it should. It finished by saying it was installed successfully and asked me to reboot one last time.Now when I start it, some text flashes rapidly on the screen. Then it stops.See attached file for screenshot of the last text shown.
View 14 Replies View Relatedtrying to understand the two underlined sentences below I got to ask Step by step. I created a new group called usb. I inserted a usb printer and scanner. I tried to find the file usbfs and there is where get stuck already. I only can find a folder with that name. The sentence (3 -) makes almost no sense to me.
a) modify file /etc/fstab clear open terminal, go to etc, su gedit fstab
b) inserting a line yes I understand that!
c) the right path and the number corresponding the "usb" group :
none /sys/bus/usb/drivers usbfs devgid=503,devmode=664 0 0
2 - locate file usbfs: in my case is /sys/bus/usb/drivers (I suggest to find the file with a usb device inserted;
3 - modify file /etc/fstab inserting a line containing the right path and the number corresponding the "usb" group :
none /sys/bus/usb/drivers usbfs devgid=503,devmode=664 0 0
i always run updates if i get prompted about it... this time i ran a couple or so updates and software updates and restarted, i realise my VirtualBox and Wine isn't running at all... i click on the icons but nothing fires up.. all my programs on Wine seem to fall under the same issue...
how do i view all the latest updates i just installed?
My USB-modem and my freerunner phone is no longer recognized by fedora. Last time this happened I just reinstalld Fedora because I had no id�a what caused the problem. But now I recognized that virtualbox was the last package I installed before the problem occured.
I tried to uninstall virutalbox but the problem remained. Is there a way to reset all the network settings without reinstalling fedora?
I'm looking to install either vmware server, virtualbox or another solution.
Which works the best with fedora 11? I'm interested in USB and performance.
btw, I wasn't sure which forum to put this in
I saw many linux OSes have a smooth stability with sun virtualbox.for example VBoxaddons already initially installed.I installed fedora 12 x86_x64 (within vbox in xp64bit)but only 800x600 resolution is avaible.Smooth Mouse jumping from Pc to vbox etc.
1.is there any good installer that have already packages initially installing for virtualbox ?
2.Which version listed below have x64 kernel?
I want to install Fedora by live disk on virtualbox.
1. I ran the live disk, it works.
2. I click "Install to Hard Drive", it shows normal.
3. I complete the installition and reboot.
4. The live disk ran again, where is the OS installed on hard drive? or it was not installed at all?
I have been messing around with F13 in VM VirtualBox for awhile now. I have read in some places that it is better to install F13 into its own partition on the hdd creating a dual boot system for, in my case, Vista and F13. Any truth to this? I have been having problems with system settings in F13 while using VB. i.e.: sometimes the system will see 3d support, other times it won't. Sometimes it will see ethernet eth0 and then other times it won't. All my hardware from my MB to Display is supported according to the documentation I have looked at.
View 2 Replies View Relatedwhere to download Guest Additions Virtualbox for Fedora 14 ?
View 4 Replies View RelatedMy laptop is running Linux Mint 9 and I am trying to install Fedora 13 in a virtual machine within Virtualbox. However, it's not working. It takes forever to get past the initial white/blue loading bar when it first boots and then it just goes white, so I can't see anything. I've already tried modifying the bootline parameter of the live CD to include noprobe, noacpi, noapic, nousb, and nofirewire. However, the result is the same. Am I missing something? Is it possible to install this?
View 1 Replies View RelatedI tried to install VirtualBox 32 bit on my 64bit Fedora11 OS. I took the 32 bit version as I want to run a 32bit software. I collected all information I could get from other forums. That's what I did: I downloaded and installed [URL]
yum groupinstall "Development Tools"
/etc/init.d/vboxdrv setup
Now I got stucked with the error Qt WARNING: QGtkStyle was unable to detect the current GTK+ theme. I searched for qt or qgtkstyle on my system and found files containing both but don't know what to do here.
Trying to install virtualbox in F12 but fails when recompiling kernel module. Output of vbox-install log is:
Attempting to install using DKMS
removing old DKMS module vboxdrv version 3.1.6
Deleting module version: 3.1.6
completely from the DKMS tree.
Creating symlink /var/lib/dkms/vboxdrv/3.1.6/source ->
/usr/src/vboxdrv-3.1.6
DKMS: add Completed.
Error! Your kernel source for kernel 2.6.32.11-99.fc12.i686.PAE cannot be found
at
/lib/modules/2.6.32.11-99.fc12.i686.PAE/build or /lib/modules/2.6.32.11-99.fc12.
code....
I'm installing Sun Virtualbox and get the following error message. The install does not stop or crash, but just don't know what to do about this message:
Code:
An error occurred while loading or saving configuration information for frontend. Some of your configuration settings may not work properly.
[code]....
my error when trying to run a VB (Virtualbox). Error as copied from error box. install the virtualbox-ose-modules package for your kernel and execute 'modprobe vboxdrv' as root. VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).
[code]...
I get this when trying to launch a VB after making one with wizzard.
how to install virtualbox on ubuntu 7.04. I tryed to install VirtualBox-3.1.2_OSE from virtualbox.org and following the instructions i have downloaded it using terminal but i dont know how to install it .
View 3 Replies View RelatedI'm currently using the PUEL version of Virtualbox 3.0.12 and whenever I open it, it prompts me to update - see screengrab.
Clicking that link and choosing to open it via the package installer (see screengrab) results in the error screen below - another screengrab.
I then realised the deb file was named Jaunty, so went to the Vbox website to download the Karmic file.
Running that via package installer produces the same error - Error: Conflicts with the installed package 'virtualbox-3.0'
Do I need to remove the old version first? If so, how do I do that (given that this is the PUEL version not the open-source version) and will my existing virtual machines (I've got WinXP and ChromeOS) be safe and still work afterwards?
My reason for wanting to upgrade is to virtually try Ubuntu 10.4 which I just cannot get to run or install in Vbox (either from a CD or from the iso image)
I was bored and decided to put ubuntu 4.10 on my virtualbox. but during the installation, this happened:
I gave it 256 MB RAM and a 20 GB Virtual Hard Drive.
I try to install virtualbox through software center, but it just doesn't install.
Code:
installArchives() failed: Selecting previously deselected package virtualbox-ose.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
[Code]....
Observed on two host systems both with openSUSE 11.3 32 bit using ext4: When a big files, in this case a 1.2 GB and a 1.7 GB is copied from DVD, usb harddrive or shared folder into a Windows 7 32 bit guest system, the copied file is corrupted. The md5sum has changed and until the guest system has been rebooted successive md5sum tests on the same file comes up with various results... After a reboot md5sum tests show consistent results, but a sum different from the original file.
View 1 Replies View RelatedI have installed VirtualBox via virtualbox-ose package and it works fine (also installed needed addons), but i can't enable USB on it. I have karmik release installed, but manual at[url].... I discover 2 problems on my system:
1. It does not have /proc/bus/usb directory and when i try to mkdir it:
Code:
baleks@BAleks-netbook:~$ LANG=C sudo mkdir /proc/bus/usb
mkdir: cannot create directory `/proc/bus/usb': No such file or directory
baleks@BAleks-netbook:~$ ls /proc/bus
input pci
so my entry in fstab to mount /proc/bus/usb not works. Moreover, when i trying to mount that in /dev/bus/usb (althought this directory already exist and with files) mount tells me: mount: unknown filesystem type 'usbfs'
2. virtualbox-ose package does not created user group vboxusers (or any like that) in /etc/group, even after reinstallation of the package. 1 and 2 is two steps to get USB work in VirtualBox, and i don't know what to do.. Attempts to google this problems almost always gets me to the posts/manuals related to older verions of ubuntu, but i have karmik..
I cannot make Virtualbox work in Ubuntu 10.04 (upgraded from Ubuntu 8.04). I tried both to install Virtualbox OSE from Package Manager and Virtualbox 3.2 downloaded from the Virtualbox site (32 bits version, as my OS). Installation is OK, but when I try to run it, I get an error message:
Error in home. virtualbox.xml (line3) cannot handle settings version 1.2-linux. Code: NS_ERROR_FAILURE (080004005). Virtualbox would be good because it allows running some Windows applications or games. Wine seems useless, only a couple of applications run in Wine and practically no games. It keeps warning me about DirectX etc. I can't understand why Wine exists at all.
I have virtualbox installed under ubuntu 8.04 x64. The kernel got updated and since then I have to reboot the computer and choose previous kernel to use virtualbox. The reason is that I can't get a hold of the virtualbox module for 2.6.24-28 generic. When the kernel has been updated in the past I would just go into synaptic and select it, but this time it doesn't show and I've waited a while now... Tried searching for the package to no avail.
View 2 Replies View RelatedI'm trying to upgrade Virtualbox but I get the following error. What can I do? I use Ubuntu Release 10.04 with Linux 2.6.32-24 generic.
View 4 Replies View Related