Guys,
kernel26-2.6.37.5-1 running in a virtualbox vm is causing a kernel crash on shutdown. The full screen of the crash is here:
http://www.3111skyline.com/dl/arch/bugs/kernel/vbox-crash-on-shutdown.jpg
The Call Trace: shows the likes of:
shrink_dcache_for_unmount_subtree shrink_dcache_for_unmount generic_shutdown_super <snip>
I'm not great at reading the screens, so if you are interested in the full error, it is shown in the link about.
Has anyone else found a workaround?
David C. Rankin wrote:
Guys,
kernel26-2.6.37.5-1 running in a virtualbox vm is causing a kernel crash on shutdown. The full screen of the crash is here:
http://www.3111skyline.com/dl/arch/bugs/kernel/vbox-crash-on-shutdown.jpg
The Call Trace: shows the likes of:
shrink_dcache_for_unmount_subtree shrink_dcache_for_unmount generic_shutdown_super
<snip>
I'm not great at reading the screens, so if you are interested in the full error, it is shown in the link about.
Has anyone else found a workaround?
-- David C. Rankin, J.D.,P.E.
Are you sure it's a kernel bug? Your screen says segmentation fault in umount, so there must be some bug in that tool, not linux. Also, if the kernel panicks, the system won't shutdown at all. BTW, I recommend using png files instead of jpg. :)
On Tue, Mar 29, 2011 at 10:38 AM, Aljosha Papsch joschi.papsch@yahoo.de wrote:
David C. Rankin wrote:
Guys,
kernel26-2.6.37.5-1 running in a virtualbox vm is causing a kernel crash on shutdown. The full screen of the crash is here:
http://www.3111skyline.com/dl/arch/bugs/kernel/vbox-crash-on-shutdown.jpg
The Call Trace: shows the likes of:
shrink_dcache_for_unmount_subtree shrink_dcache_for_unmount generic_shutdown_super
<snip>
I'm not great at reading the screens, so if you are interested in the full error, it is shown in the link about.
Has anyone else found a workaround?
-- David C. Rankin, J.D.,P.E.
Are you sure it's a kernel bug? Your screen says segmentation fault in umount, so there must be some bug in that tool, not linux. Also, if the kernel panicks, the system won't shutdown at all. BTW, I recommend using png files instead of jpg. :)
doesn't vbox have to be rebuilt everytime the kernel changes or something? or the guest additions? or both?
btw, have you tried KVM + libvirt[virtmanager/<insert one of several good webapps>]? there are a lot of great options out there now -- i haven't had a single issue with my local KVM setup, and am in the process of moving my companies infrastructure to it as well (+ some LXC goodness) ... when i used vbox it was nice, but ... yeah :-)
... libvirt can handle vbox images in transition, too; just an idea, it's been good to me.
C Anthony
C Anthony Risinger wrote:
btw, have you tried KVM + libvirt[virtmanager/<insert one of several good webapps>]? there are a lot of great options out there now -- i haven't had a single issue with my local KVM setup, and am in the process of moving my companies infrastructure to it as well (+ some LXC goodness) ... when i used vbox it was nice, but ... yeah :-)
OT:
Just to vouch for KVM + libvirt (and virtmanager). Implemented it in my company a month or so ago, longer ago personally, and works like a charm. :)
Paulo Santos
Am Tue, 29 Mar 2011 12:26:41 -0500 schrieb C Anthony Risinger anthony@extof.me:
doesn't vbox have to be rebuilt everytime the kernel changes or something? or the guest additions? or both?
When using virtualbox `/etc/rc.d/vboxdrv setup` has to be run after every kernel update on the host system.
And on the guest systems the guest additions have to be updated, too.
Heiko
On 03/29/2011 12:26 PM, C Anthony Risinger wrote:
doesn't vbox have to be rebuilt everytime the kernel changes or something? or the guest additions? or both?
Oh, yes,
If not rebuilt - you won't be able to get the started. Here, the vm runs, but there are shared folder issues and it crashes on shutdown.
This all *started* with kernel26-3.7.4. I can reload kernel26-3.7.3 and all is good. There is something new that vbox doesn't like...
On 03/29/2011 06:56 PM, David C. Rankin wrote:
On 03/29/2011 12:26 PM, C Anthony Risinger wrote:
doesn't vbox have to be rebuilt everytime the kernel changes or something? or the guest additions? or both?
Oh, yes,
If not rebuilt - you won't be able to get the started. Here, the vm runs, but there are shared folder issues and it crashes on shutdown.
This all *started* with kernel26-3.7.4. I can reload kernel26-3.7.3 and all is good. There is something new that vbox doesn't like...
And just to be clear -- this is Arch installed as the "guest". There is something that is causing problems with Arch running inside vbox with kernel26-2.7.4 and kernel26-2.7.5.
Sorry for the "3" kernel typos above :p
On 03/29/11 20:00, David C. Rankin wrote:
On 03/29/2011 06:56 PM, David C. Rankin wrote:
On 03/29/2011 12:26 PM, C Anthony Risinger wrote:
doesn't vbox have to be rebuilt everytime the kernel changes or something? or the guest additions? or both?
Oh, yes,
If not rebuilt - you won't be able to get the started. Here, the vm runs, but there are shared folder issues and it crashes on shutdown.
This all *started* with kernel26-3.7.4. I can reload kernel26-3.7.3 and all is good. There is something new that vbox doesn't like...
And just to be clear -- this is Arch installed as the "guest". There is something that is causing problems with Arch running inside vbox with kernel26-2.7.4 and kernel26-2.7.5.
Sorry for the "3" kernel typos above :p
Kernel versions resemble 2.6.33.2. Or kernel26 package versions resemble 2.6.33.2-1 . Your typoes are much worse than 2 vs 3. :-D
On 03/29/2011 07:25 PM, Isaac Dupree wrote:
Sorry for the "3" kernel typos above :p
Kernel versions resemble 2.6.33.2. Or kernel26 package versions resemble 2.6.33.2-1 . Your typoes are much worse than 2 vs 3. :-D
Oh God -- and I've been doing the books today .... :)
arch-general@lists.archlinux.org