From: Ryan Harper <ryanh@us.ibm.com>
To: Alexey Eremenko <al4321@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Bug: SCSI/VirtIO: VM unable to reboot from non-IDE controller
Date: Mon, 20 Apr 2009 09:11:31 -0500 [thread overview]
Message-ID: <20090420141131.GJ25977@us.ibm.com> (raw)
In-Reply-To: <7fac565a0904200253k7ec3e83m28401adea775436f@mail.gmail.com>
* Alexey Eremenko <al4321@gmail.com> [2009-04-20 04:56]:
> Hi All !
>
> Most Linux VMs (Ubuntu and Red Hat-based systems -- RHEL, Fedora) have
> failed during automated tests
> on SCSI and VirtIO disks on Qemu/KVM.
> It turned out to be a problem of Qemu/KVM, where after a software reboot
> (i.e. initiated by guest OS), the system is unable to boot from SCSI
> controller.
>
> To reboot successfully you need either soft reboot+IDE or Hard reboot (Qemu
> cold boot)+SCSI.
>
> The Command sent to Qemu/KVM:
> /usr/local/bin/qemu-system-x86_64 -m 512 -monitor
> tcp:localhost:4602,server,nowait -cdrom /isos/linux/Fedora-8-i386-DVD.iso
> -drive file=/vm/fedora8-32.qcow2,if=scsi,boot=on -name fedora8-32
You're using extboot (boot=on) which is part of kvm. I sent a patch[1]
to since the upstream kvm-userspace bits had the wrong option rom reset
address. This should be fixed in upstream kvm-userspace.git[2].
1. http://kerneltrap.org/mailarchive/linux-kvm/2009/4/6/5418914
2. http://git.kernel.org/?p=linux/kernel/git/avi/kvm-userspace.git;a=commit;h=a1075de527f309850df278484f2ef4127827c6f4
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com
prev parent reply other threads:[~2009-04-20 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 9:53 [Qemu-devel] Bug: SCSI/VirtIO: VM unable to reboot from non-IDE controller Alexey Eremenko
2009-04-20 14:11 ` Ryan Harper [this message]
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=20090420141131.GJ25977@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=al4321@gmail.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.