VirtualBox

Ticket #484 (closed defect: fixed)

Opened 15 years ago

Last modified 15 years ago

General proctection fault on Fedora 7 x64

Reported by: madve Owned by:
Component: other Version: VirtualBox 1.4.0
Keywords: Cc:
Guest type: other Host type: other

Description

Hi,

I installed successfully VirtualBox-1.4.0_21864_fedora7-1.x86_64.rpm on my system.

VirtualBox starts fine. After creating guest the program stops responding saying: "Starting the virtual machine... 0%"

I found the following in my messages file:

Jul  9 12:07:07 localhost kernel: sr0: CDROM not ready.  Make sure there is a disc in the drive.
Jul  9 12:07:23 localhost kernel: general protection fault: 0000 [1] SMP 
Jul  9 12:07:23 localhost kernel: last sysfs file: /devices/pci0000:00/0000:00:00.0/irq
Jul  9 12:07:23 localhost kernel: CPU 2 
Jul  9 12:07:23 localhost kernel: Modules linked in: i915 drm ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables bridge vboxdrv(U) autofs4 hidp rfcomm l2cap bluetooth sunrpc ipv6 cpufreq_ondemand acpi_cpufreq dm_mirror dm_multipath dm_mod video sbs i2c_ec button dock battery ac lp loop kvm_intel kvm snd_hda_intel snd_hda_codec r8169 snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm fw_ohci parport_pc snd_timer iTCO_wdt fw_core sr_mod cdrom parport shpchp snd soundcore iTCO_vendor_support snd_page_alloc serio_raw i2c_i801 i2c_core sg pcspkr ahci pata_jmicron ata_generic ata_piix libata sd_mod scsi_mod ext3 jbd mbcache ehci_hcd ohci_hcd uhci_hcd
Jul  9 12:07:23 localhost kernel: Pid: 3824, comm: VirtualBox Not tainted 2.6.21-1.3194.fc7 #1
Jul  9 12:07:23 localhost kernel: RIP: 0010:[<00002aaaaaad016f>]  [<00002aaaaaad016f>]
Jul  9 12:07:23 localhost kernel: RSP: 0000:ffff81002f1a3f50  EFLAGS: 00010002
Jul  9 12:07:23 localhost kernel: RAX: 0000000000000264 RBX: 00002aaaaff53320 RCX: 0000000000000000
Jul  9 12:07:23 localhost kernel: RDX: 00002aaaaff53320 RSI: 0000000000000004 RDI: 00002aaaaff53000
Jul  9 12:07:23 localhost kernel: RBP: ffff81002f1a3fa8 R08: 0000000000000000 R09: 00002aaaaff53000
Jul  9 12:07:23 localhost kernel: R10: 0000000000000000 R11: 0000000043304010 R12: 00002aaaaff53000
Jul  9 12:07:23 localhost kernel: R13: 0000000000000000 R14: 00002aaaafcf7380 R15: 0000000000a06fe0
Jul  9 12:07:23 localhost kernel: FS:  00000000415c6950(0063) GS:ffff810037c9e240(0000) knlGS:0000000000000000
Jul  9 12:07:23 localhost kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Jul  9 12:07:23 localhost kernel: CR2: 00002aaaaaf8f000 CR3: 000000004362c000 CR4: 00000000000026e0
Jul  9 12:07:23 localhost kernel: Process VirtualBox (pid: 3824, threadinfo ffff81002f1a2000, task ffff81002f6290c0)
Jul  9 12:07:23 localhost kernel: Stack:  00002aaaaaad0012 0000000000000010 ffffffff88381dab 00002aaaaff53000
Jul  9 12:07:23 localhost kernel:  0000000000000000 00000000415c5ee0 0000000000000046 0000000000000000
Jul  9 12:07:23 localhost kernel:  0000000000000000 00002aaaaff53000 00002aaaafcf7380 00000000415c5f20
Jul  9 12:07:23 localhost kernel: Call Trace:
Jul  9 12:07:23 localhost kernel:  [<ffffffff88381dab>] :vboxdrv:g_abExecMemory+0x36b/0x180000
Jul  9 12:07:23 localhost kernel:  [<ffffffff883c12e6>] :vboxdrv:g_abExecMemory+0x3f8a6/0x180000
Jul  9 12:07:23 localhost kernel: 
Jul  9 12:07:23 localhost kernel: 
Jul  9 12:07:23 localhost kernel: Code:  Bad RIP value.
Jul  9 12:07:23 localhost kernel: RIP  [<00002aaaaaad016f>]
Jul  9 12:07:23 localhost kernel:  RSP <ffff81002f1a3f50>

My system:

[root@localhost ~]# uname -a
Linux localhost.localdomain 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux

[root@localhost proc]# cat cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 Quad CPU           @ 2.40GHz
stepping        : 7
cpu MHz         : 1596.000
cache size      : 4096 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips        : 4802.52
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

...

Change History

comment:1 Changed 15 years ago by Technologov

Maybe your bug is similar to bug #520 ?

comment:2 Changed 15 years ago by madve

Yes, it seems that I'm having the same or very similar issue.

comment:3 Changed 15 years ago by sandervl73

If you have KVM installed (kernel driver), then you can try to remove it. I'm not sure if it's the same issue, but let's try to eliminate this possibility first.

comment:4 Changed 15 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

The kernel messages show clearly that the kvm_intel module is loaded. VirtualBox 1.5.0 will refuse to start in this case. BTW: VMware server 1.0.3 will show similar symptoms.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use