All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: jmce@artenumerica.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] 	qemu under x86_64: grub segfault, ld-linux.so segfault, lost ticks
Date: Thu, 17 Aug 2006 11:47:55 +0200	[thread overview]
Message-ID: <44E43B4B.2050503@bellard.org> (raw)
In-Reply-To: <44E2D26E.50101@artenumerica.com>

Hi,

You can use gdb in the virtual machine to see where are the segmentation 
faults and provide a register dump and a short disassembly output.

Regards,

Fabrice.

J M Cerqueira Esteves wrote:
> As I said before, under
> 
>  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)
>  QEMU: 0.8.2, configured with -cc=gcc-3.4 --enable-alsa
>  kqemu: 1.3.0pre9
> 
> I couldn't install Debian amd64 testing (etch)
> in a vm because of an "Unexpected exception 0x0d"
> on the host, crashing qemu.
> 
> I'm able to install If I *disable* use of kqemu, but:
> 
> - grub segfaults, failing to install the boot loader on the guest hard
>   disk (previously also noticed this installing a kubuntu guest),
>   so I used lilo;
> 
> - installing new Debian amd64 kernel packages seems to work, except
>   that I get an error like this on the console:
>      ld-linux.so.2[5145]: segfault at 00000000ffffbffc rip
>        0000000056565019 rsp ffff8100ffffc000 error 6
> 
> - I get warnings about lost ticks and the clock runs too fast:
> 
>       warning: many lost ticks
>       Your time source seems to be instable or some driver is hogging
>       interrupts
> 
> 
> Best regards
>                          J Esteves
> 

  parent reply	other threads:[~2006-08-17  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16  8:08 [Qemu-devel] qemu under x86_64: grub segfault, ld-linux.so segfault, lost ticks J M Cerqueira Esteves
2006-08-16  8:36 ` J M Cerqueira Esteves
2006-08-17  9:47 ` Fabrice Bellard [this message]
2006-12-06 16:51 ` [Qemu-devel] " Ludovic Drolez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44E43B4B.2050503@bellard.org \
    --to=fabrice@bellard.org \
    --cc=jmce@artenumerica.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.