Re: [RFC] kvm-s390: userspace snapshot

[Christian Borntraeger]

Am Donnerstag, 12. Juni 2008 schrieb Oliver Paukstadt:
 On Thu, 2008-06-12 at 00:14 +0200, Christian Borntraeger wrote:
 
  Ok, I got an idea.
  Does that patch fix the handle_should_not_happen PANIC?
  
 Patch does not fit, because my code contains
  vcpu-arch.sie_block-gmsor = 0x;
 so I changed this before I applied the patch.
 The console patch you mentioned was applied too.
 
 Now I am able to get the kernel running a little further:

good. I will make this patch proper and send it to Avi.

 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 003d72a8, 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.

A fix is upstream in Linus git since yesterday:

commit 7b439d25300dc59bba76b53eb344bb9e5a1133f2
Author: Carsten Otte [EMAIL PROTECTED]
Date:   Tue Jun 10 10:03:22 2008 +0200

[S390] vt220 console, initialize list head before use
[...]

diff --git a/drivers/s390/char/sclp_vt220.c b/drivers/s390/char/sclp_vt220.c
index 62576af..3e577f6 100644
--- a/drivers/s390/char/sclp_vt220.c
+++ b/drivers/s390/char/sclp_vt220.c
@@ -773,6 +773,7 @@ sclp_vt220_con_init(void)
 {
int rc;
 
+   INIT_LIST_HEAD(sclp_vt220_register.list);
if (!CONSOLE_IS_SCLP)
return 0;
rc = __sclp_vt220_init();
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [RFC] kvm-s390: userspace snapshot

[Oliver Paukstadt]

On Fri, 2008-06-06 at 17:54 +0200, Carsten Otte wrote:
 This patch is a full snapshot of kuli, our current userspace for
 kvm.
 It is 3000 lines of code, and it contains a bootloader as well as
 virtio backeds for console, network, and block. It's command line
 syntax
 is same as the common kvm userspace, but not all options are
 supported.
 See --help for details.
 Our next step will be to get rid of the guest phys == user virt
 address
 mapping, so that we can have the guest memory anywhere on a megabyte
 boundary in userland. After that, we'd like to integrate this into the
 common kvm userspace, it is not intended for customer production use
 but
 is a good starting point to explore what kvm can look alike on s390.
 
 Have fun reading 
I started playing around with the stuff.

I was able to get a running host kernel based on yesterdays kvm.git +
Christian's VIRTIO_BLK_F_BLK_SIZE patch + Frank's latest qeth fixes.

I decided to use the same kernel/initrd for my first guest system and
expected the kernel to run at least through initial setup code, but
there was an unexpected intercept:

init_logging: KULI logging initialized
do_ipl: perparing for IPL
get_pages: map guest memory at 0x1000 (pfn: 65536)
get_pages: map guest memory at 0x10001000 (pfn: 65537)
get_pages: map guest memory at 0x10003000 (pfn: 65539)
get_pages: map guest memory at 0x10005000 (pfn: 65541)
load_ipl: Booting from kernel image file
image-2.6.26-rc5kvm-20080609-01433-gdf4245d-dirty
load_from_files: loading ramdisk file
initrd-2.6.26-rc5kvm-20080609-01433-gdf4245d-dirty at 80
load_from_files: loading kernel parameter file parmfile
do_ipl: IPL from address 1
launch_cpu_ipl: starting guest (ipl)
run_cpu: cpu 0: activated, running work...
handle_should_not_happen: PANIC:cpu 0 caught unexpected intercept. Magic
number: 0x20

Did I miss anything, like setting up virtual consoles, addressing mode
or is there another kernel option for guests I did not see?
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?

Regards,
Oliver


--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html