Virtualbox-4.3.0 - multiple hard crashes

Discussions related to using VirtualBox on Linux hosts.

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby cac » 27. Oct 2013, 00:48

Hello
I have the same problem with Virtualbox-4.3.0, all VM windows Xp crash (Blue Death Screen), only Safe Mode work.
I running an Ubuntu Host.
To work i must disable VTx-AMDv
I'm running AMD64 host.
Regards
cac
 
Posts: 18
Joined: 5. Feb 2008, 17:38

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby Ramshankar » 27. Oct 2013, 16:54

CobrA wrote:
Ramshankar wrote:Feel free to check if this build makes things any better: http://www.virtualbox.org/download/test ... _amd64.run (link expires in ~14 days)


So far no crashes. Thanks.


post-factum wrote:That 4.3.1 build seems to work for me as well. Thanks.


Good. Thank you for testing!
Oracle Corp.
Ramshankar
Oracle Corporation
 
Posts: 787
Joined: 7. Jan 2008, 16:17

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby MarkKnecht » 3. Nov 2013, 00:17

Gentoo portage had Virtualbox-4.3.2 available today. This version did not fix the problem for me. I don't know if it should or not as I don't know what rev number the patch released here corresponds to. Anyway, 1 VM running and I hit the problem in under 30 minutes with 1 VM running. Complete hard crash. Going back to 4.2.18 again.
MarkKnecht
 
Posts: 51
Joined: 14. Feb 2010, 22:34
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: Win 7, Win XP, Gentoo 32-bit

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby antry » 3. Nov 2013, 17:37

virtualbox 4.3.2 on archliunux same behavoir.Freeze or kernel panic.
antry
 
Posts: 4
Joined: 24. Jan 2011, 11:10
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: windows 7

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby cac » 4. Nov 2013, 12:43

Hello.
This update (4.3.2) don't solve the problems.
With this this uptade, now i can't restore machine state too :

Copy of error Message
Échec de l'ouverture de session pour la machine virtuelle Xp. (Failed to open session for VM ...)

Failed to load unit 'PATM' (VERR_SSM_LOADED_TOO_MUCH).

Code d'erreur : NS_ERROR_FAILURE (0x80004005)
Composant : Console
Interface : IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

Bests Regards
cac
 
Posts: 18
Joined: 5. Feb 2008, 17:38

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby frank » 4. Nov 2013, 15:09

cac wrote:Hello.
This update (4.3.2) don't solve the problems.
With this this uptade, now i can't restore machine state too :

Copy of error Message
Échec de l'ouverture de session pour la machine virtuelle Xp. (Failed to open session for VM ...)

Failed to load unit 'PATM' (VERR_SSM_LOADED_TOO_MUCH).

Code d'erreur : NS_ERROR_FAILURE (0x80004005)
Composant : Console
Interface : IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

Bests Regards


That's a different problem.
frank
Oracle Corporation
 
Posts: 3362
Joined: 7. Jun 2007, 09:11
Location: Dresden, Germany
Primary OS: Debian Sid
VBox Version: PUEL
Guest OSses: Linux, Windows

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby cac » 4. Nov 2013, 15:37

Hello.
ok, but i still have problem with VTx-AMDv enabled.
VM windows Xp crash (Blue Death Screen).
Regards.
cac
 
Posts: 18
Joined: 5. Feb 2008, 17:38

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby saintdev » 5. Nov 2013, 07:49

MarkKnecht wrote:Gentoo portage had Virtualbox-4.3.2 available today. This version did not fix the problem for me. I don't know if it should or not as I don't know what rev number the patch released here corresponds to. Anyway, 1 VM running and I hit the problem in under 30 minutes with 1 VM running. Complete hard crash. Going back to 4.2.18 again.


I'm getting the same hard lockup, with both 4.3.0 and 4.3.2. I had an Arch guest I was testing with and after locking up the host several times and reverting to 4.2.18, the virtual disk was corrupt, only returning IO errors when the guest attempted to read/write. I deleted the guest before copying the VBox log (oops). It also happened with a Win7 guest.

I setup netconsole and was able to get the Oops output, but I didn't have frame pointers enabled, so it's not of much use. I have recompiled with frame pointers and will attempt to get a backtrace when I'm prepared to lockup my system again.

Code: Select all   Expand viewCollapse view
[183225.464031] BUG: unable to handle kernel
[183225.464045] NULL pointer dereference at 0000000000000028
[183225.464055] IP: [<ffffffffa013c3cf>] 0xffffffffa013c3ce
[183225.464065] PGD 1d1353067 PUD 180b3e067 PMD 0
[183225.464075] Oops: 0000 [#1] PREEMPT SMP
[183225.464083] Modules linked in: vboxnetflt(O) vboxnetadp(O) vboxdrv(O) snd_hda_codec_hdmi snd_usb_audio snd_usbmidi_lib nvidia(PO) uvcvideo videobuf2_vmalloc snd_hda_intel snd_hda_codec videobuf2_memops videobuf2_core firewire_ohci firewire_core snd_hwdep pata_marvell [last unloaded: kvm]
[183225.464125] CPU: 0 PID: 0 Comm: BFS/0 Tainted: P           O 3.10.17-ck.0 #2
[183225.464128] Hardware name: System manufacturer P5Q/P5Q, BIOS 2102    04/07/2009
[183225.464132] task: ffffffff8182e440 ti: ffffffff8181e000 task.ti: ffffffff8181e000
[183225.464136] RIP: 0010:[<ffffffffa013c3cf>]  [<ffffffffa013c3cf>] 0xffffffffa013c3ce
[183225.464142] RSP: 0018:ffff8801636ebc18  EFLAGS: 00010246
[183225.464145] RAX: 0000000000000000 RBX: 0000000000000a3c RCX: ffffc90011073000
[183225.464148] RDX: 0000000000000002 RSI: 0000000000000002 RDI: 0000000000000002
[183225.464151] RBP: ffff8801636ebc38 R08: 0000000000000004 R09: 0000000000000001
[183225.464155] R10: 000000000001c000 R11: 00000000ffffffff R12: ffffc9001105bae0
[183225.464158] R13: ffff8801636ebd00 R14: ffffffffa01a7ee0 R15: 0000000000004008
[183225.464162] FS:  00007f7570b5b700(0000) GS:ffff88021fc00000(0000) knlGS:0000000000000000
[183225.464166] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[183225.464169] CR2: 0000000000000028 CR3: 00000001d6110000 CR4: 00000000000027f0
[183225.464172] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[183225.464175] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[183225.464177] Stack:
[183225.464181]  ffff8801636ebfd8 00000000fffff5ca 00007f754b8d18b0 ffff8801636ebd00
[183225.464191]  ffff8801636ebc78 ffffffffa01a7f13 00007f754b8d3900 ffffc9001105ac68
[183225.464200]  00007f754b8d18b0 0000000000000004 ffffffffa01a7ee0 0000000000004008
[183225.464208] Call Trace:
[183225.464212] Code: 03 79 19 0f 85 [183225.464277] ------------[ cut here ]------------
[183225.464285] WARNING: at net/core/dev.c:3230 net_tx_action+0x147/0x150()
[183225.464287] Modules linked in: vboxnetflt(O) vboxnetadp(O) vboxdrv(O) snd_hda_codec_hdmi


Code: Select all   Expand viewCollapse view
$ uname -a
Linux khopesh 3.10.17-ck.0 #2 SMP PREEMPT Tue Oct 22 16:26:22 MDT 2013 x86_64 Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz GenuineIntel GNU/Linux
Attachments
config-3.10.17-ck.0.txt
Kernel config
(78.21 KiB) Downloaded 22 times
saintdev
 
Posts: 6
Joined: 5. Nov 2013, 07:28

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby web-devel » 7. Nov 2013, 01:34

Last week I upgraded to Suse 12.3/Virtualbox 4.3.0 and feel I now have a very similar problem. Hard freeze on the base Suse OS. The console is sadly unresponsive. Turning VM to use only one processor seems to help. I'd love to downgrade but a package < 4.3.0 does not appear to be available for Suse 12.3.
web-devel
 
Posts: 2
Joined: 7. Nov 2013, 01:25

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby Perryg » 7. Nov 2013, 02:09

web-devel wrote:Last week I upgraded to Suse 12.3/Virtualbox 4.3.0 and feel I now have a very similar problem. Hard freeze on the base Suse OS. The console is sadly unresponsive. Turning VM to use only one processor seems to help. I'd love to downgrade but a package < 4.3.0 does not appear to be available for Suse 12.3.

I would upgrade to 4.3.2 myself.
Perryg
Site Moderator
 
Posts: 34373
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby MarkKnecht » 7. Nov 2013, 02:55

Perryg wrote:
web-devel wrote:Last week I upgraded to Suse 12.3/Virtualbox 4.3.0 and feel I now have a very similar problem. Hard freeze on the base Suse OS. The console is sadly unresponsive. Turning VM to use only one processor seems to help. I'd love to downgrade but a package < 4.3.0 does not appear to be available for Suse 12.3.

I would upgrade to 4.3.2 myself.


I agree but mostly just so I can verify that others continue to have this problem. I built 4.3.2 on my Gentoo machine and found it unchanged WRT this problem. 4.2.18 continues to run fine. I do hope others will test, but I also hope that Oracle continues to look for the root cause.
MarkKnecht
 
Posts: 51
Joined: 14. Feb 2010, 22:34
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: Win 7, Win XP, Gentoo 32-bit

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby skoehler » 8. Nov 2013, 16:46

So today, my host crashes again (I'm using 4.3.2). It was a Windows XP guest with 2 guest CPUs.
I did not experience a crash with my Windows 7 guest (also 2 CPUs) when I was working with yesterday for a considerable amount of time.
skoehler
 
Posts: 116
Joined: 1. Dec 2008, 12:12

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby MarkKnecht » 8. Nov 2013, 19:07

skoehler wrote:So today, my host crashes again (I'm using 4.3.2). It was a Windows XP guest with 2 guest CPUs.
I did not experience a crash with my Windows 7 guest (also 2 CPUs) when I was working with yesterday for a considerable amount of time.


Here on Gentoo I tried 4.3.0, 4.3.0-r2 and 4.3.2. All crashed the machine hard the same way. It's not time oriented best I can tell. I will say the actual crash seemed to happen most often when I was doing something outside of the VM, but that's anecdotal at best I think. I've suffered 7 crashes at this point using the 4.3 series. When I go back to 4.2.18 I've not seen any problems. (I'm running 2 Win 7 VMs and a VMWare Player Win XP VM here and have been for the last 4 hours.)

For kicks I did a complete rebuild of the machine (emerge -e @world) to ensure every piece of software was built using the same C compiler. That didn't help.

This problem seems to be across multiple distros looking at this thread so (to me) it seems unlikely it's a specific kernel config option or anything like that. I put a bug report in the Gentoo system and a couple of other people have reported similar problems.
MarkKnecht
 
Posts: 51
Joined: 14. Feb 2010, 22:34
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: Win 7, Win XP, Gentoo 32-bit

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby skoehler » 9. Nov 2013, 15:19

MarkKnecht wrote:This problem seems to be across multiple distros looking at this thread so (to me) it seems unlikely it's a specific kernel config option or anything like that. I put a bug report in the Gentoo system and a couple of other people have reported similar problems.

Which bug number would that be?

Also, has anyone found a way to reproduce the error? For me, the last crash of my Windows XP guest was during the install of the guest additions. In the host, some flash video was playing in a browser.
skoehler
 
Posts: 116
Joined: 1. Dec 2008, 12:12

Re: Virtualbox-4.3.0 - multiple hard crashes

Postby MarkKnecht » 9. Nov 2013, 15:56

skoehler wrote:
MarkKnecht wrote:This problem seems to be across multiple distros looking at this thread so (to me) it seems unlikely it's a specific kernel config option or anything like that. I put a bug report in the Gentoo system and a couple of other people have reported similar problems.

Which bug number would that be?

Also, has anyone found a way to reproduce the error? For me, the last crash of my Windows XP guest was during the install of the guest additions. In the host, some flash video was playing in a browser.

https://bugs.gentoo.org/show_bug.cgi?id=489028
MarkKnecht
 
Posts: 51
Joined: 14. Feb 2010, 22:34
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: Win 7, Win XP, Gentoo 32-bit

PreviousNext

Return to VirtualBox on Linux Hosts

Who is online

Users browsing this forum: No registered users and 26 guests