public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Henry <adhenry-cgr7CL/LOSDk1uMJSBkQmQ@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: kvm core dumps at random
Date: Thu, 05 Apr 2007 13:58:43 +0200	[thread overview]
Message-ID: <4614E473.60708@bredband.net> (raw)


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

I am getting core dumps when running kvm at various times.  I am trying
to install WindowsXP as a guest and kvm core dumps at various times
during install, so I have not been able to finish the install.

HP Pavilion dv9297ea Intel Core2Duo 7200, 2GB RAM
VT is enabled in the BIOS and kvm-intel module is loaded successfully
Ubuntu Feisty Fawn beta 2.6.20-13
kvm 0.9.0
Installing winxp pro as guest (no slipstreamed SP, just vanilla version)

I am a member of kvm group but I still have to chmod 777 /dev/kvm to not
get error about kvm not initialized.

Starting newly created qemu image with:

kvm -m 512 -cdrom /dev/cdrom /var/qemu-images/winXP.img

-no-acpi has no affect on core dumping.

I got almost all way through installation this morning, and it core
dumped near the end: QEMU window disappears and I get lots of text in
terminal which ends with (Core dump).  As it got so far, I can now start
WinXP, but it is very slow, as if VT is not being used at all, but I get
no errors when starting kvm.

Any help greatly appreciated.

--andrew

-- 
GnuPG Key ID: ECB18ABA
Fingerprint:  FDF3 91FC F5BC 1164 E217  315E 337E 219B ECB1 8ABA



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

[-- Attachment #2: Type: text/plain, Size: 345 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

             reply	other threads:[~2007-04-05 11:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 11:58 Andrew Henry [this message]
     [not found] ` <4614E473.60708-cgr7CL/LOSDk1uMJSBkQmQ@public.gmane.org>
2007-04-05 12:24   ` kvm core dumps at random Avi Kivity
     [not found]     ` <4614EA65.5020603-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-05 13:06       ` Andrew Henry
     [not found]         ` <4614F46B.9000702-cgr7CL/LOSDk1uMJSBkQmQ@public.gmane.org>
2007-04-05 13:21           ` Avi Kivity
     [not found]             ` <4614F7E0.3050807-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-05 17:51               ` Andrew Henry
     [not found]                 ` <4615370D.8070005-cgr7CL/LOSDk1uMJSBkQmQ@public.gmane.org>
2007-04-08  6:05                   ` Avi Kivity

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=4614E473.60708@bredband.net \
    --to=adhenry-cgr7cl/losdk1umjsbkqmq@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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