#449 bug when using virtualbox and kvm
kvm module version: v2.6.30-rc8-84-gf555fb2
QEMU PC emulator version 0.9.1 (kvm-72), Copyright (c) 2003-2008 Fabrice Bellard
CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-58
Host: Debian (sid), 32 bits
Guest: moblin developer image (linux, 32 bits )
Having kvm & kvm_amd loaded, and later loading vboxdrv, running a machine inside Virtualbox, closed it and tried to run another machine but on kvm using virt-manager i got this:
72646.987931] kvm: guest NX capability removed
[72647.211827] kvm: guest NX capability removed
[72647.212598] ------------[ cut here ]------------
[72647.212602] kernel BUG at arch/x86/kvm/../../../virt/kvm/kvm_main.c:2108!
[72647.212606] invalid opcode: 0000 [#1] SMP
[72647.212610] last sysfs file: /sys/class/net/lo/operstate
[72647.212613] Modules linked in: vboxnetflt vboxdrv xt_state ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ipt_REJECT xt_tcpudp
iptable_filter ip_tables x_tables bridge stp llc tun radeon drm i2c_core rfkill_input kvm_amd kvm loop snd_hda_codec_realtek snd_hda_intel snd_hda_codec arc4 ecb cryptomgr
aead pcompress crypto_blkcipher snd_hwdep crypto_hash snd_pcm_oss crypto_algapi snd_pcm b43 snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq snd_timer snd_seq_device snd
uvcvideo mac80211 soundcore cfg80211 nsc_ircc snd_page_alloc videodev v4l1_compat serio_raw pcspkr input_polldev yenta_socket rsrc_nonstatic irda crc_ccitt battery ac shpchp
pci_hotplug rtc_cmos rtc_core rtc_lib video button processor acer_wmi rfkill led_class wmi dm_mirror dm_region_hash dm_log dm_snapshot ahci thermal fan pata_atiixp libata
atiixp ext3 jbd reiserfs [last unloaded: vboxdrv]
[72647.212690]
[72647.212695] Pid: 19018, comm: kvm Not tainted (2.6.30-rc8-obelisco-generic #25) Extensa 5420
[72647.212699] EIP: 0060:[<fa8d8341>]</fa8d8341> EFLAGS: 00210046 CPU: 0
[72647.212718] EIP is at kvm_handle_fault_on_reboot+0x19/0x1d [kvm]
[72647.212721] EAX: 00000000 EBX: f7086160 ECX: 9629646d EDX: 00000000
[72647.212725] ESI: f5f50000 EDI: 00000000 EBP: f5f50000 ESP: c4495e40
[72647.212728] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[72647.212732] Process kvm (pid: 19018, ti=c4494000 task=f5faa940 task.ti=c4494000)
[72647.212735] Stack:
[72647.212737] 9629646d fa93e32c 00d80000 000000e0 9629646d 0000ae80 f5f50000 00000000
[72647.212744] f5f50034 fa8e0d77 f5f50000 f562457c c1f99000 f5f50690 f5f50890 f5f51220
[72647.212751] f5f51228 9629646d fa8e01f4 7ffbfeff fffffffe 9629646d 0000ae80 f5cbb700
[72647.212759] Call Trace:
[72647.212762] [<fa93e32c>]</fa93e32c> ? svm_vcpu_run+0x17a/0x29f [kvm_amd]
[72647.212772] [<fa8e0d77>]</fa8e0d77> ? kvm_arch_vcpu_ioctl_run+0x572/0x885 [kvm]
[72647.212790] [<fa8e01f4>]</fa8e01f4> ? kvm_arch_vcpu_ioctl_get_sregs+0x20f/0x22b [kvm]
[72647.212808] [<fa8d86a2>]</fa8d86a2> ? kvm_vcpu_ioctl+0xf0/0x574 [kvm]
[72647.212823] [<c014b489>]</c014b489> ? do_futex+0xbb/0x78c
[72647.212831] [<fa8d85b2>]</fa8d85b2> ? kvm_vcpu_ioctl+0x0/0x574 [kvm]
[72647.212846] [<c019eeb2>]</c019eeb2> ? vfs_ioctl+0x2a/0x7f
[72647.212852] [<c019f37a>]</c019f37a> ? do_vfs_ioctl+0x473/0x4c1
[72647.212857] [<c014bc79>]</c014bc79> ? sys_futex+0x11f/0x147
[72647.212862] [<c019f40d>]</c019f40d> ? sys_ioctl+0x45/0x72
[72647.212867] [<c0102d0f>]</c0102d0f> ? sysenter_do_call+0x12/0x26
[72647.212872] Code: 14 24 65 33 15 14 00 00 00 74 05 e8 1b 0f 85 c5 59 c3 83 ec 04 65 a1 14 00 00 00 89 04 24 31 c0 80 3d f4 b1 8f fa 00 74 02 eb fe <0f> 0b eb fe 57 b9 07
00 00 00 83 ec 04 89 c7 65 a1 14 00 00 00
[72647.212909] EIP: [<fa8d8341>]</fa8d8341> kvm_handle_fault_on_reboot+0x19/0x1d [kvm] SS:ESP 0068:c4495e40
[72647.212926] ---[ end trace a16b443ec925cf9c ]---
(vboxdrv version: 2.2.4_OSE)
Dont know if its a well known "bug".
Best Regards
Costantino Leandro lcostantino@gmai.com
Related
Hi,
Do you still see this problem with recent KVM?
Jes