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.
View 1 RepliesI 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 RelatedI'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.
when i ran an upgrade in squeeze, there was an updated virtualbox package.When the upgrade of virtualbox finished, I got a warning like this one "insserv: warning: current stop runlevel(s) (1) of script `vboxdrv' overwrites defaults (0 1 6)."From my understanding, this is not critical by any means, but I would like to know a little about why this happens and if there's something you should do when it does.By the way, I get virtualbox from the "virtualbox.org" repository for squeeze.
View 2 Replies View Relatedmy 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.
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 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
View 4 Replies View RelatedSo 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 using Fedora 14 x86_64 as the host and Windows XP under VirtualBox 4.0.4. I have added two ports (TCP and UDP) to the firewall settings in 'other ports' in the Fedora firewall setings. Do i need to do this?I noticed the port forwarding option in the Fedora's firewall settings which asks for either the ports to be forwarded to either local or an ip address. Do i need to do anything here?
In the settings under VirtualBox under Network adapter 1 (which is enabled) and attached to NAT, there is a port forwarding option in the advanced settings. Can the host and the guest port be the same number? If i use 'open port checker' to check if the tcp port is open in windows xp, will it work as it does in firefox under Fedora?
I would like to know if it is possible to upgrade directly from Fedora N to Fedora N+2.
In the Fedora 11 documentation, it was said clearly that it was not possible to upgrade from 9 to 11. The Fedora 12 documentation was buggy, see #547070 In the Fedora 13 documentation, it is only mentioned from Fedora 12 to 13, but it's not clear whether one can upgrades from F11 to F13.
I mean, look at the bugzilla above.
In response to the Fedora 11 documentation which said:
Quote:
It is not possible to upgrade directly from Fedora 9 to Fedora 11. To upgrade Fedora 9 to Fedora 11, upgrade to Fedora 10 first.
Ruediger Landmann said:
Quote:
The Fedora 9 --> Fedora 11 problem was an issue specific to that release; it's no longer relevant.
So, if it's no longer relevant, one would think it is now possible to upgrade from Fedora 11 to Fedora 13.
By the way, how can I re-open a bugzilla?
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.
View 7 Replies View RelatedThis is my humble tutorial on how to get VirtualBox up and running on Fedora 12. It's located on my web blog here: How To: Install VirtualBox 3 on Fedora 12 [Tutorial]
View 7 Replies View RelatedI've been trying to get a converted virtual disk running in VirtualBox for the past several days. The VM begins to boot in a window but never gets past a black field. Until today the title bar would always change from "running" to "suspended" and just hang there. Now it just keeps saying "running" but never boots so I'm thinking the virtual disk may have become corrupted from repeated shutdowns without ever booting.
The User Manual at VirtualBox.org is of little help since it appears to assume you're using their packages. They also make references to utilities or scripts like "/etc/init.d/vboxdrv" that aren't even in the latest version so I think it hasn't been updated in a while.
There doesn't appear to be many hints in the Vbox.log either - couldn't find a way to get more verbose logging. Until now I'd get to this point and it wouldn't change until I shut it down:
I'm guessing the reason for the suspension was the message immediately above the notice. Now I just see the "unmapped device" message and the guest window says "running" indefinitely. I've attached copies of logs from a couple of sessions, one where it suspends itself (a vnc session) and another where it just stays running (a console session). Some googling suggested that the "unmapped device" message implies it can't find the boot drive or the boot sector on the virtual disk.
The host is normally accessed through a VNC session to a virtual console but VBox log messages indicate that it cannot determine the keyboard type when accessed this way so I now have to physically sit at the native console. If anyone knows of a way to overcome this limitation I'm all ears.
People don't usually respond to my threads so I'm basically talking to myself outloud here. I'll read it again later an maybe come up with something else to try. For now I'm going to remove all the VBox packages and re-install them, starting from scratch. If that doesn't get it working I'll delete the converted virtual disk and re-convert it from the original. If I still can't get VBox working after that I'll be forced to install VMware Server (resource hog). I'm getting desperate now...
[Background] Until a few weeks ago we were happily using qemu-kvm but encountered a bug when using the "-smb" argument after updating the host from Fedora 9 to 12. (re: F12: qemu-kvm with -smb hangs then dies) In an attempt to get our virtualized MS Windows Server 2003 back up and running I installed VirtualBox-OSE-3.0.10-1.fc12.x86_64 and friends over the Christmas break. I converted the qemu qcow2 image to raw then to vdi format using qemu-img and VBoxManage tools. There were no errors during the install of VirtualBox. In the beginning Bug Buddy notified of a crash whenever we started up VBox but after some digging and experimenting I believe the crashes were caused by running VBox in a VNC session instead of at the console. I haven't seen a crash when starting it in a native console session. Unfortunately, this means I can do very little remotely.
[Host Hardware]
[Host Software]
Code:
What is the best way to do this..and should it work well with F13? Can it be done with yum? I read here that you need to install Qt first but am not clear if that is really a requirement or if that can be done with yum as well:[URL]Are there any other installation requirements necessary? I saw posts mentioning specific kernel versions and deleting old kernels.... looking for the safest and simplest way to set this up
View 13 Replies View RelatedI am running Fedora 13, I have installed virtual box that is running Windows 7. I am attempting to run a few star wars video games. Everything works in the virtual machine however it doesn't see any 3D hardware therefore not letting me run these games. I had W7 installed on the computer before and I love fedora and I don't want to dual boot. Is there anyway that anyone knows how to get this working or is there another program that can run a virtual machine for me? Quick update, I installed somethings using the Device menu and Install Guest Additions. That go some mouse and a better video resolution to work however, when using dxdiag in Windows 7, it says that the 3D Acceleration is unavailable. In the settings I have 3D accelration enabled of course.
View 3 Replies View RelatedIn the about last 2 weeks is available an update for VirtualBox OSE, but it fail every time.The final error is "transaction empty" on the gui of the updater.Trying to solve I put the commands suggested by yum (--skip-broken and rpm -Va --nofiles --nodigest) with no luck.
View 4 Replies View RelatedI'm on Fedora 14 and tried to install virtualbox using yum install virtualbox It seemed to install but wouldn't run and I got messages saying there was an issue with it not recognising the kernel. I used the Add/Remove software function and added the right kernel but on reboot it didn't complete the boot up process. I get as far as the loading progress bar being fully loaded but don't get to the login screen I've tried loading earlier kernels to no avail - the same issue.
I can access the install via my live CD but I'm not that experienced a user and how to proceed. My guess is I need to remove all the Virtualbox components but I don't know how from where I am.
Can someone explain to me what virtualbox is and how it is different from wine? I've tried to read up on it but I'm not really understanding what it does.
View 8 Replies View RelatedI'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.
View 1 Replies View RelatedI had downloaded a DVD disk with Fedora 12 on it (~3.7 gig) therabouts. I used it to upgrade my F11 system to F12 or so I think. Well to make a long story short, it had installed approx 1435 files on to my computer. I never so it finish up the process because my moniter timed out and I could get it back on after it had blanked out. So I rebooted the computer (after I had removed the DVD). It showed F12 booting up but the splash screen with logon was F11's. After I logged on my nvidia driver was gone along with compiz and Avant. So I followed 'leigh123linux' response on 'Nvidia' and get it reinstalled and working along with Avant, and compiz and my rotating cube desktop. I did a yum clean to cllean up the packages and ran yum update again to refresh what may have not been installed. It show a couple hundred packages needed to be upgraded and also had alot of 'dependency' errors' for a lot of the packages. That's where I stand now. Is it 11 or still 12? Did the DVD upgrade work? Who nows.
View 2 Replies View RelatedI 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.
Maybe something in my config is stopping it?
we want to upgrade the kernel on Fedora 12 .but problem is , while doing 'make install' , it gives error as 'mkinitrd' is not available .which is required during 'make install'how to run 'make install' command on Fedora 12 without 'mkinitrd' utility.
View 9 Replies View RelatedAnyone having problems with flash after upgrading to F14? Was working fine on F13, but now on F14 it crashes - can't even load the flash test page. This is on a 64bit laptop upgraded from F13->F14 and running the 32bit adobe flash plugin with nspluginwrapper. When I browse to a page with flash in it I can see flash suck up 100% CPU and then crash. Seeing messages like these in the .xsession-errors:
Code:
*** NSPlugin Wrapper *** WARNING:(../src/npw-wrapper.c:1977):invoke_NPP_GetValue: assertion failed: (rpc_method_invoke_possible(plugin->connection))
*** NSPlugin Wrapper *** ERROR: NPP_Write() wait for reply: Message timeout
*** NSPlugin Wrapper *** WARNING:(../src/npw-wrapper.c:2239):invoke_NPP_DestroyStream: assertion failed: (rpc_method_invoke_possible(plugin->connection))
[Code]...
yesterday I've decided to upgrade my distro from F13 to F14 using preupgrade. There were no errors during installation, but after first boot I've noticed glitches in GTK widgets in GDM and other windows after logon (strange white strips on buttons, progress bars and more). Moreover there were even worse glitches in gnome-do. I've attached two screenshots to show exactly what I [URL] I think this is a problem directly connected with upgrading the distro as there are no mentioned glitches when running standard live version of Fedora 14.
View 2 Replies View RelatedEarlier in the week I ran the upgrade to move from Fedora 12 to Fedora 14 on my home workstation. After a bit of fussing I managed to get things working for the most part. The problem I have left is a show stopper for me though. I can't get k3b to work right since the upgrade. I primarily use it to copy video dvds that I've created. The first disk that I tried to copy was a dual layer disk and although it fussed about not being able to umount the disk it was able to copy it ok. Then I tried to copy a single layer dvd and can't seem to get that to work. Right away I noticed that it was reading the disk very slowly.
About a meg a second which is a LOT slower then it used to. It then didn't eject the source disk when asking for a new disk which was it's previous behavior. When I put the blank disk in the write failed immediately with an error about not having permission to write to the device. After a bit of fussing without luck to get past that I decided to try and write the disk while running k3b as root. That got me past the permissions problem but still the write failed immediately. I do need to iron out the permissions issue that currently is forcing me to do this as root but my immediate need is to be able to burn disks again.
I have 90 + clients running Fedora 12 on a beefy i7 machines used for various reasons.
The configuration is as follows:
HD = 1 Terabye with the following partition setup:
200 Meg for /boot
60 Gig for /
844 Gig for /opt
Users authenticate using NIS and have their home dirs auto mounted as well as others directories.The issue on hand:
1) We want to move up to Fedora 14 (since 12 is no longer supported).
2) The first hurdle is working around the 200 meg boot partition. Does anyone know of a process which can be automated for this? Currently, I was able resize a client by decreasing the root to 59 gigs and boot to 1.2 gigs through the use of gparted.
3) Is there a utility which will allow me to deploy this using a utility/script on all the clients?
4) Ultimately I want to automate the process without having to touch each machine.
At Present my Desktop has only 0.5 Meg Memory, F14 works well, F15 refused to Upgrade a 750 MB minimum I have gone back to 14.
View 2 Replies View RelatedI've got a problem with getting my VPN connection from my virtual machine working (a XP64 running in VirtualBox). I really need to get it working so that I can nuke my windows partition, and because I would like run linux programs while using my XP VPN connection (as I need to run some XP programs at school). I've found this manual on how to do it on Ubuntu, but I am doubt about how to translate it to Fedora (and I really prefer Fedora). [URL]
View 6 Replies View RelatedWishing 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 Replies View RelatedI wanted to try VirtualBox so I did:
Code:
yum install vboxgtk
In the list of dependencies I found that it needs to download kernel. I was just curious to know that why can't it manage with the PAE kernel. It requires the kernel 2.6.31.12-174.2.3.fc12 whereas I've got its PAE version working right now. Can someone please explain why is it so?