[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[debian-users:50603] linux-image-2.6.18-6-xen-amd64 + xen-hypervisor-3.2-1-amd64 でカーネルパニック
こうもとです。
linux-image-2.6.18-6-xen-amd64 + xen-hypervisor-3.2-1-amd64 の環境
でカーネルパニックが起こります。
5/28に、
linux-image-2.6.18-6-xen-amd64
linux-modules-2.6.18-6-xen-amd64
を2.6.18.dfsg.1-18etch5 にアップグレードしてから、2度ほど落ちまし
た。
Xen関係のパッケージは以下を使用しています。
saturn:~# dpkg -l|grep xen
ii libxenstore3.0 3.2.0-3~bpo4+2 Xenstore communications library for Xen
ii linux-image-2.6.18-6-xen-amd64 2.6.18.dfsg.1-18etch5 Linux 2.6.18 image on AMD64
ii linux-modules-2.6.18-6-xen-amd64 2.6.18.dfsg.1-18etch5 Linux 2.6.18 modules on AMD64
ii xen-docs-3.2 3.2.0-3~bpo4+2 Documentation for Xen
ii xen-hypervisor-3.2-1-amd64 3.2.0-3~bpo4+2 The Xen Hypervisor on AMD64
ii xen-tools 3.9-2~bpo40+1 Tools to manage Debian XEN virtual servers
ii xen-utils-3.2-1 3.2.0-3~bpo4+2 XEN administrative tools
ii xen-utils-common 3.2.0-1~bpo4+1 XEN administrative tools - common files
ii xenstore-utils 3.2.0-3~bpo4+2 Xenstore utilities for Xen
Xenだけbackportsから持ってきているのも原因の一部かもしれませんが、
5/28までは特に問題なく動作していたので、カーネルのアップデートを疑っ
ています。
kern.log,messages,syslogを見てみましたが、ログは一切出力されていま
せんでした。
コンソールにのみログが表示されていたので、写真に撮った物を転記しま
す。
==========================================================
[<ffffffff80360a21>] unmask_evtchn+0x2d/0xd7
[<ffffffff8026c2ae>] xen_send_IPI_mask+0x0/0xa8
[<ffffffff8027c9c6>] task_rq_lock+0x3f/0x71
[<ffffffff8027c237>] find_busiest_group+0x1d9/0x478
[<ffffffff80360a54>] unmask_evtchn+0x60/0xd7
[<ffffffff8025c56b>] error_exit+0x0/0x6e
[<ffffffff8036105a>] retrigger+0x0/0x3e
[<ffffffff80361080>] retrigger+0x26/0x3e
[<ffffffff802a06d6>] enable_irq+0x9d/0xbc
[<ffffffff8806a881>] :3c59x:vortex_timer+0x336/0x384
[<ffffffff8806a54b>] :3c59x:vortex_timer+0x0/0x384
[<ffffffff80286e26>] run_timer_softirq+0x13f/0x1c6
[<ffffffff80212593>] __do_softirq+0x62/0xdd
[<ffffffff8025cae4>] call_softirq+0x1c/0x28
[<ffffffff802665e7>] do_softirq+0x31/0x90
[<ffffffff802665ad>] do_IRQ+0x6a/0x73
[<ffffffff80361000>] evtchn_do_upcall+0x86/0xe0
[<ffffffff8025c616>] do_hypervisor_callback+0x1e/0x2c
<EOI> [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
[<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
[<ffffffff80267336>] raw_safe_halt+0x84/0xa8
[<ffffffff802645ab>] xen_idle+0x38/0x4a
[<ffffffff8024883e>] cpu_idle+0x97/0xba
==========================================================
元の写真は以下の場所に置いているので、typoの確認が必要であれば見て
ください。
http://rayearth.homelinux.net/20080530/
＃もし落ちていたら、(オレオレ証明ですが)httpsで繋いでみてください。
エラー内容にNICの名前があったので、lspciの結果も載せます。
00:00.0 Host bridge: Intel Corporation 5000V Chipset Memory
Controller Hub (rev 92)
00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 (rev 92)
00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev 92)
00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev 92)
00:10.0 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
00:10.1 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
00:10.2 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 92)
00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 92)
00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 92)
00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 92)
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)
00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)
00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)
00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)
00:1d.3 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09)
00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 21)
02:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)
02:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)
03:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)
03:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01)
04:00.0 PCI bridge: Intel Corporation 6702PXH PCI Express-to-PCI Bridge A (rev 09)
05:08.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068 PCI-X Fusion-MPT SAS (rev 01)
09:02.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]
09:09.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)
3c905は、eth1として見えています。
Xenの関係の設定ファイルは以下のようになっています。
** xend-config.sxp **
(network-script network-bridge.eth1)
(vif-script vif-bridge)
(dom0-min-mem 196)
(dom0-cpus 0)
(vncpasswd '')
** network-bridge.eth1 **
#!/bin/sh
script=/etc/xen/scripts/network-bridge
case $1 in
start|stop|status)
$script $1 netdev=eth0
$script $1 netdev=eth1
;;
*)
echo "unkown $1"
exit 1
esac
** domU1.cfg
kernel = '/boot/vmlinuz-2.6.18-6-xen-amd64'
ramdisk = '/boot/initrd.img-2.6.18-6-xen-amd64'
memory = '1500'
vcpus = 3
root = '/dev/sda1 ro'
disk = [ 'phy:/dev/sda3,sda1,w', 'phy:/dev/sda7,sda2,w' ]
name = 'domU1'
vif = [ 'mac=00:16:3e:00:00:01' ]
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
** domU2.cfg **
kernel = '/boot/vmlinuz-2.6.18-6-xen-amd64'
ramdisk = '/boot/initrd.img-2.6.18-6-xen-amd64'
memory = '4096'
vcpus = 6
root = '/dev/sda1 ro'
disk = [ 'phy:/dev/sda2,sda1,w', 'phy:/dev/sda6,sda2,w' ]
name = 'domU2'
vif = [ 'mac=00:16:3e:00:00:02', 'mac=00:16:3e:00:00:03,bridge=xenbr1' ]
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
一発でブリッジ接続にならないので、起動後にbrctlでブリッジの指定を
変えてdomU2を起動しています。
結構ややこしい環境ですが、何か見直すような設定はありますか。
----------------------------------------------------------------------
河本陽一(こうもとよういち)
mailto:youichi@xxxxxxxxxxxxxx