[Qemu-devel] kqemu in x86_64: (host) exception 0x0d in monitor space

[Qemu-devel] kqemu in x86_64: (host) exception 0x0d in monitor space

[J M Cerqueira Esteves]

Greetings

Summary: qemu-system-x86_64 with kqemu (running under Ubuntu on a Athlon
64) crashes while installing a guest Debian amd64 testing (etch) system,
with the host reporting (in kernel logs):
  kqemu: aborting: Unexpected exception 0x0d in monitor space


Host CPU: AMD Athlon 64 3500+ (machine: HP dx5150 MT)
Host operating system: Ubuntu 6.06 LTS
Host kernel: one of the Ubuntu pre-packaged ones,
             2.6.15-26-amd64-k8 (SMP PREEMPT)

VDE: 'backported' (just rebuilding the package)
     from Debian testing's vde 1.5.11-1.
QEMU: 0.8.2, configured with -cc=gcc-3.4 --enable-alsa
kqemu: 1.3.0pre9

I tried to install Debian amd64 testing (etch) from a
snapshot netinst iso image downloaded yesterday, invoking

    vdeq qemu-system-x86_64 \
	-pidfile /srv/qemu/nisaba.pid \
	-m 160 \
	-net nic,vlan=0,model=rtl8139,macaddr=4A:4D:23:00:00:01 \
	-net vde,vlan=0,sock=/var/run/vde/tap-vde-1.ctl \
	-hda /srv/qemu/$NAME.qcow \
        -cdrom /srv/ark/cd/debian-testing-amd64-netinst-20060810.iso \
	-boot d

Booted in expert mode, chose language, keyboard layout, country, locale
parameters, and just after I chose "detect and mount cdrom" qemu crashed
(apparently immediately after (very briefly) showing a progress bar with
"detecting hardware to find cd-rom drives"), with the (host-side) output

ES =0000 0000000000000000 00000000 00000000
CS =0033 0000000000000000 ffffffff 00affa00
SS =002b 0000000000000000 ffffffff 00cff200
DS =0000 0000000000000000 00000000 00000000
FS =0000 0000000000000000 00000000 00000000
GS =0000 0000000000000000 00000000 00000000
LDT=0000 0000000000000000 00000000 00008000
TR =0040 ffffffff8030e000 0000206f 80008930
GDT=     ffffffff8030c000 00000080
IDT=     ffffffff8030d000 00001000
CR0=8005003b CR2=00002b599766f800 CR3=00000000074c4000 CR4=000006e0
Unsupported return value: 0xffffffff

In a second attempt I got

RAX=00002b80af1d7d20 RBX=00002b80af1d49e8 RCX=0000000000000008
RDX=0000000000000008
RSI=00002b80af393800 RDI=000000000053f478 RBP=00007fffff9fa2c0
RSP=00007fffff9fa1d8
R8 =00002b80af393800 R9 =0000000000000000 R10=000000000053f478
R11=0000000000000002
R12=0000000000000000 R13=0000000000000005 R14=00002b80af0d54b0
R15=0000000000402a18
RIP=00002b80af0ce390 RFL=00010287 [--S--PC] CPL=3 II=0 A20=1 HLT=0
ES =0000 0000000000000000 00000000 00000000
CS =0033 0000000000000000 ffffffff 00affa00
SS =002b 0000000000000000 ffffffff 00cff200
DS =0000 0000000000000000 00000000 00000000
FS =0000 0000000000000000 00000000 00000000
GS =0000 0000000000000000 00000000 00000000
LDT=0000 0000000000000000 00000000 00008000
TR =0040 ffffffff8030e000 0000206f 80008930
GDT=     ffffffff8030c000 00000080
IDT=     ffffffff8030d000 00001000
CR0=8005003b CR2=00002b80af393800 CR3=0000000007b48000 CR4=000006e0
Unsupported return value: 0xffffffff


For every such test, the host's dmesg and kernel logs reported the
following:

kqemu: aborting: Unexpected exception 0x0d in monitor space
err=0000 CS:EIP=f180:00000000f0002806 SS:SP=0000:00000000f00c7e00


The above crash does not happen when qemu-system-x86_64 is invoked with
the additional option "-no-kqemu".

In case this issue is already known: is there any way to avoid this
crash (maybe some boot time parameter for the Debian guest kernel?)
without disabling kqemu?

Any suggestions for additional information gathering here which could
help solve this issue?


Best regards (and *many* thanks for QEMU)

                        J Esteves


-- 
+351 939838775   Skype:jmcerqueira   http://del.icio.us/jmce

Re: [Qemu-devel] kqemu in x86_64: (host) exception 0x0d in monitor space

[J M Cerqueira Esteves]

J M Cerqueira Esteves wrote:

> Summary: qemu-system-x86_64 with kqemu (running under Ubuntu on a Athlon
> 64) crashes while installing a guest Debian amd64 testing (etch) system,
> with the host reporting (in kernel logs):
>   kqemu: aborting: Unexpected exception 0x0d in monitor space


I forgot to mention that a (32 bit) Windows XP Pro guest has been
running without problems on the same qemu-system-x86_64.


-- 
+351 939838775   Skype:jmcerqueira   http://del.icio.us/jmce

[Qemu-devel] kernel command line

[Tieu Ma Dau]

[-- Attachment #1.1: Type: text/plain, Size: 900 bytes --]

Hi all, 
 I want to boot Linux using NFS root, on MSys on Windows, so the option I give to execute Qemu ARM system is as:  
 -append "root=/dev/nfs nfsroot=192.168.7.1:/c/cygwin/nfsqemu rw ip=192.168.7.2:192.168.7.1:192.168.7.1:255.255.255.0:::off" 
 (attention the ";" and ":" character) 
  
 And when Linux boots, I got the following line on the Qemu's screen: 
 Kernel command line: root=C:\msys\1.0\dev\nfs nfsroot=192.168.7.1;/c/cygwin/nfsqemu rw ip=192.168.7.2;192.168.7.1;192.168.7.1;255.255.255.0;off 
  
The kernel command line I give is changed automactically, and then Linux can not boot successfully. So I don't know exactly if this change is the reason of problem or not? 
 If it is, do you have any suggestion? 
 Thanks a lot
Tieu

 __________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[-- Attachment #1.2: Type: text/html, Size: 981 bytes --]

[-- Attachment #2: 509660205-bootscreen.JPG --]
[-- Type: image/jpeg, Size: 70619 bytes --]

Re: [Qemu-devel] kernel command line

[Paul Brook]

On Friday 11 August 2006 15:15, Tieu Ma Dau wrote:
> Hi all,
>  I want to boot Linux using NFS root, on MSys on Windows, so the option I
> give to execute Qemu ARM system is as: -append "root=/dev/nfs
> nfsroot=192.168.7.1:/c/cygwin/nfsqemu rw
> ip=192.168.7.2:192.168.7.1:192.168.7.1:255.255.255.0:::off" (attention the
> ";" and ":" character)
>
>  And when Linux boots, I got the following line on the Qemu's screen:
>  Kernel command line: root=C:\msys\1.0\dev\nfs
> nfsroot=192.168.7.1;/c/cygwin/nfsqemu rw
> ip=192.168.7.2;192.168.7.1;192.168.7.1;255.255.255.0;off
>
> The kernel command line I give is changed automactically, and then Linux
> can not boot successfully. So I don't know exactly if this change is the
> reason of problem or not? If it is, do you have any suggestion?

This is almost certainly caused by MSYS, probably your shell, and not a qemu 
problem.

Paul

Re: [Qemu-devel] kernel command line

[Jernej Simončič]

On Friday, August 11, 2006, 16:15:37, Tieu Ma Dau wrote:

>  And when Linux boots, I got the following line on the Qemu's screen: 
>  Kernel command line: root=C:\msys\1.0\dev\nfs
> nfsroot=192.168.7.1;/c/cygwin/nfsqemu rw
> ip=192.168.7.2;192.168.7.1;192.168.7.1;255.255.255.0;off 

This is a MSys feature that lets you run non-msys programs from within it's
shells. Run Qemu from cmd.exe and you won't have this problem.

-- 
< Jernej Simonèiè ><><><><>< http://deepthought.ena.si/ >

The only way a reporter should look at a politician is down.
       -- Kent's Law

Re: [Qemu-devel] kqemu in x86_64: (host) exception 0x0d in monitor space

[J M Cerqueira Esteves]

J M Cerqueira Esteves wrote:
> Summary: qemu-system-x86_64 with kqemu (running under Ubuntu on a Athlon
> 64) crashes while installing a guest Debian amd64 testing (etch) system,
> with the host reporting (in kernel logs):
>   kqemu: aborting: Unexpected exception 0x0d in monitor space

However, with the same setup, and with kqemu active, I was able to
install Kubuntu 6.06 amd64, without experiencing such a crash.

Still, two issues with that Kubuntu instance:

- grub segfaulted, failing to install the boot loader on the hard disk
  image (I ended up using lilo instead);
  this also happened previously when trying to install debian
  testing  amd64 *without using kqemu* (maybe some grub bug?);

- without or without the kernel option
      clock=pit
  I got, already at boot time:

     Losing some ticks... checking if CPU frequency changed
     [...]
     warning: many lost ticks
     Your time source seems to be instable or some driver is hogging
     interupts

  and now, about 1.5 hour after booting, the guest clock is about 1.5
  hour ahead of the host clock (maybe because the host has been idle
  and working at about 1/2 the full clock speed?) This clock shifting
  did not occur with a Windows XP Pro guest, which usually remained
  late by less than 1 minute.

Best regards
                    J Esteves

-- 
+351 939838775   Skype:jmcerqueira   http://del.icio.us/jmce

[Qemu-devel] Re: kqemu in x86_64: (host) exception 0x0d in monitor space

[Anthony Liguori]

On Fri, 11 Aug 2006 07:57:41 +0100, J M Cerqueira Esteves wrote:

> Greetings
> 
> Summary: qemu-system-x86_64 with kqemu (running under Ubuntu on a Athlon
> 64) crashes while installing a guest Debian amd64 testing (etch) system,
> with the host reporting (in kernel logs):
>   kqemu: aborting: Unexpected exception 0x0d in monitor space

Sounds like a kqemu bug.  0x0d == 14 == page fault.  The only person who
can help you here is Fabrice...

Regards,

Anthony Liguori

> 
> 
> Host CPU: AMD Athlon 64 3500+ (machine: HP dx5150 MT) Host operating
> system: Ubuntu 6.06 LTS Host kernel: one of the Ubuntu pre-packaged ones,
>              2.6.15-26-amd64-k8 (SMP PREEMPT)
> 
> VDE: 'backported' (just rebuilding the package)
>      from Debian testing's vde 1.5.11-1.
> QEMU: 0.8.2, configured with -cc=gcc-3.4 --enable-alsa kqemu: 1.3.0pre9
> 
> I tried to install Debian amd64 testing (etch) from a snapshot netinst iso
> image downloaded yesterday, invoking
> 
>     vdeq qemu-system-x86_64 \
> 	-pidfile /srv/qemu/nisaba.pid \
> 	-m 160 \
> 	-net nic,vlan=0,model=rtl8139,macaddr=4A:4D:23:00:00:01 \ -net
> 	vde,vlan=0,sock=/var/run/vde/tap-vde-1.ctl \ -hda /srv/qemu/$NAME.qcow \
>         -cdrom /srv/ark/cd/debian-testing-amd64-netinst-20060810.iso \
> 	-boot d
> 
> Booted in expert mode, chose language, keyboard layout, country, locale
> parameters, and just after I chose "detect and mount cdrom" qemu crashed
> (apparently immediately after (very briefly) showing a progress bar with
> "detecting hardware to find cd-rom drives"), with the (host-side) output
> 
> ES =0000 0000000000000000 00000000 00000000 CS =0033 0000000000000000
> ffffffff 00affa00 SS =002b 0000000000000000 ffffffff 00cff200 DS =0000
> 0000000000000000 00000000 00000000 FS =0000 0000000000000000 00000000
> 00000000 GS =0000 0000000000000000 00000000 00000000 LDT=0000
> 0000000000000000 00000000 00008000 TR =0040 ffffffff8030e000 0000206f
> 80008930 GDT=     ffffffff8030c000 00000080
> IDT=     ffffffff8030d000 00001000
> CR0=8005003b CR2=00002b599766f800 CR3=00000000074c4000 CR4=000006e0
> Unsupported return value: 0xffffffff
> 
> In a second attempt I got
> 
> RAX=00002b80af1d7d20 RBX=00002b80af1d49e8 RCX=0000000000000008
> RDX=0000000000000008
> RSI=00002b80af393800 RDI=000000000053f478 RBP=00007fffff9fa2c0
> RSP=00007fffff9fa1d8
> R8 =00002b80af393800 R9 =0000000000000000 R10=000000000053f478
> R11=0000000000000002
> R12=0000000000000000 R13=0000000000000005 R14=00002b80af0d54b0
> R15=0000000000402a18
> RIP=00002b80af0ce390 RFL=00010287 [--S--PC] CPL=3 II=0 A20=1 HLT=0 ES
> =0000 0000000000000000 00000000 00000000 CS =0033 0000000000000000
> ffffffff 00affa00 SS =002b 0000000000000000 ffffffff 00cff200 DS =0000
> 0000000000000000 00000000 00000000 FS =0000 0000000000000000 00000000
> 00000000 GS =0000 0000000000000000 00000000 00000000 LDT=0000
> 0000000000000000 00000000 00008000 TR =0040 ffffffff8030e000 0000206f
> 80008930 GDT=     ffffffff8030c000 00000080
> IDT=     ffffffff8030d000 00001000
> CR0=8005003b CR2=00002b80af393800 CR3=0000000007b48000 CR4=000006e0
> Unsupported return value: 0xffffffff
> 
> 
> For every such test, the host's dmesg and kernel logs reported the
> following:
> 
> kqemu: aborting: Unexpected exception 0x0d in monitor space err=0000
> CS:EIP=f180:00000000f0002806 SS:SP=0000:00000000f00c7e00
> 
> 
> The above crash does not happen when qemu-system-x86_64 is invoked with
> the additional option "-no-kqemu".
> 
> In case this issue is already known: is there any way to avoid this crash
> (maybe some boot time parameter for the Debian guest kernel?) without
> disabling kqemu?
> 
> Any suggestions for additional information gathering here which could help
> solve this issue?
> 
> 
> Best regards (and *many* thanks for QEMU)
> 
>                         J Esteves

Re: [Qemu-devel] Re: kqemu in x86_64: (host) exception 0x0d in monitor space

[J M Cerqueira Esteves]

Anthony Liguori wrote:
> On Fri, 11 Aug 2006 07:57:41 +0100, J M Cerqueira Esteves wrote:
>>Summary: qemu-system-x86_64 with kqemu (running under Ubuntu on a Athlon
>>64) crashes while installing a guest Debian amd64 testing (etch) system,
>>with the host reporting (in kernel logs):
>>  kqemu: aborting: Unexpected exception 0x0d in monitor space
> 
> Sounds like a kqemu bug.  0x0d == 14 == page fault.  The only person who
> can help you here is Fabrice...

Meanwhile I got some hope for a temporary trick when I tried the option
-smp 2 and this error did not show up...  but then I noticed that, with
the  -smp 2  option, kqemu is disabled...

Best regards
                       J Esteves

-- 
+351 939838775   Skype:jmcerqueira   http://del.icio.us/jmce

[Qemu-devel] kqemu in x86_64: (host) exception 0x0d in monitor space

[Mike Peters]

Hi,

Is there any known fix for the issue reported previously here -
http://www.mail-archive.com/qemu-devel@nongnu.org/msg06241.html

I'm seeing the same issue trying to install ubuntu-7.10-server-amd64 on
ubuntu-7.10-desktop-amd64 (2.6.22-14-generic #1 SMP) using the
current Ubuntu distributed qemu-0.9.0-2ubuntu4 and kqemu 1.3.0-pre11

I'm running qemu with:
qemu-system-x86_64 -hda ubuntu-server.img
-cdrom ubuntu-7.10-server-amd64.iso -boot d -m 256

The install starts but aborts after the language select screen with:

RAX=00002b9063757fe0 RBX=00007fff47352fc0 RCX=0000000000000000
RDX=000a24fd61624b91 RSI=0000000000000000 RDI=00007fff47352fc0
RBP=00007fff47352fb0 RSP=00007fff47352f90 R8 =0000000000000000 R9
=0000000000000000 R10=0000000000000000 R11=0000000000000200
R12=0000000000000000 R13=0000000000000000 R14=0000000000000000
R15=0000000000000000 RIP=00002b9063757ffe RFL=00010202 [-------] CPL=3
II=0 A20=1 SMM=0 HLT=0 ES =0000 0000000000000000 00000000 00000000 CS
=0033 0000000000000000 ffffffff 00affb00 SS =002b 0000000000000000
ffffffff 00cff300 DS =0000 0000000000000000 00000000 00000000
FS =0000 0000000000000000 00000000 00000000
GS =0000 0000000000000000 00000000 00000000
LDT=0000 0000000000000000 00000000 00008000
TR =0040 ffff810001005000 0000206f 01008900
GDT=     ffffffff80580000 00000080
IDT=     ffffffff805de000 00000fff
CR0=8005003b CR2=00002b9063972be0 CR3=0000000001094000 CR4=000006e0
Unsupported return value: 0xffffffff

/var/log/messages shows:

Nov 20 23:21:46 rincewind kernel: [1419344.733628] kqemu: aborting:
Unexpected e xception 0x0d in monitor space
Nov 20 23:21:46 rincewind kernel: [1419344.733633] err=0000
CS:EIP=f180:00000000 f0001f77 SS:SP=0000:00000000f00c6df0


Everything runs fine (if very slow) when I append the -no-kqemu
option to the startup.

Thanks
-- 
Mike
Web Site: http://www.ice2o.com
Photos: http://www.flickr.com/photos/mikedpeters/
Registered Linux User #247123

Q:	What's a WASP's idea of open-mindedness?
A:	Dating a Canadian.

Re: [Qemu-devel] kqemu in x86_64: (host) exception 0x0d in monitor space

[Werner Dittmann]

Even in a fairly new CVS snapshot this problem ist not
solved, at least not on my 64bit openSUSE system. Adding
-no-kqemu works, slow but when I try to install a 64bit
openSUSE in qemu then GRUB hangs (at the very end end of the
installation). This IMHO x86_64 bit support in Qemu is somewhat
instable.

One poster proposed to use Lilo instead fo GRUB, didn't check
that because -no-kqemu is far to slow to work in some normal
way.

Regards,
Werner

Mike Peters schrieb:
> Hi,
> 
> Is there any known fix for the issue reported previously here -
> http://www.mail-archive.com/qemu-devel@nongnu.org/msg06241.html
> 
> I'm seeing the same issue trying to install ubuntu-7.10-server-amd64 on
> ubuntu-7.10-desktop-amd64 (2.6.22-14-generic #1 SMP) using the
> current Ubuntu distributed qemu-0.9.0-2ubuntu4 and kqemu 1.3.0-pre11
> 
> I'm running qemu with:
> qemu-system-x86_64 -hda ubuntu-server.img
> -cdrom ubuntu-7.10-server-amd64.iso -boot d -m 256
> 
> The install starts but aborts after the language select screen with:
> 
> RAX=00002b9063757fe0 RBX=00007fff47352fc0 RCX=0000000000000000
> RDX=000a24fd61624b91 RSI=0000000000000000 RDI=00007fff47352fc0
> RBP=00007fff47352fb0 RSP=00007fff47352f90 R8 =0000000000000000 R9
> =0000000000000000 R10=0000000000000000 R11=0000000000000200
> R12=0000000000000000 R13=0000000000000000 R14=0000000000000000
> R15=0000000000000000 RIP=00002b9063757ffe RFL=00010202 [-------] CPL=3
> II=0 A20=1 SMM=0 HLT=0 ES =0000 0000000000000000 00000000 00000000 CS
> =0033 0000000000000000 ffffffff 00affb00 SS =002b 0000000000000000
> ffffffff 00cff300 DS =0000 0000000000000000 00000000 00000000
> FS =0000 0000000000000000 00000000 00000000
> GS =0000 0000000000000000 00000000 00000000
> LDT=0000 0000000000000000 00000000 00008000
> TR =0040 ffff810001005000 0000206f 01008900
> GDT=     ffffffff80580000 00000080
> IDT=     ffffffff805de000 00000fff
> CR0=8005003b CR2=00002b9063972be0 CR3=0000000001094000 CR4=000006e0
> Unsupported return value: 0xffffffff
> 
> /var/log/messages shows:
> 
> Nov 20 23:21:46 rincewind kernel: [1419344.733628] kqemu: aborting:
> Unexpected e xception 0x0d in monitor space
> Nov 20 23:21:46 rincewind kernel: [1419344.733633] err=0000
> CS:EIP=f180:00000000 f0001f77 SS:SP=0000:00000000f00c6df0
> 
> 
> Everything runs fine (if very slow) when I append the -no-kqemu
> option to the startup.
> 
> Thanks