Custom Query (16363 matches)
Results (289 - 291 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9282 | duplicate | virtualbox 4.1.0 vboxdrv causes kernel panic when hibernating with Linux 2.6.36 + tuxonice | ||
| Description |
I'm using Linux kernel 2.6.36 patched with the latest tuxonice. The virtualbox modules I have were generated with /etc/rc.d/vboxdrv setup . When I attempt to hibernate, the kernel panics during the "Doing atomic copy/restore" portion. The image has already been created by this point, and attempting to resume from it also causes a panic. Attempting to hibernate without vboxnetadp or vboxnetflt inserted, but with vboxdrv has the same results. Attempting to hibernate with none of the vbox modules inserted is successful, as is resuming from this image. There is no problem hibernating or resuming from an image with the drivers from virtualbox-4.0.8 inserted. $ uname -a Linux localhost 2.6.36-tuxonice-r4 #7 SMP PREEMPT Sun May 15 05:48:12 EDT 2011 i686 Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz GenuineIntel GNU/Linux What other information would be found useful to resolve this? |
|||
| #7908 | fixed | virtualbox 4.0 crashes - linux host - vboxnetflt => Fixed in SVN | ||
| Description |
Just upgraded to virtualbox 4.0 from 3.2.10. Tried to start my VM's and immediately got a kernel panic (attached) Linux host, debian kernel 2.6.26-2-686 |
|||
| #8209 | wontfix | virtualbox 4 does not migrate old vms | ||
| Description |
there may be a reason for this, but on the surface it seems to create a confusing split situation. New VMs are created in the new location and file structure of version 4.x, and while it reads the old VMs from the old location and structure, it does not migrate or upgrade them. This results in storage of VMs in two locations instead of one which is not optimal. |
|||

