As many of you know by my many e-mails regarding the subject, I'm
working with PCI and graphics passthrough on my systems. I'm running
into yet another issue. Seems that if I bump the RAM assigned to the
domU up over 2GB (I've tried 3GB and 4GB), I run into some sort of error
or bug, or perhaps a misconfiguration. The problem manifests itself in
the domU hanging and not responding, and in some interesting output in
dmesg (see below). Any ideas? I'm running Xen 4.0.0 on openSUSE 11.3.
Xen is 4.0.0_21091_05-6.6, kernel is 2.6.34.4-0.1-xen (not pvops). Also
below is the domU configuration:
Thanks,
Nick
--domU config--
name="SomeName"
description="Some Description"
uuid="6a9c4b14-d6a7-d673-ffdb-81a8faca17e2"
memory=4096
maxmem=4096
vcpus=4
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=1
keymap="en-us"
builder="hvm"
device_model="/usr/lib/xen/bin/qemu-dm"
kernel="/usr/lib/xen/boot/hvmloader"
boot="c"
disk=[ 'phy:/dev/local/Local7,hda,w', ',hdc:cdrom,r',]
vif=[ 'mac=00:16:3e:31:b7:71,bridge=br0,model=rtl8139', ]
videoram=32
extid=0
hpet=1
viridian=1
localtime=1
usb=1
acpi=1
pae=1
usbdevice='tablet'
serial="pty"
gfx_passthru=1
pci=['00:02.0', '00:02.1', '00:1d.0', '00:1d.1', '00:1d.2', '00:1a.0',
'00:1a.1', '00:1a.2', '00:1b.0', '00:1a.7', '00:1d.7']
--End domU config--
--dmesg output--
[ 1141.197051] device vif4.0 entered promiscuous mode
[ 1141.209930] (cdrom_add_media_watch()
file=/usr/src/packages/BUILD/kernel-xen-2.6.34.4/linux-2.6.34/drivers/xen/blkback/cdrom.c,
line=108) nodename:backend/vbd/4/768
[ 1141.209940] (cdrom_is_type()
file=/usr/src/packages/BUILD/kernel-xen-2.6.34.4/linux-2.6.34/drivers/xen/blkback/cdrom.c,
line=95) type:0
[ 1142.240237] device tap4.0 entered promiscuous mode
[ 1359.863445] BUG: soft lockup - CPU#3 stuck for 203s! [xend:7685]
[ 1359.863445] Modules linked in: tun usbbk usbcore gntdev netbk blkbk
blkback_pagemap blktap evtchn autofs4 edd nfs lockd fscache nfs_acl
auth_rpcgss sunrpc af_packet fuse loop b
rcompat_mod openvswitch_mod dcdbas domctl ppdev parport_pc parport
iTCO_wdt dell_wmi e1000e i2c_i801 iTCO_vendor_support sg wmi pcspkr
8250_pci 8250_pnp 8250 serial_core serio_raw
linear i915 drm_kms_helper drm i2c_algo_bit i2c_core video output
sd_mod button intel_agp agpgart dm_snapshot dm_mod xenblk cdrom xennet
fan processor ahci ata_generic libata scs
i_mod thermal thermal_sys hwmon pciback xenbus_be
[ 1359.863445] CPU 3
[ 1359.863445] Modules linked in: tun usbbk usbcore gntdev netbk blkbk
blkback_pagemap blktap evtchn autofs4 edd nfs lockd fscache nfs_acl
auth_rpcgss sunrpc af_packet fuse loop b
rcompat_mod openvswitch_mod dcdbas domctl ppdev parport_pc parport
iTCO_wdt dell_wmi e1000e i2c_i801 iTCO_vendor_support sg wmi pcspkr
8250_pci 8250_pnp 8250 serial_core serio_raw
linear i915 drm_kms_helper drm i2c_algo_bit i2c_core video output
sd_mod button intel_agp agpgart dm_snapshot dm_mod xenblk cdrom xennet
fan processor ahci ata_generic libata scs
i_mod thermal thermal_sys hwmon pciback xenbus_be
[ 1359.863445]
[ 1359.863445] Pid: 7685, comm: xend Not tainted 2.6.34.4-0.1-xen #1
03NVJ6/OptiPlex 780
[ 1359.863445] RIP: e030:[<ffffffff8000348a>] [<ffffffff8000348a>]
0xffffffff8000348a
[ 1359.863445] RSP: e02b:ffff8800d880ddb0 EFLAGS: 00000282
[ 1359.863445] RAX: 0000000000000000 RBX: ffff8800d880de38 RCX:
ffffffff8000348a
[ 1359.863445] RDX: 00007fdf211b3a6c RSI: ffffffff013d0540 RDI:
0000000001c2e000
[ 1359.863445] RBP: ffffffff80003480 R08: 00007fdf2b2ae318 R09:
00007fdf211b3a70
[ 1359.863445] R10: 00007fdf211b3a70 R11: 0000000000000282 R12:
0000000000305000
[ 1359.863445] R13: 0000000000000000 R14: ffffffff802e1f50 R15:
ffff8801e3185040
[ 1359.863445] FS: 00007fdf211b7710(0000) GS:ffff880002044000(0000)
knlGS:0000000000000000
[ 1359.863445] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1359.863445] CR2: 0000000001c2e000 CR3: 00000001e2bf5000 CR4:
0000000000002660
[ 1359.863445] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 1359.863445] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[ 1359.863445] Process xend (pid: 7685, threadinfo ffff8800d880c000,
task ffff8800cb2e6580)
[ 1359.863445] Stack:
[ 1359.863445] 0000000000000246 0000000000000000 ffffffff802e206d
ffff8800d881d000
[ 1359.863445] <0> 0000000000000000 80000001e488d167 ffffffff80024691
0000000000000000
[ 1359.863445] <0> ffff8800d8ad1db0 ffff880006c5d520 ffffffff800ec5c5
0000000000000024
[ 1359.863445] Call Trace:
[ 1359.863445] [<ffffffff802e206d>] privcmd_ioctl+0x11d/0xa40
[ 1359.863445] [<ffffffff8016ca74>] proc_reg_unlocked_ioctl+0x94/0x170
[ 1359.863445] [<ffffffff801237d9>] vfs_ioctl+0x39/0xc0
[ 1359.863445] [<ffffffff80123d70>] do_vfs_ioctl+0x70/0x3f0
[ 1359.863445] [<ffffffff80124170>] sys_ioctl+0x80/0xa0
[ 1359.863445] [<ffffffff80007438>] system_call_fastpath+0x16/0x1b
[ 1359.863445] [<00007fdf2a2e5e87>] 0x7fdf2a2e5e87
[ 1359.863445] Code: cc 51 41 53 b8 23 00 00 00 0f 05 41 5b 59 c3 cc cc
cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 24 00 00 00
0f 05 <41> 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc
[ 1359.863445] Call Trace:
[ 1359.863445] [<ffffffff802e206d>] privcmd_ioctl+0x11d/0xa40
[ 1359.863445] [<ffffffff8016ca74>] proc_reg_unlocked_ioctl+0x94/0x170
[ 1359.863445] [<ffffffff801237d9>] vfs_ioctl+0x39/0xc0
[ 1359.863445] [<ffffffff80123d70>] do_vfs_ioctl+0x70/0x3f0
[ 1359.863445] [<ffffffff80124170>] sys_ioctl+0x80/0xa0
[ 1359.863445] [<ffffffff80007438>] system_call_fastpath+0x16/0x1b
[ 1359.863445] [<00007fdf2a2e5e87>] 0x7fdf2a2e5e87
--End dmesg output--
--------
This e-mail may contain confidential and privileged material for the sole use
of the intended recipient. If this email is not intended for you, or you are
not responsible for the delivery of this message to the intended recipient,
please note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information. In such a case, you are strictly
prohibited from downloading, photocopying, distributing or otherwise using this
message, its contents or attachments in any way. If you have received this
message in error, please notify us immediately by replying to this e-mail and
delete the message from your mailbox. Information contained in this message
that does not relate to the business of SEAKR is neither endorsed by nor
attributable to SEAKR.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home