search for: zipl

...en issuing a FIBMAP ioctl for a block written right before while the FS is under high load (RH build universe), the assertion !journal->j_running_transaction fails at the bottom of journal_flush() in fs/jbd/journal.c. We encountered this problem with the arch=s390x (64 bit big endian) bootloader zipl, I'll try to reproduce it with 2.4.latest on arch=i386. I'll try to create a stack backtrace as well by inserting a BUG();. Strace of problem: ioctl(5, FIBMAP, 0x1ffffffe528) = 0 close(5) = 0 write(4, "\0\342\0\6\4\20\0\0\0\0\0\0\0\0\0\0\0\0\0\0\...

I wonder if there would be anyone who would be willing to add extlinux support to RedHat's grubby program. From the looks of it, they already have grub, lilo, zipl, elilo, yaboot, and silo support, so I can't imagine it's that complex. -hpa

...v Well, I really had to use start --console from the beginning. It would have safe the time. # start --console s390_generic Using guessed DASD geometry. Using ECKD scheme (block size 4096), CDL ! No zIPL section in IPL2 record. ! -- With best regards, Matwey V. Kornilov

...rt --console from the beginning. It would >have safe the time. > ># start --console s390_generic >Using guessed DASD geometry. > Using ECKD scheme (block size 4096), CDL > > ! >No zIPL section in IPL2 record. ! > Yeah, it all looked like the guest OS just ends normally itself. So precisely what libvirt was reporting. I'm glad this is resolved. Have a nice day, Martin

...+is given as arguement: +KVM_S390_STORE_STATUS_NOADDR - the CPU stores its status to the save area in +absolute lowcore as defined by the principles of operation +KVM_S390_STORE_STATUS_PREFIXED - the CPU stores its status to the save area in +its prefix page just like the dump tool that comes with zipl. This is useful +to create a system dump for use with lkcdutils or crash. + +ioctl: KVM_S390_SET_INITIAL_PSW +args: struct kvm_s390_psw * +see also: include/linux/kvm.h +This ioctl can be used to set the processor status word (psw) of a stopped cpu +prior to running it with KVM_RUN. Note that thi...

...+is given as arguement: +KVM_S390_STORE_STATUS_NOADDR - the CPU stores its status to the save area in +absolute lowcore as defined by the principles of operation +KVM_S390_STORE_STATUS_PREFIXED - the CPU stores its status to the save area in +its prefix page just like the dump tool that comes with zipl. This is useful +to create a system dump for use with lkcdutils or crash. + +ioctl: KVM_S390_SET_INITIAL_PSW +args: struct kvm_s390_psw * +see also: include/linux/kvm.h +This ioctl can be used to set the processor status word (psw) of a stopped cpu +prior to running it with KVM_RUN. Note that thi...

On Fri, Oct 20, 2017 at 10:12:19PM +0300, Matwey V. Kornilov wrote: >2017-10-20 17:14 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: >> 2017-10-20 15:16 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: >>> On Fri, Oct 20, 2017 at 03:07:19PM +0300, Matwey V. Kornilov wrote: >>>> >>>> 2017-10-20 14:59 GMT+03:00 Martin Kletzander

This patch series introduces a backend for kvm to run on IBM System z machines that uses the mainframe's sie virtualization capability. This work runs 64bit guests on z800/z890/z900/z990/z9/z10 class machines with a 64bit linux host. Userspace will follow once we're done brushing it over. The patch queue consists of the following patches, which can be applied in sequence on top of kvm.git

This patch series introduces a backend for kvm to run on IBM System z machines that uses the mainframe's sie virtualization capability. This work runs 64bit guests on z800/z890/z900/z990/z9/z10 class machines with a 64bit linux host. Userspace will follow once we're done brushing it over. The patch queue consists of the following patches, which can be applied in sequence on top of kvm.git