Fedora Installation :: VirtualBox: Can't Start After Upgrading From 11 To 12?
Mar 5, 2010
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.
I am running Fedora 13 and have VirtualBox 3.2 installed. I see in yum list that VirtualBox-4.0.i686 is available but apparently I do not get updated to this version running yum update. How can I update to VirtualBox-4.0.i686 ? I uninstalled 3.2 and simply installed 4.02 and everything worked fine. Previous virtual machines are compatible and still work as before.
I'm currently running VB 3.0.10 on Fedora 12 64 bit.
When I attempt to upgrade my current install to 3.1 I get the following:
I am somewhat puzzled as this is a upgrade from a stable installed version. I have confirmed I have libcrypto.so.8 . . . from what I can tell its part of the openssl package but I've got the most current so I don't know how to obtain the libcrypto.so.10 file to correct this issue.
My Windows Vista installation won't start after upgrading from Karmic to Lucid. If I select it on GRUB2, it leaves a blinking cursor on screen. And I tried doing the whole test disk thing and the boot info script. This is what my Results.txt file says
Every time I try to start a virtual machine in VirtualBox I get this error:
Code: Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
'/etc/init.d/vboxdrv setup' as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. So I run '/etc/init.d/vboxdrv setup' in the terminal as root and I get this:
Trying to run windows only apps. I installed Wine first from software center. Most progs I try to run only give me the 'working' icon for 20 seconds then nothing. I did modify properties to allow .exe to run. I Dl'ed & installed the VirtualBox package w sw center and same deal- nothing. No error messages or anythng.
Running Ubuntu maverick. My Cpu is a compaq presario laptop CQ50, dual core intel T3200. Not the best but should at least start the progs yes?
Can't really troubleshoot as I have no feedback at all.
after upgrading VirtualBox from 3.0.x to VirtualBox-OSE-3.1.2-1.fc12.x86_64 VBox fails to start any virtual machine with error: Failed to open/create the internal network 'HostInterfaceNetworking-eth0' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
I get FATAL: Error inserting vboxnetflt (/lib/modules/2.6.31.12-174.2.19.fc12.x86_64/extra/VirtualBox-OSE/vboxnetflt.ko): Invalid module format FATAL: Error inserting vboxnetadp (/lib/modules/2.6.31.12-174.2.19.fc12.x86_64/extra/VirtualBox-OSE/vboxnetadp.ko): Invalid module format Kernel is (obviously) kernel-2.6.31.12-174.2.19.fc12.x86_64, but same thing happens with any installed kernel, IE kernel-rt-2.6.31.12-1.rt20.1.fc12.ccrma.x86_64
I reinstalled VBox and kmods got rebuilt but the problem persists.
Can anyone help me with how to create an init.d script that will startup a vm machine in virtualbox at boot? I found this script:[URL]..But it is for ubuntu. I am running fedora 12 x386 and using it as an Amahi server. Very cool, but it would be extra cool if I had a virtual windows machine startup when I booted up this server. Then I could just rdp into it when I needed something in windows.
I just did a distribution upgrade on my laptop from 9.1 to 10.04, and it went fine for the most part except this issue. After it boots up, I don't see any window titles/scrollbars/borders and on clicking the icon for "Show desktop" on the bottom left, I see the following error message:
"Your window manager does not support the show desktop button, or you are not running a window manager."
After googling a bit, I realized that gnome-wm is not starting automatically and so I have to manually start each time to see the windows working properly. Can somebody tell me if there is a way to make sure that gnome-wm starts automatically? I know I can put it in my .bashrc but I want to do it the correct way if possible. If not, I will have to go with that workaround.
I just did a distribution upgrade on my laptop from 9.1 to 10.04, and it went fine for the most part except this issue. After it boots up, I don't see any window titles/scrollbars/borders and on clicking the icon for "Show desktop" on the bottom left I see the following error message: "Your window manager does not support the show desktop button, or you are not running a window manager."
After googling a bit, I realized that gnome-wm is not starting automatically and so I have to manually start each time to see the windows working properly. Can somebody tell me if there is a way to make sure that gnome-wm starts automatically? I know I can put it in my .bashrc but I want to do it the correct way if possible. If not, I will have to go with that workaround
I was trying to install VirtualBox through the YaST > Software Management but it is not working, someone in the forum told me that I have to download the OSE version and do it manual way. Finally I am able to start up VB but not able to use the network connection. Thus I am trying to do this:
/etc/init.d/vboxdrv setup. I get this error:
[code]...
When I type dmesg, it shows me a bunch of info which I don't know what should look for. When I type modprobe vboxnetflt, I get the error: FATAL: Error inserting vboxnetflt (/lib/modules/2.6.37.1-1.2-default/updates/vboxnetflt.ko): Invalid module format. what should I do in order to get my VB to be able to connect to the internet?
Running 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.
i am trying to upgrade to ubuntu 10.04 from 8.04, and am getting this warning:"Upgrading may reduce desktop effects, and performance in games and other graphically intensive programs.This computer is currently using the AMD 'fglrx' graphics driver. No version of this driver is available that works with your hardware in Ubuntu 10.04 LTS.Do you want to continue?"should i continue? i have no idea what a 'fglrx graphics driver' is
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'm trying to upgrade PHP on my Fedora Core 6 web server. I currently have 5.1.6, all I need is verson 5.2 or higher, it is a requirement of some software I want to install. I am not really a server admin or very Linux savvy, I've been able to get around doing what I need to use this a web development server, but trying to do this is beyond me. I tried updating using yum, but I guess the latest version in the Fedora Core 6 repositories are 5.16. I've never really dealt with installing binaries, so I am stumped as to how to get this done.
I had fedora 10 a while back,and when fedora 11 came out a few days later my PC prompted me to upgrade.. all from desktop.. clicked one button and that was it, 10 minutes later it was upgraded... perfect.
This time, I'm sat on fedora 11 looking at the timeline for the 12 release, it gets released and i'm still waiting for 11 to tell me i can upgrade... I know I can upgrade manually, but im quite interested as to why it hasnt asked me automatically this time.
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.
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.
Actually, Slack64 runs just fine under VirtualBox on my old HP under WinXP, But the installer for Slack86 won't boot under VirtualBox on my Toshiba Netbook under Win7 starter. I tried updating the 13.1 install I have on there, but I get the same kernel panic when I try to reboot that. It always bails just as it is switching over to the new kernel. The dump fills my screen so I can't see the actual error. How can I capture that initial startup log? Slack86 runs just fine on my old Compac Armada 1700 (266PII 92M/12G), but that's a very different environment.
I've never compiled a kernel before and I'm in need of the 2.6.28 kernel (two words: macbook aluminium).
I guess my biggest question is, will this guide work well for F10? I would hate to get half-way through it just to find out that F10 does something different than F08 or F09. Is there anything that you experts can see right away that would possibly be disastrous? If things do come to worse, I can simply select the previous kernel at GRUB boot right?
Or will the Fedora team be releasing the update soon through the package manager? Is there a way I can activate the development version and only get the kernel update?
I am planning on doing an upgrade on one of our systems from Fedora Core 7 to the Fedora Core 12 distribution. I have read Bruce Byfield's article "Upgrading to the newest Fedora release", and the approach that I am planning on taking is the upgrading via the DVD medium.
Quote: Please don't even bother trying this... each upgrade between fedora versions has it's risks, I'd give you a 4% chance of success between these two versions. And if you upgrade, you'll not end up with FC12, you'll end up with a horribley messy mish mash of a distribution that just happens to mostly contain FC12 rpms. Do yourself a proper favour and save important data and configs, and reinstall. and then keep it up to date properly. Another quote was as follows:
Quote: Glennzo posted a thread in [URL] about upgrading which surfaced in a recent thread. If it's a production system I'd strongly suggest copying the setup to a test slash staging server to see if cleanly installing and modifying F12 versus upgrading to 8, 9, 10, 11, 12 is more efficient slash less error-prone. I am inclined to try doing the upgrade on a test server to see if it works. Should I even bother with that approach or just proceed with the scratch install?
I'd like to reproduce the way I got to f12 from f11, but obviously to f13 basically I started out on the f11 rawhide repos, then as f12 got released a yum update updated my fedora-release and then hey presto I was automatically upgraded to f12 final release if I now turn on my rawhide repos, as f13 is nearing completion, will I be updated to the latest f13 release (RC3 I believe) and then as f13 gets released my fedora-release will be updated and i will then be upgraded to f13 final as happened before?I don't want to download a whole dvd iso and then upgrade when f13 is final, I'd like to do a gradual transition ie..
f12 -> f13 RC3 via rawhide f13 RC3 -> f13 Final via yum update
I want to upgrade my 32bit Fedora from 11 to 13 version. I tried both options: via preupgrade tool and via installation media (DVD). Both options failed with following Anaconda error at the beginning of installation process:
I switched to terminal, and discovered that size of this file is 0.
I downloaded installation DVD from official torrent, so checksum was autmatically checked. Verification test at the beginnig of installation was also successfully passed. So media is OK. Moreover, I also tried to upgrade via preupgrade tool with the same results.
I found similar bug with unclear status in Fedora Bug Tracking system for Anaconda in F12: [URL]
I have a fedora 15 beta installation medium , can I upgrade to the stable version after installation ? is this the same as hitting the update manager or is there any thing special I need to do
I'm trying to upgrade my vim to 7.2. Did an rpm check and have downloaded the package package vim-7.2-8.1. But then upon installing, it give me this "package vim-7.2-8.1 is already installed" which I guess to me it has been successfully installed. However when I start vim, it is still on version 6.3.
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?
