You are not logged in.
I don't know if it's BFS itself or one of my customized options specifically, but if I try to play Netflix inside my Windows XP virtual machine it is terrible and my CPU load is quite high.
If I boot into the stock Arch kernel I do not have this problem. Anyone else experience this?
Offline
Have you recompiled the kernel modules (i.e. virtualbox, nvidia/ATI and whatever else) for your BFS kernel?
Offline
If I could get the kernel26-core2 headers installed I would check this out for you, but IIRC everything was fine for me.
Offline
@OP - I've been running the kernel26-ck package since before I took it over as the maintainer; I also make excessive use of Virtualbox with it and have experienced no issues whatsoever.
@brebs - I think the OP must have compiled the module, else it wouldn't run, no?
@brando - Off topic but as I read your reply, I got the impression that you can't access the repo to install the headers package? Is something wrong? Please contact me via email or in the kernel26-ck repo thread so I can fix if so.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
must have compiled the module, else it wouldn't run
It depends on the config - hopefully "uname -r" is different. If it's the same, the kernel modules might not have been recompiled, and this can sometimes introduce subtle problems, e.g. performance. Since I remember Arch using this unsafe practice (of not changing "uname -r", and also of not recompiling kernel modules unless they *see* a problem), I thought it wise to check.
Edit: I use 2.6.38-pf8 (pf patchset with additional vanilla & Fedora patches, with the binary VirtualBox 4.0.10, with no performance issue.
Last edited by brebs (2011-08-01 07:01:36)
Offline
So it seems like it's just me and my config.
uname -r is different, and I have compiled the kernel modules for it.
It is only in the last few weeks/month that the performance issue is there.
Sometimes, when I run the VM, it'll drop me to TTY1 which a bunch of magic output, but it's not a kernel panic. I can switch back to my graphical TTY and everything is fine except the VM is just a black window and has to be forced to close via my WM.
I'm not sure what kernel config options would do something like this. I have my timer frequency at 1000Hz, which is the main thing I've seen on the Google that can cause problems.
I am on a Core i3 processor with intel graphics.
If I post my kernel config, do you think you'd be able to spot anything that would mess up Virtualbox in this subtle way?
Any ideas? I'm guessing I'm probably on my own.
Offline
I use 300hz, because 1000 seems excessive, especially with >1 core.
Can't think of any kernel options which are "dangerous" for virtualbox.
You might get a better result by posting on the virtualbox forum.
Might help if you take a camera shot of the error message also.
Offline