VirtualBox

Opened 17 years ago

Closed 17 years ago

Last modified 17 years ago

#520 closed defect (duplicate)

VB 1.4 crashes on fedora 7 launching a vm

Reported by: jcezanna56 Owned by:
Component: other Version: VirtualBox 1.4.0
Keywords: crash kernel fault Cc:
Guest type: other Host type: other

Description

I can create a vm but when I try to launch it to install, a new window is opened, a dialog annouces starting and everything freezes. I have to kill and xkill everything. VirtualBox is unusable.


$ ls -d /opt/V* ; uname -a /opt/VirtualBox-1.4.0 Linux nadiav12 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686 i686 i386 GNU/Linux


Syslog messages : Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: general protection fault: 0000 #2 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: SMP Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: CPU: 1 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: EIP: 0060:[<052a10de>] Tainted: P VLI Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: EFLAGS: 00010002 (2.6.22.1-27.fc7 #1) Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: EIP is at 0x52a10de Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: eax: 00000254 ebx: 00000046 ecx: 00000000 edx: 03e7e300 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: esi: 00000000 edi: 00000000 ebp: ea6c8fc4 esp: ea6c8f70 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: ds: 007b es: 007b fs: 0000 gs: 0033 ss: 0068 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: Process VirtualBox (pid: 11132, ti=ea6c8000 task=ed67a000 task.ti=ea6c8000) Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: Stack: 052a100b ec2b0060 f8c8c307 03e7e000 ed67a000 ed67a000 00000046 08e712e0 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: ea6c8fb8 ea6c8000 c0407bc4 00000046 b66da0a0 00000001 00000003 08e712e0 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: b66da0e0 c0405082 03e7e000 64726962 03e7e000 b66da1a8 f8c68034 03e7e000 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: [<c0407bc4>] do_syscall_trace+0x2f/0xc2 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: Call Trace: Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: [<c0405082>] syscall_exit_work+0x12/0x17 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: [<c060007b>] xfrm_user_rcv_msg+0xac/0xfc Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: ======================= Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: Code: Bad EIP value. Message from syslogd@ at Thu Jul 26 16:49:04 2007 ...

Change History (5)

comment:1 by Technologov, 17 years ago

How you tried with SELinux enabled or disabled ? (VBox doesn't like SELinux)

comment:2 by Technologov, 17 years ago

Also 2.6.22 is not F7 kernel, it's your own kernel. F7 uses 2.6.21 kernel.

How you installed VBOX:

Did you compile youself ?

Did you used official F7 RPMs ?

Did you used all-distro installer (.run) ?

In my practise, the all-distro installer is the most stable way to get VBox up and running.

comment:3 by daves, 17 years ago

I'm having the same (or very similar) issue - details below. Technologov for info 2.6.22 is an official Fedora kernel, see my uname output below, kernel was updated via yum just a few days ago from official repository. I only see this issue on x86_64 - I have an installation running perfectly well on same kernel version but 32bit i686. SELinux is disabled and I used the official F7 x86_64 rpm (.run) from www.virtualbox.org

uname: Linux orac.bluecoat.notts.sch.uk 2.6.22.1-33.fc7 #1 SMP Mon Jul 23 16:59:15 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux

dmesg: general protection fault: 0000 [5] SMP last sysfs file: /devices/pci0000:00/0000:00:00.0/irq CPU 1 Modules linked in: nls_utf8 hfsplus vboxdrv(U) radeon drm autofs4 hidp rfcomm l2cap bluetooth sunrpc ipv6 cpufreq_ondemand dm_multipath video sbs button dock battery ac lp loop snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device firewire_ohci snd_pcm_oss snd_mixer_oss snd_pcm sr_mod k8temp parport_pc cdrom hwmon r8169 ata_generic i2c_nforce2 parport snd_timer forcedeth rtc_cmos firewire_core i2c_core snd soundcore snd_page_alloc shpchp crc_itu_t serio_raw sg dm_snapshot dm_zero dm_mirror dm_mod pata_amd sata_nv libata sd_mod scsi_mod ext3 jbd mbcache ehci_hcd ohci_hcd uhci_hcd Pid: 13194, comm: VirtualBox Tainted: P 2.6.22.1-33.fc7 #1 RIP: 0010:[<ffffffff883c5b76>] [<ffffffff883c5b76>] :vboxdrv:g_abExecMemory+0x3156/0x180000 RSP: 0000:ffff8100434e3f50 EFLAGS: 00010056 RAX: 0000000000001d01 RBX: 000000000000091b RCX: 00000000c0000080 RDX: 0000000000000000 RSI: 0000000000000d01 RDI: 00002aaab4847000 RBP: ffff8100434e3f58 R08: 0000000069746e65 R09: 0000000001000020 R10: 0000000000002001 R11: 00000000444d4163 R12: 00002aaab4847000 R13: 0000000000010004 R14: 0000000000000097 R15: 00002aaab01f50d0 FS: 0000000041fa6950(0063) GS:ffff810002382280(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00002aaab5427930 CR3: 000000005cb20000 CR4: 00000000000006e0 Process VirtualBox (pid: 13194, threadinfo ffff8100434e2000, task ffff810022696800) Stack: 0000000000000000 ffff8100434e3fa8 ffffffff883c2f81 0000000000000000

00002aaab4847000 0000000041fa5f20 0000000000000097 0000000000000000 00002aaab4847000 00002aaab00dbd20 00002aaaafa30380 0000000041fa5f20

Call Trace:

[<ffffffff883c2f81>] :vboxdrv:g_abExecMemory+0x561/0x180000 [<ffffffff884022c6>] :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 [<ffffffff883c5b76>] :vboxdrv:g_abExecMemory+0x3156/0x180000

RSP <ffff8100434e3f50>

comment:4 by Sander van Leeuwen, 17 years ago

Resolution: duplicate
Status: newclosed

Duplicate of 482.

comment:5 by madve, 17 years ago

It is duplicate of 484, isn't it?

http://www.virtualbox.org/ticket/484

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use