On Dec 8, 2015, at 9:34 AM, Michael Weiner wrote:
> Has anyone experience a slow YAST response?
I had this experience if my guest had insufficient storage. ISTR the transition
from SLES10 to SLES11 meant we needed 384 MB storage, instead of 256 MB, in
order to survive YaST2 during installation.
No problems here, also on 11 sp3 (at very current maintenance).
are you using the X version or the ncurses one?
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael
Weiner
Sent: Tuesday, December 08, 2015 9:35 AM
To: LINUX-390@VM.MARIST.EDU
Sub
On Tue, 8 Dec 2015 14:04:15 -0800
Tom Huegel wrote:
> When I try to do this:
> [root@fedora ~]# dnf groupinstall "KDE Plasma Workspaces"
>
> I get this:
> Last metadata expiration check performed 2:55:39 ago on Tue Dec 8
> 14:04:18
> 2015.
> Error: nothing provides plasmashell >= 5.4 needed by
>
When I try to do this:
[root@fedora ~]# dnf groupinstall "KDE Plasma Workspaces"
I get this:
Last metadata expiration check performed 2:55:39 ago on Tue Dec 8 14:04:18
2015.
Error: nothing provides plasmashell >= 5.4 needed by
plasma-workspace-5.4.2-4.fc23.s390.
nothing provides pulseaudio-module
Hello all.
Has anyone experience a slow YAST response?
For example, I am navigating through the partitioner and it is extremely
slow.
It takes a long time too load and a long time to do anything really.
Any suggestions?
I am running on z/VM SLES 11 SP3
--
Michael Weiner
Systems Admin
Infinit
Dan/Jan,
I tried Jan's suggestion and replaced
root=live:
https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/s390x/os/images/install.img
with:
inst.repo=
https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/s390x/os/
Now it is working..
Thanks
On Tue, Dec 8, 201
On Tue, 8 Dec 2015 08:25:12 -0800
Tom Huegel wrote:
> Dan,
> That line is OK, it is just the display that looks funky.
ah, then the mail client :-)
But do you have more of the logs? I can't see an other error in the
parts you posted.
Dan
> I get the error after several scree
Hi,
does it work if you replace:
root=live:https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/s390x/os/images/install.img
with:
inst.repo=https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/s390x/os/
?
On 8.12.2015 16:22, Tom Huegel wrote:
I am trying to do a z
Dan,
That line is OK, it is just the display that looks funky.
I get the error after several screens of this:
[ [32m OK [0m] Started Show Plymouth Boot
Screen.
[ [32m OK [0m] Reached target
Paths.
[ [32m OK [0m] Reached target Basic
System.
[ 27.999173] dracut-initqueue[719]: % Total
On Tuesday, 12/08/2015 at 02:46 GMT, Bruce Hayden
wrote:
> Note that CPFMTXA refers to the blocks on FB-512 disks as "pages" and
there
> are 8 blocks in a page. So the reserved area at the start of a FB-512
> volume is 4 pages but 32 blocks. In EXTENT CONTROL, you'd start at 32,
not
> 4.
>
>
On Tue, 8 Dec 2015 07:22:21 -0800
Tom Huegel wrote:
> I am trying to do a z/VM install of F23 via a virtual reader IPL. This
> worked with F21.
>
> Here is the error.
>
> [ 565.043571] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0
> auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracu
I am trying to do a z/VM install of F23 via a virtual reader IPL. This
worked with F21.
Here is the error.
[ 565.043571] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-initqu
eue comm="systemd" exe="/usr/lib/systemd/systemd" hostnam
Note that CPFMTXA refers to the blocks on FB-512 disks as "pages" and there
are 8 blocks in a page. So the reserved area at the start of a FB-512
volume is 4 pages but 32 blocks. In EXTENT CONTROL, you'd start at 32, not
4.
But - EXTENT CONTROL allows a keyword "Start" for the beginning
allocati
On Tuesday, 12/08/2015 at 02:13 GMT, "Will, Chris"
wrote:
> I have been investigating using EDEV devices (EMC SAN) for Linux guest
> deployment. What I would like to do is request say a 1TB LUN, assign it
to
> z/VM in a DIRMAINT pool, and then deploy 40G of space to the guests. I
see how
> to
I have been investigating using EDEV devices (EMC SAN) for Linux guest
deployment. What I would like to do is request say a 1TB LUN, assign it to
z/VM in a DIRMAINT pool, and then deploy 40G of space to the guests. I see how
to create EDEV devices and I see a few examples of 9336 type devices
15 matches
Mail list logo