From: Sid Boyce <g3vbv@blueyonder.co.uk>
To: Avi Kivity <avi@redhat.com>
Cc: linux-kernel@vger.kernel.org, Sid Boyce <sboyce@blueyonder.co.uk>,
KVM list <kvm@vger.kernel.org>
Subject: Re: OpenSolaris boot failure with KVM and VirtualBox
Date: Sun, 26 Jul 2009 22:59:09 +0100 [thread overview]
Message-ID: <4A6CD1AD.6090009@blueyonder.co.uk> (raw)
In-Reply-To: <4A6C9DE6.8080002@redhat.com>
On 26/07/09 19:18, Avi Kivity wrote:
> On 07/26/2009 09:14 PM, Sid Boyce wrote:
>>
>>> Is this a regression from previous kernel versions? What userspace are
>>> you using?
>>>
>>>
>>
>> Currently running 2.6.31-rc4 with the original kqemu-1.4.0pre1 on
>> openSUSE 11.2 Milestone 4 and it boots OK - a 200G disk image used.
>> qemu-system-x86_64 -cdrom /ISO/osol-0906-ai-x86.iso -boot d
>> /osol0906.qcow2 -smp 4 -m 500M&
>>
>
> Wait, are you using kqemu or kvm?
>
# l /dev/kvm
crw-rw----+ 1 root root 10, 232 2009-07-24 20:26 /dev/kvm
# lsmod|grep kvm
kvm_amd 41908 0
kvm 180488 1 kvm_amd
>From long ago I read that kvm needed kqemu, so I have always built the
module, but I see here it's not used.
lsmod|grep qemu
kqemu 173496 0
# rpm -qf /usr/bin/qemu-system-x86_64
qemu-0.10.1-2.21
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
next prev parent reply other threads:[~2009-07-26 21:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 7:30 OpenSolaris boot failure with KVM and VirtualBox Sid Boyce
2009-07-26 16:13 ` Avi Kivity
2009-07-26 16:48 ` Heinz Diehl
2009-07-26 18:14 ` Sid Boyce
2009-07-26 18:18 ` Avi Kivity
2009-07-26 21:59 ` Sid Boyce [this message]
2009-07-27 5:36 ` Alexander Graf
2009-07-27 11:11 ` Sid Boyce
[not found] ` <8A7B7BFF-9561-478A-898F-DD7031558960@suse.de>
2009-07-27 11:28 ` Sid Boyce
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=4A6CD1AD.6090009@blueyonder.co.uk \
--to=g3vbv@blueyonder.co.uk \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyce@blueyonder.co.uk \
/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