In 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 RepliesI was notified by the updater that VirtualBox-3.2-3.2.10_66523_fedora12-1 (x86_64) was available to install. So I clicked [Install Update] and got the following Transaction error:The GPG keys listed for the "Fedora 12 - x86_64 - VirtualBox" repository are already installed but they are not correct for this package.Check that the correct key URLs are configured for this repository.
View 2 Replies View Relatedi 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?
After updating to kernel-2.6.33.6-147.fc13.x86_64 (and updating all kmods) VirtualBox guests no longer boot.
I had a Windows guest (from now on refereed as Crapdows) that worked normally. After the update, I could get to the "Start Windows Normally" screen, but then Crapdows refused to boot. At first, I thought it was a crappy M$ bug, but after creating another VM (Doublecrap), and starting from scratch, I was able to get to the "Windows is loading files" screen, and then the guest hangs again.
This problem is generalized to all OS'es I've tried. In Ubuntu, I can get to the language selection screen before the installation freezes. The same applies for Fedora and SUSE guests.
Is it time to get my hammer?
I am running Fedora 12 on an Intel Core 2 Duo system.
I ran a software update which installed a new kernel (2.6.32.23-170.fc12.i686.PAE) along with many other things.
I am now unable to run VirtualBox which I had installed and running successfully before the update.
I tried removing and reinstalling VirtualBox from YUMEX, and rebooting. This did not help.
When I launch VirtualBox from a terminal, it produces the following output:
VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: VBoxVMM.so: cannot open shared object file: No such file or directory
I'm not sure what it is complaining about. The files VirtualBox.so and VBoxVMM.so both exist in the /usr/lib/virtualbox directory.
What can be done to get VirtualBox working again on this system?
I'm trying to update VirtualBox but I'm getting a few problems:
1. When I go into YAST, it doesn't show any other versions available (just 3.0.x)
2. When I download the rpm from the website, I keep getting some insanely long error that says something about NOKEY perhaps? (It's a long error that gets cut off by the screen height)
recently i updated to a kernel version 2.6.31-22-generic and now I cannot start my virtual machines from virtualbox-ose.
View 3 Replies View RelatedJust updated wheezy 2.6.35-2-amd64 from to 2.6.38-2-amd64 and noticed that virtualbox-3.2 stopped working.
View 4 Replies View RelatedI 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 RelatedHave similar issues with Slackware, since the latest Xorg updates I cant run KDE anymore. I am using VBox 3.2.10, so thats not the issue, i suppose.
Here is the error from kdm.log:
Code:
Backtrace:
Fatal server error:
Also when the system is booting I get a warning like this:
Code:
Trying to start a running installation of virtualbox I get:
And it seems that it doesn't work with the new 275 build I got pushed when updating. Updating virtualbox didn't help. Besides uninstalling the 275 version of nvidia and installing the 270.
On a Xp host I installed last version of VirtualBox and I created a 9.10 Ubuntu 'guest'.While I can surf the net, I cant 'sudo apt-get update' nor do a 'reload' from 'Synaptic Package Manager'.
PS Here are some facts:
<<
Host:
PC:
Thinkcenter 9640-7BG
Network adapters:
[Code]...
Just installed 10.10 under Oracle VM VirtualBox and then installed VBOX additions to clear up monitor issues. Mozilla Firefox works and so does Evolution mail client (needs work though). Everything seems to work EXCEPT Update Manager.I consistently get Failure message: "Failed to download package files".
View 4 Replies View RelatedI have installed both 32 and 64 bit versions of Ubuntu 11.04 in VirtualBox 4.0.6 and have installed the VBox Additions. When I try to add new software or update software I get a package operation failed error.
installArchives() failed: Setting up tzdata (2011g-0ubuntu0.11.04) ...
Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.[code]....
I have used the same install media to install Ubuntu on a stand alone system and it works fine.
I use Arch Linux and the kernel got upgraded, and it broke VirtualBox. It says to run "/etc/init.d/vboxdrv setup", but such a file does not exist. The Arch Wiki says "/etc/rc.d/rc.vboxdrv setup", but that doesn't exist either. What should I do?
And is it possible to write a script that runs on startup that automatically fixes VirtualBox whenever the kernel is upgraded?
I recently applied a bunch of updates to my guest OS (Ubuntu) inside VirtualBox (NOTE: NOT updates to virtual box. Updates to the OS) and now on startup, I get the error:
"An error occurred while mounting /media/share. Press S to skip mounting or M for manual recovery"
I tried a fix which said to comment out the mounting in /etc/fstab and instead put it into rc.local, but this does not work.
Also, when I press "M" to try it manually and type:
mount.vboxsf -w mysharedfolder /media/share
I get the error:
mount.vboxsf: mounting failed with the error: No such device
But before I updated Ubuntu, that shared folder worked perfectly!
I'm running Virtualbox from the Sun website (need the USB support) and it breaks after each kernel update.The problem is that I installed a lot of Ubuntu systems for transitioning windows users with Windows in virtualbox to ease the migration but I have to rerun vboxdrv setup after each kernel patch.
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.
If I run Vista through VirtualBoxOSE (on Natty) will I be able to update my MS Zune? Short replies welcome, just want to know if it's worth the trouble
View 2 Replies View RelatedObserved 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 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?
This 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 RelatedI 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 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'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 Related