public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Paukstadt <pstadt@sourcentral.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Carsten Otte <cotte@de.ibm.com>, kvm@vger.kernel.org
Subject: Re: [RFC] kvm-s390: userspace snapshot
Date: Thu, 12 Jun 2008 21:56:45 +0200	[thread overview]
Message-ID: <1213300605.18768.21.camel@nerve> (raw)
In-Reply-To: <200806121614.26600.borntraeger@de.ibm.com>

On Thu, 2008-06-12 at 16:14 +0200, Christian Borntraeger wrote:
> Am Donnerstag, 12. Juni 2008 schrieb Oliver Paukstadt:
> > PID hash table entries: 256 (order: 8, 2048 bytes)
> > console [hvc0] enabled
> > sclp vt220 tty driver: could not register vt220 - sclp_register returned
> > -5
> > list_del corruption. prev->next should be 00000000003d72a8, but was
> 
> Yes, Carsten ran into that as well, when we changed from vt220 to 
> virtio_console. Looks like the vt220 driver doesnt like it, when there is no 
> sclp available.
> 
Thanks, looks like my new toy is running ;-)
Great job!

VM00 Name:            KVMguest
VM00 Control Program: KVM/Linux       
VM00 Adjustment:      1000
VM00 CPUs Total:      1
VM00 CPUs Configured: 1
VM00 CPUs Standby:    0
VM00 CPUs Reserved:   0

VM01 Name:            KVM01   
VM01 Control Program: z/VM    5.3.0   
VM01 Adjustment:      285
VM01 CPUs Total:      4
VM01 CPUs Configured: 4
VM01 CPUs Standby:    0
VM01 CPUs Reserved:   0



      reply	other threads:[~2008-06-12 19:56 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
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 [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=1213300605.18768.21.camel@nerve \
    --to=pstadt@sourcentral.org \
    --cc=borntraeger@de.ibm.com \
    --cc=cotte@de.ibm.com \
    --cc=kvm@vger.kernel.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