From: "T. Weyergraf" <kirk@colinet.de>
To: kvm@vger.kernel.org
Subject: Solaris Guest Failures
Date: Sat, 01 Nov 2008 15:51:11 +0100 [thread overview]
Message-ID: <490C6CDF.70505@colinet.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1777 bytes --]
Hi,
installing Solairs 10/08 x86 crashes the Host-Kernel on my
System.
System: Intel Q6600-base, Fedora 9 x86_64, lastest Kernel
Version 2.6.26.6-79.fc9.x86_64, kvm completely replaced
by kvm-77 (Modules und Userspace).
My 'standard' kvm-commandline:
kvm -smp 2 -m 3072 -net nic,macaddr=DE:AD:BE:EF:02:01,model=e1000 -net
tap,script=no -drive
index=0,media=disk,if=ide,file=/dev/hydra/opensol0508 -cdrom
/home/iso/sol-10-u6-ga1-x86-dvd.iso -boot d -daemonize
Desription: The VM boots the Solaris installkernel using
Grub. While booting, Solaris already fails to configure the
NIC, detected as e1000g0. This should not happen, since the
above Network-Config allows access to the DHCP-Server.
After choosing the 'Solaris interactive Installation", the
System walks through the initial configuration dialog up
to the point, were it starts the graphical installer. The
graphics-Screen fails to detect the mouse and falls back
to the text-session. After configuring the Network (either
manually, giving static adress oder using dhcp), the Host
kernel OOPSes shortly after. See the attached OOPS for
details.
Notes: I have also tried non-SMP and no-acpi with various
combinations, even reducing the memory-size to 2048. I always
get the same result. I have not yet tried '-no-kvm' but could
at your request. The Host-OS and hardware runs other VMs without
any trouble and sees high loads regularily, so I can rule
out any hardware or OS-related troubles with fair confidence.
If you need further information, or want me to test different
configurations, let me know.
As a side note: Thanks for kvm, great job!
Regards,
Thomas Weyergraf
--
Thomas Weyergraf kirk@colinet.de
--- Life is what happens while you have other plans ---
[-- Attachment #2: kvm-oops-solaris-1010-install.txt --]
[-- Type: text/plain, Size: 3685 bytes --]
Kernel failure message 1:
BUG: unable to handle kernel paging request at ffff811e001e0ec0
IP: [<ffffffffa0a9fc57>] :kvm:paging64_shadow_invlpg_entry+0x12/0x63
PGD 8063 PUD 0
Oops: 0000 [1] SMP
CPU 1
Modules linked in: tun ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 ipt_REJECT iptable_filter ip_tables bnep rfcomm l2cap bluetooth iscsi_trgt crc32c libcrc32c coretemp it87 hwmon_vid hwmon fuse sunrpc bridge bonding ip6t_REJECT xt_tcpudp nf_conntrack_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables x_tables ipv6 cpufreq_ondemand acpi_cpufreq freq_table dm_multipath kvm_intel kvm e1000 snd_hda_intel nvidia(P) snd_seq_dummy snd_seq_oss jedec_probe snd_seq_midi_event snd_seq snd_seq_device cfi_probe gen_probe i2c_nforce2 shpchp snd_pcm_oss snd_mixer_oss mtd chipreg snd_pcm ppdev snd_timer snd_page_alloc snd_hwdep pcspkr serio_raw firewire_ohci firewire_core snd soundcore pata_amd parport_pc parport map_funcs i2c_core sata_sil24 forcedeth crc_itu_t sg dm_snapshot dm_zero dm_mirror dm_log dm_mod sata_nv ata_generic pata_acpi libata sd_mod scsi_mod raid456 async_xor async_memcpy async_tx xor raid1 ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: microcode]
Pid: 26540, comm: kvm Tainted: P 2.6.26.6-79.fc9.x86_64 #1
RIP: 0010:[<ffffffffa0a9fc57>] [<ffffffffa0a9fc57>] :kvm:paging64_shadow_invlpg_entry+0x12/0x63
RSP: 0018:ffff810131a0fc28 EFLAGS: 00010246
RAX: ffff8101a8d74fa0 RBX: ffff811e001e0ec0 RCX: ffff811e001e0ec0
RDX: 00000000907d8000 RSI: ffff8101a8d74fa0 RDI: ffff810131a0fc88
RBP: ffff810131a0fc38 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000003
R13: ffff8101a8d74fa0 R14: ffff811e001e0ec0 R15: 00000000907d8000
FS: 00000000420e6950(0000) GS:ffff81023fc04880(0000) knlGS:0000000000000000
CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b
CR2: ffff811e001e0ec0 CR3: 000000013b5cc000 CR4: 00000000000026e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kvm (pid: 26540, threadinfo ffff810131a0e000, task ffff810221272d40)
Stack: ffff810131a0fc38 0000000000000001 ffff810131a0fc78 ffffffffa0a9f13c
ffff810131a0fc88 ffff8101a8d74fa0 00000000907d8000 000000000000000e
ffff81013970a000 ffff8101a8d751a0 ffff810131a0fcc8 ffffffffa0a9f1bb
Call Trace:
[<ffffffffa0a9f13c>] :kvm:walk_shadow+0x8c/0xb1
[<ffffffffa0a9f1bb>] :kvm:paging64_invlpg+0x32/0x34
[<ffffffffa0a9fc45>] ? :kvm:paging64_shadow_invlpg_entry+0x0/0x63
[<ffffffffa0a9f6df>] :kvm:kvm_mmu_invlpg+0x25/0x3e
[<ffffffffa0abf0ce>] :kvm_intel:handle_invlpg+0x1c/0x2d
[<ffffffffa0abf6d3>] :kvm_intel:kvm_handle_exit+0x201/0x223
[<ffffffff8129d514>] ? __down_read+0x1a/0xa6
[<ffffffffa0a9cefd>] :kvm:kvm_arch_vcpu_ioctl_run+0x506/0x777
[<ffffffff81055634>] ? do_futex+0xb5/0x962
[<ffffffff810a755c>] ? kfree+0x1/0xbc
[<ffffffffa0a9659d>] :kvm:kvm_vcpu_ioctl+0xf6/0x485
[<ffffffffa0a984e0>] ? :kvm:kvm_vm_ioctl+0x4fc/0x51c
[<ffffffff8100a710>] ? __switch_to+0xaa/0x39a
[<ffffffff8102a1d4>] ? hrtick_start_fair+0x14a/0x190
[<ffffffff810b9546>] vfs_ioctl+0x2a/0x78
[<ffffffff810b97db>] do_vfs_ioctl+0x247/0x261
[<ffffffff810b984a>] sys_ioctl+0x55/0x77
[<ffffffff8100c2c1>] tracesys+0xd0/0xd5
Nov 1 00:04:35 quad kernel:
Code: 20 48 85 ff 74 06 31 c0 31 c9 eb e5 0f 0b eb fe 5b 41 5c 41 5d 41 5e c9 c3 55 48 89 f0 48 89 e5 53 48 89 cb 48 83 ec 08 41 ff c8 <48> 8b 11 75 2e 48 3b 15 85 8b 01 00 74 14 48 3b 15 84 8b 01 00
RIP [<ffffffffa0a9fc57>] :kvm:paging64_shadow_invlpg_entry+0x12/0x63
RSP <ffff810131a0fc28>
CR2: ffff811e001e0ec0
---[ end trace 6d9980f93e35eed6 ]---
reply other threads:[~2008-11-01 14:51 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=490C6CDF.70505@colinet.de \
--to=kirk@colinet.de \
--cc=kvm@vger.kernel.org \
/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.