Problem in VirtualBOX.

I got a problem in VirtualBOX, hope someone can help me.
Why is my mouse (or touch pad) response sluggish when I installing the Window 7 (or Ubuntu 10.4) in VirtualBOX ?
the host OS works fine but VirtualBOX.
I share 4GB memory and 128MB video memory to VirtualBOX, is it any setting I should change ?
PS : My NB is Macbook Pro 15" i7. (8GB memory)
Thanks in advance ~ ^^

I have used VB on my MBP for some time and have Win7 (64bit), Win2000 and Ubuntu virtual machines all working well.
I suspect that you may have allocated all CPU cores to each VM. I found that will cause the whole machine to become sluggish. I reduced the numbers of cores to: Win7, two (of four on my MBP), and; Win2000 and Ubuntu, one each.
Of course, only have one machine, including the MBP, doing heavy processing at once.
Also keep in mind that installing an operating system is CPU intensive.
Hope that helps.

Similar Messages

Problems in VirtualBox with Plasma

Hi there,
I recently set up a fresh arch install in Oracle VirtualBox (4.3.22)(host is Windows 7 64bit) with having installed xorg, sddm and plasma-meta for a desktop environment. I basically followed the Beginners Guide and Installation steps for Arch Linux guests. Thanks to that info a lot is already working fine (writing this from within the VM) but I'm having a few issues and don't really know how to go on.
Most prominently, the autoresize feature of virtualbox isn't working (neither is fullscreen or seamless mode correctly), and Display Configuration in System Settings is only offering me quite a limited and impractical set of resolutions.
I enabled the vboxservice and made and linked an autostart script in ~/.config/autostart/ that calls 'VBoxClient --clipboard --display --checkhostversion'
[psifi@archolamin ~]$ systemctl status vboxservice.service -l
● vboxservice.service - VirtualBox Guest Service
Loaded: loaded (/usr/lib/systemd/system/vboxservice.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2015-02-27 00:33:38 CET; 2min 15s ago
Process: 184 ExecStartPre=/usr/bin/modprobe vboxsf (code=exited, status=0/SUCCESS)
Process: 179 ExecStartPre=/usr/bin/modprobe vboxvideo (code=exited, status=0/SUCCESS)
Process: 176 ExecStartPre=/usr/bin/modprobe vboxguest (code=exited, status=0/SUCCESS)
Main PID: 189 (VBoxService)
CGroup: /system.slice/vboxservice.service
└─189 /usr/bin/VBoxService -f
Feb 27 00:33:38 archolamin VBoxService[189]: VBoxService 4.3.22_OSE r98236 (verbosity: 0) linux.amd64 (Feb 18 2015 21:08:37) release log
Feb 27 00:33:38 archolamin VBoxService[189]: 00:00:00.000080 main Log opened 2015-02-26T23:33:38.884466000Z
Feb 27 00:33:38 archolamin VBoxService[189]: 00:00:00.000190 main OS Product: Linux
Feb 27 00:33:38 archolamin VBoxService[189]: 00:00:00.000228 main OS Release: 3.18.6-1-ARCH
Feb 27 00:33:38 archolamin VBoxService[189]: 00:00:00.000263 main OS Version: #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015
Feb 27 00:33:38 archolamin VBoxService[189]: 00:00:00.000296 main OS Service Pack: #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015
Feb 27 00:33:38 archolamin VBoxService[189]: 00:00:00.000333 main Executable: /usr/bin/VBoxService
Feb 27 00:33:38 archolamin VBoxService[189]: 00:00:00.000334 main Process ID: 189
Feb 27 00:33:38 archolamin VBoxService[189]: 00:00:00.000335 main Package type: LINUX_64BITS_GENERIC (OSE)
Feb 27 00:33:38 archolamin VBoxService[189]: 00:00:00.001657 main 4.3.22_OSE r98236 started. Verbose level = 0
[psifi@archolamin ~]$ lsmod | grep vb
vboxsf 41351 0
vboxvideo 12437 1
drm 263481 3 vboxvideo
vboxguest 206333 5 vboxsf
[psifi@archolamin ~]$ pgrep -a VB
189 /usr/bin/VBoxService -f
392 /usr/bin/VBoxClient --clipboard
393 /usr/bin/VBoxClient --clipboard
405 /usr/bin/VBoxClient --display
414 /usr/bin/VBoxClient --seamless
415 /usr/bin/VBoxClient --seamless
421 /usr/bin/VBoxClient --draganddrop
422 /usr/bin/VBoxClient --draganddrop
Everything seems to be running and other features do work (like the shared clipboard) but not the resolution thingy. Also, something already seems a little weird, notice the multiple VBoxClient instances shown by pgrep. Now it get's more funny.
After some extended but fruitless searching and analyzing I tried to disable all vbox components to get to the root of the problem. But:
## 2 modules get loaded and I don't know why
[psifi@archolamin ~]$ systemctl status vboxservice.service
● vboxservice.service - VirtualBox Guest Service
Loaded: loaded (/usr/lib/systemd/system/vboxservice.service; disabled; vendor preset: disabled)
Active: inactive (dead)
[psifi@archolamin ~]$ ls -l /etc/modules-load.d/
total 0
[psifi@archolamin ~]$ lsmod | grep vb
vboxguest 206333 3
vboxvideo 12437 1
drm 263481 3 vboxvideo
## VBoxClients still running and I don't know why
[psifi@archolamin ~]$ ls -l .config/autostart/
total 0
[psifi@archolamin ~]$ pgrep -a VB
380 /usr/bin/VBoxClient --display
1103 /usr/bin/VBoxClient --display
1345 /usr/bin/VBoxClient --clipboard
1346 /usr/bin/VBoxClient --clipboard
1358 /usr/bin/VBoxClient --display
1366 /usr/bin/VBoxClient --seamless
1368 /usr/bin/VBoxClient --seamless
1372 /usr/bin/VBoxClient --draganddrop
1373 /usr/bin/VBoxClient --draganddrop
I really don't understand what's going on here. Killing and restarting the VBoxClient processes doesn't seem to make a difference (except removing the duplicates). Oh, and there also is, possibly related:
[psifi@archolamin ~]$ cat /var/log/Xorg.0.log | grep EE
[ 655.104] Current Operating System: Linux archolamin 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 655.125] (EE) systemd-logind: failed to get session: PID 1177 does not belong to any known session
[ 655.134] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 655.134] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 655.978] (EE) AIGLX error: vboxvideo does not export required DRI extension
[ 655.978] (EE) AIGLX: reverting to software rendering
[ 656.038] (II) XINPUT: Adding extended input device "VirtualBox mouse integration" (type: TOUCHSCREEN, id 9)
(3D acceleration in the preferences of the vm is disabled because for me with it enabled plasma was hardly working at all, completely unusable)
So I wonder
Why is the resizing and screen resolution in general not working as intended? Probably something to do with the video driver?
Why or where are the modules and VBoxClient loaded?
I hope somebody can point me in the right direction. Maybe plasma 5 simply isn't ready enough yet for this to work? I've read somewhere that it uses quite a different graphics architecture, but for me this stuff still feels a bit over my head
On a side note - other problems that I haven't really looked into yet:
(*) switching tty completely destroys plasma session
(*) scrolling with mousewheel sometimes is "hanging" or even going in the opposite direction

arcaloid wrote:
however I have turned off 3d acceleration in the configuration of the vm (because otherwise plasma5 only was a flickering mess so far) and hence it isn't supposed to be 3d accelerated anyway, right?
the resolution issue has recently resolved on it's own over the course of a few system updates, but numerous other issues keep coming and going instead. I guess that's just the thing with bleeding edge software.
If it's any consolation, the problem with Plasma 5 and "vboxvideo" happens here as well. The host system is Linux from Scratch and KDE4 worked flawless as a VirtualBox (4.3.26) Arch.x86_64 guest system. Just a few hours ago, I took the plunge and switched to Plasma 5 on a fully-updated Arch platform with kernel 3.19.2 and all the latest Xorg and Mesa packages.
It was necessary to disable "3D Acceleration" for the system to be usable. Prior to doing so, the display looked nice and pretty but all input events (mouse and keyboard) were not recognized. Plus the bottom-screen panel was not visible.
For what it's worth, KaOS.x86_64 was tried a month ago on VirtualBox. Its Plasma 5 environment was totally unusable with or without "3D Acceleration". Problems ranged from a black screen with only the Oxygen mouse cursor to erratic, flashing video.
Frankly, I still consider KF5/Plasma 5 to be in a state of flux (to put it kindly). I have successfully built and installed it on my LFS platform with zero errors during the compile process. But at launch time, all that occurs is a black screen with the Oyxgen mouse cursor. That said, sddm works fine and I'm now using it for my display manager rather than KDM.
I think KF5/Plasma 5 show great potential but like its KDE4 predecessor (which I love), it'll take some time to mature.

Problems patching VirtualBox s10x_u8 BE

Hi,
I'm having problems patching a VirtualBox Solaris 10 x86 environment with the latest patch cluster from December.
I've unloaded the zip file in /var/tmp and attempted to apply-prereq to the current BE prior to the ABE. This fails during the checkinstall process for 119255-71 (patching of patchadd etc). These are the first patches applied to this s10x_u8 install - the only additional pkg is SUNWvboxguest.
It reports:
/var/tmp/10_x86_Recommended/patches/119255-71/SUNWinstall-patch-utils-root/install/checkinstall: /var/tmp/10_x86_Recommended/patches/119255-71/SUNWinstall-patch-utils-root/install/checkinstall: cannot open
pkgadd: ERROR: checkinstall script did not complete successfully
I've tried applying this patch outside 'installcluster' using patchadd and the same issue is reported.
I cannot see anything obvious in any of the 'readme's and checked a number of solutions regarding loopback filesystems etc.
Are there any further methods of debugging this issue and does anyone know why this patchadd is not working?

Hi Darren,
Thanks for that - I think I've seen this one before (before Solaris 10) and never twigged that it would/could back to haunt me!
# echo<span style="color:#000000"> "install:x:0:1:installpatch braindamage:/:/bin/true"</span> >> /etc/passwd
# pwconv
# cd /tmp
# patchadd 119255-71
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
119255-71
Checking installed patches...
Executing prepatch script...
Installing patch packages...
Patch 119255-71 has been successfully installed.
See /var/sadm/patch/119255-71/log for details
Executing postpatch script...
Patch packages installed:
SUNWinstall-patch-utils-root
SUNWpkgcmdsr
SUNWpkgcmdsu
SUNWswmt
# userdel installI then deleted the user and continued the patching of the alt BE - It did not appear to require the user for the remaining pre-req patches or the other BE!
# cd /var/tmp/10_x*
# ./installcluster --apply-prereq --s10cluster
Setup .......
Solaris 10 x86 Recommended Patch Cluster (2010.01.06)
Application of patches started : 2010.01.14 16:48:36
Applying 120901-03 (1 of 9) ... skipped
Applying 121334-04 (2 of 9) ... skipped
Applying 119255-71 (3 of 9) ... skipped
Applying 119318-01 (4 of 9) ... skipped
Applying 121297-01 (5 of 9) ... skipped
Applying 122035-05 (6 of 9) ... skipped
Applying 127885-01 (7 of 9) ... skipped
Applying 141589-03 (8 of 9) ... skipped
Applying 142252-01 (9 of 9) ... skipped
Application of patches finished : 2010.01.14 16:49:01
Following patches were skipped :
Patches already applied
120901-03     119255-71     121297-01     127885-01     142252-01
121334-04     119318-01     122035-05     141589-03
Installation of prerequisite patches complete.
Install log files written :
/var/sadm/install_data/s10x_rec_cluster_short_2010.01.14_16.48.36.log
/var/sadm/install_data/s10x_rec_cluster_verbose_2010.01.14_16.48.36.log
# lustatus
Boot Environment           Is       Active Active    Can    Copy
Name                       Complete Now    On Reboot Delete Status
s10x_u8a                   yes      no     no        yes    -
s10x_u8b                   yes      yes    yes       no     -
# ./installcluster -B s10x_u8a --s10cluster
Setup ............
Solaris 10 x86 Recommended Patch Cluster (2010.01.06)
Application of patches started : 2010.01.14 16:50:59
Applying 120901-03 ( 1 of 172) ... skipped
Applying 121334-04 ( 2 of 172) ... skipped
Applying 119255-71 ( 3 of 172) ... success
Applying 119318-01 ( 4 of 172) ... skipped
...I'll add a further update once the other 172 patches have been tried and whether the BE boots or not.
Regards, Clive

Problems with Virtualbox

Hey Guys.
I'm runned into a problem with my Virtualbox installation about the network setup.
Followed the guide http://wiki.archlinux.org/index.php/VirtualBox#Usin
But each time I'm starting my Virtualbox - I'm getting the this error:
Failed to initialize Host Interface Networking.
VBox status code: -3100 (VERR_HOSTIF_INIT_FAILED).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}
How can I make bridged network to work here - and can someone tell me the error:
/etc/conf.d/bridges:
bridge_br0="eth0 wlan0"
BRIDGE_INTERFACES=(br0)
Lines from rc.conf:
MODULES=(sky2 iwl4965 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore vboxdrv autofs4 bridge)
eth0="dhcp"
wlan0="dhcp"
br0="dhcp"
ppp0="dhcp"
INTERFACES=(eth0 wlan0 br0 ppp0)
/etc/vbox/interfaces ( needed to make that file manually)
vbox0 pbj br0
I've installed bridge-utils and the obnly error i'm getting is this - each time I set the network settings in the virtualbox guest machine settings to host interface???
What Am I doing wrong. - since I only have these options from the menu
Not connected.
NAT
Host INterface
Internal Interface
From my dmesg:
vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: Successfully done.
vboxdrv: Found 2 processor cores.
vboxdrv: fAsync=0 offMin=0x18f offMax=0x979
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 2.0.0 (interface 0x00090000).
Bridge firewalling registered
firmware: requesting iwlwifi-4965-1.ucode
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
sky2 eth0: enabling interface
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control rx
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): wlan0: link is not ready
eth0: no IPv6 routers present
vbox0: no IPv6 routers present
Can someone point me in the rigth direction???

Well a little bit further I guess.
put tun into MODULES
Made this scripts as from alehtos
sudo brctl addbr br0
sudo ifconfig eth0 0.0.0.0 promisc
sudo brctl addif br0 eth0
sudo dhclient br0
sudo chmod 0666 /dev/net/tun
sudo tunctl -t tap0 -u *username*
sudo ifconfig tap0 up
sudo brctl addif br0 tap0
And gives me this:
$ ifconfig
br0 Link encap:Ethernet HWaddr 00:1D:09:42:99:7F
inet addr:172.16.50.200 Bcast:172.16.51.255 Mask:255.255.254.0
inet6 addr: fe80::21d:9ff:fe42:997f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1888 errors:0 dropped:0 overruns:0 frame:0
TX packets:752 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:674889 (659.0 Kb) TX bytes:134636 (131.4 Kb)
eth0 Link encap:Ethernet HWaddr 00:1D:09:42:99:7F
inet6 addr: fe80::21d:9ff:fe42:997f/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:54932 errors:0 dropped:0 overruns:0 frame:0
TX packets:24515 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:43322296 (41.3 Mb) TX bytes:2325893 (2.2 Mb)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:136 errors:0 dropped:0 overruns:0 frame:0
TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4108 (4.0 Kb) TX bytes:4108 (4.0 Kb)
tap0 Link encap:Ethernet HWaddr 00:FF:B0:92:FE:4A
inet6 addr: fe80::2ff:b0ff:fe92:fe4a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:172 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 b) TX bytes:60 (60.0 b)
wlan0 Link encap:Ethernet HWaddr 00:1F:3B:61:C9:27
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmaster0 Link encap:UNSPEC HWaddr 00-1F-3B-61-C9-27-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
And this works as the following way - Gives the Host machine a IP adress - but not the guest. On the guest - it cannot get an IP address.
Could this error hove something to do with it all:
s# /etc/rc.d/vboxnet restart
shell-init: error retrieving current directory: getcwd: cannot access parent directories: Ingen sådan fil eller filkatalog
:: Shutting down VirtualBox host networking [DONE]
:: Starting VirtualBox host networking [DONE]
Last edited by peque (2008-09-18 13:19:12)

Usb problem with VirtualBox 4.1.2.

Hello all
I have a usb problem with my VirtualBox 4.1.2.
I installed VirtualBox 4.1.2 with VirtualBox Extension Pack 4.1.2. on vista 64 bit host
but when I run Win 2003 guest I get the following :
Failed to access the USB subsystem.
Could not load the Host USB Proxy Service
(VERR_FILE_NOT_FOUND). The service might not be
installed on the host computer.Can any one help on how to resolve this ?

I too an facing the same problem.
if u have some solution then plz mail it to me.
regards
Dinesh Singh
Nucleus Software Exports Ltd
[email protected]

[Solved] problem with virtualbox-iso-additions for virtualbox v. 4.2

VirtualBox 4.2 was released recently and one of the features mentioned is support for Mac OSX. However, having installed it (an Arch virtualbox 4.2 host, and an osx guest), I found that I couldn't install guest additions via the devices menu on my osx guest. Whereupon I examined the file corresponding to virtualbox-iso-additions (/usr/lib/virtualbox/additions/VBoxGuestAdditions.iso) and found that in fact there were no scripts or drivers for osx (darwin) like there are for windows and linux. Is it possible that the Arch release of this file has not been updated properly or am I missing anything else?
Update: I downloaded the current iso (VBoxGuestAdditions_4.2.0.iso) from http://download.virtualbox.org/virtualbox/4.2.0/ and found that that too has no files that appear linked to osx or darwin. That rules out an Arch packaging issue and I'll need to pursue things at virtualbox.org itself.
Last edited by kinleyd (2013-07-18 12:03:48)

I think I've figured it out, finally. It seems v. 4.2 introduces virtualbox on a mac osx host. osx guests are apparently not officially supported with guest additions. I had assumed that host support already existed, and that the new stuff in v. 4.2 was for guests.

Major mouse problems in Virtualbox 3.0.2

I'm running an Arch Linux VM running on VB version 3.0.2 running under an Arch Linux host (both x86_64 if that matters). As you x86_64 guys know, one must use thotypous's package in the AUR for VB on x86_64. Anyway, the VM boots up just fine and is fully functional, except that the mouse in the VM simply stops working after a while. It seems to be stuck and invisible trapped in the lower right of the screen; my only option is to restart the VM.
Has anyone else experienced something similar?

I ended-up nuking my VM and hdd file, rebuilding it from scratch and am experiencing exactly the same issue w/ the mouse. Everything is fine in my XP VM, it's just my Arch x86_64 VM that has this damn mouse problem!

Problem with VirtualBox Appliance Image Solaris 10 10/09 (solaris_10_u8)

I'm running Virtualbox 3.1.2 r56127 on Mac OS X Leopard 10.5.8. I click File > Import Appliance and choose solaris_10_u8.ovf. I leave all the default settings and click Import. I then receive the error "Cannot register the machine 'Solaris_10_u8' because it has 2 medium attachments" (screenshot[1]).
I've just tried the same thing on Mac OS X Snow Leopard 10.6.2 and it imports correctly.
Is it by design that this will not work on Virtualbox under Leopard, or am I doing something else wrong?
Cheers, Chris
[1] http://skitch.com/chrisroos/nuan7/virtualbox

There is nothing in the s10 10/09 appliance image that would cause it to work or fail on a specific OS. I suggest you visit the forums at virtualbox.org and see if someone might be able to help there.
-- Alan

Problem with VirtualBox

I installed Virtualbox following the wiki. Add my user to the vboxusers group. Added vboxdrv to Modules in /etc/rc.conf. But when I start the program it gives me the tollowing error "The vboxdrv kernel module is not loaded".
I also tried modprobe vboxdrv, just in case I did something wrong in the rc.conf file, but it says the following "bash: modprobe: command not found".
Any help, would be appreciated.
Cheers.

IlPrincipino wrote:
wonder wrote:fix your shell configuration. ~/.bashrc ~/.bash_profile
Thanks. But it says the following now: sudo: /home/user/.bashrc: command not found
Please post the commands you're issuing, not only the output.
Running
sudo /home/user/.bashrc
doesn't make sense as .bashrc is a config file, not a program. You need to edit it, e.g.
sudo vim /home/user/.bashrc
Edit: And you should be using your user name ('karol' for me), not 'user' literally.
Last edited by karol (2011-12-15 14:00:17)

Strange fonts problem in VirtualBox

Hello!
I've got some strange font artifacts, could anyone suggest something?
http://imagebin.ca/view/WJVkiH2n.html

I have used VB on my MBP for some time and have Win7 (64bit), Win2000 and Ubuntu virtual machines all working well.
I suspect that you may have allocated all CPU cores to each VM. I found that will cause the whole machine to become sluggish. I reduced the numbers of cores to: Win7, two (of four on my MBP), and; Win2000 and Ubuntu, one each.
Of course, only have one machine, including the MBP, doing heavy processing at once.
Also keep in mind that installing an operating system is CPU intensive.
Hope that helps.

VirtualBox 4.0.2 internal DHCP problem in Host-only mode?

Hi,
dos anyone have experience problems with VirtualBox 4.0.2 internal DHCP not working when running Oracle Linux and a Host-Only adapter.
More detailed described my problem is that Oracle Linux don't get a ip from the internal DHCP server om my system. My host is Win 7 (64 bit) and Guest Oracle Linux (64 bit). I have read that there are several ohers who experienced the same problem with the open source version, but that patching the Guest Tools to 4.0.3 helped them. Sadly this is not the case for me. Any suggestions are welcome and thanks in advance.

Thanks for your reply - my problem is that the build in dhcp server is not working for some reason and i dont't gen any ip address assigned. I can see from the VBoxManager that it is running, but i can't get i contact with it from the linux guest.

Problem upgrading and installing virtualbox-modules

Have some problems upgrading and installing virtualbox-modules
[elgringo@compjotr Desktop]$ sudo pacman -S community/virtualbox-modules
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: lirc: requires kernel26>=2.6.26-1
:: nvidia: requires kernel26>=2.6.26-1
Had to uninstall lirc nvidia and virtualbox-modules before I could upgrade the kernel and now I can't install the virtualbox-modules.
Anyone else who experienced the same problems?

virtualbox-modules depends on the kernel in core. If you want to use the kernel in testing, you'll need to rebuild the virtualbox-modules against it.
Virtualbox-modules will be fixed when kernel 2.6.26 will be moved in core. So you can wait if you prefer.

Virtualbox no longer detects system theme

Hi. I just upgraded all the virtualbox packages. I replaced virtualbox-additions with virtualbox-iso-additions, and virtualbox-modules with virtualbox-host-modules <-- I think those were the replacements. There were two that pacman asked me about and I chose the default answer, which was Y.
I also re-installed the updated virtualbox-ext-oracle from the aur. So, everything still works ok, but the virtualbox manager is not detecting my system theme properly. By properly, I mean that it detects some stuff - for example, the menus and toolbar look right, but the sections with text are giving me white on white. See below,
>>moderator edit: Removed large image. Please read Forum Etiquette: Pasting Pictures and Code. Thanks. --fsckd<<
I used to have the problem that virtualbox wouldn't detect the system theme AT ALL. After reading some threads, I just installed libgnomeui and that fixed the problem, and virtualbox looked just fine up until this recent update.
Anyone know what's going on here?
Last edited by fsckd (2012-09-20 16:43:29)

https://wiki.archlinux.org/index.php/ABS
# pacman -S abs
# abs
$ mkdir -p ~/.builds/virtualbox
$ cp /var/abs/community/virtualbox/* ~/.builds/virtualbox
$ cd ~/.builds/virtualbox
$ makepkg -do
Then have fun poking around in:
"~/.builds/virtualbox/src/VirtualBox-4.2.0/src/VBox/Frontends/VBoxManage/"
"~/.builds/virtualbox/src/VirtualBox-4.2.0/src/VBox/Frontends/VirtualBox/"
When you're done, build and tell pacman to install it with:
$ makepkg -si
Edit: Then again, you should probably ask on their forum or IRC channel (#vbox on freenode).
Last edited by DSpider (2012-09-22 13:33:19)

Virtualbox - install build and header files for your current kernel

I have initially installed virtualbox before upgrading the Arch
Also took backup of the kernle before upgrading since kernel26 2.6.30 is having problem with virtualbox
After upgrading I have configure the grub to use the previous kernel i.e 2.6.28
Later installed xorg and want to install the video drivers from VBox additions
but running
sh VBoxLinuxAdditions_x86.run
i get the following
install build and header files for your current kernel
The current kernel version is 2.6.28 Arch
What are the build and header files I have to install or search with pacman
And since i have upgraded the system will I able to look up the header and build files needed for kernel 2.6.28

dmartins - he's talking about his kernel's headers, not the kernel-headers package - they are two very differnet things.
sant527 - when you backed up the 2.6.28 kernel, did you remember the files in /usr/src/linux-2.6.28-ARCH/ ? They're what VBox is looking for.

VirtualBox freezes computer

I'm trying to use virtualbox ( version 2.2) but everytime I start a virtual machine my computer just freezes. No error messages, no logs... nothing.
Do any of you guys know anything about this problem? Is it a known bug? Couldn't find about it on google
Thanks for your help!

I had a somewhat similar problem, where Virtualbox would randomly crash and reboot my system. Unfortunately I never did find out what was wrong, I couldn't find any error logs and Google had nothing, so I had to simply switch to VMWare. Not a great solution, but I couldn't think of anything else to do. I thought it might be bad RAM or something, but Virtualbox was the only program that did it, I was rather puzzled.

Problem in VirtualBOX.

Similar Messages

Maybe you are looking for