Fedora :: Can't Get USB Pot Work In Vbox!
Jan 11, 2011I'm running fedora 12 and can't get my usb work in vbox does anyone have a solution?
View 3 RepliesI'm running fedora 12 and can't get my usb work in vbox does anyone have a solution?
View 3 RepliesHost: CentOS 5.4 x32
Guest: FC12 x32
Virtual machine: Virtual Box (VBox) 3.1.4
The 640 x 480 video display on my FC12 guest is driving me nuts! The VBox Guest Additions are installed. How do I get FC12 to recognize the VBox video driver?
Extra information:
Auto resize works great on my Windows guests. On FC12, I just get a lot of extra white space.
FC12's installer does not detect a video card. You have to use the stand display option (second one down) to get FC12 to go into a full graphical installer. If you use the regular install, hoping to do a graphical install, FC 12 only install the bare basics. No video support. You get what looks like a rescue cd. No Gnone, no X etc.
I do believe that FC12 has no idea that the VBox's fake video adapter even exists.
I juat got 11.04 and as usual the additions will not install on Ubuntu.Does anyone take charge of making sure that ubuntu will work in VBox?
View 1 Replies View RelatedOk, so i just got fedora 12 all set up in Virtual Box and got the guest additions and stuff so i can have max screen res. I went to set up compiz following this site (google Using Compiz on Fedora 12 as Linux Guest in VirtualBox) installed dkms, rebooted and now after it loads the bar at the bottom that says fedora 12, it gives a blank black screen with a solid white line at the top like a c prompt curser. Whats the deal here? did dkms break my install or something? Its on a vm so no big loss but id still like to know.
View 9 Replies View RelatedGetting this error message and can't get by it........
Problems were found which would prevent the Guest Additions from installing.
I just installed a Puppy Linux 5.1 to a VirtualBox VM and selected hardware virtualization. It installed ok and then later I noticed I had not unloaded the kvm and kvm_intel modules. I was then surprised to notice the vbox modules were also loaded. It used to be you had to kick out the kvm modules before you could even boot a VM in VirtualBox using SVM or VT-X. If you didn't you'd get some error message in Vbox have to quit and restart it after removed the kvm modules.
Is this a neat new functionality of VirtualBox or something that was improved in Fedora?
I have Fedora configured using XP and VBox. I am now out of space. As anyone run into this issue? What do you recommend that I do to transfer my current Fedora contents to a new virtual file?
View 9 Replies View RelatedI have recently installed virtual box on fc14 using add /remove software . However so far i have not been able to install any OS on that. I put the OS CD the cdrom and click on start virtual machine..it gives following errors ..
I have followed the instructions given there but all in vain...
Code:
[root@Fedora Raman]# /etc/sysconfig/modules/VirtualBox-OSE.modules
ERROR: modinfo: could not find module vboxdrv
ERROR: modinfo: could not find module vboxnetflt
ERROR: modinfo: could not find module vboxnetadp
If i specify 512MB memory from my 2GB RAM, is it reserved forever? or only works when i am running vbox guest os?
View 4 Replies View RelatedI have install windows XP and Fedora-14-X86_64 on dual boot, I want to run other OS on fedora by using Virtual machine. I have download and installed VirtaulBox-4.0.0 successfully but I cannot able to start it. I got error about Vbox driver not installed [error code:1908]. I have also installed DKMS package, but also didn't work.
Finally I found the actual problem was kernel not compatible with latest version of vbox and I need to update my kernel-headers. I also meet that solution by using command: yum install binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel and its work fine, this command download and install the kernel compatible VirtualBox-3.2.* and now its works fine.
But problem is that when I booting my PC, it shows 3 options for entering OS rather then 2.
1. Fedora-14 (2.6.35.10.74.X86_64) [which is new one/updated after using that command]
2. Fedora-14 (2.6.35.6.45fc14.X86_64) [which is new one/updated after using that command]
3. Other [windows XP]
How can i delete that old version- No.2?
I finally got magicjack working under a winxp running on a vbox. But somehow I have to login as root and run the vbox as root. otherwise if I run the vbox as a normal user, I cannot mount the magicjack usb device, it appears as a grey disabled box. I am sure this is some kind of permission issue, but not sure how to grant the permission.
View 3 Replies View RelatedI am trying to install this particular Debian-based distro in VirtualBox, but upon trying to install it, I get the massage
Code: This kernel requires an x86-64 CPU, but only detected an i646 CPU.The host system is 64 Natty, with i5-M460. What am I missing? I thought everything is 64 bit in front of me...
I did it, I don't know exactly what I did, but OpenSuse 11.4 only boots to CLI when I fire it up using vbox 4.0.10. I was not able to attached a screenshot, I got an error saying that I did not have sufficient rights or something.
View 5 Replies View RelatedI have Vbox 4.0.4_OSE installed on my 11.4/KDE4.7 Laptop with Win7 and WinXP VMs installed. Generally runs well, although the Win7 VM seems to lock up on occasion if I ignore it for too long. Compared to having to reboot to Win7 to do the few things still stuck on Windoze, it is a GREAT solution.
Question: I have seen several forum items related to difficulty with dual boot systems and the installation of Win7SP1, regarding SP1s checking the MBR for the Win7 boot loader. Has anyone done a SP1 update to a VM on Vbox? It is sort of unclear what SP1 might see in the VM disk container associated with the VM. Since the initial load process for a new VM is time consuming, I thought I would ask first before blowing up my otherwise working Vbox system and then having to reload from scratch.
I keep losing my keyboard in Virtualbox. I "fix" it be reverting back to the host and then switching to the VM and it will be back. Googling brought up others having similar issues with Ubuntu, but no solution that I saw.My host is Jessie and client is Wheezy, both with Xfce. The mouse works just fine.
View 4 Replies View Related#1. Host Wheezy 7.8 KDE 64 bit
VBox 4.1.18_Debian r78361
Ext.Pack 4.1.18 r78361
Can use a WIN XP appliance (from my old PCLinuxOS) as guest there without any issues.
Added a second guest - Jessie 8.0 KDE 64 bit. Works, but no seamless display, mouse issue ...
So added inside guest:
non-X11 guest utilities + X11 guest utilities from the repositories
(These utilities are meant to be run inside the the virtual machine. They provide closer integration ...)
I simply don't know, how to run those utilities ...
What I get is
Code: Select all# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● virtualbox-guest-utils.service loaded failed failed LSB: VirtualBox Linux Additions
● virtualbox-guest-x11.service loaded failed failed LSB: VirtualBox Linux X11 Additions
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
2 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
#2. Host Jessie 8.0 KDE 64 bit (on a second hdd)
VBox 4.3.18_Debian r96516
Ext.Pack 4.3.26 r98988
VNC 4.3.18 r96516
Same situation as in #1.
How do I run those xxx VBox applications inside guest?
launching vBox lately pops-up this; but if I allow it to go ahead, I get this.. : the window has no end (!), no scroll bars nor any further info. If I first uninstall in Yast, will I lose all of my machines? Up until now these periodic updates have been a breeze, only sometimes needing a vbox setup afterwards to tweak the kernel
View 6 Replies View RelatedI have been trying to run my vmachines in virtualbox with no success so I decided to install upgraded packages for upgraded kernel, this means to install them from Virtualization-kernel-HEAD repo.The error is about that known issue where the kernel module can't start.
View 3 Replies View RelatedI'm using Ubuntu 9.10 and recently installed Virtualbox PUEL edition that I downloaded from the Virtual box website. So I installed a virtual windows XP and it works fine. However, when the virtual XP is running, my computer can't go to hibernate when I click the hibernate button.The screen just turns black for several seconds and then brings me back to the login screen. When I shut down the virtual xp, the computer can go to hibernate the normal way.Why is it that running the virtual machine prevents my pc from hibernating?Is there a setting to enable hibernation while the virtual machine is running?
View 4 Replies View RelatedI put vbox on my wife's Dell Inspiron 6000 to play Netflix but the video won't play. After buffering it says there's an "internet connection problem". From what I've read that means the connection is too slow. Netflix works fine on my wired desktop (also Lucid+vbox) and on the same laptop booting into Windows (not VM). So I'm thinking there's a problem with vbox slowing the connection between the laptop's wireless and the VM?
I don't know if it will help with Netflix but 2D video acceleration is grayed out on vbox. Strangely, the 3D acceleration is fine and I can select it. If this is due to an unsupported video driver, can I change it?
I went to the Kodak website to see if I can download Kodak ESP 3200 series for Ubuntu, but it only has them for windows and MAC is there a way around this other than using VBOX?
View 2 Replies View RelatedInstalled debian lenny one hour ago, and starte customising it for my needs.
i have a small problem after installing VirtualBox, after installation no shortcut icon is added .
I can use VBox from terminal, but wanted to ask what may br the problme.
I installed recently opensuse 11.3 and then Virtualbox from Sun Webpage. I have a local printer connected to one of the usb ports. With 11.2, VBox saw perfectly that printer and I could connect normally to it. Now, VBox sees the printer: if I click on the usb icon in the status bar it appears, but dimmed, and I cannot connect to it. I tried to disconnect and reconnect the printer physically, but nothing changed.
View 6 Replies View RelatedI have downloaded vbox from its site and installed it. I created a vm but when I try to start it, I get error:
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.
And when I try 'sudo /etc/init.d/vboxdrv setup', I get:
Stopping VirtualBox kernel modules done
Uninstalling old VirtualBox DKMS kernel modules done
Trying to register the VirtualBox kernel modules using DKMS failed
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules failed
(Look at /var/log/vbox-install.log to find out what went wrong)
And this is /var/log/vbox-install.log:
Makefile:159: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
I have a virtual XP as guest in VirtualBox on a computer running Hardy. I used to be able to access the internet from the virtual XP, using Internet Explorer or Google Chrome with no problem - it just used the Ubuntu host's connection, whch it seemed to see as a "NAT Adapter".
It still sees this NAT connection - if I hover the pointer over the Network icon in VBox it says "Adapter 1 (NAT): cable connected". And if I use Firefox from the host OS, it connects just fine.
Why can the virtual XP no longer access the internet?
I am running Ubuntu 10.04 (the guest) in VBox 3.2.4 which is running in Vista (in a dual core AMD Athlon). Ubuntu works okay except the screen size is one-quarter of the space available on the 22" widescreen monitor. I read that installing BoxAdditions_3.2.4_62467 can solve the problem. When I run the terminal command (using the appropriate file) sudo sh ./VBoxLinuxAdditions-amd64.run I get an error message --> sh: Can't open .VBoxLinuxAdditions-amd64.run
View 7 Replies View RelatedVirtual Box.in "VB host only Ethernet adapeter mode" i am able to communicate with Vbox via WinSCP and browser(ip address)
BUT when i switch to Bridge mode/NAT (pref bridge) in Vbox i am unable to get external internet access [to install app's from internet
Current host config
XP
Dynamic IP
host subnet 255.255.255.0
Host gateway 192.168.1.1
code....
I have a distro-neutral VirtualBox shell install: VirtualBox-xxx.run
you type: sh VirtualBox-xxx.run install
this goes through but the screen says "could not compile the kernel module vboxdrv.ko, see the install log"
the install log in /var/log says this:
test -e include/linux/autoconf.h -a -e include/config/auto.conf
echo " ERROR KErnel configuration is invalid
echo " include/linux/autoconf.h or include/config/auto.conf are missing
echo " run 'make oldconfig && make prepare' on kernel src to fix it"
ok, I've left out a bunch of stuff but, NO these 2 files are NOT missing. I have all the required compile-type packages and the source and headers. Under /usr/src there are :
1: /linux-2.6.31.12-0.2
2: /linux-2.6.31.12-0.2-obj
3: /linux/obj
4: linux
num 4 is a symbolic which points to 1:. num 3 has a sub-dir /i386/default which links to the /default in 2:
the supposed missing files are in sub-dir in 2:
This is what I did. I changed num 4: to point to 2:, deleted all the vbox stuff and re-tried install - still same result.
I reset num 4: to point to 1: and did the "make oldconfig && make prepare". This put new sub-dir entries under 1: with the 2 files in correct sub-dirs. Delete vbox and try re-install - still same result.
Some things I left out of the error log at the start show that the install's use of "make" relates to both dirs 1: and 2: so even with both having the files the install is still barfing.
Perhaps related to this, at the log end there are errors about the /tmp/vbox and some SUPdrv.c files.
I looked in the forums and there are suggestions wrt errors about these missing files that the fault lies with kernels 2.6.33 which puts these missing files in a different named sub-dir - /generated. Well as you see above, kernel is a 2.6.31
There's supposed to be a command line option for the shell install where you add " -- xxxxx " where xxxxx is extra instructions. I tried to put definitive pointers to the sub-dirs involved there but not successful.
I am trying to setup a virtual machine on virtualbox on slack64 13.1. It's purpose is to be gateway pc, so the vm's are only gonna be here until a VM server will be setup - but that could easily complete after 2 months. The test-phase setup is that this gw () is part of the internal network and I have only attached 1-2 clients that it serves (ie these clients belong to a 2nd level internal network). I do most of the setup by ssh'ing from the INET if (my pc is also part of the internal network and not of the 2nd level one).
As fas as my vm in vbox is concerned, I have setup a bridged connection to eth0 (the LOCAL if), since I'm gonna be running a printer server out of that vm (so NAT'ing would perplex the setup) The problem is that all of a sudden, when virtualbox is running the INET if gets broken, and I lose connection to the gw, from the INET side only! the LOCAL if is still working, the 2nd level clients are working fine. Locally, I can do
[Code]...
I doesn't occur when I do something specific but it is a frequent crash nevertheless. I can push my luck too; from the INET side of the gw I had :-an ssh session open, -an X session open - so that I could have access to the gui of virtualbox application and my running vm. -an ssh tunnel on port 139 in order to bypass the gw's firewall and get access to some samba shares on the gw. I tried 3 times to copy a 2GB iso image from my pc to the gw and all 3 times the INET if broke. Finally, if i disable start up of the virtualbox and restart the machine, the problem doesn't occur.. (i'm 16h without virtualbox and the INET if hasn't broken - the same was true before I started setting up my vm).Has anyone experienced problems with virtualbox and the physical interfaces? Especially when using bridged virtual interfaces?
have the latest Vbox installed on CentOS 5.4, i have a XP home VM & Server 2003 VM set up. Im using the T1000 Emulated network driver and only getting 100-150mbps throughput when checked with QCheck. I tried the virtio-net (paravirtualized) drivers and only getting 50-90mbps using it, which i found odd. Is there any way i can increase the througput to my VMs? I seen some people on forums talking about getting 300-350mbps, but im no where close to that. When i check throughput to the host (CentOS) i get at least 800 mbps.
View 2 Replies View Related