I've been having problem after problem trying to install virtualbox 4.0.2, on 32 bit opensuse 11.3. I've been able to jump over a few hurdles by installing the kernel source. But now I get this error when starting virtualbox from the command line:
Code:
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (2.6.34-12-default) or it failed to
[code]....
I am have some issues getting VboxAddtions installed. I try to mount a shared folder and I get... FATAL: Module vboxvfs not found. When I try to install the additions I get...
Code:
jgleaso@linux-s7o8:/media/VBOXADDITIONS_4.0.4_70112> sudo ./VBoxLinuxAdditions.run
root's password:
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.0.4 Guest Additions for Linux.........
[code]....
openSUSE, just installed 11.2 some days ago and have several problems with kernel 2.6.31 and my hardware, i was wondering if there is a way to upgrade it to version 2.6.32... that i know i dont have any problems with it.The problems that i have is with my ath9x driver, iv'e experience it before with other distros and the same kernel (2.6.31)Another question i have is about VirtualBox, i use it to run windows, and i'm amazed of the lack of speed and performance i have in openSUSE, i dont know if it's because i'm doing something wrong, quite possible since i'm not familiar with the -suse way- of using linux... i read the wiki about virtualbox made all that it's said (used OSE and non-OSE) and nothing changed... it's unusable. i used to use it in other distros with no problems, but in suse i have alot of issues.
apart from all the issues i have concerning speed and performance in openSUSE it's worth of a try.hope that configuring it better will speed up and increase performance.btw, i have a amd athlon x2 2.1ghz, ati radeon hd3200 using fglrx module and 4gb of ram.
I have Sun VirtualBox setup on my OpenSUSE 11.2 system.(KDE)
How can I run VirtualBox when Linux boots?
Is there a way to pin VirtualBox to Desktop 2?
Im trying to install opensuse 64 bit on virtualbox, but it keeps telling me virtualbox is a 32 bit machine. Is there anyway to do this, I'm pretty sure i'm using 64 bit virtualbox.
View 4 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.
I tried to install VirtualBox by using the "Help->Check For Updates" in VirtualBox and then downloading the rpm. When it finished, it popped up a huge error window that was too tall for the screen (and I couldn't copy the text). It wouldn't install. It said something about how the files in virtualBox 3.2.6 conflicted with those in 3.0.12.
How do I upgrade to the new version?
Added the repo and installed Virtualbox.
Added user as vboxusers group
Added the following packages according to the error log
- make gcc kernel-source dkms
Finally /etc/init.d/vboxdrv setup reports an error
Stopping VirtualBox kernel modules done
Uninstalling old VirtualBox DKMS kernel
[Code].....
I'm trying to run OpenSUSE 11.2 on VirtualBox (ver3.0.8 on Ubuntu 9.10). The installation proceeds without a hitch, but when I try to login, the login manager (kdm?) complains that the login failed. When I go to the console, my login/password do no work there either. I've tried installing OpenSUSE 11.2 three times -- the first two times, it complained about the simplicity of my password -- and all three times I've run into this problem.Have other users encountered a similar problem? It doesn't seem like a VirtualBox-specific issue. Is the /etc/password being changed somehow?
View 5 Replies View RelatedWhen there is a total of 2 GB of physical RAM, how much RAM would you give to openSUSE-11.2 (i586) with KDE as a VirtualBox guest in Vista? There is no intention of running a second VM at the same time.
View 6 Replies View RelatedInstalled OpenSUSE in VirtualBox to try out. Boots ok but can't capture mouse! I installed with all defaults and using Gnome. Host OS is Ubuntu. I'm running XP fine in VirtualBox and wanted to test drive OpenSUSE.
View 9 Replies View RelatedI am running OpenSuse 11.3 64 bit and I just tried to install Virtualbox 4.0.0-22.1 from the Virtualization repository.
--
ttblum@toddb05:~> VirtualBox
VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed:
[code]....
Ive been running VirtualBox with a windows XP installation for some time, on an opensuse 11.0 host for some time. Recently, however ive been having issues with suse, and want to take my virtual XP and make it a primary bootable physical partition, on a second disk
I know it can be done, but im not finding how exactly.
What ive tried so far. I've taken VBoxManage terminal tool and converted the VDI to a .img file, and tried to move that to my second physical disk, but it didnt work at all.
After some thinking, I booted to acronis true image within my virtual machine, and cloned the C:/ drive of windows over to my second hard drive. That got me further, but doesn't boot fully. Comes up to windows xp logo, and black screen boot loops.
Ive heard about using vditool to create a .raw file, and then go from there, but im at a loss to find vdi tool
How can i move my virtual machine to a physical, bootable partition on a second drive?
I am finding that plasma-desktop crashes on a freshly installed 11.3 64-bit VM in VirtualBox whenever memory is set to 512MB. I created the VM with 1GB, which is overkill for what I am using it for. At that point all was well. After lowing memory to 512MB, it boots and starts to load the desktop, which fails - error log below. Increasing memory to 756MB allows it to load fine again.
I don't really need a desktop environment on this VM, but it seems odd this is happening at all. 512MB should be fine to run a basic VM with KDE and per Hardware requirements - openSUSE 256MB is the minimum, and 512MB is recommended.
While it's not a big deal, I am a bit curious why this really needs 756MB to run a bare bones system and just launch KDE. Really? We've come to that?
Perhaps I just long for the halcyon days when Linux would run, including a desktop environment, on a 486 with 256MB . . .
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 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?
I was trying to install VirtualBox from AUR [URL]... it wants libpng12, which is outdated and makepkg cannot install it. Whan should I do? Here is what happens:
[code]...
I have been going through forums and following "how to's" and walkthroughs on how to use VirtualBox to run my Win 7 VM. I have a pre-created VHD that I am importing to my OpenSuse 11.4 machine. One vhd was created in Hyper-V and has hardware and cpu cross compatibility turned on. Everything works perfect when booting it up on my Hyper-V server. When I move it over to my OpenSuse VirtualBox the VM will not boot. It gets to the "Starting Windows" screen and then throws an error screen that the VM encountered errors while booting. It then runs the Window's startup recovery tool and even tried to do a system restore. Nothing works and it never progresses beyond that point. Figuring there was something with the vhd file. I used Acronis Advanced Backup and Recovery to create a non hardware dependent backup that was automatically converted to a vhd. I know the process works as that is how I have converted the bulk of the servers at work into VM's. However, when I move the vhd file to the OpenSuse VirtualBox... it does the same thing.
So I am trying to figure out what might be going on here. Is VirtualBox not able to virtualize Win 7? If not then what VM software should I use? VMWare, Xen, ???
A long time I used the Virtualization:VirtualBox-Repository (which is still suggested in the yast-repository-module) to get the latest version, but the version 3.1.6 is still missing here.I found that this repository will be dropped and instead Virtualization:VirtualBox_backports should be used.But the packages there have two problems:No localization is available, you can just use english.The kernel-modules are just available for Kernel 2.6.31.5 (there is no update-repo for updated kernels)
View 7 Replies View RelatedI tried upgrading today from VirtualBox 3.1 to 3.2 (VirtualBox-3.2-3.2.0_61806_openSUSE111-1.x86_64.rpm) on my openSUSE 11.2 system and it's not cooperating. The installation itself went fine, but as soon as I try to start a guest, the VirtualBox process ramps up to 100% and stays there until I poweroff the guest. The guest itself is VERY slow. These guests worked fine on 3.1.
For example, if I start an openSUSE guest and stop the Grub counter, therefore leaving the screen at the Grub bootloader, the VirtualBox process remains at 100% forever, without any activity on the guest.I also have a Windows guest and it has the same problem.
I can obviously try downgrading again to 3.1, but I was hoping that someone else has run into this issue and knows what to do about it.
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)
I currently have vbox 2.0.6 OSE and its been running awesome except I get errors with directx when running 3D apps cause of the video card driver that comes with vbox(at least so far thats I narrowed it down to). So, Im trying to update to 3.2.2 but cant seem to find an easy way to do it. I downloaded the RPM for OpenSUSE 11.1 from Sun's website and when installing it I got errors about files conflicting with the previous version. So I ran a "zypper rm vbox" to remove the current one and then ran the RPM again and it seemed to finish the installation fine, I just cant find it to run it.I currently have the 2.0.6 version installed again just so I can use it... but now am back to trying to get 3.2 installed before looking in another direction.
View 5 Replies View RelatedSo after a series of uninstalling and reinstalling VirtualBox to get the updated version, I was able to get it installed and working but it seemed to be crashing my computer as everytime i walked away for 10 minutes and came back, it would be at the login screen. It never did it while I was on it though so I never saw any errors. Now after a couple days of that... Whenever I start it I get an error:
Failed to create VirtualBox COM object
The application will now terminate.
Could not load the settings file '/home/user/.VirtualBox/VirtualBox.xml'
[code]....
Earlier i installed Virtualbox from Package Repository. Now VB Repository doesn't work anymore. I only get en error-msg if i try to ad VB in Package Repository. I've been always adviced to install from repos than downloading. What happens with Virtualbox?
View 5 Replies View RelatedSo, on OpenSuse 11.3 I installed VirtualBox, and I would like to put other account to be able to start virtual os-es, but... I would like to have them 2-3 and that other users see them when they start VirtualBox and that they can start them, but not to add new one..
View 9 Replies View Relatedi have virtualbox installed from the oracle virtualbox repositorie and had trouble with running virtual machines. It was a permission error: VERR_SUPLIB_OWNER_NOT_ROOT
Turns out after some searching that the permission had changed on /usr to
owner:chris and group:vboxusers. Directories inside /usr still belonged to the user root and the group root.
I don't know how much of a security issue this is, but i wanted it to let
you all know just in case it is. I changed /usr again to root:root and all is well again.
I have previously been using VirtualBox on an Ubuntu installation, but have now switched to openSUSE 11.4. I have a .vdi file that I want to continue using and would like to know if it is possible to import this to the (preferred?) hypervisor which appears in the openSUSE System menu, which I assume is XEN.
Never having used XEN,
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 RelatedWhat 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'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.