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

2006-08-11 Thread 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 =   
CS =0033   00affa00
SS =002b   00cff200
DS =   
FS =   
GS =   
LDT=   8000
TR =0040 8030e000 206f 80008930
GDT= 8030c000 0080
IDT= 8030d000 1000
CR0=8005003b CR2=2b599766f800 CR3=074c4000 CR4=06e0
Unsupported return value: 0x

In a second attempt I got

RAX=2b80af1d7d20 RBX=2b80af1d49e8 RCX=0008
RDX=0008
RSI=2b80af393800 RDI=0053f478 RBP=7f9fa2c0
RSP=7f9fa1d8
R8 =2b80af393800 R9 = R10=0053f478
R11=0002
R12= R13=0005 R14=2b80af0d54b0
R15=00402a18
RIP=2b80af0ce390 RFL=00010287 [--S--PC] CPL=3 II=0 A20=1 HLT=0
ES =   
CS =0033   00affa00
SS =002b   00cff200
DS =   
FS =   
GS =   
LDT=   8000
TR =0040 8030e000 206f 80008930
GDT= 8030c000 0080
IDT= 8030d000 1000
CR0=8005003b CR2=2b80af393800 CR3=07b48000 CR4=06e0
Unsupported return value: 0x


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

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


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


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


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

2006-08-11 Thread 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 mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


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

2006-08-11 Thread 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 mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


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

2006-08-11 Thread 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 =    CS =0033 
  00affa00 SS =002b   00cff200 DS =
    FS =  
  GS =    LDT=
   8000 TR =0040 8030e000 206f
 80008930 GDT= 8030c000 0080
 IDT= 8030d000 1000
 CR0=8005003b CR2=2b599766f800 CR3=074c4000 CR4=06e0
 Unsupported return value: 0x
 
 In a second attempt I got
 
 RAX=2b80af1d7d20 RBX=2b80af1d49e8 RCX=0008
 RDX=0008
 RSI=2b80af393800 RDI=0053f478 RBP=7f9fa2c0
 RSP=7f9fa1d8
 R8 =2b80af393800 R9 = R10=0053f478
 R11=0002
 R12= R13=0005 R14=2b80af0d54b0
 R15=00402a18
 RIP=2b80af0ce390 RFL=00010287 [--S--PC] CPL=3 II=0 A20=1 HLT=0 ES
 =    CS =0033 
  00affa00 SS =002b   00cff200 DS =
    FS =  
  GS =    LDT=
   8000 TR =0040 8030e000 206f
 80008930 GDT= 8030c000 0080
 IDT= 8030d000 1000
 CR0=8005003b CR2=2b80af393800 CR3=07b48000 CR4=06e0
 Unsupported return value: 0x
 
 
 For every such test, the host's dmesg and kernel logs reported the
 following:
 
 kqemu: aborting: Unexpected exception 0x0d in monitor space err=
 CS:EIP=f180:f0002806 SS:SP=:f00c7e00
 
 
 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




___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] kernel command line

2006-08-11 Thread 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



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


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

2006-08-11 Thread 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 mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] qemu usb-linux.c vl.h hw/esp.c hw/lsi53c895a.c ...

2006-08-11 Thread Paul Brook
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Paul Brook pbrook 06/08/12 01:04:27

Modified files:
.  : usb-linux.c vl.h 
hw : esp.c lsi53c895a.c scsi-disk.c usb-hid.c 
 usb-hub.c usb-msd.c usb-ohci.c usb-uhci.c usb.c 
 usb.h 
pc-bios: openbios-sparc32 
Added files:
pc-bios: openbios-esp.diff 

Log message:
SCSI and USB async IO support.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/usb-linux.c?cvsroot=qemur1=1.8r2=1.9
http://cvs.savannah.gnu.org/viewcvs/qemu/vl.h?cvsroot=qemur1=1.140r2=1.141
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/esp.c?cvsroot=qemur1=1.12r2=1.13
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/lsi53c895a.c?cvsroot=qemur1=1.1r2=1.2
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/scsi-disk.c?cvsroot=qemur1=1.9r2=1.10
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/usb-hid.c?cvsroot=qemur1=1.5r2=1.6
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/usb-hub.c?cvsroot=qemur1=1.8r2=1.9
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/usb-msd.c?cvsroot=qemur1=1.4r2=1.5
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/usb-ohci.c?cvsroot=qemur1=1.3r2=1.4
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/usb-uhci.c?cvsroot=qemur1=1.11r2=1.12
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/usb.c?cvsroot=qemur1=1.8r2=1.9
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/usb.h?cvsroot=qemur1=1.9r2=1.10
http://cvs.savannah.gnu.org/viewcvs/qemu/pc-bios/openbios-sparc32?cvsroot=qemurev=1.2
http://cvs.savannah.gnu.org/viewcvs/qemu/pc-bios/openbios-esp.diff?cvsroot=qemurev=1.1


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel