Opened 10 years ago
Closed 8 years ago
#12998 closed defect (obsolete)
VirtualBox crash inside guest OS
| Reported by: | drazzib | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.3.10 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Linux |
Description
Host: VirtualBox 4.3.10-93012~Debian~wheezy Guest: /opt/VBoxGuestAdditions-4.3.10/bin/VBoxControl version 4.3.10r93012
Both host and guest under Debian Wheezy linux kernel : Debian 3.2.54-2 x86_64 GNU/Linux
Guest kernel crash during IO access to an VDI disk :
[300445.159483] BUG: unable to handle kernel paging request at 0000006c00000018 [300445.160369] IP: [<ffffffffa01cae99>] vbglPhysHeapExcludeBlock+0xd/0x4b [vboxguest] [300445.161234] PGD 215ed2067 PUD 0 [300445.161412] Oops: 0002 [#1] SMP [300445.161865] CPU 0 [300445.162086] Modules linked in: xt_multiport vboxsf(O) nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables ext2 loop vboxvideo(O) drm snd_pcm snd_page_alloc snd_timer snd vboxguest(O) i2c_piix4 soundcore parport_pc i2c_core parport psmouse processor serio_raw pcspkr evdev ac button power_supply thermal_sys ext4 crc16 jbd2 mbcache dm_mod sg sr_mod sd_mod cdrom crc_t10dif ata_generic ahci libahci ata_piix libata e1000 scsi_mod [last unloaded: scsi_wait_scan] [300445.163199] [300445.163199] Pid: 3207, comm: vminfo Tainted: G O 3.2.0-4-amd64 #1 Debian 3.2.54-2 innotek GmbH VirtualBox/VirtualBox [300445.163199] RIP: 0010:[<ffffffffa01cae99>] [<ffffffffa01cae99>] vbglPhysHeapExcludeBlock+0xd/0x4b [vboxguest] [300445.163199] RSP: 0018:ffff880214263d50 EFLAGS: 00010206 [300445.163199] RAX: 0000006c00000000 RBX: ffff88003742014c RCX: 0000000000010000 [300445.163199] RDX: ffff880037420124 RSI: ffff880037420124 RDI: ffff88003742016c [300445.163199] RBP: ffff880037420124 R08: 0000000000000020 R09: 0000000000000020 [300445.163199] R10: 0000000000000246 R11: 0000000000000246 R12: ffff880214263e50 [300445.163199] R13: ffff880216276a10 R14: ffff880214263e70 R15: 00000000000000d8 [300445.163199] FS: 00007fd61edfc700(0000) GS:ffff88021fc00000(0000) knlGS:0000000000000000 [300445.163199] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [300445.163199] CR2: 0000006c00000018 CR3: 0000000215875000 CR4: 00000000000006f0 [300445.163199] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [300445.163199] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [300445.163199] Process vminfo (pid: 3207, threadinfo ffff880214262000, task ffff880214675810) [300445.163199] Stack: [300445.163199] ffffffffa01cb281 0000000000000000 00000000fffff4a7 ffffffffa01e5440 [300445.163199] ffffffffa01c867b 0000000000000000 0000000000000000 0000000000000050 [300445.163199] ffff880214263e70 ffff880213bc5740 00000000ffffff9d 0000000000000020 [300445.163199] Call Trace: [300445.163199] [<ffffffffa01cb281>] ? VbglPhysHeapFree+0x74/0xaf [vboxguest] [300445.163199] [<ffffffffa01c867b>] ? VBoxGuestCommonIOCtl+0x3d0/0x16e4 [vboxguest] [300445.163199] [<ffffffffa01c66cf>] ? vboxguestLinuxIOCtl+0x1b1/0x1c6 [vboxguest] [300445.163199] [<ffffffffa01c65fb>] ? vboxguestLinuxIOCtl+0xdd/0x1c6 [vboxguest] [300445.163199] [<ffffffff81107e35>] ? do_vfs_ioctl+0x459/0x49a [300445.163199] [<ffffffff8110a9a6>] ? dput+0xe2/0xee [300445.163199] [<ffffffff810fb8ce>] ? fput+0x17a/0x1a1 [300445.163199] [<ffffffff81107ec1>] ? sys_ioctl+0x4b/0x72 [300445.163199] [<ffffffff81354d92>] ? system_call_fastpath+0x16/0x1b [300445.163199] Code: eb 0a c7 05 86 a7 01 00 00 00 00 00 48 83 c4 10 89 d8 5b 5d 41 5c c3 e9 5c ff ff ff 90 90 48 8b 47 10 48 85 c0 74 08 48 8b 57 18 <48> 89 50 18 48 8b 57 18 48 8b 47 10 48 85 d2 74 06 48 89 42 10 [300445.163199] RIP [<ffffffffa01cae99>] vbglPhysHeapExcludeBlock+0xd/0x4b [vboxguest] [300445.163199] RSP <ffff880214263d50> [300445.163199] CR2: 0000006c00000018 [300445.230559] ---[ end trace 98f6b72d6168cf80 ]---
Change History (4)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Please could you attach the vboxguest.ko kernel module which was in use when this guest panic happened? Thank you!
comment:3 by , 9 years ago
And I would also like to have a look at the VBox.log file (not necessarily the exact one for the session which crashed).
comment:4 by , 8 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
This is still a reproducible problem with guest additions version 4.3.20: