From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Oliver Paukstadt <pstadt@sourcentral.org>
Cc: Carsten Otte <cotte@de.ibm.com>,
kvm@vger.kernel.org, Avi Kivity <avi@qumranet.com>,
aliguori@us.ibm.com, jblunck@suse.de, ihno@suse.de,
rvdheij@gmail.com, rusty@rustcorp.com.au
Subject: Re: [RFC] kvm-s390: userspace snapshot
Date: Wed, 11 Jun 2008 16:35:19 +0200 [thread overview]
Message-ID: <200806111635.19865.borntraeger@de.ibm.com> (raw)
In-Reply-To: <1213077358.3120.33.camel@nerve>
Am Dienstag, 10. Juni 2008 schrieb Oliver Paukstadt:
> Did I miss anything, like setting up virtual consoles, addressing mode
> or is there another kernel option for guests I did not see?
It is not related to the problem you are seeing, but you will need
virtio_console kernel support before you get any console output.
I am currently at the KVM forum, but I plan to continue the following patch
set:
http://www.gossamer-threads.com/lists/linux/kernel/929047
This patch set should work nevertheless.
> Documentation is a little short, any hint appreciated ;-)
> I did this test running the host system as guest in z/VM 5.3 on z900, is
> this "supported"?
Hmm, I have no z900 to test on, currently we prototype on an z9. It used to
work under z/VM - I have to retest.
Can you run kuli with the -sysdump parameter and check
in /sys/kernel/debug/s390dbf/kvm-*/sprintf for
"unhandled validity intercept code %d"
and tell us about %d
while the dump is taken?
Christian
next prev parent reply other threads:[~2008-06-11 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 15:54 [RFC] kvm-s390: userspace snapshot Carsten Otte
2008-06-10 5:55 ` Oliver Paukstadt
2008-06-11 14:35 ` Christian Borntraeger [this message]
2008-06-11 20:53 ` Oliver Paukstadt
2008-06-11 22:14 ` Christian Borntraeger
2008-06-12 5:39 ` Oliver Paukstadt
2008-06-12 14:14 ` Christian Borntraeger
2008-06-12 19:56 ` Oliver Paukstadt
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=200806111635.19865.borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=avi@qumranet.com \
--cc=cotte@de.ibm.com \
--cc=ihno@suse.de \
--cc=jblunck@suse.de \
--cc=kvm@vger.kernel.org \
--cc=pstadt@sourcentral.org \
--cc=rusty@rustcorp.com.au \
--cc=rvdheij@gmail.com \
/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