Crash with latest VirtualBox (Solved )

[[ Xi0N ]]

Code: Select all

Oct  4 19:39:11 VirtualUbuntu kernel: [   26.674166] vboxpci: IOMMU not found (not compiled)
Oct  4 19:39:13 VirtualUbuntu kernel: [   29.124699] bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex
Oct  4 19:39:13 VirtualUbuntu kernel: [   29.221213] bonding: bond0: link status definitely up for interface eth0.
Oct  4 19:39:13 VirtualUbuntu kernel: [   29.221879] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Oct  4 19:39:14 VirtualUbuntu kernel: [   29.611541] bnx2: eth1 NIC Copper Link is Up, 1000 Mbps full duplex
Oct  4 19:39:14 VirtualUbuntu kernel: [   29.620543] bonding: bond0: link status definitely up for interface eth1.
Oct  4 19:39:24 VirtualUbuntu kernel: [   39.554148] bond0: no IPv6 routers present
Oct  4 19:39:32 VirtualUbuntu nss_wins[1082]: step time server 91.189.94.4 offset -0.872747 sec
Oct  4 19:39:48 VirtualUbuntu kernel: [   64.982496] CE: hpet5 increasing min_delta_ns to 15000 nsec
Oct  4 19:39:48 VirtualUbuntu kernel: [   64.982505] CE: hpet5 increasing min_delta_ns to 22500 nsec
Oct  4 19:46:34 VirtualUbuntu kernel: [  470.050464] CE: hpet4 increasing min_delta_ns to 15000 nsec
Oct  4 19:46:34 VirtualUbuntu kernel: [  470.050476] CE: hpet4 increasing min_delta_ns to 22500 nsec
Oct  4 19:46:45 VirtualUbuntu kernel: [  481.419268] warning: `VBoxHeadless' uses 32-bit capabilities (legacy support in use)
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.086545] general protection fault: 0000 [#1] SMP 
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.087077] last sysfs file: /sys/devices/system/cpu/cpu3/online
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.087384] CPU 1 
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.087676] Modules linked in: pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv kvm_intel kvm bonding joydev dell_wmi dcdbas fbcon tileblit font bitblit softcursor vga16fb vgastate bnx2 power_meter lp parport usbhid hid mptsas mptscsih mptbase ahci scsi_transport_sas
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.092856] Pid: 1895, comm: VBoxHeadless Not tainted 2.6.32-34-server #77-Ubuntu PowerEdge R210
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.093287] RIP: 0010:[<ffffc900117dfb82>]  [<ffffc900117dfb82>] 0xffffc900117dfb82
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.093831] RSP: 0018:ffff880224d3bd00  EFLAGS: 00010002
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.094119] RAX: 0000000000000264 RBX: ffffc9001193d340 RCX: 0000000000000000
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.094458] RDX: ffffc9001193d340 RSI: 0000000000000000 RDI: 0000000000000000
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.094797] RBP: ffff880224d3bd58 R08: 000000000001ae80 R09: ffffc9001193d000
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.095135] R10: 0000000000040000 R11: 0000000000000000 R12: 0000000000000000
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.095474] R13: 0000000000000206 R14: ffff88022289c610 R15: ffff880233ef5500
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.095813] FS:  00007f37742d1700(0000) GS:ffff880008e20000(0000) knlGS:0000000000000000
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.096225] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.096525] CR2: 00007f3775698080 CR3: 0000000224ba8000 CR4: 00000000000026e0
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.096864] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.097203] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.097542] Process VBoxHeadless (pid: 1895, threadinfo ffff880224d3a000, task ffff880233c18000)
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.097972] Stack:
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.098166]  ffffc900117df8f2 0000000000000010 ffffffffa01a58c9 0000000000000001
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.112700] <0> ffff880233c18000 ffffffff81086170 00ff880224d3bd30 ffff880224d3bd30
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.141668] <0> ffff88022289c610 ffff880222a9e810 ffffffffa031e100 ffff880224d3bd98
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170607] Call Trace:
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170620]  [<ffffffffa01a58c9>] ? g_abExecMemory+0x166a9/0x180000 [vboxdrv]
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170625]  [<ffffffff81086170>] ? wake_bit_function+0x0/0x40
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170632]  [<ffffffffa01a61a5>] g_abExecMemory+0x16f85/0x180000 [vboxdrv]
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170636]  [<ffffffff810f62ee>] ? find_get_page+0x1e/0xa0
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170638]  [<ffffffff810f7d0b>] ? filemap_fault+0x8b/0x450
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170645]  [<ffffffffa0176d8d>] supdrvIOCtl+0x14cd/0x28b0 [vboxdrv]
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170654]  [<ffffffffa017b5af>] ? rtR0MemAllocEx+0x7f/0x150 [vboxdrv]
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170656]  [<ffffffff810f65f7>] ? unlock_page+0x27/0x30
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170663]  [<ffffffffa01713b1>] VBoxDrvLinuxIOCtl+0x111/0x1d0 [vboxdrv]
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170667]  [<ffffffff81156c72>] vfs_ioctl+0x22/0xa0
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170672]  [<ffffffff81558ce9>] ? thread_return+0x48/0x41f
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170674]  [<ffffffff81156e11>] do_vfs_ioctl+0x81/0x410
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170677]  [<ffffffff8155dc73>] ? do_page_fault+0x153/0x3b0
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170679]  [<ffffffff81157221>] sys_ioctl+0x81/0xa0
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170684]  [<ffffffff81013172>] system_call_fastpath+0x16/0x1b
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170685] Code: 00 0f 20 d8 4a 89 84 02 80 06 00 00 0f 20 e0 4a 89 84 02 88 06 00 00 48 83 e0 70 42 8b 8c 02 68 0a 00 00 23 4a 20 09 c8 0b 42 24 <0f> 22 e0 42 8b 84 02 50 0a 00 00 83 e0 04 0d 3b 00 00 80 0f 22 
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170699] RIP  [<ffffc900117dfb82>] 0xffffc900117dfb82
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170701]  RSP <ffff880224d3bd00>
Oct  4 19:46:46 VirtualUbuntu kernel: [  482.170703] ---[ end trace 03bad65eb8627481 ]---

I just updated Virtualbox from 4.1.2 to 4.1.4, in the same update process, my kernel got updated to

Code: Select all

Linux VirtualUbuntu 2.6.32-34-server #77-Ubuntu SMP Tue Sep 13 20:54:38 UTC 2011 x86_64 GNU/Linux

Now, i enter via phpvirtualbox (latest up to today) and if i try to start a virtual machine, this happens..... and the machine stays in "Aborted" mode...... i really messed it up now.... any help, please?? Im kind of eating my nails here.....

[[ Xi0N ]]

Trying to run a VM manually from console gives the following error:

Code: Select all

VBoxManage startvm "Checkpoint"
Waiting for VM "Checkpoint" to power on...
VBoxManage: error: The virtual machine 'Checkpoint' has terminated unexpectedly during startup with exit code 0
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Machine, interface IMachine, callee 

Please, PLEASE... help-----

[Perryg]

The error code usually means the guest is not there or VirtualBox can not see it.
What version were/was the guest/s created with?
Do you see the VirtualBox.xml and can you see the guest *.vbox & *.vdi files?
Did you have snap shots?

[[ Xi0N ]]

Ok,
The guests were created with previous versions of VirtualBox. Can't remember which version, but previous to 4.0....
If i create a new vm, i get the same kind of problems.....
I see VirtualBox.xml under .VirtualBox in the home directory
I do have snapshots in some of them, but then again: I create a new vm: No snapshots at all, and i still have the very same problems....
Help please....

Do you think a downgrade to 4.1.2 would fix it? I cannot find this package to download, though...... [edit: found the download link, going to try a downgrade]
EDIT1: Downgrading didn't do any good...

[[ Xi0N ]]

I renamed the folders VirtualBox VMs and .VirtualBox, so the system would re-generate them...... i created a virtual machine from scratch and yet still, I have the same problem....
I really need help with this.....

EDIT: Booting an older kernel does not fix the thing......

EDIT1: I did sudo aptitude remove --purge virtualbox-4.1 , and reinstalled back again: Same error - Strange thoug, since i didn't install the extension pack, but it seems like it remained installed, even after uninstalling with purge....

EDIT2: I erased everything under /usr/lib/dkms/vbox* and re-compiler the modules: Nothing

Conclussion: I would retry the complete reinstall of the program, and it seems like --purge still leaves something around the system.. can anyone tell me where else to look, in order to leave the system completely virtualbox-free?
This issue is giving me a big BIG headache......


EDIT3: I'm afraid i cannot stay like this, im backing my virtual machines up to an external hard disk... in 3 or 4 hours, i will start installing arch linux and configure it as the host machine from now on: This way i will say goodbye for good to ubuntu and its problems.
I need a last advice, though: The folders .VirtualBox and VirtualBox VMs under my /home are the only thing i need to take to the new machine, aren't they?
I must be really careful with this aspect since the VMs i have are priceless for me.... if i lose them i lose the work i have been doing for the last year....
Anyway, wish me luck....

[Perryg]

Well you have been busy while I was in bed. Anyway I see no reason to jump out of the frying pan and into the fire. Arch is not a friendly as a debian product.
If you are bent on a different system why not just use Debian stable. Don't install the virtual kernel and you should be fine. Who talked you into that anyway?
Anyway let me know if you have changed your mind and need more help.

[[ Xi0N ]]

Well, im trying to boot arch with no success... i forgot i had this issue in the past..... i didn't delete anything yet and i see no way to install arch just now...
More help would be really nice.....
I'll be here for some hours still so, tell me what to try, please!!!

[Perryg]

The first thing that you need to do is find out what happened to the host. VirtualBox is after all an application that runs in the host.
You said that the kernel updated as well. Can you try to boot to the previous kernel? Ubuntu requires you to hold the shift key down to enter the grub screen.
Then see if you can install and run VirtualBox. I would select a guest that is not my total favorite though to be safe.

[[ Xi0N ]]

The first thing that you need to do is find out what happened to the host. VirtualBox is after all an application that runs in the host.
You said that the kernel updated as well. Can you try to boot to the previous kernel? Ubuntu requires you to hold the shift key down to enter the grub screen.
Then see if you can install and run VirtualBox. I would select a guest that is not my total favorite though to be safe.

I already tried with the previous kernel... the one i know that was working yesterday, before i updated.....

[Perryg]

kvm_intel kvm shows in your first post. Since you can not run 2 virtualizers at the same time on 64 bit try stopping the KVM and see if you can get VBox to work.
https://help.ubuntu.com/community/KVM/FAQ

[[ Xi0N ]]

kvm_intel kvm shows in your first post. Since you can not run 2 virtualizers at the same time on 64 bit try stopping the KVM and see if you can get VBox to work.
https://help.ubuntu.com/community/KVM/FAQ

I thought i got rid of that before!!!!

Will try... anyway... i will investigate how to do what you say but maybe you have the straightforward answer?
If not, don't worry, i think i can find how to.... this thing is killing my nerves! (Recorded a debian iso, btw... just in case i cannot get this working)


EDIT: Funny fact: I was trying to boot arch linux live cd for the last time before reading this post (i will try whats on it).... the 64bit version does not boot correctly, while the 32 bit one does..... really weird....

EDIT2: I think i found the cause!!! a couple days ago, installed qemu for converting a vmdk image of a hdd to binary, so i caould convert it to .vdi ... and i had qemu-kvm installed... i just removed it and i am currently restarting... fingers crossed....

[Perryg]

Well if it works you will still need to deal with this in the future. The virtualkernel thing is not something you need to use VirtualBox and removing the kernel and going back to a standard kernel is the real solution. But the thing that concerns me is the guests with snapshots. With all the do this do that purge and install you have done these guests may be left with broken snapshot chains. Not an issue if these were created in version =>4.* but if they were originally created before your chain information will have been in the VirtualBox.xml and not in the guests *.vbox file.

My suggestion would be to get this to work and make sure that you merge all snapshots so you have a single *.vdi so if you need to you can easily move to a different distro.
Oh and do this from the console and *not phpvirtualbox. You don't need any other things in your way until this is fixed.

[[ Xi0N ]]

WORKING!!!!!
For some reason, the module kvm-intel was loaded, and i know i dealt with it before so.. i think, in the past, i might have added an entry to /etc/modprobe.d/blacklist for not letting it to start, but, maybe some update deleted this file, letting this module to load....

EVERYTHING seems to be working.. and i assume including the snapshots... I didn't try to merge any or restore any of them, but the system should fail to boot if they were corrupted, wouldn't they?
Anyway..... i need an advice for those old vms that you said, because of being created with a version previous to 4.0, could give problems....


Thank you very much... you have been my saviour!!!

[Perryg]

What you are looking to do is to get all the guests that were created <=4.* to have a single *.vdi file. with no snapshots.
You can then convert these to the new format by removing them from the VirtualBox main manager (but do not delete) and then creating a new guest and add the original VDI when asked if you want to create a new HDD or use an existing one. Make sure that you record the settings before you do this for each guest. You should also create a folder in the VirtualBox VMs folder called the same as the guest and place the *.vdi file in there before you add it to the main manager. This will keep the same file structure and everything will be in its own folder in a central location.

Added benefit is portability and backup.

[[ Xi0N ]]

What you are looking to do is to get all the guests that were created <=4.* to have a single *.vdi file. with no snapshots.
You can then convert these to the new format by removing them from the VirtualBox main manager (but do not delete) and then creating a new guest and add the original VDI when asked if you want to create a new HDD or use an existing one. Make sure that you record the settings before you do this for each guest. You should also create a folder in the VirtualBox VMs folder called the same as the guest and place the *.vdi file in there before you add it to the main manager. This will keep the same file structure and everything will be in its own folder in a central location.

Added benefit is portability and backup.

Hmmm... maybe this is the reason while last time i checked, cloning was failing because of some error with snapshots?... I see... wow... thank you, man... thank you....