Perryg wrote:Debian Version 5.03 64 bit (net install) installed and works fine on (Ubuntu 9.04 64 bit). I will monitor the kernel today but it looks like it is fairly stable in VBox 3.0.6.
But as Sasquatch said there have been reports of 64 bit problems in 3.0.6 that affect some and not others. Most of them on 32 bit host though IIRC.
I mean Debian is completely useable, it just gives that kernel error... Should I even care...?
(Also I can't run the 32bit version because won't virtualbox not let me 64 and 32bit together?)
Also I am on a Windows host you said you tried it on Jaunty Jackalope, which could be a problem.
I started getting the kernel error today as well but have not tracked it down.
Everything seems to work but at boot the error pops up. I am working on isolating it down though.
My logs showed an avahi error as well so it has something to do with Debian and not VBox. Hang in there I should be able to find out what is going on.
Perryg wrote:I started getting the kernel error today as well but have not tracked it down.
Everything seems to work but at boot the error pops up. I am working on isolating it down though.
My logs showed an avahi error as well so it has something to do with Debian and not VBox. Hang in there I should be able to find out what is going on.
Apparently virtual box 3.0.8 just came out. I am trying that now
Perryg wrote:I did and it still did. I really think it has something to do with the Debian kernel, but will know more tomorrow.
Yeah still have the same problem. I hope they fix it, I am trying to switch my Ubuntu vms to Debian since Debian uses quite a bit less resources. I mean everything works, but I don't know how long everything will work
jigglywiggly wrote:I mean Debian is completely useable, it just gives that kernel error... Should I even care...?
(Also I can't run the 32bit version because won't virtualbox not let me 64 and 32bit together?)
Also I am on a Windows host you said you tried it on Jaunty Jackalope, which could be a problem.
You can run 32 bit Guests along side 64 bit Guests. The only point that you have to take into account is that when you run them simultaneous, you need to enable Hardware-V for the 32 bit Guest too. You can't run software and hardware virtualization at the same time.
I have this on 64 and 64. So I am not sure that is all there is to it. It appears that something is getting loaded and then fails thus the error.
Then reloaded after the error and that is why it actually works. Probably why it still works OK. Anyway at this point it appears to not suffer from this except the initial Kernel Panic.
This is the warning that is causing the kernel panic warning, and is the exact same warning that I am getting. It does not appear to effect the way that Debian 5 works and is (IMHO) simply the way it detects everything. Since this is virtualized, I am not sure what the warning actually is getting at. You really have (2) choices here. (1) report this to Debian and/or bugtracker, or (2) the next time you see the error tell it to never send error messages and be done with it.
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] WARNING: strange, CPU MTRRs all blank?
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] ------------[ cut here ]------------
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] WARNING: at arch/x86/kernel/cpu/mtrr/main.c:696 mtrr_trim_uncached_memory+0x18d/0x198()
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] Modules linked in:
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] Pid: 0, comm: swapper Not tainted 2.6.26-2-amd64 #1
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000]
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] Call Trace:
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] [<ffffffff80234a2c>] warn_on_slowpath+0x51/0x7a
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] [<ffffffff80235481>] printk+0x4e/0x56
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] [<ffffffff802181b3>] post_set+0x46/0x52
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] [<ffffffff80587015>] get_mtrr_state+0x2f1/0x2fd
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] [<ffffffff8042a2dd>] _spin_lock_irqsave+0x16/0x30
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] [<ffffffff8057d79f>] do_early_param+0x37/0x7d
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] [<ffffffff80586aa5>] mtrr_trim_uncached_memory+0x18d/0x198
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] [<ffffffff80586c3d>] mtrr_bp_init+0x18d/0x198
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] [<ffffffff80583c8a>] setup_arch+0x2c5/0x580
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] [<ffffffff80592718>] cgroup_init_subsys+0x48/0xaa
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] [<ffffffff8057dafb>] start_kernel+0x7a/0x35c
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] [<ffffffff8058e5d6>] cleanup_highmap+0x5d/0x78
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] [<ffffffff8057d459>] x86_64_start_kernel+0x25e/0x267
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000]
Oct 4 16:01:56 Apache-Server-Backup kernel: [ 0.000000] ---[ end trace 4eaa2a86a8e2da22 ]---
Searching other virtual programs it appears to be a common issue and some have created filters to suppress this notification. I have noticed this only in the actual Debian OS and not in any of the others that I have tested, so I would go the Debian route to see if there is something that you can do to stop seeing this error. http://www.google.com/search?q=warning+ ... +all+blank
