Hi, In snv118 kqemu crashes Solaris also but now there's a message in /var/adm/messages:
Jul 18 15:25:24 t61p ^Mpanic[cpu0]/thread=ffffff01d7fe7380: Jul 18 15:25:24 t61p genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=ffffff000847c930 addr=30 occurred in module "unix" due to a NULL pointer dereference Jul 18 15:25:24 t61p unix: [ID 100000 kern.notice] Jul 18 15:25:24 t61p unix: [ID 839527 kern.notice] qemu: Jul 18 15:25:24 t61p unix: [ID 753105 kern.notice] #pf Page fault Jul 18 15:25:24 t61p unix: [ID 532287 kern.notice] Bad kernel fault at addr=0x30 Jul 18 15:25:24 t61p unix: [ID 243837 kern.notice] pid=3405, pc=0xfffffffffb8561c4, sp=0xffffff000847ca28, eflags=0x10202 Jul 18 15:25:24 t61p unix: [ID 211416 kern.notice] cr0: 80050033<pg,wp,ne,et,mp,pe> cr4: 6f8<xmme,fxsr,pge,mce,pae,pse,de> Jul 18 15:25:24 t61p unix: [ID 624947 kern.notice] cr2: 30 Jul 18 15:25:24 t61p unix: [ID 625075 kern.notice] cr3: 93063000 Jul 18 15:25:24 t61p unix: [ID 625715 kern.notice] cr8: c Jul 18 15:25:24 t61p unix: [ID 100000 kern.notice] Jul 18 15:25:24 t61p unix: [ID 592667 kern.notice] rdi: 30 rsi: 1 rdx: ffffff01d7fe7380 Jul 18 15:25:24 t61p unix: [ID 592667 kern.notice] rcx: 1000 r8: 1000 r9: 7fffff80f15 Jul 18 15:25:24 t61p unix: [ID 592667 kern.notice] rax: d7cc000 rbx: 2 rbp: ffffff000847caa0 Jul 18 15:25:24 t61p unix: [ID 592667 kern.notice] r10: 7fffff80f15 r11: ffffff0000003000 r12: d7cd000 Jul 18 15:25:24 t61p unix: [ID 592667 kern.notice] r13: d7cc000 r14: 0 r15: 30 Jul 18 15:25:24 t61p unix: [ID 592667 kern.notice] fsb: fffffd7fff0f2a00 gsb: fffffffffbc2e5f0 ds: 4b Jul 18 15:25:24 t61p unix: [ID 592667 kern.notice] es: 4b fs: 0 gs: 0 Jul 18 15:25:24 t61p unix: [ID 592667 kern.notice] trp: e err: 0 rip: fffffffffb8561c4 Jul 18 15:25:24 t61p unix: [ID 592667 kern.notice] cs: 30 rfl: 10202 rsp: ffffff000847ca28 Jul 18 15:25:24 t61p unix: [ID 266532 kern.notice] ss: 38 Jul 18 15:25:24 t61p unix: [ID 100000 kern.notice] Jul 18 15:25:24 t61p genunix: [ID 655072 kern.notice] ffffff000847c810 unix:die+dd () Jul 18 15:25:24 t61p genunix: [ID 655072 kern.notice] ffffff000847c920 unix:trap+1779 () Jul 18 15:25:24 t61p genunix: [ID 655072 kern.notice] ffffff000847c930 unix:cmntrap+e6 () Jul 18 15:25:24 t61p genunix: [ID 655072 kern.notice] ffffff000847caa0 unix:rw_enter+14 () Jul 18 15:25:24 t61p genunix: [ID 655072 kern.notice] ffffff000847cb20 kqemu:kqemu_lock_user_page+57 () Jul 18 15:25:24 t61p genunix: [ID 655072 kern.notice] ffffff01e2e6a000 kqemu:mon_user_map+52 () Jul 18 15:25:24 t61p unix: [ID 100000 kern.notice] Jul 18 15:25:24 t61p genunix: [ID 672855 kern.notice] syncing file systems... Jul 18 15:25:24 t61p genunix: [ID 904073 kern.notice] done Jul 18 15:25:25 t61p genunix: [ID 111219 kern.notice] dumping to /dev/zvol/dsk/rpool/dump, offset 65536, content: kernel Jul 18 15:25:25 t61p ahci: [ID 405573 kern.info] NOTICE: ahci0: ahci_tran_reset_dport port 0 reset port Jul 18 15:25:41 t61p genunix: [ID 409368 kern.notice] ^M100% done: 146829 pages dumped, compression ratio 3.11, Jul 18 15:25:41 t61p genunix: [ID 851671 kern.notice] dump succeeded Jul 18 15:26:38 t61p genunix: [ID 540533 kern.notice] ^MSunOS Release 5.11 Version snv_118 64-bit regards Bernd Ben Taylor wrote: > On Sat, Jun 27, 2009 at 2:19 PM, Bernd Schemmer<Bernd.Schemmer at gmx.de> > wrote: > >> Hi, >> >> the usage of QEMU 0.10.5 with kqemu qemu-1.4.0pre1 crashes OpenSolaris >> snv_117 . This worked fine in OpenSolaris snv_111 >> >> Unfortunately there is no core file or crash dump -- and there are no error >> messages written to the session - after call qemu the display fills up with >> garbagge and that's it ... QEMU without kqemu works in OpenSolaris snv_117. >> >> The kqemu driver itself loads without problems : >> >> xtrnaw7 at t61p:/data/develop/source/kqemu-1.4.0pre1-sol$ modinfo -c | grep >> -i >> qemu >> 270 2 kqemu LOADED/INSTALLED >> >> xtrnaw7 at t61p:/data/develop/source/kqemu-1.4.0pre1-sol$ modinfo | grep -i >> qemu >> 270 fffffffff853b000 28d28 264 1 kqemu (kqemu accelerator v0.2) >> >> Are there any change between snv_111 and snv_117 that prevent kqemu from >> working? >> > > Just a guess, but I'd suspect that something in the kernel has probably > changed > and this is causing the problem. Unfortunately, I haven't been > tracking qemu/kqemu > for a few months, and if this is a kernel change, there's probably one > or two people > on the list probably capable of diagnosising and fixing the issue in kqemu. > > Ben > > -- Bernd Schemmer, Frankfurt am Main, Germany http://bnsmb.de/ M s temprano que tarde el mundo cambiar . Fidel Castro
