Robin van Leeuwen - NYK Logistics Edam BV
2005-Aug-05 21:37 UTC
[Xen-users] Qemu and module Kqemu under Xen
Hi I''m having trouble running qemu, or win4lin pro with the kqemu module. When the module is loaded it (winpro) gives a segmentation fault. This is under Debian Xen 2.0.6 , kernel 2.6.10 and 2.6.8 : anybody? more info needed? dmesg shows: ------------ QEMU Accelerator Module version 1.0.0, Copyright (c) 2005 Fabrice Bellard This is a proprietary product. Read the LICENSE file for more information Redistribution of this module is prohibited without authorization KQEMU installed, max_instances=4 max_locked_mem=112884kB. general protection fault: 0000 [#2] Modules linked in: kqemu drbd CPU: 0 EIP: 0061:[<f8d3e45d>] Tainted: PF VLI EFLAGS: 00211246 (2.6.10) EIP is at kqemu_init+0x89/0x54c [kqemu] eax: f8d43000 ebx: 00444000 ecx: f9187000 edx: ffffffff esi: d9d4c820 edi: bffff140 ebp: f8d43000 esp: e921df24 ds: 007b es: 007b ss: 0069 Process mergepro-core (pid: 10463, threadinfo=e921c000 task=e112f020) Stack: f8d43000 00000000 00444000 00000000 c01fcc62 e921df64 bffff140 00000000 d9d4c820 bffff140 fffffff4 f8d3738b e921df64 00006e3d 00000014 00000000 4077e000 1f850000 607d1000 607d0000 607f1000 ca09d36c e71ac198 e71ac18c Call Trace: [<c01fcc62>] copy_from_user+0x42/0x70 [<f8d3738b>] kqemu_ioctl+0xab/0x160 [kqemu] [<c0162869>] sys_ioctl+0xc9/0x240 [<c0109350>] syscall_call+0x7/0xb Code: 05 8d 98 ff 3f 05 00 83 ec 0c 81 e3 00 f0 ff ff 53 e8 f8 8c ff ff 89 c5 83 c4 10 31 c0 85 ed 74 d2 50 53 6a 00 55 e8 93 fb ff ff <0f> 20 e0 c1 e8 05 c7 45 14 80 f1 00 00 83 e0 01 89 45 70 8b 45 ----------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I''m having trouble running qemu, or win4lin pro with the kqemu module. > When the module is loaded it (winpro) gives a segmentation fault.I didn''t think win4lin pro used the kqemu module? The kqemu does things (e.g. sti and cli instructions) that a Xen guest can''t do, so I''m not surprised it breaks. There are probably other places it breaks too - which is possibly what you''re seeing. The module would definitely need compiling against XenLinux, rather than native Linux. Quite likely some source code changes would also be required... For getting this done free, you might like to check out "qvm86", which is an open source reimplementation of the kqemu module. Alternatively, the Win4Lin people recently made some announcement about supporting XenLinux as a host, although I don''t have any details. You might want to try contacting them... Cheers, Mark> This is under Debian Xen 2.0.6 , kernel 2.6.10 and 2.6.8 : > > anybody? more info needed? > > dmesg shows: > ------------ > QEMU Accelerator Module version 1.0.0, Copyright (c) 2005 Fabrice Bellard > This is a proprietary product. Read the LICENSE file for more information > Redistribution of this module is prohibited without authorization > KQEMU installed, max_instances=4 max_locked_mem=112884kB. > general protection fault: 0000 [#2] > Modules linked in: kqemu drbd > CPU: 0 > EIP: 0061:[<f8d3e45d>] Tainted: PF VLI > EFLAGS: 00211246 (2.6.10) > EIP is at kqemu_init+0x89/0x54c [kqemu] > eax: f8d43000 ebx: 00444000 ecx: f9187000 edx: ffffffff > esi: d9d4c820 edi: bffff140 ebp: f8d43000 esp: e921df24 > ds: 007b es: 007b ss: 0069 > Process mergepro-core (pid: 10463, threadinfo=e921c000 task=e112f020) > Stack: f8d43000 00000000 00444000 00000000 c01fcc62 e921df64 bffff140 > 00000000 > d9d4c820 bffff140 fffffff4 f8d3738b e921df64 00006e3d 00000014 00000000 > 4077e000 1f850000 607d1000 607d0000 607f1000 ca09d36c e71ac198 e71ac18c > Call Trace: > [<c01fcc62>] copy_from_user+0x42/0x70 > [<f8d3738b>] kqemu_ioctl+0xab/0x160 [kqemu] > [<c0162869>] sys_ioctl+0xc9/0x240 > [<c0109350>] syscall_call+0x7/0xb > Code: 05 8d 98 ff 3f 05 00 83 ec 0c 81 e3 00 f0 ff ff 53 e8 f8 8c ff ff > 89 c5 83 c4 10 31 c0 85 ed 74 d2 50 53 6a 00 55 e8 93 fb ff ff <0f> 20 > e0 c1 e8 05 c7 45 14 80 f1 00 00 83 e0 01 89 45 70 8b 45 > ----------------- > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Robin van Leeuwen <robin.van.leeuwen@nl.nyklogistics.com> wrote:> I''m having trouble running qemu, or win4lin pro with the kqemu module. > When the module is loaded it (winpro) gives a segmentation fault. > > This is under Debian Xen 2.0.6 , kernel 2.6.10 and 2.6.8 :http://www.win4lin.com/content/view/175/202/ says, that Win4Lin is now Xen compliant. by Töns -- There is no safe distance. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users