Re: KVM on IBM System z
Hi all, many thanks to Carsten. And i think i found one more way: [root@linux qemu]# ./bin/qemu-system-s390x -monitor stdio -machine type=s390-virtio,accel=kvm VNC server running on `127.0.0.1:5900' QEMU 1.2.0 monitor - type 'help' for more information (qemu) info kvm kvm support: enabled (qemu) By the way, is there any support for the virtual nics in the current s390x distros? I suppose qeth and iucv will not work with the network interfaces. Kind regards, Tobias > Your qemu process should have kvm file descriptors open in /proc/fds/ > and you should see a debug area in /sys/kernel/debug/s390dbf/kvm-/ > > with kind regards > Carsten Otte > System z firmware development / Boeblingen lab > --- > Every revolution was first a thought in one man's mind; > and when the same thought occurs to another man, it is the key to that era. > - Ralph Waldo Emerson, Essays: First Series, 1841 > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Query for Destination z article on chargeback systems
Query for Destination z article on chargeback systems I'm writing article for Destination z -- http://destinationz.org/ -- giving tips on chargeback systems. I'm interested in reasons for/against implementing chargeback; technical tips for implementing; political hints for inflicting, including getting management buy-in; financial aspects for setting fair rates; suggestions for DEFINING fair rates; native tools, vendor and free offerings, home-grown systems; problems/pitfalls/gotchas/solutions; reality matters for preventing mainframes from being burdened with unrelated costs and overheads; etc. For this one, brief anecdotes -- war/horror stories describing good/bad/neutral experiences -- will be useful. I'll review list archives but pointers to relevant threads will help. Operating system-agnostic tips and system-specific issues/tips/tools are both essential. As usual, please copy me directly so I don't miss responses in list digests. Thanks... -- Gabriel Goldberg, Computers and Publishing, Inc. g...@gabegold.com 3401 Silver Maple Place, Falls Church, VA 22042 (703) 204-0433 LinkedIn: http://www.linkedin.com/in/gabegoldTwitter: GabeG0 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Moving Root DASD
>>> On 10/11/2012 at 03:41 PM, Ben Duncan wrote: > Hi group. Need to some help in transferring and recreating the ROOT ( / > ) dasd device to another dasd > Specifically we want to migrate from a 300MB partition and replace it > with a 2Gb partition which is > already formatted and prepped. > > > Any pointer or how to's on this ? I wouldn't do it in the first place. If you need additional space, add DASD volumes, use them to create an LVM VG and LVs, and migrate things like /usr, /var, /tmp, etc. to them using http://linuxvm.org/Info/HOWTOs/movefs.html Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Moving Root DASD
The easiest thing to do is bring the guest down and LINK these 2 disks from another running Linux .. mount them as /mnt /mnt/disk1 and 2 and copy - I would use rsync: rsync -av /mnt/disk1/ /mnt/disk2 Unmount, detach - and swap the disks in the directory so the big disk is the same address as the old small one. If you don't have another running Linux you can do something similar by booting the install kernel from the reader and getting into the recovery shell.. I don't think the rsync command is there, so you'd have to use the 'cp' command or a tar pipe. Scott Rohling On Thu, Oct 11, 2012 at 12:41 PM, Ben Duncan wrote: > Hi group. Need to some help in transferring and recreating the ROOT ( / > ) dasd device to another dasd > Specifically we want to migrate from a 300MB partition and replace it > with a 2Gb partition which is > already formatted and prepped. > > > Any pointer or how to's on this ? > > Thanks ... > > Ben Duncan - Business Network Solutions, Inc. 336 Elton Road Jackson > MS, 39212 > "Never attribute to malice, that which can be adequately explained by > stupidity" > - Hanlon's Razor > > > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Moving Root DASD
Hi group. Need to some help in transferring and recreating the ROOT ( / ) dasd device to another dasd Specifically we want to migrate from a 300MB partition and replace it with a 2Gb partition which is already formatted and prepped. Any pointer or how to's on this ? Thanks ... Ben Duncan - Business Network Solutions, Inc. 336 Elton Road Jackson MS, 39212 "Never attribute to malice, that which can be adequately explained by stupidity" - Hanlon's Razor -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: HyperPAV and LVM striping
Leland Lucius already pointed out how to work around this ("lvextend -I 1").
Tom may not have seen that as an option because he used YaST. You have to
run the component parts (lvextend and ext2online) by hand to change the
striping. (You may also have to do that to get a helpful error message;
my memory is that YaST failed saying no space, which was really confusing
when we could see free cylinders in the volume group.)
Ted Rodriguez-Bell
Wells Fargo, Mainframe and Midrange Services
Company policy requires: This message may contain confidential and/or
privileged information. If you are not the addressee or authorized to receive
this for the addressee, you must not use, copy, disclose, or take any action
based on this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail and
delete this message. Thank you for your cooperation.
-Original Message-
From: Duerbusch, Tom [mailto:duerbus...@stlouis-mo.gov]
Sent: Wednesday, October 10, 2012 11:37 AM
Subject: Re: HyperPAV and LVM striping
So that might have been my problem (but not necessarily limited to that
one).
I was on Suse 10 system. I initially stripped the LVM. When it got nearly
full, I tried to add a pack. Couldn't do it. So I went back and recreated
the LVM without striping and I could add a pack. I want to say that the
documentation at that time, also said you couldn't add packs to a striped
LVM, but that was a while ago.
Anyway, it hasn't been a performance issue. But that is due to us not
needing the I/O performance.
Thanks for the update. I'm updating my notes.
Tom Duerbusch
THD Consulting
On Wed, Oct 10, 2012 at 12:53 PM, Mark Post wrote:
> >>> On 10/10/2012 at 11:35 AM, "Duerbusch, Tom"
> wrote:
>
> > Just speaking to LVM...
> >
> > Striping the data across multiple volumes (which in modern dasd is
> already
> > stripped in the Raid array), would give you the best performance.
> > Especially if you can strip across multiple DS8000 (or other dasd
> > subsystems).
> >
> > But you can also use LVM as a pool of DASD, with no striping involved.
> >
> > In case 1, if you need to expand the LVM pool, it is a hassle. It might
> > mean backing up, reformatting and reloading the data. In any case, it
> > involves a knowledgeable person and most likely, downtime.
>
> This is simply not true. Expanding a striped LV can be done dynamically
> with no downtime. The only aspect that is different from a non-striped LV
> is that you have to have enough free space on as many different PVs as the
> number of stripes you have. That is, if you did an "lvcreate -i 2" then
> when you do an lvextend/lvresize, you have to have free space available on
> 2 different PVs in the pool. An "lvcreate -i 3" means you need free space
> on 3 PVs, etc.
>
> A lot of people tend to add space to a volume group one PV at a time. If
> you're using striped LVs, that won't work unless you make sure that the
> existing PVs have enough free space on them to accommodate additional
> stripes being allocated.
>
>
> Mark Post
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
--
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Destination z article: Competent complaining creates constructive catastrophe conclusion climate
Competent complaining creates constructive catastrophe conclusion climate http://destinationz.org/Mainframe-Solution/Systems-Administration/Competent-Complaining-Creates-Constructive-Catastr.aspx Thanks for input; next query to come shortly... -- Gabriel Goldberg, Computers and Publishing, Inc. g...@gabegold.com 3401 Silver Maple Place, Falls Church, VA 22042 (703) 204-0433 LinkedIn: http://www.linkedin.com/in/gabegoldTwitter: GabeG0 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Antwort: Re: KVM on IBM System z
Your qemu process should have kvm file descriptors open in /proc/fds/ and you should see a debug area in /sys/kernel/debug/s390dbf/kvm-/ with kind regards Carsten Otte System z firmware development / Boeblingen lab --- Every revolution was first a thought in one man's mind; and when the same thought occurs to another man, it is the key to that era. - Ralph Waldo Emerson, Essays: First Series, 1841 -Linux on 390 Port schrieb: - An: LINUX-390@vm.marist.edu Von: Tobias Doerkes Gesendet von: Linux on 390 Port Datum: 11.10.2012 07:15 Betreff: Re: KVM on IBM System z Hi all, one more question regarding KVM on IBM System z: Is there a way to check wether KVM is using hardware virtualisation (SIE instruction)? I installed SLES 11 and virt-host-validate is missing. In FC 17 it returns only software virtualisation: QEMU: Checking for hardware virtualization : WARN (Only emulated CPUs are available, performance will be significantly limited) QEMU: Checking for device /dev/vhost-net : PASS QEMU: Checking for device /dev/net/tun : PASS LXC: Checking for Linux >= 2.6.26 : PASS But i think virt-host-validate in FC17 has no support for s390x. So i want to check wether SIE is used or not. Kind regards, Tobias. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
