From: Matthias Meyer <Matthias.Meyer@gmx.li>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Vista guest doesn t start after libvirt/qemu upgrade
Date: Tue, 22 Feb 2011 07:51:19 +0100 [thread overview]
Message-ID: <201102220751.20175.Matthias.Meyer@gmx.li> (raw)
Hi,
I've updated my Debian lenny to Debian squeeze last week. So I have now:
qemu 0.12.5+dfsg-3
qemu-keymaps 0.12.5+dfsg-3
qemu-kvm 0.12.5+dfsg-5
qemu-system 0.12.5+dfsg-3
qemu-user 0.12.5+dfsg-3
qemu-utils 0.12.5+dfsg-3
libvirt 0.8.3-5
virt-manager 0.8.4-8
Yesterday I try to start my Vista quest again. I am surprised because it
won't starts. In "/var/log/libvirt/qemu/devel-vista.log" stands "Read
failed". The Console stays as a black screen after a short SeaBIOS message.
I tried system recovery too but Vista system recovery identified the Vista
installation without any errors.
Nearly the same occurs with my Windows7 guest. The logfile seems fine but the
console present me:
Starting SeaBIOS (version...)
Booting from Hard Disk...
Boot failed: not a bootable disk
I tried system recovery too and indeed, W7 doesn't found a Windows
Installation.
linux-dev:~# LANG==C ls -lh --block-size=1M /var/lib/libvirt/images/
total 90399
-rwxr-xr-x 1 root root 10000 Feb 12 19:20 devel-CentOS.img
-rwxr-xr-x 1 root root 10000 Feb 15 20:17 devel-SUSE.img
-rwxr-xr-x 1 root root 10001 Feb 16 22:55 devel-fedora.img
-rwxr-xr-x 1 root root 10000 Feb 16 19:23 devel-ubuntu.img
-rwxr-xr-x 1 root root 12575 Feb 1 07:56 devel-vista.qcow2
-rwxr-xr-x 1 libvirt-qemu kvm 40961 Feb 21 23:50 devel-vista.qcow2.2del
-rwxr-xr-x 1 root root 9330 Jan 23 18:03 devel-w7.qcow2
-rwxr-xr-x 1 root root 10136 Feb 13 20:58 devel-w7.qcow2.2del
-rwxr-xr-x 1 root root 10241 Feb 22 00:34 devel-xp.qcow2
the *.2del files are the original images which doesn't start. The responding
files without .2del are restored from a backup.
WindowsXP as well as different Linux guests start and run fine.
There are any experience with this obscurse behavior?
Thanks in advance
Matthias
--
Don't Panic
reply other threads:[~2011-02-22 6:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201102220751.20175.Matthias.Meyer@gmx.li \
--to=matthias.meyer@gmx.li \
--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).