You are not logged in.
I'm running an XP Pro guest OS on my Archx86_64 host and have observed some really quirky behaviors with SMP enabled. Mainly, the guest OS is very choppy and takes much longer to accomplish tasks with 2, 3, or 4 CPUs enabled than it does with just 1. Even booting takes 2-3x longer
My host machine is an X3360 (Xeon quad). I don't think SMP is ready for primetime use just yet but wanted to soliciate some feedback from others. Please post your experiences using SMP under VB 3.0.0 here.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
virtualbox 3 is incredibly slow and unstable. With more than 1 CPUs is even more slower. Downgrade to version 2...
Last edited by cinan (2009-07-04 11:57:08)
Offline
Same over here.
Core2Duo E4500@2.2Ghz, 320HDD, 2GB, GF7100GS, WinXP Guest.
unfortunately I had to rollback to vmware. I _do need_ stability and vbox started to let me down since 2.2.
They say that if you play a Win cd backward you hear satanic messages. That's nothing! 'cause if you play it forwards, it installs windows.
Offline
I have reported about that in AUR (and requested the maintainer for a 2.2.4 pkgbuild which the maintainer kindly provided) and other thread here on the forum.
Virtualbox 3 is still too unstable for serious work as of yet, they have introduced many new things in this new version, just stick with vbox 2 for a while and keep giving vbox 3 a go until you don't have problems and can keep it.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
@Rookie - yeah, I kept the PKGBUILD from 2.2.4 as well and have downgraded to it.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Works fine here.
Excuse my poor English.
Offline
i can confirm the flakness
from documentation:
Chapter 13. Known limitations
The following section describes some issues that are known not to work in VirtualBox 3.0.0. Unless marked otherwise these issues are planned to be fixed in later releases.
* The following Guest SMP (multiprocessor) limitations exist:
o Bad performance with 32-bit guests on AMD CPUs. This affects mainly Windows and Solaris guests, but possibly also some Linux kernel revisions.
o 64-bit guests on 32-bit hosts do not support SMP yet (except on Mac OS X).
* 64-bit guests on some 32-bit host systems with VT-x can cause instabilities to your system. If you experience this, do not attempt to execute 64-bit guests. Refer to the VirtualBox user forum for additional information.
mmmh...
Arch64 on intel core here with 32bit guest. a pain with anything else than 1 processor.
I think there is more problems than those issued in chapter 13. maybe only on cases of different architecture host-guest?
Offline
@Rookie - yeah, I kept the PKGBUILD from 2.2.4 as well and have downgraded to it.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Hello all, I have sucessfully removed VirtualBox v3 but then when I try and install VirtualBox v2 I get the following error about the Kernel module.
VirtualBox has been installed successfully, but the kernel module could not
be built. When you have fixed the problems preventing this, execute
/etc/init.d/vboxdrv setup
as administrator to build it.
I am running an x86-64 in KDEMod. I have obtained the v2 from the VirtualBox website under other OS
Can anyone assist please? Thanks
Offline
archP4 - this thread is a year old. Are you experiencing the issue reported by the OP with the most recent Virtualbox release i.e. 3.2.6?
Offline
FYI - 3.2.6 is great for SMP.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
...and to build the kernel module you need the package 'kernel26-headers' installed.
You should probably read the wiki rather than resurrect old and irrelevant threads.
Offline
I followed the instructions in this thread so thought it would make sense to bump it, rather than start the whole discussion again.
sandman - it builds the kernel OK for version 3 but not 2. This is not an issue covered in the Wiki
Offline
I followed the instructions in this thread so thought it would make sense to bump it, rather than start the whole discussion again.
you say you are trying to build a version from the 'other OS' section on the virtualbox website, so you didn't follow the instructions in this thread since nobody advised you to do so.
this topic is about flaky smp performance under virtualbox 3.0.0, is that exactly what you are experiencing?
sandman - it builds the kernel OK for version 3 but not 2. This is not an issue covered in the Wiki
as graysky said, version 3.2.6 can't be compared to 3.0.0. then, if you really want to build 2.x, start by trying one of the aur packages and report there if you have build problems.
ᶘ ᵒᴥᵒᶅ
Offline
archP4 wrote:I followed the instructions in this thread so thought it would make sense to bump it, rather than start the whole discussion again.
you say you are trying to build a version from the 'other OS' section on the virtualbox website, so you didn't follow the instructions in this thread since nobody advised you to do so.
You're being pedantic.
The link in the instructions is to the i686 version and I have already advised I am using x86-64
I will seek assistance elsewhere
Offline
You're being pedantic.
and you're being a smartass
The link in the instructions is to the i686 version
no it isn't
ᶘ ᵒᴥᵒᶅ
Offline
ArchP4 - people are trying to help you here, but they will stop doing so if you don't answer their questions. For example, you still haven't answered my question in post #10 above.
You should also note that as this is the Arch forum, it is strongly recommended that you do things the Arch way - in this case, that means building an Arch package for Virtualbox with makepkg, and installing that package with pacman.
litemotiv - don't insult people in this forum. If you encounter behaviour that you believe is unacceptable, report it to the moderator team.
Offline