qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: J M Cerqueira Esteves <jmce@artenumerica.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu under x86_64: grub segfault, ld-linux.so segfault, lost ticks
Date: Wed, 16 Aug 2006 09:08:14 +0100	[thread overview]
Message-ID: <44E2D26E.50101@artenumerica.com> (raw)

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

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

             reply	other threads:[~2006-08-16  8:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16  8:08 J M Cerqueira Esteves [this message]
2006-08-16  8:36 ` [Qemu-devel] qemu under x86_64: grub segfault, ld-linux.so segfault, lost ticks J M Cerqueira Esteves
2006-08-17  9:47 ` Fabrice Bellard
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=44E2D26E.50101@artenumerica.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).