Starting any guest causes crash

Discussions related to using VirtualBox on Linux hosts.

Starting any guest causes crash

Postby Tiber » 21. May 2007, 11:20

Hello,

on a system with an AMD Athlon 64 X2 3600+ (the 65W variant) and a Gigabyte M61P-S3 board, virtualbox 1.3.8 crashes as soon as a guest is started. The OS is Debian Etch with kernel 2.6.18-4-k7 (SMP). I've tried Suse and Ubuntu as host OS as well, but virtualbox always crashes.

That's the the trace from the syslog:

Code: Select all   Expand viewCollapse view
kernel: general protection fault: 0000 [#1]
kernel: SMP
kernel: Modules linked in: vboxdrv ppdev lp button ac battery lirc_serial lirc_dev ipv6 nls_iso8859_1 nls_cp437 vfat fat dm_snapshot dm_mirror dm_mod sbp2 loop cx88_dvb cx88_vp3054_i2c mt352 dvb_pll or51132 video_buf_dvb nxt200x isl6421 zl10353 cx24123 lgdt330x cx22702 tsdev cx88_blackbird cx8802 cx2341x dvb_ttpci lnbp21 l64781 saa7146_vv saa7146 ves1820 stv0299 dvb_core cx8800 cx88xx tda8083 sp8870 firmware_class ir_common stv0297 ves1x93 i2c_algo_bit parport_pc ttpci_eeprom psmouse video_buf tveeprom i2c_core compat_ioctl32 btcx_risc videodev v4l1_compat v4l2_common evdev parport serio_raw pcspkr eth1394 rtc_dev rtc_core rtc_lib ext3 jbd mbcache ide_disk ide_cd cdrom sd_mod ohci1394 ieee1394 hpt366 ohci_hcd ehci_hcd forcedeth sata_nv usbcore libata scsi_mod amd74xx generic ide_core thermal processor fan
kernel: CPU:    1
kernel: EIP:    0060:[<fa2a958b>]    Tainted: GF     VLI
kernel: EFLAGS: 00210006   (2.6.18-4-k7 #1)
kernel: EIP is at 0xfa2a958b
kernel: eax: 00001000   ebx: 00001000   ecx: c0000080   edx: 00000000
kernel: esi: 00000000   edi: b3681000   ebp: f6ccff94   esp: f6ccfec4
kernel: ds: 007b   es: 007b   ss: 0068
kernel: Process VirtualBox (pid: 8683, ti=f6cce000 task=f7b90550 task.ti=f6cce000)
kernel: Stack: 01000020 69746e65 00000001 c010f7ad 00000000 00000000 00000000 00000000
kernel:        00000000 00000001 00000001 00000000 00000000 00000000 00000000 00000000
kernel:        00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
kernel: Call Trace:
kernel:  [<c010f7ad>] do_flush_tlb_all+0x0/0x5a
kernel:  [<c016993a>] do_ioctl+0x4e/0x5d
kernel:  [<c0169b9b>] vfs_ioctl+0x252/0x264
kernel:  [<c0169bf5>] sys_ioctl+0x48/0x5f
kernel:  [<c0169c05>] sys_ioctl+0x58/0x5f
kernel: Code: c8 25 00 10 00 00 89 95 44 ff ff ff 31 d2 09 c2 89 85 40 ff ff ff 75 15 8b 5d c8 8b b5 4c ff ff ff 81 cb 00 10 00 00 89 d8 89 f2 <0f> 30 8b 85 50 ff ff ff 8b 95 4c ff ff ff 89 c1 89 45 c0 31 c0
kernel: EIP: [<fa2a958b>] 0xfa2a958b SS:ESP 0068:f6ccfec4


Any idea what's going wrong here? Maybe it's the same problem as reported in ticket #317 http://www.virtualbox.org/ticket/317?

bye,

Tobias
Tiber
 
Posts: 4
Joined: 21. May 2007, 11:06

Postby Tiber » 22. May 2007, 23:32

Just tested it with the current SVN snapshot - same problem:

Code: Select all   Expand viewCollapse view
May 22 23:25:21 vdr kernel: CPU:    0
kernel: EIP:    0060:[<fa4d591b>]    Tainted: GF     VLI
kernel: EFLAGS: 00210006   (2.6.18-4-k7 #1)
kernel: EIP is at 0xfa4d591b
kernel: eax: 00001000   ebx: 00001000   ecx: c0000080   edx: 00000000
kernel: esi: 00000000   edi: b3f34000   ebp: e4f5ff74   esp: e4f5fea4
kernel: ds: 007b   es: 007b   ss: 0068
kernel: Process VirtualBox (pid: 7402, ti=e4f5e000 task=d4e83aa0 task.ti=e4f5e000)
kernel: Stack: 01000020 69746e65 00000000 000200d2 00000000 00000000 00000000 00000000
kernel:        00000000 00000000 00000001 c010f7ad 00000000 00000000 00000000 00000000
kernel:        00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
kernel: Call Trace:
kernel:  [<c010f7ad>] do_flush_tlb_all+0x0/0x5a
kernel:  [<c0169b9b>] vfs_ioctl+0x252/0x264
kernel:  [<c0169bf5>] sys_ioctl+0x48/0x5f
kernel: Code: c8 25 00 10 00 00 89 95 44 ff ff ff 31 d2 09 c2 89 85 40 ff ff ff 75 15 8b 5d c8 8b b5 4c ff ff ff 81 cb 00 10 00 00 89 d8 89 f2 <0f> 30 8b 85 50 ff ff ff 8b 95 4c ff ff ff 89 c1 89 45 c0 31 c0
kernel: EIP: [<fa4d591b>] 0xfa4d591b SS:ESP 0068:e4f5fea4
Tiber
 
Posts: 4
Joined: 21. May 2007, 11:06

Postby michael » 23. May 2007, 11:00

Is that a crash of the host OS?
michael
Oracle Corporation
 
Posts: 336
Joined: 10. May 2007, 09:46

Postby Tiber » 24. May 2007, 09:07

michael wrote:Is that a crash of the host OS?


Yes, it crashes on the host side. But it's not the OS that goes to hell, it's VirtualBox. As soon as I start a client, VirtualBox crashes. It really seems to be a problem with the CPU. I tried Suse, Ubuntu and Debian as host OS. I tried the latest release of VirtualBox as well as a SVN snapshot. If I run VirtualBox, create a new virtual machine and start it, it immediately crashes leaving a dead process behind, that I must kill manually.

Here's a screenshot when it crashed:

http://www.e-tobi.net/stuff/Bildschirmphoto1.png

I don't have this problem on other machines with a different CPU.

Tobias[/img]
Tiber
 
Posts: 4
Joined: 21. May 2007, 11:06

Postby michael » 24. May 2007, 09:37

I added a link to this thread to the bug-tracker ticket you quoted below.
michael
Oracle Corporation
 
Posts: 336
Joined: 10. May 2007, 09:46

Postby Tiber » 24. May 2007, 10:13

Thanks!
Tiber
 
Posts: 4
Joined: 21. May 2007, 11:06

Postby DOCXP » 12. Jun 2007, 20:33

I have the same problem, when I start a virtual machine the system crashes.
My system is Debian Lenny, kernel 2.6.21, CPU Core 2 Duo, virtualbox 1.4.0.
DOCXP
 
Posts: 2
Joined: 12. Jun 2007, 20:17

I experienced this on a Dell laptop....

Postby ttolstead » 14. Jun 2007, 20:21

with a transplanted vm, it turned out to be that the memory allocation for the vm was too high for the machine I was running it on.... tat
ttolstead
 
Posts: 5
Joined: 14. Jun 2007, 17:34
Location: United States

same problem

Postby jcezanna56 » 26. Jul 2007, 16:53

I got the same problem, vbox crashes and display starting 0%
Any solution ?


Dell Dimension 9200, core 2, RAM 4 Go.
Fedora 7, Vbox 1.4
jcezanna56
 
Posts: 14
Joined: 1. Jul 2007, 16:54

confirmed

Postby cpanceac » 16. Aug 2007, 19:08

same issue, fedora 7, virtualbox 1.4.0, host ram 2GiB, guest ram 512 MiB, amd athlon64 x2 5600+
cpanceac
 
Posts: 1
Joined: 16. Aug 2007, 19:03

vbox GPF on virtual machine start

Postby docpneumo » 18. Aug 2007, 19:06

I'm seeing the same behavior.

SETUP:
MB: Abit KN9 SLI
Processor: AMD Athlon 64 X2 Dual Core Processor 4800+
RAM: 2 Gig
HD: Maxtor SATA II/300 160GB
CD: R/RW IDE Slave (sr1)
DVD: R/RW IDE Master (sr0)
GC: e-GeForce 7600 GS
USB: OHCI Host Controller (Onboard)
EHCI NEC USB2 PCI Hub
FD: none

Host:
uname -a: 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
VB: VirtualBox-1.4.0_21864_fedora7-1.x86_64.rpm (compiled without error messages)

Guest:
F7 General
Name F7
OS Type Linux 2.6
Base Memory 512 MB
Video Memory 8 MB
Boot Order CD/DVD-ROM, Hard Disk
ACPI Enabled
IO APIC Disabled
Hard Disks
Primary Master F7.vdi [Normal, 20.00 GB]
Floppy
Not mounted
CD/DVD-ROM
Image fedora_7_i386_dvd.iso
Audio
Disabled
Network
Adapter 0 NAT
USB Controller
Disabled
Remote Display
Disabled

dmesg > vbF7start.messages
general protection fault: 0000 [1] SMP
last sysfs file: /devices/pci0000:00/0000:00:00.0/irq
CPU 1
Modules linked in: ipt_MASQUERADE iptable_nat nf_nat bridge vboxdrv(U) autofs4 hidp rfcomm l2cap bluetooth sunrpc ipv6 nf_conntrack_netbios_ns nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink xt_tcpudp ipt_REJECT iptable_filter ip_tables x_tables cpufreq_ondemand dm_multipath video sbs button dock battery ac kvm snd_usb_audio snd_usb_lib snd_rawmidi snd_hwdep sr_mod cdrom snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss firewire_ohci snd_mixer_oss i2c_nforce2 firewire_core snd_pcm k8temp i2c_core snd_timer crc_itu_t rtc_cmos snd hwmon shpchp soundcore floppy forcedeth joydev pata_amd snd_page_alloc sg dm_snapshot dm_zero dm_mirror dm_mod ata_generic sata_nv libata sd_mod scsi_mod ext3 jbd mbcache ehci_hcd ohci_hcd uhci_hcd
Pid: 3012, comm: VirtualBox Not tainted 2.6.22.1-41.fc7 #1
RIP: 0010:[<ffffffff883f8b76>] [<ffffffff883f8b76>] :vboxdrv:g_abExecMemory+0x3156/0x180000
RSP: 0000:ffff810063c21f50 EFLAGS: 00010056
RAX: 0000000000001d01 RBX: 00000000000008d7 RCX: 00000000c0000080
RDX: 0000000000000000 RSI: 0000000000000d01 RDI: 00002aaab021c000
RBP: ffff810063c21f58 R08: 0000000069746e65 R09: 0000000001000020
R10: 0000000000002001 R11: 00000000444d4163 R12: 00002aaab021c000
R13: 0000000000010004 R14: 0000000000000097 R15: 00000000009f2840
FS: 00000000415a5950(0063) GS:ffff810002381280(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00002aaab10f5930 CR3: 0000000063cff000 CR4: 00000000000006e0
Process VirtualBox (pid: 3012, threadinfo ffff810063c20000, task ffff81006648b800)
Stack: 0000000000000000 ffff810063c21fa8 ffffffff883f5f81 0000000000000000
00002aaab021c000 00000000415a4f20 0000000000000097 0000000000000000
00002aaab021c000 0000000000907a60 00002aaaafc6c380 00000000415a4f20
Call Trace:
[<ffffffff883f5f81>] :vboxdrv:g_abExecMemory+0x561/0x180000
[<ffffffff884352c6>] :vboxdrv:g_abExecMemory+0x3f8a6/0x180000


Code: 0f 30 f7 c6 00 10 00 00 74 a3 b8 0a 00 00 80 c6 87 c8 dd 00
RIP [<ffffffff883f8b76>] :vboxdrv:g_abExecMemory+0x3156/0x180000
RSP <ffff810063c21f50>
[/quote]
docpneumo
 
Posts: 1
Joined: 18. Aug 2007, 18:51


Return to VirtualBox on Linux Hosts

Who is online

Users browsing this forum: No registered users and 36 guests