From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: (qemu)info registers -- Not working for me. Date: Tue, 02 Mar 2010 09:17:35 +0100 Message-ID: <4B8CC99F.5040703@web.de> References: <4B8AB58B.2050209@web.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig2BB938FF08FDC47976628EC3" Cc: kvm@vger.kernel.org To: Zachery Salwasser Return-path: Received: from fmmailgate01.web.de ([217.72.192.221]:42617 "EHLO fmmailgate01.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753470Ab0CBIU0 (ORCPT ); Tue, 2 Mar 2010 03:20:26 -0500 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2BB938FF08FDC47976628EC3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Zachery Salwasser wrote: > Thank you for the prompt reply, you were correct, and I was able to > resolve the issue by being a little more careful with my header files. > I will close the issue on sourceforge. >=20 OK, so we can safely conclude your problem was due to local changes in the kvm headers? I would just like to exclude that there might be issues due to different compilers / their switches / whatever, and that already with vanilla headers. Jan >=20 > On Sun, Feb 28, 2010 at 1:27 PM, Jan Kiszka wrote: >> Zachery Salwasser wrote: >>> I have been having trouble with reading the extended registers >>> normally read by kvm_get_sregs() on host kernels ~2.6.32 and higher. >>> >>> I am currently running Linux 2.6.32-8, kvm-kmod 2.6.32.8, and qemu 0.= 12.2. >>> >>> I get the following output when I try info registers on the qemu cons= ole: >>> >>> (qemu) info registers >>> EAX=3D6d63c93d EBX=3Dffdffc70 ECX=3Dffdffc70 EDX=3D00000000 >>> ESI=3Dffdffc50 EDI=3D823e7b68 EBP=3D80550f50 ESP=3D80550f34 >>> EIP=3Df8621d3e EFL=3D00000246 [---Z-P-] CPL=3D0 II=3D0 A20=3D1 SMM=3D= 0 HLT=3D0 >>> ES =3D3d65 00001000 b772bdf8 3fffe800 DPL=3D3 Reserved >>> CS =3D4fe1 b7d59ff4 b7d5b3a0 6b300100 >>> SS =3D0000 b772bde8 0847ab38 6f300a00 >>> DS =3Db3d0 b7d5b3cc 00000000 7bffd500 DPL=3D2 DS [E-A] >>> FS =3De008 b7d5b3a0 b7d59ff4 005bb900 DPL=3D1 CS32 [--A] >>> GS =3Dffff ffffffff 00000007 7fffff00 DPL=3D3 CS64 [CRA] >>> LDT=3D9ff4 b772bde0 00000008 7ffff500 DPL=3D3 DS [E-A] >>> TR =3D0000 00000080 b7fb63ab 00f00000 >>> GDT=3D 00014fe1 00000100 >>> IDT=3D b7d5b3cc 0000b3d0 >>> CR0=3D08000101 CR2=3D00002000 CR3=3D00000000 CR4=3D08000101 >>> DR0=3D00000000 DR1=3D00000000 DR2=3D00000000 DR3=3D00000000 >>> DR6=3Dffff0ff0 DR7=3D00000000 >>> FCW=3D027f FSW=3D0000 [ST=3D0] FTW=3D00 MXCSR=3D00000000 >>> FPR0=3D0000000000000000 ffff FPR1=3D00ff00ff00ff00ff ffff >>> FPR2=3D0000000000000000 ffff FPR3=3D00fe000d009900ee ffff >>> FPR4=3Dff0d9aefff6a604c ffff FPR5=3D00ff000d009a00ef ffff >>> FPR6=3D0000000000000000 ffff FPR7=3D0080008000800080 ffff >>> XMM00=3D >>> 00000020000000000000000000000001 XMM01=3D81181ab88055f980e115d0000000= 0020 >>> XMM02=3Df79092a481181ab8c03845740dd1d000 XMM03=3D81181ab8c03845740000= 016d804e93e0 >>> XMM04=3Dc0384574000000000000000100000000 XMM05=3De1150000804e7e36f790= 931400000000 >>> XMM06=3D806f02980000000000000000c0384574 XMM07=3D000000028055f6200000= 0080c0384574 >>> >>> Note that cr3 is 0, which doesn't seem possible. The contents of the= >>> sregs is also static across invocations of info registers (whereas th= e >>> "regs" chang), indicating that the values that are there are garbage.= >>> >>> Delving deeper, when I check actual invocations of kvm_get_sregs(), i= t >>> usually returns either 0 or -22, neither value indicating success. >> -22 indicates something bad is happening. Maybe sizeof(struct kvm_sreg= s) >> is different from kernel and user space POV on your host. That would >> cause KVM_GET_SREGS to have different values, thus the kernel would be= >> unable to dispatch the request. Could you check this? >> >> Jan >> >> --------------enig2BB938FF08FDC47976628EC3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkuMyZ8ACgkQitSsb3rl5xRANQCg7k8Dcg4df1Q08f1EEhzUuKL7 mPQAnAmN5fSMLoRlNxzASr8zcFfiiZti =52nO -----END PGP SIGNATURE----- --------------enig2BB938FF08FDC47976628EC3--