From: Tomas Rusnak <linker@korex.sk>
To: kvm-devel@lists.sourceforge.net
Subject: Booting with lilo after kvm upgrade to kvm-64
Date: Mon, 21 Apr 2008 10:17:55 +0200 [thread overview]
Message-ID: <480C4DB3.6060207@korex.sk> (raw)
Hello everybody
After I update to KVM-66 (from 65), I have problem to boot guests with
lilo installed. Boot sequence always stop with "LIL" output. With kvm-65
everythink works great. I have also windows XP guest, which boot without
problem. With -no-kvm guests boot ok.
Processor: AMD Opteron 2210
KVM: kvm-64
Host: gentoo-sources-2.6.25-r1
Arch: x86_64
Guests: gentoo, 2.6.25, x86_64
dmesg:
Apr 21 09:53:37 kvm BUG: unable to handle kernel NULL pointer
dereference at 0000000000000000
Apr 21 09:53:37 kvm IP: [<ffffffff88029c85>]
:kvm:x86_emulate_insn+0x3a47/0x468f
Apr 21 09:53:37 kvm PGD 11e989067 PUD 11ec0a067 PMD 0
Apr 21 09:53:37 kvm Oops: 0002 [2] SMP
Apr 21 09:53:37 kvm CPU 2
Apr 21 09:53:37 kvm Modules linked in: w83627hf hwmon_vid xt_tcpudp
xt_state iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4
nf_conntrack iptable_filter ip_tables x_tables tun kvm_amd kvm shpchp
pci_hotplug k8temp i2c_nforce2 i2c_core
Apr 21 09:53:37 kvm Pid: 7130, comm: kvm Tainted: G D
2.6.25-gentoo-r1 #1
Apr 21 09:53:37 kvm RIP: 0010:[<ffffffff88029c85>] [<ffffffff88029c85>]
:kvm:x86_emulate_insn+0x3a47/0x468f
Apr 21 09:53:37 kvm RSP: 0018:ffff81011e3e5738 EFLAGS: 00010246
Apr 21 09:53:37 kvm RAX: 0000000000000010 RBX: 0000000000000000 RCX:
ffff81011e3e7378
Apr 21 09:53:37 kvm RDX: 0000000000000000 RSI: 0000000000000000 RDI:
ffff81011e3e6000
Apr 21 09:53:37 kvm RBP: ffff81011e3e7378 R08: 0000000000000000 R09:
0000000000000000
Apr 21 09:53:37 kvm R10: ffffffff88041988 R11: ffff81011e3e7378 R12:
ffff81011e3e7330
Apr 21 09:53:37 kvm R13: 0000000000000000 R14: ffffffff88033a20 R15:
0000000000000ce3
Apr 21 09:53:37 kvm FS: 0000000041e68950(0063)
GS:ffff81011ff1b000(0000) knlGS:0000000000000000
Apr 21 09:53:37 kvm CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Apr 21 09:53:37 kvm CR2: 0000000000000000 CR3: 000000011e1af000 CR4:
00000000000006e0
Apr 21 09:53:37 kvm DR0: ffffffff805b34f8 DR1: 0000000000000000 DR2:
0000000000000000
Apr 21 09:53:37 kvm DR3: 0000000000000000 DR6: 00000000ffff0ff1 DR7:
0000000000000701
Apr 21 09:53:37 kvm Process kvm (pid: 7130, threadinfo ffff81011e3e4000,
task ffff81011e560000)
Apr 21 09:53:37 kvm Stack: ffffffff8021a311 000000000000000f
00000000fffffff7 ffffffff8021a49b
Apr 21 09:53:37 kvm 00000000ffffffff ffff81011ed41d00 ffffc20001926000
0000000000000000
Apr 21 09:53:37 kvm ffffffff8021a311 ffffffff802347a0 ffff81011ed41d00
ffffffff880419e0
Apr 21 09:53:37 kvm Call Trace:
Apr 21 09:53:37 kvm [<ffffffff8021a311>] ? do_flush_tlb_all+0x0/0x2f
Apr 21 09:53:37 kvm [<ffffffff8021a49b>] ? smp_call_function_mask+0x47/0x55
Apr 21 09:53:37 kvm [<ffffffff8021a311>] ? do_flush_tlb_all+0x0/0x2f
Apr 21 09:53:37 kvm [<ffffffff802347a0>] ? on_each_cpu+0x19/0x25
Apr 21 09:53:37 kvm [<ffffffff880419e0>]
Apr 21 09:53:37 kvm [<ffffffff88020501>] ?
:kvm:kvm_get_cs_db_l_bits+0x9/0x2f
Apr 21 09:53:37 kvm [<ffffffff8801f101>] ?
:kvm:emulate_instruction+0x1ef/0x3a5
Apr 21 09:53:37 kvm [<ffffffff8801f101>] ?
:kvm:emulate_instruction+0x1ef/0x3a5
Apr 21 09:53:37 kvm [<ffffffff88041fbc>]
Apr 21 09:53:37 kvm [<ffffffff88020148>] ?
:kvm:kvm_arch_vcpu_ioctl_run+0x44a/0x5b8
Apr 21 09:53:37 kvm [<ffffffff8801bf23>] ? :kvm:kvm_resched+0x1b4/0x9b7
Apr 21 09:53:37 kvm [<ffffffff8802ad63>] ? :kvm:kvm_pic_set_irq+0x21/0x6b
Apr 21 09:53:37 kvm [<ffffffff8801e81b>] ?
:kvm:kvm_arch_vm_ioctl+0x38e/0x5e6
Apr 21 09:53:37 kvm [<ffffffff8026217b>] ? zone_statistics+0x41/0x94
Apr 21 09:53:37 kvm [<ffffffff8025bc16>] ?
get_page_from_freelist+0x457/0x5af
Apr 21 09:53:37 kvm [<ffffffff8025bdc0>] ? __alloc_pages+0x52/0x2ee
Apr 21 09:53:37 kvm [<ffffffff80225e50>] ? source_load+0x25/0x41
Apr 21 09:53:37 kvm [<ffffffff802286f1>] ? find_busiest_group+0x268/0x742
Apr 21 09:53:37 kvm [<ffffffff80225552>] ? hrtick_set+0x99/0x107
Apr 21 09:53:37 kvm [<ffffffff805b3aae>] ? thread_return+0x64/0xa5
Apr 21 09:53:37 kvm [<ffffffff80249099>] ? get_futex_key+0x76/0x14d
Apr 21 09:53:37 kvm [<ffffffff80249816>] ? unqueue_me+0x6b/0x73
Apr 21 09:53:37 kvm [<ffffffff80249bc1>] ? futex_wait+0x290/0x327
Apr 21 09:53:37 kvm [<ffffffff80227c36>] ? try_to_wake_up+0xfa/0x10c
Apr 21 09:53:37 kvm [<ffffffff80229752>] ? __wake_up_common+0x49/0x74
Apr 21 09:53:37 kvm [<ffffffff80268c29>] ? find_extend_vma+0x16/0x61
Apr 21 09:53:37 kvm [<ffffffff80249099>] ? get_futex_key+0x76/0x14d
Apr 21 09:53:37 kvm [<ffffffff803c1439>] ? __up_read+0x10/0x8a
Apr 21 09:53:37 kvm [<ffffffff8024955e>] ? futex_wake+0xfa/0x10c
Apr 21 09:53:37 kvm [<ffffffff80242e5a>] ? ktime_get_ts+0x56/0x5d
Apr 21 09:53:37 kvm [<ffffffff8801c3cb>] ? :kvm:kvm_resched+0x65c/0x9b7
Apr 21 09:53:37 kvm [<ffffffff80225552>] ? hrtick_set+0x99/0x107
Apr 21 09:53:37 kvm [<ffffffff8028a311>] ? vfs_ioctl+0x29/0x6f
Apr 21 09:53:37 kvm [<ffffffff8028a5a4>] ? do_vfs_ioctl+0x24d/0x25c
Apr 21 09:53:37 kvm [<ffffffff8028a5ef>] ? sys_ioctl+0x3c/0x61
Apr 21 09:53:37 kvm [<ffffffff8020b09b>] ?
system_call_after_swapgs+0x7b/0x80
Apr 21 09:53:37 kvm
Apr 21 09:53:37 kvm
Apr 21 09:53:37 kvm Code: 02 74 20 77 06 ff c8 74 0e eb 78 83 f8 04 74
20 83 f8 08 74 27 eb 6c 48 8b 51 40 48 8b 41 30 88 02 eb 60 48 8b 51 40
48 8b 41 30 <66> 89 02 eb 53 48 8b 41 40 8b 49 30 48 89 08 eb 47 48 8b 51 40
Apr 21 09:53:37 kvm RIP [<ffffffff88029c85>]
:kvm:x86_emulate_insn+0x3a47/0x468f
Apr 21 09:53:37 kvm RSP <ffff81011e3e5738>
Apr 21 09:53:37 kvm CR2: 0000000000000000
Apr 21 09:53:37 kvm ---[ end trace 8b01d2fbd0fdd57f ]---
--
Tomas Rusnak
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
reply other threads:[~2008-04-21 8:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=480C4DB3.6060207@korex.sk \
--to=linker@korex.sk \
--cc=kvm-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.