>>> Tetsuo Handa <[email protected]> 27.01.2009 01:54 >>> Hello.
Thank you for trying. Vadim Korschok wrote: > After that i have installed KVM-82 to start my virtual machines. But i have > no chance to, dmesg shows me: >Is it possible to get function names in call trace? >I think you can get function names by > CONFIG_KALLSYMS=y > CONFIG_KALLSYMS_ALL=y >in your kernel config. >I want to see a call trace like >https://bugs.launchpad.net/ubuntu/+source/linux/+bug/258450/+viewstatus . Thats my output with 2.6.27-ccs-hardened-r4 and KALLSYMS_ALL: SAKURA: 1.6.5 2008/11/11 TOMOYO: 1.6.5+ 2008/12/10 Mandatory Access Control activated. SAKURA-NOTICE: 'mount proc on /proc/ 0xE' accepted. SAKURA-NOTICE: 'mount sysfs on /sys/ 0xE' accepted. SAKURA-NOTICE: 'mount tmpfs on /dev/ 0x2' accepted. udev: renamed network interface eth2 to eth0 udev: renamed network interface eth0_rename to eth2 SAKURA-NOTICE: 'mount devpts on /dev/pts/ 0xA' accepted. SAKURA-NOTICE: 'mount -o remount / 0x400' accepted. EXT3 FS on hda3, internal journal loaded kvm module (kvm-81) SAKURA-NOTICE: 'mount -t ext3 /dev/hda1 /boot/ 0x400' accepted. kjournald starting. Commit interval 5 seconds EXT3 FS on hda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. SAKURA-NOTICE: 'mount usbfs on /proc/bus/usb/ 0xA' accepted. SAKURA-NOTICE: 'mount securityfs on /sys/kernel/security/ 0xE' accepted. Adding 2008116k swap on /dev/hda2. Priority:-1 extents:1 across:2008116k device eth0 entered promiscuous mode 0000:00:19.0: eth0: Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX 0000:00:19.0: eth0: 10/100 speed: disabling TSO brlan: port 1(eth0) entering learning state brlan: topology change detected, propagating brlan: port 1(eth0) entering forwarding state device tap0 entered promiscuous mode brlan: port 2(tap0) entering learning state kvm: 6199: cpu0 unhandled wrmsr: 0xc0010117 data 0 PAX: kvm:6209, uid/euid: 0/0, attempted to modify kernel code BUG: unable to handle kernel paging request at ffffffff8059b040 IP: [<ffffffffa00394d3>] intel_iommu_found+0x4d3/0x4075 [kvm_intel] PGD 591067 PUD 596063 PMD 4001e1 Oops: 0003 [1] SMP CPU 3 Modules linked in: kvm_intel kvm Pid: 6209, comm: kvm Not tainted 2.6.27-ccs_hardened-r1 #3 RIP: 0010:[<ffffffffa00394d3>] [<ffffffffa00394d3>] intel_iommu_found+0x4d3/0x4075 [kvm_intel] RSP: 0018:ffff880129147d98 EFLAGS: 00010286 RAX: 8000898068402087 RBX: ffff8801278e0040 RCX: ffffffff8059b000 RDX: 0000090000000000 RSI: ffff880129147de8 RDI: ffff8801278e0040 RBP: 00000000fffffffc R08: 0000000000000001 R09: 0000000000000000 R10: ff2002ffff2002ff R11: ffffffffa003a128 R12: 00000000fffffffc R13: ffff880127db4000 R14: 0000000000000000 R15: 0000000000000000 FS: 00000000417ac950(0063) GS:ffff88012badcdc0(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffff8059b040 CR3: 0000000128070000 CR4: 00000000000026e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process kvm (pid: 6209, threadinfo ffff880129146000, task ffff8801286f4c70) Stack: ffff8059b000007f 000000000000ffff ffff8801278e0040 ffff8801278e0040 00000000fffffffc ffffffffa0016b9b ffff8801278e0040 ffffffffa001313d ffff8801278e0040 ffffffffa00196d1 fffffffe7ffbfeff ffff880128deb400 Call Trace: [<ffffffffa0016b9b>] ? kvm_arch_vcpu_put+0xe/0x218 [kvm] [<ffffffffa001313d>] ? vcpu_put+0x9/0x9d [kvm] [<ffffffffa00196d1>] ? kvm_arch_vcpu_ioctl_run+0x5df/0x5ea [kvm] [<ffffffffa001474b>] ? kvm_resched+0x1c5/0x1048 [kvm] [<ffffffff8034a8f1>] ? ccs_capable+0xe1/0x1a6 [<ffffffff8028a2a6>] ? vfs_ioctl+0x46/0x8f [<ffffffff8028a518>] ? do_vfs_ioctl+0x229/0x235 [<ffffffff8028a575>] ? sys_ioctl+0x51/0x74 [<ffffffff8020250b>] ? system_call_fastpath+0x16/0x1b Code: c1 ea 20 0f 30 55 9d 0f 01 04 24 48 8b 4c 24 02 48 b8 ff ff ff ff ff f0 ff ff 48 ba 00 00 00 00 00 09 00 00 48 23 41 40 48 09 d0 <48> 89 41 40 0f 20 c2 48 89 d0 48 25 ff ff fe ff 0f 22 c0 b8 40 RIP [<ffffffffa00394d3>] intel_iommu_found+0x4d3/0x4075 [kvm_intel] RSP <ffff880129147d98> CR2: ffffffff8059b040 ---[ end trace cad6e6f057fe3dea ]--- brlan: topology change detected, propagating brlan: port 2(tap0) entering forwarding state Is this output enough, or do you need something else ? > If i'm using the hardened-sources-2.6.28 with PaX support all is working fine. > Did you try hardened-sources 2.6.27-r4 (or 2.6.27-r7) with PaX support > (i.e. without TOMOYO patch applied)? I've tried hardened-sources-2.6.27-r7 and PaX enabled (without TOMOYO): localhost ~ # pspax | grep kvm USER PID PAX MAPS ETYPE NAME CAPS ATTR root 6123 PeMRs w^x ET_DYN kvm = localhost ~ # paxctl -v /usr/bin/kvm PaX control v0.5 Copyright 2004,2005,2006,2007 PaX Team <[email protected]> - PaX flags: -------x-e-- [/usr/bin/kvm] RANDEXEC is disabled EMUTRAMP is disabled I've tried hardened-sources-2.6.28 and PaX enabled (without TOMOYO): localhost ~ # pspax | grep kvm USER PID PAX MAPS ETYPE NAME CAPS ATTR root 6544 PeMRs w^x ET_DYN kvm = localhost ~ # paxctl -v /usr/bin/kvm PaX control v0.5 Copyright 2004,2005,2006,2007 PaX Team <[email protected]> - PaX flags: -------x-e-- [/usr/bin/kvm] RANDEXEC is disabled EMUTRAMP is disabled both are working. > "PaX, even when completely disabled, is incompatible with a > VirtualBox/VMWare host (it can still be used on a guest OS). The > source of the incompatibility is not yet known." That's new for me, but how it looks, it's working fine with hardened-sources + enabled PaX. Regards. _______________________________________________ tomoyo-users-en mailing list [email protected] http://lists.sourceforge.jp/mailman/listinfo/tomoyo-users-en
