From gjn at gjn.priv.at Mon Sep 1 02:56:02 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Mon, 01 Sep 2014 10:56:02 +0200
Subject: [sles-beta] openldap Packet broken
In-Reply-To: <20140901080126.GA2329@mrakoplas.suse.cz>
References: <2178527.vkkg8vLgvR@gjn.priv.at> <2269910.96t0uo2KNg@gjn.priv.at>
<20140901080126.GA2329@mrakoplas.suse.cz>
Message-ID: <3169516.F4RgFcridJ@gjn.priv.at>
Hello,
Am Montag, 1. September 2014, 10:01:26 schrieb Martin Vidner:
> On Sat, Aug 30, 2014 at 12:04:18PM +0200, G?nther J. Niederwimmer wrote:
> > Am Freitag, 29. August 2014, 21:41:26 schrieb Thorsten Kukuk:
> ...
>
> > > So the user and group ldap should be created.
> > > Please look in /var/log/zypp/history, if there is an error
> > > message about openldap installation.
> > > For me, it works.
> >
> > I tested it today ;)
> >
> > You are right, when I Install openlad as single packet I have the user /
> > group ldap.
> >
> > But when I install over YaST2 auth Server I have no user / group ldap
> >
> > now I start to test to config openldap handy.
> >
> > after install with YaST2 Auth Server I have always the Error
> > "Implementation Error" when I like to change anything, also when I
> > create user / group ldap ?
> That looks like a bug in the YaST module. Please enter a bug in
> Bugzilla and attach YaST logs.
> https://en.opensuse.org/openSUSE:Report_a_YaST_bug
I have open a #SR 10909975181 with Supportconfig output,
When you like more YaST Log, tell me.
But I have a other question to Ldap.(YaST2)
With YasT I can create a mirror Mode config but afterward i cant change the DB,
with a single installation it is possible (olcSyncRepl)
The next is the YaST Module SUSEMirrorMode?
What should this Module do ???
I mean it is broken !!
I canT create a mirror Server with this Module, the Module tell me the YaST
created ldap config is broken, I have to canche the ldap server.
when I have a hand createt mirror ( it is possible from a single installation)
The tool let me only delete a create mirror ??
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From gjn at gjn.priv.at Mon Sep 1 03:15:51 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Mon, 01 Sep 2014 11:15:51 +0200
Subject: [sles-beta] openldap Packet broken
In-Reply-To: <54042FD6.3090202@b1-systems.de>
References: <2178527.vkkg8vLgvR@gjn.priv.at>
<20140901080126.GA2329@mrakoplas.suse.cz>
<54042FD6.3090202@b1-systems.de>
Message-ID: <1846825.5CPqRbIVza@gjn.priv.at>
Am Montag, 1. September 2014, 10:35:34 schrieb Florian Winkler:
> Hello,
>
> Am 01.09.2014 10:01, schrieb Martin Vidner:
> > On Sat, Aug 30, 2014 at 12:04:18PM +0200, G?nther J. Niederwimmer wrote:
> >> Am Freitag, 29. August 2014, 21:41:26 schrieb Thorsten Kukuk:
> > ...
> >
> >>> So the user and group ldap should be created.
> >>> Please look in /var/log/zypp/history, if there is an error
> >>> message about openldap installation.
> >>> For me, it works.
> >>
> >> I tested it today ;)
> >>
> >> You are right, when I Install openlad as single packet I have the user /
> >> group ldap.
> >>
> >> But when I install over YaST2 auth Server I have no user / group ldap
> >>
> >> now I start to test to config openldap handy.
> >>
> >> after install with YaST2 Auth Server I have always the Error
> >> "Implementation Error" when I like to change anything, also when I
> >> create user / group ldap ?>
> > That looks like a bug in the YaST module. Please enter a bug in
> > Bugzilla and attach YaST logs.
> > https://en.opensuse.org/openSUSE:Report_a_YaST_bug
>
> i cannot reproduce this erratic behaviour here. I used the YaST module
> to create an Auth Server and everything seems to work just fine. User
> and group 'ldap' are present and i don't get any errors. I have tested
> it today with the RC2. Which actual steps led you the error?
I mean this Problem is starting with RC1 I found it with RC2
this is a minimal (no gnome no 32 Bit) installation in text mode. I install
over ssh -X on my system, the most time the user / group ldap is not installed
but sometime it is created ? Or i install openldap before YaST AUTH-server..
The YAST Module auth-server don't check if the user / group ldap exists ?
I can start the YaST module after broken installation "normal"
My test is now after installation "su ldap" when I have no user ldap then I
install again openldap packet then i have a user / group ldap
It is broken with master / single installation.
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From kukuk at suse.de Mon Sep 1 03:23:44 2014
From: kukuk at suse.de (Thorsten Kukuk)
Date: Mon, 1 Sep 2014 11:23:44 +0200
Subject: [sles-beta] openldap Packet broken
In-Reply-To: <1846825.5CPqRbIVza@gjn.priv.at>
References: <2178527.vkkg8vLgvR@gjn.priv.at>
<20140901080126.GA2329@mrakoplas.suse.cz>
<54042FD6.3090202@b1-systems.de> <1846825.5CPqRbIVza@gjn.priv.at>
Message-ID: <20140901092344.GA14263@suse.de>
On Mon, Sep 01, G?nther J. Niederwimmer wrote:
> this is a minimal (no gnome no 32 Bit) installation in text mode. I install
> over ssh -X on my system, the most time the user / group ldap is not installed
> but sometime it is created ? Or i install openldap before YaST AUTH-server..
Did you look meanwhile if there is an error message in /var/log/zypp/history
when installing openldap packages?
> The YAST Module auth-server don't check if the user / group ldap exists ?
Of course not, why should it? That's all part of the openldap package
itself.
Thorsten
--
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
From uwedr at suse.com Mon Sep 1 06:15:23 2014
From: uwedr at suse.com (Uwe Drechsel)
Date: Mon, 1 Sep 2014 14:15:23 +0200
Subject: [sles-beta] SLES-12 Beta9 X86_64
In-Reply-To: <1526371.HXpvGIRJYO@gjn.priv.at>
References: <1526371.HXpvGIRJYO@gjn.priv.at>
Message-ID: <20140901121523.GV5019@suse.com>
On Sun, Aug 31, G?nther J.Niederwimmer wrote:
> can I found on any place Beta9 for Download again?
>
Sorry, this is no longer available on the download servers.
Uwe
--
mathematician, n:
Someone who believes imaginary things appear right before your i's.
From S.M.Flood at ucs.cam.ac.uk Tue Sep 2 08:07:32 2014
From: S.M.Flood at ucs.cam.ac.uk (Simon Flood)
Date: Tue, 02 Sep 2014 15:07:32 +0100
Subject: [sles-beta] SLES12 :: BTRFS RAID5
In-Reply-To: <5405C691.8050509@unify.com>
References: <5405C691.8050509@unify.com>
Message-ID: <5405CF24.1070409@ucs.cam.ac.uk>
On 02/09/2014 14:30, Lawton Bonnevialle wrote:
> The BTRFS will work very well with RAID5?
Are you asking about hardware or software-based RAID5?
HTH,
Simon
--
Simon Flood
Senior Systems Specialist
University of Cambridge
United Kingdom
www.linkedin.com/in/simonflood
Novell/SUSE/NetIQ Knowledge Partner
From S.M.Flood at ucs.cam.ac.uk Tue Sep 2 08:29:46 2014
From: S.M.Flood at ucs.cam.ac.uk (Simon Flood)
Date: Tue, 02 Sep 2014 15:29:46 +0100
Subject: [sles-beta] SLES12 :: BTRFS RAID5
In-Reply-To: <5405D03E.7060005@unify.com>
References: <5405C691.8050509@unify.com> <5405CF24.1070409@ucs.cam.ac.uk>
<5405D03E.7060005@unify.com>
Message-ID: <5405D45A.3090208@ucs.cam.ac.uk>
On 02/09/2014 15:12, Lawton Bonnevialle wrote:
> Hardware
From the hardware RAID side of things there shouldn't be a problem as
it doesn't care what file system is being used - all it sees are bits.
As for Btrfs it'll see a single disk (device) unless you carve up your
RAIDed physical disks into multiple logical disks.
Personally I'd prefer the RAID aspects to be handled by hardware rather
than software.
HTH,
Simon
--
Simon Flood
Senior Systems Specialist
University of Cambridge
United Kingdom
www.linkedin.com/in/simonflood
Novell/SUSE/NetIQ Knowledge Partner
From bjoern.lotz at suse.com Tue Sep 2 09:05:11 2014
From: bjoern.lotz at suse.com (Bjoern Lotz)
Date: Tue, 02 Sep 2014 17:05:11 +0200
Subject: [sles-beta] SLES12 :: BTRFS RAID5
In-Reply-To: <5405D5DF.5060402@unify.com>
References: <5405C691.8050509@unify.com>
<5405CF24.1070409@ucs.cam.ac.uk> <5405D03E.7060005@unify.com>
<5405D45A.3090208@ucs.cam.ac.uk> <5405D5DF.5060402@unify.com>
Message-ID: <5405DCA7.8080207@suse.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
independently of the RAID question, that size does not sound like it
is used for the / file system but for some partition that holds data
of some sort.
The recommendation for data partitions is to use XFS, not Btrfs, so
maybe Btrfs is not the perfect choice anyway, RAID or no RAID.
Kind regards,
Bj?rn
On 02.09.2014 16:36, Lawton Bonnevialle wrote:
> Do you feel good work it on a server with 4 or 6 4TB drives (SATA)
> in RAID5? Is stable for production server?
>
>
> On 09/02/2014 11:29 AM, Simon Flood wrote:
>> On 02/09/2014 15:12, Lawton Bonnevialle wrote:
>>
>>> Hardware
>>
>> From the hardware RAID side of things there shouldn't be a
>> problem as it doesn't care what file system is being used - all
>> it sees are bits.
>>
>> As for Btrfs it'll see a single disk (device) unless you carve up
>> your RAIDed physical disks into multiple logical disks.
>>
>> Personally I'd prefer the RAID aspects to be handled by hardware
>> rather than software.
>>
>> HTH, Simon
- --
Dr. Bj?rn Lotz, Instructional Designer, CISSP
SUSE Linux GmbH, Maxfeldstrasse 5, 90409 N?rnberg
Tel: +49 89 8639 9664 Mobil: +49 173 5876724
bjoern.lotz at suse.com PGP-ID: 0xD437D363
- ------------------
SUSE Linux GmbH, N?rnberg; HRB 21284 (AG N?rnberg)
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlQF3J8ACgkQKZToxtQ302OEuwCdEzwAZvsPqXeCMDfo+0WURcq8
1JEAn0/XwBlhjw3D0ucaEaxZ/kJhMFrb
=H4am
-----END PGP SIGNATURE-----
From mge at suse.com Tue Sep 2 10:10:05 2014
From: mge at suse.com (Matthias G. Eckermann)
Date: Tue, 2 Sep 2014 18:10:05 +0200
Subject: [sles-beta] SLES12 :: BTRFS RAID5
In-Reply-To: <5405DCA7.8080207@suse.com>
<5405D5DF.5060402@unify.com>
Message-ID: <20140902161005.GA15091@suse.com>
Hello Lawton and all,
On 2014-09-02 T 11:36 -0300 Lawton Bonnevialle wrote:
> Do you feel good work it on a server with 4 or 6 4TB
> drives (SATA) in RAID5? Is stable for production
> server?
- Hardware RAID: yes.
- Software RAID using "MD RAID": yes.
- We do not (yet) support using RAID 5 with btrfs'
native RAID implementation, and in fact the btrfs
kernel module on SUSE Linux Enterprise 12 does
not show this option even, .... This will need
some time to mature.
On 2014-09-02 T 17:05 +0200 Bjoern Lotz wrote:
> independently of the RAID question, that size does
> not sound like it is used for the / file system but
> for some partition that holds data of some sort.
>
> The recommendation for data partitions is to use XFS,
> not Btrfs, so maybe Btrfs is not the perfect choice
> anyway, RAID or no RAID.
That's true as well. Except for specific use cases
(such as using a Samba Fileserver with snapshots
(Windows versioning) via the btrfs backend) we
recommend xfs as the filesystem for data.
so long -
MgE
--
Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise
Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com
SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
From lawton.silva at unify.com Tue Sep 2 10:15:57 2014
From: lawton.silva at unify.com (Lawton Bonnevialle)
Date: Tue, 2 Sep 2014 13:15:57 -0300
Subject: [sles-beta] SLES12 :: BTRFS RAID5
In-Reply-To: <20140902161005.GA15091@suse.com>
References: <20140902161005.GA15091@suse.com>
Message-ID: <5405ED3D.6030206@unify.com>
Thanks ALL.
On 09/02/2014 01:10 PM, Matthias G. Eckermann wrote:
> Hello Lawton and all,
>
> On 2014-09-02 T 11:36 -0300 Lawton Bonnevialle wrote:
>
>> Do you feel good work it on a server with 4 or 6 4TB
>> drives (SATA) in RAID5? Is stable for production
>> server?
> - Hardware RAID: yes.
>
> - Software RAID using "MD RAID": yes.
>
> - We do not (yet) support using RAID 5 with btrfs'
> native RAID implementation, and in fact the btrfs
> kernel module on SUSE Linux Enterprise 12 does
> not show this option even, .... This will need
> some time to mature.
>
> On 2014-09-02 T 17:05 +0200 Bjoern Lotz wrote:
>
>> independently of the RAID question, that size does
>> not sound like it is used for the / file system but
>> for some partition that holds data of some sort.
>>
>> The recommendation for data partitions is to use XFS,
>> not Btrfs, so maybe Btrfs is not the perfect choice
>> anyway, RAID or no RAID.
>
> That's true as well. Except for specific use cases
> (such as using a Samba Fileserver with snapshots
> (Windows versioning) via the btrfs backend) we
> recommend xfs as the filesystem for data.
>
> so long -
> MgE
>
--
- no title specified
UNIFY ? Solu??es em Tecnologia da Informa??o LTDA.
R&D E4
Tel.: +55 41 3341 6624
lawton.silva at unify.com
www.unify.com
UNIFY ? Solu??es em Tecnologia da Informa??o LTDA. IMPORTANTE: Este
e-mail e seus anexos cont?m informa??o corporativa de propriedade
exclusiva. Se voc? recebeu essa mensagem por engano, favor notificar o
respons?vel imediatamente respondendo a esse e-mail e delet?-lo
juntamente com seus anexos de seu sistema. Obrigado.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From stephan.kurth at kucoug.de Tue Sep 2 09:43:04 2014
From: stephan.kurth at kucoug.de (Stephan Kurth)
Date: Tue, 02 Sep 2014 17:43:04 +0200
Subject: [sles-beta] SLES 12 rc 1 iso download
Message-ID:
Hello.
Is it possible that I could get the link to download the iso again?
I have dropped it and can't find the link or announcement.
The
Stephan
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit 1&1 Mail gesendet.
Pawel Wieczorkiewicz schrieb:
On Wed, 6 Aug 2014 13:42:30 +0000
wrote:
> Hi
> When installing SLES12 x86_64 on HP Proliangt Blade BL460c-Gen8 using
> the boot parameters ipv4=1 ipv6=0 ipv4only, the installation does
> work, but afterwards the network is dead
>
> # wicked ifstatus eth0 does show me the following
>
> [cid:image001.png at 01CFB18C.6B748590]
>
> Somehow the static network configuration does not get applied
> [cid:image002.png at 01CFB18C.6B748590]
>
> So in my mind there is a bug again with wicked preventing my server
> from having network connection
>
> The device is known, but it is not taken. Wicked takes eth0 as
> unknown device [cid:image003.png at 01CFB18D.04417EE0]
>
> I am really not happy about this, because the installation did work
> perfectly under SLES12 Beta9, with this configuration and
> autoinst.xml It also works best under SLES11-SP3
>
> regards
>
> Urs Frey
> Post CH AG
> Informationstechnologie
> IT Betrieb
> Webergutstrasse 12
> 3030 Bern (Zollikofen)
> Telefon : ++41 (0)58 338 58 70
> FAX : ++41 (0)58 667 30 07
> E-Mail: urs.frey at post.ch
>
>
Hi,
Thank you for reporting this.
I believe this has been already fixed in 0.6.1 version of wicked, but
to be sure I would need to look into the logs of wickedd and
wickedd-nanny.
I think the logs attached to:
Bug 890643 - wicked doesn't wait long enough on large networks
(https://bugzilla.novell.com/show_bug.cgi?id=890643)
already correspond to this issue, isn't it?
Otherwise could you please attach new logs as per instruction:
? set DEBUG=all in /etc/sysconfig/network/config
? systemctl restart wickedd
? wicked --debug all ifup all # systemctl restart wicked
? wicked ifstatus all > status.log
? wicked show-config > configs.log
? journalctl -b -o short-iso > wicked.log
Thank you.
P.S. If you are willing to re-test with wicked 0.6.1, I can provide you
with the RPMs. Just tell me...
--
Best Regards,
Pawel Wieczorkiewicz , Linux System Developer
SUSE LINUX Products GmbH
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG
N?rnberg) Maxfeldstr. 5 / D-90409 N?rnberg / Phone: +49-911-740 53 - 613
_____________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From uwedr at suse.com Tue Sep 2 11:50:47 2014
From: uwedr at suse.com (Uwe Drechsel)
Date: Tue, 2 Sep 2014 19:50:47 +0200
Subject: [sles-beta] SLES 12 rc 1 iso download
In-Reply-To:
References:
Message-ID: <20140902175047.GE5019@suse.com>
On Tue, Sep 02, Stephan Kurth wrote:
> Hello.
>
> Is it possible that I could get the link to download the iso again?
>
http://download.novell.com/Download?buildid=Uhn2fg6VMyk~
Uwe
--
Uwe Drechsel
Project Manager
SUSE Linux Products GmbH
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
From gjn at gjn.priv.at Wed Sep 3 02:47:57 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Wed, 03 Sep 2014 10:47:57 +0200
Subject: [sles-beta] kerberos config with auth-server
Message-ID: <1922962.tVOxx6uXip@gjn.priv.at>
Hello,
can any tell me what the YaSt module read for the configuration?
I have a problem with the krb5 config?
My Princip?al kadmin/.........com at XXX.XXX have the wrong hostname.
The internal Name from the Serevr ........prv
Is this from the Certificate?
Then I have to change the Certificate.
Now i have altname ....com and subaltname .........prv
Thanks,
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From gjn at gjn.priv.at Wed Sep 3 16:16:33 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Thu, 04 Sep 2014 00:16:33 +0200
Subject: [sles-beta] SLES 12 Server Broken
Message-ID: <1428714.YUH85Ua6Ov@gjn.priv.at>
Hello,
it is not possible to connect to the SLES 12 server.
Zypper say no https:// possible.
Can any repair this Problem ?
Thank's
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From gjn at gjn.priv.at Thu Sep 4 02:17:20 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Thu, 04 Sep 2014 10:17:20 +0200
Subject: [sles-beta] Zypper and a broken Uplink
Message-ID: <26113437.EfZtUrLRDH@gjn.priv.at>
Hello,
is this a good Idea when it is not possible to install a packet from the iso
when the Uplink is broken.
Yesterday the Uplink was broken and I have to install a packet to configure
sssd this is not possible. the iso is integrated in repositorys.
OK, I don't change the Priority ?
But the only way to install is extract the rpm Packet and install it with "rpm
-Uhv XXX"
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From lmb at suse.com Thu Sep 4 02:22:49 2014
From: lmb at suse.com (Lars Marowsky-Bree)
Date: Thu, 4 Sep 2014 10:22:49 +0200
Subject: [sles-beta] Zypper and a broken Uplink
In-Reply-To: <26113437.EfZtUrLRDH@gjn.priv.at>
References: <26113437.EfZtUrLRDH@gjn.priv.at>
Message-ID: <20140904082249.GB2642@suse.de>
On 2014-09-04T10:17:20, "G?nther J. Niederwimmer" wrote:
> Hello,
>
> is this a good Idea when it is not possible to install a packet from the iso
> when the Uplink is broken.
>
> Yesterday the Uplink was broken and I have to install a packet to configure
> sssd this is not possible. the iso is integrated in repositorys.
>
> OK, I don't change the Priority ?
>
> But the only way to install is extract the rpm Packet and install it with "rpm
> -Uhv XXX"
What command were you running exactly and what error message did you
get?
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 21284 (AG N?rnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
From jreidinger at suse.com Thu Sep 4 02:24:33 2014
From: jreidinger at suse.com (Josef Reidinger)
Date: Thu, 4 Sep 2014 10:24:33 +0200
Subject: [sles-beta] Zypper and a broken Uplink
In-Reply-To: <26113437.EfZtUrLRDH@gjn.priv.at>
References: <26113437.EfZtUrLRDH@gjn.priv.at>
Message-ID: <20140904102433.4ea44309@dhcp150.suse.cz>
On Thu, 04 Sep 2014 10:17:20 +0200
"G?nther J.Niederwimmer" wrote:
> Hello,
>
> is this a good Idea when it is not possible to install a packet from
> the iso when the Uplink is broken.
>
> Yesterday the Uplink was broken and I have to install a packet to
> configure sssd this is not possible. the iso is integrated in
> repositorys.
>
> OK, I don't change the Priority ?
>
> But the only way to install is extract the rpm Packet and install it
> with "rpm -Uhv XXX"
>
Hi G?nther,
in this case zypper have powerful ability to disable all remote
repositories:
zypper modifyrepo --disable --remote
This way it just disable all remote repositories, so you can install
from local one and when you link is up again you can simple enable it
with
zypper modifyrepo --enable --remote
Hope that it helps.
Josef
From gjn at gjn.priv.at Thu Sep 4 03:48:58 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Thu, 04 Sep 2014 11:48:58 +0200
Subject: [sles-beta] Zypper and a broken Uplink
In-Reply-To: <20140904082249.GB2642@suse.de>
References: <26113437.EfZtUrLRDH@gjn.priv.at> <20140904082249.GB2642@suse.de>
Message-ID: <1724982.0Gj5YBEU8B@gjn.priv.at>
Hello,
Am Donnerstag, 4. September 2014, 10:22:49 schrieb Lars Marowsky-Bree:
> On 2014-09-04T10:17:20, "G?nther J. Niederwimmer" wrote:
> > Hello,
> >
> > is this a good Idea when it is not possible to install a packet from the
> > iso when the Uplink is broken.
> >
> > Yesterday the Uplink was broken and I have to install a packet to
> > configure
> > sssd this is not possible. the iso is integrated in repositorys.
> >
> > OK, I don't change the Priority ?
> >
> > But the only way to install is extract the rpm Packet and install it with
> > "rpm -Uhv XXX"
>
> What command were you running exactly and what error message did you
> get?
i put in
zypper in sssd-krb5
Today I have also Problems with zypper, a reregister make no change.
The Error is the same then yesterday
zypper up
Dienst 'SUSE_Linux_Enterprise_Server_12_x86_64' wird aktualisiert.
Fehler beim Download (curl) f?r
'https://nu.novell.com/SUSE:/Products:/SLE-12/images/repo/SLE-12-module-adv-systems-management-POOL-x86_64-Media1/repodata/repomd.xml?da6d00302e67952da50f3370302a77a0091ad24b90cff67fe954254b6a818bf3f31d45f227c54710cd02337704bf11':
Fehlercode: ' Bad URL'
Fehlermeldung: 'Protocol http not supported or disabled in libcurl'
Abbrechen, wiederholen, ignorieren? [a/w/i/? zeigt alle Optionen] (a):
and so on
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From trenn at suse.de Thu Sep 4 03:39:38 2014
From: trenn at suse.de (Thomas Renninger)
Date: Thu, 04 Sep 2014 11:39:38 +0200
Subject: [sles-beta] DMESG error
In-Reply-To: <6B6D440AC88B9D4BA615C54243DD03478A8CFC0E@gbtmail03.gigabyte.intra>
References: <6B6D440AC88B9D4BA615C54243DD03478A8CFC0E@gbtmail03.gigabyte.intra>
Message-ID: <1504660.nOHHVA4YfP@d46>
On Monday, August 25, 2014 07:54:00 AM tom.su wrote:
> Hi All,
> Does anyone know, what is happen in below issues? Thank you.
>
> 1.acpi PNP0A03:02: ACPI _OSC support notification failed, disabling PCIe
> ASPM
The ACPI _OSC function is missing or wrongly interpreted, ending up in
ASPM (Active State Power Management for PCIe) being disabled.
This could be intended and it should not make much difference in power
consumption anyway. Just ignore if devices work as expected.
> 2.ioapic: probe of 0000:80:05.4 failed with error -22
I remember a similar bug. There it was that the device in SLE11 does
correctly not show up, but in newer kernels it seem to try to poke
the PCI bus/slot wrongly.
-> Should not that bad (if it isn't something else, but you should see
a PCI device not working then).
> 3.mei_me 0000:00:16.0: initialization failed.
Mei driver is evil, but gets better...
Thomas
From gjn at gjn.priv.at Thu Sep 4 03:55:05 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Thu, 04 Sep 2014 11:55:05 +0200
Subject: [sles-beta] Zypper and a broken Uplink
In-Reply-To: <20140904102433.4ea44309@dhcp150.suse.cz>
References: <26113437.EfZtUrLRDH@gjn.priv.at>
<20140904102433.4ea44309@dhcp150.suse.cz>
Message-ID: <9934026.AKQPVBT61h@gjn.priv.at>
Hello Josef,
Am Donnerstag, 4. September 2014, 10:24:33 schrieb Josef Reidinger:
> On Thu, 04 Sep 2014 10:17:20 +0200
>
> "G?nther J.Niederwimmer" wrote:
> > Hello,
> >
> > is this a good Idea when it is not possible to install a packet from
> > the iso when the Uplink is broken.
> >
> > Yesterday the Uplink was broken and I have to install a packet to
> > configure sssd this is not possible. the iso is integrated in
> > repositorys.
> >
> > OK, I don't change the Priority ?
> >
> > But the only way to install is extract the rpm Packet and install it
> > with "rpm -Uhv XXX"
>
> Hi G?nther,
> in this case zypper have powerful ability to disable all remote
> repositories:
> zypper modifyrepo --disable --remote
>
> This way it just disable all remote repositories, so you can install
> from local one and when you link is up again you can simple enable it
> with
> zypper modifyrepo --enable --remote
>
> Hope that it helps.
Thanks, for this help, I search yesterday ;-) but don't found quickly.
But what is wrong with the Uplink server ??
I mean I make a Update, is this the Problem ?
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From gjn at gjn.priv.at Thu Sep 4 04:07:52 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Thu, 04 Sep 2014 12:07:52 +0200
Subject: [sles-beta] A Problem with KVM Guest ?
Message-ID: <9342276.3cAOVIAMni@gjn.priv.at>
Hello,
I found a Problem with KVM_clock?
on my Installation I have a KVM Server and KVM Clients all SLES 12 Server
The KVM Host have a NTP Server configured and have a correct time
date
Don Sep 4 12:00:19 CEST 2014
all clients have this Time
date
Don Sep 4 02:15:24 CEST 2014
the timezone is correct but the time is wrong ?
OK,I know I can install NTP on the client.
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From aginies at suse.com Thu Sep 4 04:24:02 2014
From: aginies at suse.com (Antoine Ginies)
Date: Thu, 4 Sep 2014 12:24:02 +0200
Subject: [sles-beta] A Problem with KVM Guest ?
In-Reply-To: <9342276.3cAOVIAMni@gjn.priv.at>
References: <9342276.3cAOVIAMni@gjn.priv.at>
Message-ID: <20140904102402.GC3755@linux-w520.guibland.com>
G?nther J. Niederwimmer:
> Hello,
> I found a Problem with KVM_clock?
> on my Installation I have a KVM Server and KVM Clients all SLES 12 Server
> The KVM Host have a NTP Server configured and have a correct time
>
> date
> Don Sep 4 12:00:19 CEST 2014
> all clients have this Time
> date
> Don Sep 4 02:15:24 CEST 2014
>
> the timezone is correct but the time is wrong ?
Hello,
Can you check that your VM is currently using kvm_clock?
-------------
root # cat /sys/devices/system/clocksource/clocksource0/current_clocksource
kvm-clock
------------
> OK,I know I can install NTP on the client.
No, it is not recommened to install an NTP client on the VM guest while
using kvm-clock.
regards.
--
Antoine Ginies
Project Manager
SUSE France
From gjn at gjn.priv.at Thu Sep 4 04:36:08 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Thu, 04 Sep 2014 12:36:08 +0200
Subject: [sles-beta] A Problem with KVM Guest ?
In-Reply-To: <20140904102402.GC3755@linux-w520.guibland.com>
References: <9342276.3cAOVIAMni@gjn.priv.at>
<20140904102402.GC3755@linux-w520.guibland.com>
Message-ID: <6271582.DurtbegMc0@gjn.priv.at>
Am Donnerstag, 4. September 2014, 12:24:02 schrieb Antoine Ginies:
> G?nther J. Niederwimmer:
> > Hello,
> > I found a Problem with KVM_clock?
> > on my Installation I have a KVM Server and KVM Clients all SLES 12 Server
> > The KVM Host have a NTP Server configured and have a correct time
> >
> > date
> > Don Sep 4 12:00:19 CEST 2014
> > all clients have this Time
> > date
> > Don Sep 4 02:15:24 CEST 2014
> >
> > the timezone is correct but the time is wrong ?
>
> Hello,
> Can you check that your VM is currently using kvm_clock?
akerb:~ # dmesg | grep kvm-clock
[ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
[ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, boot clock
[ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, primary cpu clock
[ 0.004000] kvm-clock: cpu 1, msr 1:3ff18041, secondary cpu clock
[ 0.004000] kvm-clock: cpu 2, msr 1:3ff18081, secondary cpu clock
[ 0.004000] kvm-clock: cpu 3, msr 1:3ff180c1, secondary cpu clock
[ 0.134685] Switched to clocksource kvm-clock
This is the client
root# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
I have on the Server
tsc
This is a original YaSt Installation
can I change this manual ?
> ---------
> ------------
>
> > OK,I know I can install NTP on the client.
>
> No, it is not recommened to install an NTP client on the VM guest while
> using kvm-clock.
>
> regards.
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From juwolf at suse.de Thu Sep 4 05:35:15 2014
From: juwolf at suse.de (Julian Wolf)
Date: Thu, 04 Sep 2014 13:35:15 +0200
Subject: [sles-beta] SLES12 x86_64 RC2,
/etc/sysconfig/kernel INITRD_MODULES
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F9D45E9@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F9D45E9@HXMB12.pnet.ch>
Message-ID: <1986990.7ZqZXMj9nK@f48>
Hi.
Am Donnerstag, 4. September 2014, 09:14:36 schrieb urs.frey at post.ch:
>
> IF the method has changed:
> WHERE do I have to define my kernel modules to have them loaded into the
> initrd? Description?
>
I don't know whether or how this configuration file is still used at some point,
but with dracut you should be able to include kernel modules into the initrd
that way:
"If you need a special kernel module in the initramfs, which is not
automatically picked up by dracut, you have the use the --add-drivers option
on the command line or the drivers vaiable in the /etc/dracut.conf or
/etc/dracut.conf.d/myconf.conf configuration file (see dracut.conf(5))"
https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_adding_kernel_modules
Regards, Julian
Julian Wolf, Working student
SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB
16746 (AG N?rnberg)
Maxfeldstr. 5 / D-90409 N?rnberg
From urs.frey at post.ch Thu Sep 4 05:52:23 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Thu, 4 Sep 2014 11:52:23 +0000
Subject: [sles-beta] SLES12 x86_64 RC2,
/etc/sysconfig/kernel INITRD_MODULES
In-Reply-To: <1986990.7ZqZXMj9nK@f48>
References: <40637DBB36AF3941B243A286A432CA0B0F9D45E9@HXMB12.pnet.ch>
<1986990.7ZqZXMj9nK@f48>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F9D4660@HXMB12.pnet.ch>
Hello Julian
Thank you very much.
So I will have a closer look at dracut.conf and the files in /etc/dacut.conf.d
>From my point of view, the sles-admin handbook documentation should be reviewed in context of the issue /etc/sysconfig/kernel file usage
It does not make sense to have a configuration file on the system and in the documentation which is obviously no longer in use
Thanks
Best regards
Urs Frey?????????????????????????????????????????????
Post CH AG
Informationstechnologie
IT Betrieb
Webergutstrasse 12
3030 Bern (Zollikofen)
Telefon : ++41 (0)58 338 58 70
FAX???? : ++41 (0)58 667 30 07
E-Mail:?? urs.frey at post.ch
-----Urspr?ngliche Nachricht-----
Von: Julian Wolf [mailto:juwolf at suse.de]
Gesendet: Thursday, September 04, 2014 1:35 PM
An: Frey Urs, IT222
Cc: sles-beta at lists.suse.com
Betreff: Re: [sles-beta] SLES12 x86_64 RC2, /etc/sysconfig/kernel INITRD_MODULES
Hi.
Am Donnerstag, 4. September 2014, 09:14:36 schrieb urs.frey at post.ch:
>
> IF the method has changed:
> WHERE do I have to define my kernel modules to have them loaded into the
> initrd? Description?
>
I don't know whether or how this configuration file is still used at some point,
but with dracut you should be able to include kernel modules into the initrd
that way:
"If you need a special kernel module in the initramfs, which is not
automatically picked up by dracut, you have the use the --add-drivers option
on the command line or the drivers vaiable in the /etc/dracut.conf or
/etc/dracut.conf.d/myconf.conf configuration file (see dracut.conf(5))"
https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_adding_kernel_modules
Regards, Julian
Julian Wolf, Working student
SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB
16746 (AG N?rnberg)
Maxfeldstr. 5 / D-90409 N?rnberg
From aginies at suse.com Thu Sep 4 05:57:01 2014
From: aginies at suse.com (Antoine Ginies)
Date: Thu, 4 Sep 2014 13:57:01 +0200
Subject: [sles-beta] A Problem with KVM Guest ?
In-Reply-To: <6271582.DurtbegMc0@gjn.priv.at>
References: <9342276.3cAOVIAMni@gjn.priv.at>
<20140904102402.GC3755@linux-w520.guibland.com>
<6271582.DurtbegMc0@gjn.priv.at>
Message-ID: <20140904115701.GD3755@linux-w520.guibland.com>
G?nther J. Niederwimmer:
> Am Donnerstag, 4. September 2014, 12:24:02 schrieb Antoine Ginies:
> > G?nther J. Niederwimmer:
> > > Hello,
> > > I found a Problem with KVM_clock?
> > > on my Installation I have a KVM Server and KVM Clients all SLES 12 Server
> > > The KVM Host have a NTP Server configured and have a correct time
> > >
> > > date
> > > Don Sep 4 12:00:19 CEST 2014
> > > all clients have this Time
> > > date
> > > Don Sep 4 02:15:24 CEST 2014
> > >
> > > the timezone is correct but the time is wrong ?
> >
> > Hello,
> > Can you check that your VM is currently using kvm_clock?
>
> akerb:~ # dmesg | grep kvm-clock
> [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
> [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, boot clock
> [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, primary cpu clock
> [ 0.004000] kvm-clock: cpu 1, msr 1:3ff18041, secondary cpu clock
> [ 0.004000] kvm-clock: cpu 2, msr 1:3ff18081, secondary cpu clock
> [ 0.004000] kvm-clock: cpu 3, msr 1:3ff180c1, secondary cpu clock
> [ 0.134685] Switched to clocksource kvm-clock
>
> This is the client
>
> root# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
You forget the value, but according to dmesg it was kvm-clock at
0.134685 until something else has switched to another value.
------------
root # dmesg | grep clocksource
------------
will let you know if there is any change.
> I have on the Server
> tsc
>
> This is a original YaSt Installation
>
> can I change this manual ?
On VM guest you can change it with echo:
----------
echo tsc > /sys/devices/system/clocksource/clocksource0/current_clocksource
echo kvm-clock > /sys/devices/system/clocksource/clocksource0/current_clocksource
----------
You should see a dmesg in the console of your VM guest saying that
clocksource has switched.
--
Antoine Ginies
Project Manager
SUSE France
From mge at suse.com Thu Sep 4 07:51:02 2014
From: mge at suse.com (Matthias G. Eckermann)
Date: Thu, 4 Sep 2014 15:51:02 +0200
Subject: [sles-beta] SLES12 x86_64 RC2,
/etc/sysconfig/kernel INITRD_MODULES
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F9D4660@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F9D45E9@HXMB12.pnet.ch>
<1986990.7ZqZXMj9nK@f48>
<40637DBB36AF3941B243A286A432CA0B0F9D4660@HXMB12.pnet.ch>
Message-ID: <20140904135102.GA22912@suse.com>
Hello Urs,
please open an SR, thus we can track it.
TIA -
MgE
On 2014-09-04 T 11:52 +0000 urs.frey at post.ch wrote:
> Hello Julian
> Thank you very much.
> So I will have a closer look at dracut.conf and the files in /etc/dacut.conf.d
>
> From my point of view, the sles-admin handbook documentation should be reviewed in context of the issue /etc/sysconfig/kernel file usage
> It does not make sense to have a configuration file on the system and in the documentation which is obviously no longer in use
>
> Thanks
> Best regards
>
> Urs Frey?????????????????????????????????????????????
> Post CH AG
> Informationstechnologie
> IT Betrieb
> Webergutstrasse 12
> 3030 Bern (Zollikofen)
> Telefon : ++41 (0)58 338 58 70
> FAX???? : ++41 (0)58 667 30 07
> E-Mail:?? urs.frey at post.ch
>
> -----Urspr?ngliche Nachricht-----
> Von: Julian Wolf [mailto:juwolf at suse.de]
> Gesendet: Thursday, September 04, 2014 1:35 PM
> An: Frey Urs, IT222
> Cc: sles-beta at lists.suse.com
> Betreff: Re: [sles-beta] SLES12 x86_64 RC2, /etc/sysconfig/kernel INITRD_MODULES
>
> Hi.
>
> Am Donnerstag, 4. September 2014, 09:14:36 schrieb urs.frey at post.ch:
>
> >
> > IF the method has changed:
> > WHERE do I have to define my kernel modules to have them loaded into the
> > initrd? Description?
> >
>
> I don't know whether or how this configuration file is still used at some point,
> but with dracut you should be able to include kernel modules into the initrd
> that way:
>
> "If you need a special kernel module in the initramfs, which is not
> automatically picked up by dracut, you have the use the --add-drivers option
> on the command line or the drivers vaiable in the /etc/dracut.conf or
> /etc/dracut.conf.d/myconf.conf configuration file (see dracut.conf(5))"
>
> https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_adding_kernel_modules
>
> Regards, Julian
>
> Julian Wolf, Working student
> SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB
> 16746 (AG N?rnberg)
> Maxfeldstr. 5 / D-90409 N?rnberg
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
>
--
Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise
SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
From kukuk at suse.de Thu Sep 4 08:00:35 2014
From: kukuk at suse.de (Thorsten Kukuk)
Date: Thu, 4 Sep 2014 16:00:35 +0200
Subject: [sles-beta] SLES12 x86_64 RC2,
/etc/sysconfig/kernel INITRD_MODULES
In-Reply-To: <20140904135102.GA22912@suse.com>
References: <40637DBB36AF3941B243A286A432CA0B0F9D45E9@HXMB12.pnet.ch>
<1986990.7ZqZXMj9nK@f48>
<40637DBB36AF3941B243A286A432CA0B0F9D4660@HXMB12.pnet.ch>
<20140904135102.GA22912@suse.com>
Message-ID: <20140904140035.GA14726@suse.de>
On Thu, Sep 04, Matthias G. Eckermann wrote:
> Hello Urs,
>
> please open an SR, thus we can track it.
No, please don't so.
Thorsten
> On 2014-09-04 T 11:52 +0000 urs.frey at post.ch wrote:
> > Hello Julian
> > Thank you very much.
> > So I will have a closer look at dracut.conf and the files in /etc/dacut.conf.d
> >
> > From my point of view, the sles-admin handbook documentation should be reviewed in context of the issue /etc/sysconfig/kernel file usage
> > It does not make sense to have a configuration file on the system and in the documentation which is obviously no longer in use
> >
> > Thanks
> > Best regards
> >
> > Urs Frey?????????????????????????????????????????????
> > Post CH AG
> > Informationstechnologie
> > IT Betrieb
> > Webergutstrasse 12
> > 3030 Bern (Zollikofen)
> > Telefon : ++41 (0)58 338 58 70
> > FAX???? : ++41 (0)58 667 30 07
> > E-Mail:?? urs.frey at post.ch
> >
> > -----Urspr?ngliche Nachricht-----
> > Von: Julian Wolf [mailto:juwolf at suse.de]
> > Gesendet: Thursday, September 04, 2014 1:35 PM
> > An: Frey Urs, IT222
> > Cc: sles-beta at lists.suse.com
> > Betreff: Re: [sles-beta] SLES12 x86_64 RC2, /etc/sysconfig/kernel INITRD_MODULES
> >
> > Hi.
> >
> > Am Donnerstag, 4. September 2014, 09:14:36 schrieb urs.frey at post.ch:
> >
> > >
> > > IF the method has changed:
> > > WHERE do I have to define my kernel modules to have them loaded into the
> > > initrd? Description?
> > >
> >
> > I don't know whether or how this configuration file is still used at some point,
> > but with dracut you should be able to include kernel modules into the initrd
> > that way:
> >
> > "If you need a special kernel module in the initramfs, which is not
> > automatically picked up by dracut, you have the use the --add-drivers option
> > on the command line or the drivers vaiable in the /etc/dracut.conf or
> > /etc/dracut.conf.d/myconf.conf configuration file (see dracut.conf(5))"
> >
> > https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_adding_kernel_modules
> >
> > Regards, Julian
> >
> > Julian Wolf, Working student
> > SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB
> > 16746 (AG N?rnberg)
> > Maxfeldstr. 5 / D-90409 N?rnberg
> > _______________________________________________
> > sles-beta mailing list
> > sles-beta at lists.suse.com
> > http://lists.suse.com/mailman/listinfo/sles-beta
> >
>
> --
> Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise
> SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
--
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
From urs.frey at post.ch Thu Sep 4 08:06:06 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Thu, 4 Sep 2014 14:06:06 +0000
Subject: [sles-beta] SLES12 x86_64 RC2,
/etc/sysconfig/kernel INITRD_MODULES
In-Reply-To: <20140904140035.GA14726@suse.de>
References: <40637DBB36AF3941B243A286A432CA0B0F9D45E9@HXMB12.pnet.ch>
<1986990.7ZqZXMj9nK@f48>
<40637DBB36AF3941B243A286A432CA0B0F9D4660@HXMB12.pnet.ch>
<20140904135102.GA22912@suse.com> <20140904140035.GA14726@suse.de>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F9D46D5@HXMB12.pnet.ch>
Hi Thorsten
OK, supportconfig cancelled
Best regards
Urs Frey?????????????????????????????????????????????
Post CH AG
Informationstechnologie
IT Betrieb
Webergutstrasse 12
3030 Bern (Zollikofen)
Telefon : ++41 (0)58 338 58 70
FAX???? : ++41 (0)58 667 30 07
E-Mail:?? urs.frey at post.ch
-----Urspr?ngliche Nachricht-----
Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Thorsten Kukuk
Gesendet: Thursday, September 04, 2014 4:01 PM
An: sles-beta at lists.suse.com
Betreff: Re: [sles-beta] SLES12 x86_64 RC2, /etc/sysconfig/kernel INITRD_MODULES
On Thu, Sep 04, Matthias G. Eckermann wrote:
> Hello Urs,
>
> please open an SR, thus we can track it.
No, please don't so.
Thorsten
> On 2014-09-04 T 11:52 +0000 urs.frey at post.ch wrote:
> > Hello Julian
> > Thank you very much.
> > So I will have a closer look at dracut.conf and the files in /etc/dacut.conf.d
> >
> > From my point of view, the sles-admin handbook documentation should be reviewed in context of the issue /etc/sysconfig/kernel file usage
> > It does not make sense to have a configuration file on the system and in the documentation which is obviously no longer in use
> >
> > Thanks
> > Best regards
> >
> > Urs Frey?????????????????????????????????????????????
> > Post CH AG
> > Informationstechnologie
> > IT Betrieb
> > Webergutstrasse 12
> > 3030 Bern (Zollikofen)
> > Telefon : ++41 (0)58 338 58 70
> > FAX???? : ++41 (0)58 667 30 07
> > E-Mail:?? urs.frey at post.ch
> >
> > -----Urspr?ngliche Nachricht-----
> > Von: Julian Wolf [mailto:juwolf at suse.de]
> > Gesendet: Thursday, September 04, 2014 1:35 PM
> > An: Frey Urs, IT222
> > Cc: sles-beta at lists.suse.com
> > Betreff: Re: [sles-beta] SLES12 x86_64 RC2, /etc/sysconfig/kernel INITRD_MODULES
> >
> > Hi.
> >
> > Am Donnerstag, 4. September 2014, 09:14:36 schrieb urs.frey at post.ch:
> >
> > >
> > > IF the method has changed:
> > > WHERE do I have to define my kernel modules to have them loaded into the
> > > initrd? Description?
> > >
> >
> > I don't know whether or how this configuration file is still used at some point,
> > but with dracut you should be able to include kernel modules into the initrd
> > that way:
> >
> > "If you need a special kernel module in the initramfs, which is not
> > automatically picked up by dracut, you have the use the --add-drivers option
> > on the command line or the drivers vaiable in the /etc/dracut.conf or
> > /etc/dracut.conf.d/myconf.conf configuration file (see dracut.conf(5))"
> >
> > https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_adding_kernel_modules
> >
> > Regards, Julian
> >
> > Julian Wolf, Working student
> > SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB
> > 16746 (AG N?rnberg)
> > Maxfeldstr. 5 / D-90409 N?rnberg
> > _______________________________________________
> > sles-beta mailing list
> > sles-beta at lists.suse.com
> > http://lists.suse.com/mailman/listinfo/sles-beta
> >
>
> --
> Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise
> SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
--
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta
From gjn at gjn.priv.at Thu Sep 4 08:08:17 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Thu, 04 Sep 2014 16:08:17 +0200
Subject: [sles-beta] A Problem with KVM Guest ?
In-Reply-To: <20140904115701.GD3755@linux-w520.guibland.com>
References: <9342276.3cAOVIAMni@gjn.priv.at> <6271582.DurtbegMc0@gjn.priv.at>
<20140904115701.GD3755@linux-w520.guibland.com>
Message-ID: <1965493.Q1jz5XN88y@gjn.priv.at>
Am Donnerstag, 4. September 2014, 13:57:01 schrieb Antoine Ginies:
> G?nther J. Niederwimmer:
> > Am Donnerstag, 4. September 2014, 12:24:02 schrieb Antoine Ginies:
> > > G?nther J. Niederwimmer:
> > > > Hello,
> > > > I found a Problem with KVM_clock?
> > > > on my Installation I have a KVM Server and KVM Clients all SLES 12
> > > > Server
> > > > The KVM Host have a NTP Server configured and have a correct time
> > > >
> > > > date
> > > > Don Sep 4 12:00:19 CEST 2014
> > > > all clients have this Time
> > > > date
> > > > Don Sep 4 02:15:24 CEST 2014
> > > >
> > > > the timezone is correct but the time is wrong ?
> > >
> > > Hello,
> > > Can you check that your VM is currently using kvm_clock?
> >
> > akerb:~ # dmesg | grep kvm-clock
> > [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
> > [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, boot clock
> > [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, primary cpu clock
> > [ 0.004000] kvm-clock: cpu 1, msr 1:3ff18041, secondary cpu clock
> > [ 0.004000] kvm-clock: cpu 2, msr 1:3ff18081, secondary cpu clock
> > [ 0.004000] kvm-clock: cpu 3, msr 1:3ff180c1, secondary cpu clock
> > [ 0.134685] Switched to clocksource kvm-clock
> >
> > This is the client
> >
> > root# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
>
> You forget the value, but according to dmesg it was kvm-clock at
> 0.134685 until something else has switched to another value.
I mean we miss understand use
The behind is from a CLIENT
This is from the HOST !!
dmesg | grep clocksource
[ 0.560063] Switched to clocksource hpet
[ 2.329666] tsc: Refined TSC clocksource calibration: 3700.000 MHz
[ 3.645349] Switched to clocksource tsc
and I like to change this for Tests.
> ------------
> root # dmesg | grep clocksource
> ------------
> will let you know if there is any change.
>
> > I have on the Server
> > tsc
> >
> > This is a original YaSt Installation
> >
> > can I change this manual ?
>
> On VM guest you can change it with echo:
> ----------
> echo tsc > /sys/devices/system/clocksource/clocksource0/current_clocksource
> echo kvm-clock >
> /sys/devices/system/clocksource/clocksource0/current_clocksource ----------
>
> You should see a dmesg in the console of your VM guest saying that
> clocksource has switched.
Have I to open a SR ?
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From aginies at suse.com Thu Sep 4 08:23:29 2014
From: aginies at suse.com (Antoine Ginies)
Date: Thu, 4 Sep 2014 16:23:29 +0200
Subject: [sles-beta] A Problem with KVM Guest ?
In-Reply-To: <1965493.Q1jz5XN88y@gjn.priv.at>
References: <9342276.3cAOVIAMni@gjn.priv.at> <6271582.DurtbegMc0@gjn.priv.at>
<20140904115701.GD3755@linux-w520.guibland.com>
<1965493.Q1jz5XN88y@gjn.priv.at>
Message-ID: <20140904142329.GF3755@linux-w520.guibland.com>
G?nther J. Niederwimmer:
> Am Donnerstag, 4. September 2014, 13:57:01 schrieb Antoine Ginies:
> > G?nther J. Niederwimmer:
> > > Am Donnerstag, 4. September 2014, 12:24:02 schrieb Antoine Ginies:
> > > > G?nther J. Niederwimmer:
> > > > > Hello,
> > > > > I found a Problem with KVM_clock?
> > > > > on my Installation I have a KVM Server and KVM Clients all SLES 12
> > > > > Server
> > > > > The KVM Host have a NTP Server configured and have a correct time
> > > > >
> > > > > date
> > > > > Don Sep 4 12:00:19 CEST 2014
> > > > > all clients have this Time
> > > > > date
> > > > > Don Sep 4 02:15:24 CEST 2014
> > > > >
> > > > > the timezone is correct but the time is wrong ?
> > > >
> > > > Hello,
> > > > Can you check that your VM is currently using kvm_clock?
> > >
> > > akerb:~ # dmesg | grep kvm-clock
> > > [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
> > > [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, boot clock
> > > [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, primary cpu clock
> > > [ 0.004000] kvm-clock: cpu 1, msr 1:3ff18041, secondary cpu clock
> > > [ 0.004000] kvm-clock: cpu 2, msr 1:3ff18081, secondary cpu clock
> > > [ 0.004000] kvm-clock: cpu 3, msr 1:3ff180c1, secondary cpu clock
> > > [ 0.134685] Switched to clocksource kvm-clock
> > >
> > > This is the client
> > >
> > > root# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> >
> > You forget the value, but according to dmesg it was kvm-clock at
> > 0.134685 until something else has switched to another value.
>
> I mean we miss understand use
>
> The behind is from a CLIENT
kvm-clock clocksource is for the VM guest.
> This is from the HOST !!
The host doesn't provide kvm-clock source:
-----------------------------------------
root # cat /sys/devices/system/clocksource/clocksource0/available_clocksource
tsc hpet acpi_pm
-----------------------------------------
It's tsc by default.
So everything is ok.
regards.
>
> dmesg | grep clocksource
> [ 0.560063] Switched to clocksource hpet
> [ 2.329666] tsc: Refined TSC clocksource calibration: 3700.000 MHz
> [ 3.645349] Switched to clocksource tsc
>
> and I like to change this for Tests.
> > ------------
> > root # dmesg | grep clocksource
> > ------------
> > will let you know if there is any change.
> >
> > > I have on the Server
> > > tsc
> > >
> > > This is a original YaSt Installation
> > >
> > > can I change this manual ?
> >
> > On VM guest you can change it with echo:
> > ----------
> > echo tsc > /sys/devices/system/clocksource/clocksource0/current_clocksource
> > echo kvm-clock >
> > /sys/devices/system/clocksource/clocksource0/current_clocksource ----------
> >
> > You should see a dmesg in the console of your VM guest saying that
> > clocksource has switched.
>
> Have I to open a SR ?
>
> --
> mit freundlichen Gr??en / best Regards,
>
> G?nther J. Niederwimmer
>
--
Antoine Ginies
Project Manager
SUSE France
From gjn at gjn.priv.at Thu Sep 4 08:35:29 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Thu, 04 Sep 2014 16:35:29 +0200
Subject: [sles-beta] A Problem with KVM Guest ?
In-Reply-To: <20140904142329.GF3755@linux-w520.guibland.com>
References: <9342276.3cAOVIAMni@gjn.priv.at> <1965493.Q1jz5XN88y@gjn.priv.at>
<20140904142329.GF3755@linux-w520.guibland.com>
Message-ID: <2370164.ARCIkxNOyk@gjn.priv.at>
Hello Antoine,
Am Donnerstag, 4. September 2014, 16:23:29 schrieb Antoine Ginies:
> G?nther J. Niederwimmer:
> > Am Donnerstag, 4. September 2014, 13:57:01 schrieb Antoine Ginies:
> > > G?nther J. Niederwimmer:
> > > > Am Donnerstag, 4. September 2014, 12:24:02 schrieb Antoine Ginies:
> > > > > G?nther J. Niederwimmer:
> > > > > > Hello,
> > > > > > I found a Problem with KVM_clock?
> > > > > > on my Installation I have a KVM Server and KVM Clients all SLES 12
> > > > > > Server
> > > > > > The KVM Host have a NTP Server configured and have a correct time
> > > > > >
> > > > > > date
> > > > > > Don Sep 4 12:00:19 CEST 2014
> > > > > > all clients have this Time
> > > > > > date
> > > > > > Don Sep 4 02:15:24 CEST 2014
> > > > > >
> > > > > > the timezone is correct but the time is wrong ?
> > > > >
> > > > > Hello,
> > > > > Can you check that your VM is currently using kvm_clock?
> > > >
> > > > akerb:~ # dmesg | grep kvm-clock
> > > > [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
> > > > [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, boot clock
> > > > [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, primary cpu clock
> > > > [ 0.004000] kvm-clock: cpu 1, msr 1:3ff18041, secondary cpu clock
> > > > [ 0.004000] kvm-clock: cpu 2, msr 1:3ff18081, secondary cpu clock
> > > > [ 0.004000] kvm-clock: cpu 3, msr 1:3ff180c1, secondary cpu clock
> > > > [ 0.134685] Switched to clocksource kvm-clock
> > > >
> > > > This is the client
> > > >
> > > > root# cat
> > > > /sys/devices/system/clocksource/clocksource0/current_clocksource
> > >
> > > You forget the value, but according to dmesg it was kvm-clock at
> > > 0.134685 until something else has switched to another value.
> >
> > I mean we miss understand use
> >
> > The behind is from a CLIENT
>
> kvm-clock clocksource is for the VM guest.
>
> > This is from the HOST !!
>
> The host doesn't provide kvm-clock source:
> -----------------------------------------
> root # cat
> /sys/devices/system/clocksource/clocksource0/available_clocksource tsc hpet
> acpi_pm
> -----------------------------------------
>
> It's tsc by default.
> So everything is ok.
:-))).
why I have then a wrong Time !
anything must be wrong, the question is what?
> > dmesg | grep clocksource
> >
> > [ 0.560063] Switched to clocksource hpet
> > [ 2.329666] tsc: Refined TSC clocksource calibration: 3700.000 MHz
> > [ 3.645349] Switched to clocksource tsc
> >
> > and I like to change this for Tests.
> >
> > > ------------
> > > root # dmesg | grep clocksource
> > > ------------
> > > will let you know if there is any change.
> > >
> > > > I have on the Server
> > > > tsc
> > > >
> > > > This is a original YaSt Installation
> > > >
> > > > can I change this manual ?
> > >
> > > On VM guest you can change it with echo:
> > > ----------
> > > echo tsc >
> > > /sys/devices/system/clocksource/clocksource0/current_clocksource
> > > echo kvm-clock >
> > > /sys/devices/system/clocksource/clocksource0/current_clocksource
> > > ----------
> > >
> > > You should see a dmesg in the console of your VM guest saying that
> > > clocksource has switched.
> >
> > Have I to open a SR ?
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From gjn at gjn.priv.at Thu Sep 4 08:43:50 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Thu, 04 Sep 2014 16:43:50 +0200
Subject: [sles-beta] UPLINK Server no connect
Message-ID: <5735723.cTtDF3qMXY@gjn.priv.at>
Hello,
Is it possible to know what is with the UPLINK Server?
have I a broken Update imported or is this a SUSE Server Problem
Thanks for a answer.
I have to download same SDK Packets
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From aginies at suse.com Thu Sep 4 08:47:23 2014
From: aginies at suse.com (Antoine Ginies)
Date: Thu, 4 Sep 2014 16:47:23 +0200
Subject: [sles-beta] A Problem with KVM Guest ?
In-Reply-To: <2370164.ARCIkxNOyk@gjn.priv.at>
References: <9342276.3cAOVIAMni@gjn.priv.at> <1965493.Q1jz5XN88y@gjn.priv.at>
<20140904142329.GF3755@linux-w520.guibland.com>
<2370164.ARCIkxNOyk@gjn.priv.at>
Message-ID: <20140904144723.GG3755@linux-w520.guibland.com>
G?nther J. Niederwimmer:
> Hello Antoine,
>
> Am Donnerstag, 4. September 2014, 16:23:29 schrieb Antoine Ginies:
> > G?nther J. Niederwimmer:
> > > Am Donnerstag, 4. September 2014, 13:57:01 schrieb Antoine Ginies:
> > > > G?nther J. Niederwimmer:
> > > > > Am Donnerstag, 4. September 2014, 12:24:02 schrieb Antoine Ginies:
> > > > > > G?nther J. Niederwimmer:
> > > > > > > Hello,
> > > > > > > I found a Problem with KVM_clock?
> > > > > > > on my Installation I have a KVM Server and KVM Clients all SLES 12
> > > > > > > Server
> > > > > > > The KVM Host have a NTP Server configured and have a correct time
> > > > > > >
> > > > > > > date
> > > > > > > Don Sep 4 12:00:19 CEST 2014
> > > > > > > all clients have this Time
> > > > > > > date
> > > > > > > Don Sep 4 02:15:24 CEST 2014
> > > > > > >
> > > > > > > the timezone is correct but the time is wrong ?
> > > > > >
> > > > > > Hello,
> > > > > > Can you check that your VM is currently using kvm_clock?
> > > > >
> > > > > akerb:~ # dmesg | grep kvm-clock
> > > > > [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
> > > > > [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, boot clock
> > > > > [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, primary cpu clock
> > > > > [ 0.004000] kvm-clock: cpu 1, msr 1:3ff18041, secondary cpu clock
> > > > > [ 0.004000] kvm-clock: cpu 2, msr 1:3ff18081, secondary cpu clock
> > > > > [ 0.004000] kvm-clock: cpu 3, msr 1:3ff180c1, secondary cpu clock
> > > > > [ 0.134685] Switched to clocksource kvm-clock
> > > > >
> > > > > This is the client
> > > > >
> > > > > root# cat
> > > > > /sys/devices/system/clocksource/clocksource0/current_clocksource
> > > >
> > > > You forget the value, but according to dmesg it was kvm-clock at
> > > > 0.134685 until something else has switched to another value.
> > >
> > > I mean we miss understand use
> > >
> > > The behind is from a CLIENT
> >
> > kvm-clock clocksource is for the VM guest.
> >
> > > This is from the HOST !!
> >
> > The host doesn't provide kvm-clock source:
> > -----------------------------------------
> > root # cat
> > /sys/devices/system/clocksource/clocksource0/available_clocksource tsc hpet
> > acpi_pm
> > -----------------------------------------
> >
> > It's tsc by default.
> > So everything is ok.
>
> :-))).
> why I have then a wrong Time !
Perhaps the ntpd service was not started on the host before the VM guest start?
have you tried to start the ntpd server on the host, then
start a VM guest and check if time are synchronized?
>
> anything must be wrong, the question is what?
>
> > > dmesg | grep clocksource
> > >
> > > [ 0.560063] Switched to clocksource hpet
> > > [ 2.329666] tsc: Refined TSC clocksource calibration: 3700.000 MHz
> > > [ 3.645349] Switched to clocksource tsc
> > >
> > > and I like to change this for Tests.
> > >
> > > > ------------
> > > > root # dmesg | grep clocksource
> > > > ------------
> > > > will let you know if there is any change.
> > > >
> > > > > I have on the Server
> > > > > tsc
> > > > >
> > > > > This is a original YaSt Installation
> > > > >
> > > > > can I change this manual ?
> > > >
> > > > On VM guest you can change it with echo:
> > > > ----------
> > > > echo tsc >
> > > > /sys/devices/system/clocksource/clocksource0/current_clocksource
> > > > echo kvm-clock >
> > > > /sys/devices/system/clocksource/clocksource0/current_clocksource
> > > > ----------
> > > >
> > > > You should see a dmesg in the console of your VM guest saying that
> > > > clocksource has switched.
> > >
> > > Have I to open a SR ?
>
> --
> mit freundlichen Gr??en / best Regards,
>
> G?nther J. Niederwimmer
>
--
Antoine Ginies
Project Manager
SUSE France
From meissner at suse.de Thu Sep 4 08:48:32 2014
From: meissner at suse.de (Marcus Meissner)
Date: Thu, 4 Sep 2014 16:48:32 +0200
Subject: [sles-beta] UPLINK Server no connect
In-Reply-To: <5735723.cTtDF3qMXY@gjn.priv.at>
References: <5735723.cTtDF3qMXY@gjn.priv.at>
Message-ID: <20140904144832.GP13725@suse.de>
On Thu, Sep 04, 2014 at 04:43:50PM +0200, G?nther J. Niederwimmer wrote:
> Hello,
>
> Is it possible to know what is with the UPLINK Server?
>
> have I a broken Update imported or is this a SUSE Server Problem
>
> Thanks for a answer.
>
> I have to download same SDK Packets
What error message do you get and where?
Ciao, Marcus
From gjn at gjn.priv.at Thu Sep 4 09:08:30 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Thu, 04 Sep 2014 17:08:30 +0200
Subject: [sles-beta] A Problem with KVM Guest ?
In-Reply-To: <20140904144723.GG3755@linux-w520.guibland.com>
References: <9342276.3cAOVIAMni@gjn.priv.at> <2370164.ARCIkxNOyk@gjn.priv.at>
<20140904144723.GG3755@linux-w520.guibland.com>
Message-ID: <2508821.N5cP5OUrh5@gjn.priv.at>
Am Donnerstag, 4. September 2014, 16:47:23 schrieb Antoine Ginies:
> G?nther J. Niederwimmer:
> > Hello Antoine,
> >
> > Am Donnerstag, 4. September 2014, 16:23:29 schrieb Antoine Ginies:
> > > G?nther J. Niederwimmer:
> > > > Am Donnerstag, 4. September 2014, 13:57:01 schrieb Antoine Ginies:
> > > > > G?nther J. Niederwimmer:
> > > > > > Am Donnerstag, 4. September 2014, 12:24:02 schrieb Antoine Ginies:
> > > > > > > G?nther J. Niederwimmer:
> > > > > > > > Hello,
> > > > > > > > I found a Problem with KVM_clock?
> > > > > > > > on my Installation I have a KVM Server and KVM Clients all
> > > > > > > > SLES 12
> > > > > > > > Server
> > > > > > > > The KVM Host have a NTP Server configured and have a correct
> > > > > > > > time
> > > > > > > >
> > > > > > > > date
> > > > > > > > Don Sep 4 12:00:19 CEST 2014
> > > > > > > > all clients have this Time
> > > > > > > > date
> > > > > > > > Don Sep 4 02:15:24 CEST 2014
> > > > > > > >
> > > > > > > > the timezone is correct but the time is wrong ?
> > > > > > >
> > > > > > > Hello,
> > > > > > > Can you check that your VM is currently using kvm_clock?
> > > > > >
> > > > > > akerb:~ # dmesg | grep kvm-clock
> > > > > > [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
> > > > > > [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, boot clock
> > > > > > [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, primary cpu clock
> > > > > > [ 0.004000] kvm-clock: cpu 1, msr 1:3ff18041, secondary cpu
> > > > > > clock
> > > > > > [ 0.004000] kvm-clock: cpu 2, msr 1:3ff18081, secondary cpu
> > > > > > clock
> > > > > > [ 0.004000] kvm-clock: cpu 3, msr 1:3ff180c1, secondary cpu
> > > > > > clock
> > > > > > [ 0.134685] Switched to clocksource kvm-clock
> > > > > >
> > > > > > This is the client
> > > > > >
> > > > > > root# cat
> > > > > > /sys/devices/system/clocksource/clocksource0/current_clocksource
> > > > >
> > > > > You forget the value, but according to dmesg it was kvm-clock at
> > > > > 0.134685 until something else has switched to another value.
> > > >
> > > > I mean we miss understand use
> > > >
> > > > The behind is from a CLIENT
> > >
> > > kvm-clock clocksource is for the VM guest.
> > >
> > > > This is from the HOST !!
> > >
> > > The host doesn't provide kvm-clock source:
> > > -----------------------------------------
> > > root # cat
> > > /sys/devices/system/clocksource/clocksource0/available_clocksource tsc
> > > hpet
> > > acpi_pm
> > > -----------------------------------------
> > >
> > > It's tsc by default.
> > > So everything is ok.
> > :
> > :-))).
> >
> > why I have then a wrong Time !
>
> Perhaps the ntpd service was not started on the host before the VM guest
> start? have you tried to start the ntpd server on the host, then
> start a VM guest and check if time are synchronized?
Yes, you are right, this is the Problem, NTP Server is starting to late for
the VM clients
always this Problems with systemd :-(.
Now I have to check what can I do, a kerberos test in the moment is not the
best Timing ;-)
Thanks, I hope you find a way to clear this Problem.
Thanks again.
> > anything must be wrong, the question is what?
> >
> > > > dmesg | grep clocksource
> > > >
> > > > [ 0.560063] Switched to clocksource hpet
> > > > [ 2.329666] tsc: Refined TSC clocksource calibration: 3700.000 MHz
> > > > [ 3.645349] Switched to clocksource tsc
> > > >
> > > > and I like to change this for Tests.
> > > >
> > > > > ------------
> > > > > root # dmesg | grep clocksource
> > > > > ------------
> > > > > will let you know if there is any change.
> > > > >
> > > > > > I have on the Server
> > > > > > tsc
> > > > > >
> > > > > > This is a original YaSt Installation
> > > > > >
> > > > > > can I change this manual ?
> > > > >
> > > > > On VM guest you can change it with echo:
> > > > > ----------
> > > > > echo tsc >
> > > > > /sys/devices/system/clocksource/clocksource0/current_clocksource
> > > > > echo kvm-clock >
> > > > > /sys/devices/system/clocksource/clocksource0/current_clocksource
> > > > > ----------
> > > > >
> > > > > You should see a dmesg in the console of your VM guest saying that
> > > > > clocksource has switched.
> > > >
> > > > Have I to open a SR ?
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From meissner at suse.de Thu Sep 4 09:29:20 2014
From: meissner at suse.de (Marcus Meissner)
Date: Thu, 4 Sep 2014 17:29:20 +0200
Subject: [sles-beta] UPLINK Server no connect
In-Reply-To: <20140904144832.GP13725@suse.de>
References: <5735723.cTtDF3qMXY@gjn.priv.at> <20140904144832.GP13725@suse.de>
Message-ID: <20140904152920.GQ13725@suse.de>
On Thu, Sep 04, 2014 at 04:48:32PM +0200, Marcus Meissner wrote:
> On Thu, Sep 04, 2014 at 04:43:50PM +0200, G?nther J. Niederwimmer wrote:
> > Hello,
> >
> > Is it possible to know what is with the UPLINK Server?
> >
> > have I a broken Update imported or is this a SUSE Server Problem
> >
> > Thanks for a answer.
> >
> > I have to download same SDK Packets
>
> What error message do you get and where?
Apparently something at SUSE is broken, we are trying to find out.
SCC is also still a bit in Beta ;)
Ciao, Marcus
From gjn at gjn.priv.at Thu Sep 4 09:38:42 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Thu, 04 Sep 2014 17:38:42 +0200
Subject: [sles-beta] UPLINK Server no connect
In-Reply-To: <20140904152920.GQ13725@suse.de>
References: <5735723.cTtDF3qMXY@gjn.priv.at> <20140904144832.GP13725@suse.de>
<20140904152920.GQ13725@suse.de>
Message-ID: <1970970.sghYlp3dDk@gjn.priv.at>
Hello Marcus,
Am Donnerstag, 4. September 2014, 17:29:20 schrieb Marcus Meissner:
> On Thu, Sep 04, 2014 at 04:48:32PM +0200, Marcus Meissner wrote:
> > On Thu, Sep 04, 2014 at 04:43:50PM +0200, G?nther J. Niederwimmer wrote:
> > > Hello,
> > >
> > > Is it possible to know what is with the UPLINK Server?
> > >
> > > have I a broken Update imported or is this a SUSE Server Problem
> > >
> > > Thanks for a answer.
> > >
> > > I have to download same SDK Packets
> >
> > What error message do you get and where?
Fehler beim Download (curl) f?r
'https://nu.novell.com/SUSE:/Products:/SLE-12/images/repo/SLE-12-Server-POOL-x86_64-Media1/repodata/repomd.xml?da6d00302e67952da50f3370302a77a0091ad24b90cff67fe95425446a8081f3282fc6a75985c20b657e11f67c1c08':
Fehlercode: ' Bad URL'
Fehlermeldung: 'Protocol http not supported or disabled in libcurl'
Abbrechen, wiederholen, ignorieren? [a/w/i/? zeigt alle Optionen] (a): a
> Apparently something at SUSE is broken, we are trying to find out.
>
> SCC is also still a bit in Beta ;)
Thanks for this answer, this is now clear and I don't have to search on my
system.
Thanks.
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From msvec at suse.com Thu Sep 4 09:47:28 2014
From: msvec at suse.com (Michal Svec)
Date: Thu, 4 Sep 2014 17:47:28 +0200 (CEST)
Subject: [sles-beta] A Problem with KVM Guest ?
In-Reply-To: <2508821.N5cP5OUrh5@gjn.priv.at>
References: <9342276.3cAOVIAMni@gjn.priv.at> <2370164.ARCIkxNOyk@gjn.priv.at>
<20140904144723.GG3755@linux-w520.guibland.com>
<2508821.N5cP5OUrh5@gjn.priv.at>
Message-ID:
On Thu, 4 Sep 2014, G?nther J. Niederwimmer wrote:
> Am Donnerstag, 4. September 2014, 16:47:23 schrieb Antoine Ginies:
>> G?nther J. Niederwimmer:
>>> Hello Antoine,
>>>
>>> Am Donnerstag, 4. September 2014, 16:23:29 schrieb Antoine Ginies:
>>>> G?nther J. Niederwimmer:
>>>>> Am Donnerstag, 4. September 2014, 13:57:01 schrieb Antoine Ginies:
>>>>>> G?nther J. Niederwimmer:
>>>>>>> Am Donnerstag, 4. September 2014, 12:24:02 schrieb Antoine Ginies:
>>>>>>>> G?nther J. Niederwimmer:
>>>>>>>>> Hello,
>>>>>>>>> I found a Problem with KVM_clock?
>>>>>>>>> on my Installation I have a KVM Server and KVM Clients all
>>>>>>>>> SLES 12
>>>>>>>>> Server
>>>>>>>>> The KVM Host have a NTP Server configured and have a correct
>>>>>>>>> time
>>>>>>>>>
>>>>>>>>> date
>>>>>>>>> Don Sep 4 12:00:19 CEST 2014
>>>>>>>>> all clients have this Time
>>>>>>>>> date
>>>>>>>>> Don Sep 4 02:15:24 CEST 2014
>>>>>>>>>
>>>>>>>>> the timezone is correct but the time is wrong ?
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>> Can you check that your VM is currently using kvm_clock?
>>>>>>>
>>>>>>> akerb:~ # dmesg | grep kvm-clock
>>>>>>> [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
>>>>>>> [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, boot clock
>>>>>>> [ 0.000000] kvm-clock: cpu 0, msr 1:3ff18001, primary cpu clock
>>>>>>> [ 0.004000] kvm-clock: cpu 1, msr 1:3ff18041, secondary cpu
>>>>>>> clock
>>>>>>> [ 0.004000] kvm-clock: cpu 2, msr 1:3ff18081, secondary cpu
>>>>>>> clock
>>>>>>> [ 0.004000] kvm-clock: cpu 3, msr 1:3ff180c1, secondary cpu
>>>>>>> clock
>>>>>>> [ 0.134685] Switched to clocksource kvm-clock
>>>>>>>
>>>>>>> This is the client
>>>>>>>
>>>>>>> root# cat
>>>>>>> /sys/devices/system/clocksource/clocksource0/current_clocksource
>>>>>>
>>>>>> You forget the value, but according to dmesg it was kvm-clock at
>>>>>> 0.134685 until something else has switched to another value.
>>>>>
>>>>> I mean we miss understand use
>>>>>
>>>>> The behind is from a CLIENT
>>>>
>>>> kvm-clock clocksource is for the VM guest.
>>>>
>>>>> This is from the HOST !!
>>>>
>>>> The host doesn't provide kvm-clock source:
>>>> -----------------------------------------
>>>> root # cat
>>>> /sys/devices/system/clocksource/clocksource0/available_clocksource tsc
>>>> hpet
>>>> acpi_pm
>>>> -----------------------------------------
>>>>
>>>> It's tsc by default.
>>>> So everything is ok.
>>> :
>>> :-))).
>>>
>>> why I have then a wrong Time !
>>
>> Perhaps the ntpd service was not started on the host before the VM guest
>> start? have you tried to start the ntpd server on the host, then
>> start a VM guest and check if time are synchronized?
>
> Yes, you are right, this is the Problem, NTP Server is starting to late for
> the VM clients
>
> always this Problems with systemd :-(.
>
> Now I have to check what can I do, a kerberos test in the moment is not the
> best Timing ;-)
>
> Thanks, I hope you find a way to clear this Problem.
This indeed sounds like a bug (in boot order dependencies), please open a
Service Request and we will have a look at a fix.
Thanks!
Michal
> Thanks again.
>
>>> anything must be wrong, the question is what?
>>>
>>>>> dmesg | grep clocksource
>>>>>
>>>>> [ 0.560063] Switched to clocksource hpet
>>>>> [ 2.329666] tsc: Refined TSC clocksource calibration: 3700.000 MHz
>>>>> [ 3.645349] Switched to clocksource tsc
>>>>>
>>>>> and I like to change this for Tests.
>>>>>
>>>>>> ------------
>>>>>> root # dmesg | grep clocksource
>>>>>> ------------
>>>>>> will let you know if there is any change.
>>>>>>
>>>>>>> I have on the Server
>>>>>>> tsc
>>>>>>>
>>>>>>> This is a original YaSt Installation
>>>>>>>
>>>>>>> can I change this manual ?
>>>>>>
>>>>>> On VM guest you can change it with echo:
>>>>>> ----------
>>>>>> echo tsc >
>>>>>> /sys/devices/system/clocksource/clocksource0/current_clocksource
>>>>>> echo kvm-clock >
>>>>>> /sys/devices/system/clocksource/clocksource0/current_clocksource
>>>>>> ----------
>>>>>>
>>>>>> You should see a dmesg in the console of your VM guest saying that
>>>>>> clocksource has switched.
>>>>>
>>>>> Have I to open a SR ?
>
> --
> mit freundlichen Gr??en / best Regards,
>
> G?nther J. Niederwimmer
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
>
From tparker at cbnco.com Thu Sep 4 13:37:50 2014
From: tparker at cbnco.com (Tom Parker)
Date: Thu, 4 Sep 2014 15:37:50 -0400
Subject: [sles-beta] Network Interfaces change name between install and
first boot
Message-ID: <5408BF8E.8090606@cbnco.com>
Hello
We are doing some RC2 testing with booting servers using /boot on
microSD cards and / on iscsi with software initiators.
We have run into problems today on our test PC that has 1 onboard nic
and 1 PCI nic with 4 ports. During the installation process the onboard
nic appears as eth3 but after the first reboot it is eth0.
This is obviously causing havoc with the network setup as dracut is
setting up the wrong interface on first boot and / is not found.
Should I submit an SR for this?
Tom
From darrent at akurit.com.au Thu Sep 4 15:24:44 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Fri, 5 Sep 2014 07:24:44 +1000
Subject: [sles-beta] Network Interfaces change name between install and
first boot
In-Reply-To: <5408BF8E.8090606@cbnco.com>
References: <5408BF8E.8090606@cbnco.com>
Message-ID:
Tom/team
Is this a case where the "ugly but constant" port naming scheme may be more
useful than the more traditional eth(X) port names?
Darren
Darren Thompson
Professional Services Engineer / Consultant
*[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*
Level 3, 60 City Road
Southgate, VIC 3006
Mb: 0400 640 414
Mail: darrent at akurit.com.au
Web: www.akurit.com.au
On 5 September 2014 05:37, Tom Parker wrote:
> Hello
>
> We are doing some RC2 testing with booting servers using /boot on
> microSD cards and / on iscsi with software initiators.
>
> We have run into problems today on our test PC that has 1 onboard nic
> and 1 PCI nic with 4 ports. During the installation process the onboard
> nic appears as eth3 but after the first reboot it is eth0.
>
> This is obviously causing havoc with the network setup as dracut is
> setting up the wrong interface on first boot and / is not found.
>
> Should I submit an SR for this?
>
> Tom
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL:
From gsu at axway.com Thu Sep 4 16:07:57 2014
From: gsu at axway.com (Guang Su)
Date: Thu, 4 Sep 2014 22:07:57 +0000
Subject: [sles-beta] RC2 PXE imaging error
Message-ID:
Hi,
I tried SLES12 RC2 PXE installation on Dell PowerEdge R620 server and saw this YaST error. Has anyone seen this error before? I did not see this issue in beta testing. See attached y2log from the server.
[cid:image001.png at 01CFC851.B8CE0790]
Thanks
--Guang
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 17164 bytes
Desc: image001.png
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: y2log
Type: application/octet-stream
Size: 163978 bytes
Desc: y2log
URL:
From darrent at akurit.com.au Thu Sep 4 17:44:12 2014
From: darrent at akurit.com.au (Darren Thompson)
Date: Fri, 5 Sep 2014 09:44:12 +1000
Subject: [sles-beta] Network Interfaces change name between install and
first boot
In-Reply-To: <90308142-AEDD-4753-B03F-F75039B61114@ricis.com>
References: <5408BF8E.8090606@cbnco.com>
<90308142-AEDD-4753-B03F-F75039B61114@ricis.com>
Message-ID:
Gregory/Team
This would have been my preference also: "Maybe the older style Ethernet
ethx names could become default aliases of the hardware specific names."
I was advised that it was not possible to do, but did not investigate it
myself.
Perhaps some clever crafting of "udev" rules could achieve the same, even
as a "post install" process.
Darren
Darren Thompson
Professional Services Engineer / Consultant
*[image: cid:image001.jpg at 01CB7C0C.6C6A2AE0]*
Level 3, 60 City Road
Southgate, VIC 3006
Mb: 0400 640 414
Mail: darrent at akurit.com.au
Web: www.akurit.com.au
On 5 September 2014 09:05, Gregory D. Rosenberg wrote:
> Darren,
>
> I agree, but I think have an alias name for local use would be good. That
> way it would make it easier on admins at the command promote. Maybe the
> older style Ethernet ethx names could become default aliases of the
> hardware specific names.
>
> On Sep 4, 2014, at 16:24 CDT, Darren Thompson
> wrote:
>
> Tom/team
>
> Is this a case where the "ugly but constant" port naming scheme may be
> more useful than the more traditional eth(X) port names?
>
> Darren
>
> Darren Thompson
>
> Professional Services Engineer / Consultant
>
> **
>
> Level 3, 60 City Road
>
> Southgate, VIC 3006
>
> Mb: 0400 640 414
>
> Mail: darrent at akurit.com.au
> Web: www.akurit.com.au
>
>
>
> On 5 September 2014 05:37, Tom Parker wrote:
>
>> Hello
>>
>> We are doing some RC2 testing with booting servers using /boot on
>> microSD cards and / on iscsi with software initiators.
>>
>> We have run into problems today on our test PC that has 1 onboard nic
>> and 1 PCI nic with 4 ports. During the installation process the onboard
>> nic appears as eth3 but after the first reboot it is eth0.
>>
>> This is obviously causing havoc with the network setup as dracut is
>> setting up the wrong interface on first boot and / is not found.
>>
>> Should I submit an SR for this?
>>
>> Tom
>> _______________________________________________
>> sles-beta mailing list
>> sles-beta at lists.suse.com
>> http://lists.suse.com/mailman/listinfo/sles-beta
>>
>
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
>
>
>
>
> P.S. Text the word BLIND to 85944 to donate $10 to the NFB Imagination
> Fund via your phone bill.
>
> The National Federation of the Blind knows that blindness is not the
> characteristic that defines you or your future. Every day we raise the
> expectations of blind people, because low expectations create obstacles
> between blind people and our dreams. You can have the life you want;
> blindness is not what holds you back.
>
> --
> 73' & 75'
> Gregory D. Rosenberg AB9MZ
> gregg at ricis.com
>
> RICIS, Inc.
> 7849 Bristol Park Drive
> Tinley Park, IL 60477-4594
> http://www.ricis.com
>
> 708-267-6664 Cell
> 708-444-2690 Office
> 708-444-1115 Fax
> (Please call before sending a fax)
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL:
From jreidinger at suse.com Fri Sep 5 01:33:22 2014
From: jreidinger at suse.com (Josef Reidinger)
Date: Fri, 5 Sep 2014 09:33:22 +0200
Subject: [sles-beta] RC2 PXE imaging error
In-Reply-To:
References:
Message-ID: <20140905093322.007e6adb@linux-5mqx.site>
On Thu, 4 Sep 2014 22:07:57 +0000
"Guang Su" wrote:
> Hi,
>
> I tried SLES12 RC2 PXE installation on Dell PowerEdge R620 server and
> saw this YaST error. Has anyone seen this error before? I did not see
> this issue in beta testing. See attached y2log from the server.
> [cid:image001.png at 01CFC851.B8CE0790]
>
> Thanks
>
> --Guang
Hi Guang,
this error said that yast have problem to find any product in
installation repository. I see you use PXE boot, what repository do you
use as base for such installation?
Josef
From kukuk at suse.de Fri Sep 5 02:57:46 2014
From: kukuk at suse.de (Thorsten Kukuk)
Date: Fri, 5 Sep 2014 10:57:46 +0200
Subject: [sles-beta] UPLINK Server no connect
In-Reply-To: <1970970.sghYlp3dDk@gjn.priv.at>
References: <5735723.cTtDF3qMXY@gjn.priv.at> <20140904144832.GP13725@suse.de>
<20140904152920.GQ13725@suse.de> <1970970.sghYlp3dDk@gjn.priv.at>
Message-ID: <20140905085746.GA7140@suse.de>
On Thu, Sep 04, G?nther J. Niederwimmer wrote:
> > SCC is also still a bit in Beta ;)
>
> Thanks for this answer, this is now clear and I don't have to search on my
> system.
Should work again, at least it does for me.
But the current setup was/is only temporary to let us internal
test the release of patches. You should not plan to have always
access to the online channels until the release of SLES12.
Thorsten
--
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
From gjn at gjn.priv.at Fri Sep 5 02:58:47 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Fri, 05 Sep 2014 10:58:47 +0200
Subject: [sles-beta] snapper Problem
Message-ID: <140999116.HM1P8Z7HZp@gjn.priv.at>
Hello,
can any tell me the new way to activate snapper after the installation?
On some of my Clients snapper is not activated automatic by the installation?
Btrfs File system installed, one of old Bugs I reported.
But I mean before RC2 we have in the btrfs config Window a Icon to activate
snapper, this is now missing ?
Or is this now on a other Place and I cant find it,
Thanks for a answer.
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From kukuk at suse.de Fri Sep 5 03:15:34 2014
From: kukuk at suse.de (Thorsten Kukuk)
Date: Fri, 5 Sep 2014 11:15:34 +0200
Subject: [sles-beta] snapper Problem
In-Reply-To: <140999116.HM1P8Z7HZp@gjn.priv.at>
References: <140999116.HM1P8Z7HZp@gjn.priv.at>
Message-ID: <20140905091534.GA7513@suse.de>
Hi,
On Fri, Sep 05, G?nther J. Niederwimmer wrote:
> Hello,
>
> can any tell me the new way to activate snapper after the installation?
man snapper
Look for create-config.
>
> On some of my Clients snapper is not activated automatic by the installation?
Most likely your partition is too small for snapshots.
> But I mean before RC2 we have in the btrfs config Window a Icon to activate
> snapper, this is now missing ?
Don't know which window you mean, but in the storage proposal
editor during installation I still have the snapper check box
if I format with btrfs.
Thorsten
--
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
From urs.frey at post.ch Fri Sep 5 03:21:00 2014
From: urs.frey at post.ch (urs.frey at post.ch)
Date: Fri, 5 Sep 2014 09:21:00 +0000
Subject: [sles-beta] snapper Problem
In-Reply-To: <140999116.HM1P8Z7HZp@gjn.priv.at>
References: <140999116.HM1P8Z7HZp@gjn.priv.at>
Message-ID: <40637DBB36AF3941B243A286A432CA0B0F9D4855@HXMB12.pnet.ch>
Hello G?nther
You can manually create snapper configuration
The manual snapper configuration for root does create an entry in /etc/sysconfig/snapper : SNAPPER_CONFIGS="root", and also builds the snapshot root /@ and does also create the file /etc/snapper/configs/root from templates:
v03er9:~ # snapper list
Unknown config.
v03er9:~ # cat /etc/sysconfig/snapper
## Path: System/Snapper
## Type: string
## Default: ""
# List of snapper configurations.
SNAPPER_CONFIGS=""
v03er9:~ # ls -lsa /etc/snapper/configs/
total 0
0 drwxr-xr-x 1 root root 0 May 5 19:30 .
0 drwxr-xr-x 1 root root 92 May 16 2014 ..
v03er9:~ # ls -lsa /etc/snapper/config-templates/
total 4
0 drwxr-xr-x 1 root root 14 May 16 2014 .
0 drwxr-xr-x 1 root root 92 May 16 2014 ..
4 -rw-r--r-- 1 root root 929 May 5 19:30 default
v03er9:~ #
v03er9:~ # snapper -c root create-config /
v03er9:~ # snapper list
Type | # | Pre # | Date | User | Cleanup | Description | Userdata
-------+---+-------+------+------+---------+-------------+---------
single | 0 | | | root | | current |
v03er9:~ # cat /etc/sysconfig/snapper
## Path: System/Snapper
## Type: string
## Default: ""
# List of snapper configurations.
SNAPPER_CONFIGS="root"
v03er9:~ # ls -lsa /etc/snapper/configs/
total 4
0 drwxr-xr-x 1 root root 8 May 16 10:18 .
0 drwxr-xr-x 1 root root 92 May 16 2014 ..
4 -rw-r----- 1 root root 929 May 16 10:18 root
v03er9:~ #
Snapper initialization in autoyast is like this : true in the drive section under partitioning
/dev/sda
gpt
true
true
Best regards
Urs Frey?????????????????????????????????????????????
Post CH AG
Informationstechnologie
IT Betrieb
Webergutstrasse 12
3030 Bern (Zollikofen)
Telefon : ++41 (0)58 338 58 70
FAX???? : ++41 (0)58 667 30 07
E-Mail:?? urs.frey at post.ch
-----Urspr?ngliche Nachricht-----
Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von G?nther J. Niederwimmer
Gesendet: Friday, September 05, 2014 10:59 AM
An: sles-beta at lists.suse.com
Betreff: [sles-beta] snapper Problem
Hello,
can any tell me the new way to activate snapper after the installation?
On some of my Clients snapper is not activated automatic by the installation?
Btrfs File system installed, one of old Bugs I reported.
But I mean before RC2 we have in the btrfs config Window a Icon to activate
snapper, this is now missing ?
Or is this now on a other Place and I cant find it,
Thanks for a answer.
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta
From gjn at gjn.priv.at Fri Sep 5 04:01:05 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Fri, 05 Sep 2014 12:01:05 +0200
Subject: [sles-beta] snapper Problem
In-Reply-To: <20140905091534.GA7513@suse.de>
References: <140999116.HM1P8Z7HZp@gjn.priv.at> <20140905091534.GA7513@suse.de>
Message-ID: <4972840.xo2eHL6sjv@gjn.priv.at>
Hello Thorsten,
Am Freitag, 5. September 2014, 11:15:34 schrieb Thorsten Kukuk:
> Hi,
>
> On Fri, Sep 05, G?nther J. Niederwimmer wrote:
> > Hello,
> >
> > can any tell me the new way to activate snapper after the installation?
>
> man snapper
>
> Look for create-config.
>
> > On some of my Clients snapper is not activated automatic by the
> > installation?
> Most likely your partition is too small for snapshots.
>
> > But I mean before RC2 we have in the btrfs config Window a Icon to
> > activate
> > snapper, this is now missing ?
>
> Don't know which window you mean, but in the storage proposal
> editor during installation I still have the snapper check box
> if I format with btrfs.
OK, Storage Proposal ;)
I have create on all Client the same Partition ->50GB this Problem exist when
I install new on a existing Partition.
Yes, you are right, it is on the Installation Screen but not always selected
, but on a Installed system. I can't activate Shnappshot later.
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From kukuk at suse.de Fri Sep 5 04:16:38 2014
From: kukuk at suse.de (Thorsten Kukuk)
Date: Fri, 5 Sep 2014 12:16:38 +0200
Subject: [sles-beta] snapper Problem
In-Reply-To: <4972840.xo2eHL6sjv@gjn.priv.at>
References: <140999116.HM1P8Z7HZp@gjn.priv.at> <20140905091534.GA7513@suse.de>
<4972840.xo2eHL6sjv@gjn.priv.at>
Message-ID: <20140905101638.GA9493@suse.de>
On Fri, Sep 05, G?nther J. Niederwimmer wrote:
> I have create on all Client the same Partition ->50GB this Problem exist when
> I install new on a existing Partition.
>
> Yes, you are right, it is on the Installation Screen but not always selected
If the existing partition is also 50GB and in some cases snapshots
are enabled, but in other not, please create a SR with the yast2
log files of the cases, where it is not enabled.
> , but on a Installed system. I can't activate Shnappshot later.
If you mean in the storage proposal: possible, at least not if
you don't reformat it.
But with snapper it should be always possible.
Thorsten
--
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
From mge at suse.com Fri Sep 5 04:16:42 2014
From: mge at suse.com (Matthias G. Eckermann)
Date: Fri, 5 Sep 2014 12:16:42 +0200
Subject: [sles-beta] snapper Problem
In-Reply-To: <4972840.xo2eHL6sjv@gjn.priv.at>
References: <140999116.HM1P8Z7HZp@gjn.priv.at> <20140905091534.GA7513@suse.de>
<4972840.xo2eHL6sjv@gjn.priv.at>
Message-ID: <20140905101642.GC16014@suse.com>
On 2014-09-05 T 12:01 +0200 G?nther J. Niederwimmer wrote:
> I have create on all Client the same Partition ->50GB
> this Problem exist when I install new on a existing
> Partition.
You must allow the partitioner to format your existing
partition as the "/" filesystem, to create the proper
subvolume setup. Only then snapshotting will properly
work, and will be enabled.
so long -
MgE
--
Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise
Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com
SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
From gjn at gjn.priv.at Fri Sep 5 04:33:14 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Fri, 05 Sep 2014 12:33:14 +0200
Subject: [sles-beta] snapper Problem
In-Reply-To: <20140905101642.GC16014@suse.com>
References: <140999116.HM1P8Z7HZp@gjn.priv.at> <4972840.xo2eHL6sjv@gjn.priv.at>
<20140905101642.GC16014@suse.com>
Message-ID: <2115857.xh0LfohKbP@gjn.priv.at>
Hell Matthias,
Am Freitag, 5. September 2014, 12:16:42 schrieb Matthias G. Eckermann:
> On 2014-09-05 T 12:01 +0200 G?nther J. Niederwimmer wrote:
> > I have create on all Client the same Partition ->50GB
> > this Problem exist when I install new on a existing
> > Partition.
>
> You must allow the partitioner to format your existing
> partition as the "/" filesystem, to create the proper
> subvolume setup. Only then snapshotting will properly
> work, and will be enabled.
The "/" is always "automatic" format when I install new ;).
But I found the way to activate snapper by hand. In YaST2 the activate snapper
is gone after Installation :(.
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From juwolf at suse.de Fri Sep 5 05:00:58 2014
From: juwolf at suse.de (Julian Wolf)
Date: Fri, 05 Sep 2014 13:00:58 +0200
Subject: [sles-beta] SLES12 RC2 x86_64 dracut: touch failed. Couldn't
create logfile.
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F9D488F@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F9D488F@HXMB12.pnet.ch>
Message-ID: <2720572.BRHtMEadcN@f48>
Am Freitag, 5. September 2014, 09:52:03 schrieb urs.frey at post.ch:
> Hi
>
> With SLES12 x86_64 RC2 on every command using dracut I note this error
> output
>
> h039ua:~ # dracut --list-modules
> dracut: touch failed. Couldn't create logfile.
> Executing: /usr/bin/dracut --list-modules
Hi,
this is already fixed and shouldn't occur anymore with the next release.
Regards, Julian
--
Julian Wolf, Working student
SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB
16746 (AG N?rnberg)
Maxfeldstr. 5 / D-90409 N?rnberg
From cyberorg at opensuse.org Fri Sep 5 05:50:00 2014
From: cyberorg at opensuse.org (Jigish Gohil)
Date: Fri, 5 Sep 2014 17:20:00 +0530
Subject: [sles-beta] default user management to ldap
Message-ID:
Hi
The installer does not seem to give option to setup CA and ldap server
for user management during installation as in previous SLEs, is there
a way to set default user management to ldap when yast2 users is
started?
-J
From jreidinger at suse.com Fri Sep 5 05:59:05 2014
From: jreidinger at suse.com (Josef Reidinger)
Date: Fri, 5 Sep 2014 13:59:05 +0200
Subject: [sles-beta] default user management to ldap
In-Reply-To:
References:
Message-ID: <20140905135905.3f22a4c4@linux-5mqx.site>
On Fri, 5 Sep 2014 17:20:00 +0530
"Jigish Gohil" wrote:
> Hi
>
> The installer does not seem to give option to setup CA and ldap server
> for user management during installation as in previous SLEs, is there
> a way to set default user management to ldap when yast2 users is
> started?
>
> -J
Hi Jigish,
yes, we remove such functionality from installer to have installer
simplier and allow configuration of more complex authentication
methods after boot, where is more easily to fix issues via e.g.
maintenance update.
For such task is there modules like yast2-ca-management and
yast2-auth-client.
Josef
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
>
From tparker at cbnco.com Fri Sep 5 07:25:58 2014
From: tparker at cbnco.com (Tom Parker)
Date: Fri, 5 Sep 2014 09:25:58 -0400
Subject: [sles-beta] Network Interfaces change name between install and
first boot
In-Reply-To:
References: <5408BF8E.8090606@cbnco.com>
Message-ID: <5409B9E6.6000603@cbnco.com>
Hi Darren. For sure and that is my next step, but this works every time
with SLES 11 and the "normal" ethX names are default now
Many people who are not part of the beta and were not there for the
"ugly" names will likely find this to be a problem.
Tom
On 04/09/14 05:24 PM, Darren Thompson wrote:
> Tom/team
>
> Is this a case where the "ugly but constant" port naming scheme may be
> more useful than the more traditional eth(X) port names?
>
> Darren
>
> Darren Thompson
>
> Professional Services Engineer / Consultant
>
> *cid:image001.jpg at 01CB7C0C.6C6A2AE0*
>
> Level 3, 60 City Road
>
> Southgate, VIC 3006
>
> Mb: 0400 640 414
>
> Mail: darrent at akurit.com.au
> Web: www.akurit.com.au
>
>
>
> On 5 September 2014 05:37, Tom Parker > wrote:
>
> Hello
>
> We are doing some RC2 testing with booting servers using /boot on
> microSD cards and / on iscsi with software initiators.
>
> We have run into problems today on our test PC that has 1 onboard nic
> and 1 PCI nic with 4 ports. During the installation process the
> onboard
> nic appears as eth3 but after the first reboot it is eth0.
>
> This is obviously causing havoc with the network setup as dracut is
> setting up the wrong interface on first boot and / is not found.
>
> Should I submit an SR for this?
>
> Tom
> _______________________________________________
> sles-beta mailing list
> sles-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/sles-beta
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 3692 bytes
Desc: not available
URL:
From gjn at gjn.priv.at Fri Sep 5 07:42:24 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Fri, 05 Sep 2014 15:42:24 +0200
Subject: [sles-beta] saslauth initfile broken
Message-ID: <36160275.9s2j40LFdY@gjn.priv.at>
Hello,
when I like to start saslauthd I have this?
smtp:~ # systemctl status saslauthd
saslauthd.service - saslauthd Server Daemon
Loaded: loaded (/usr/lib/systemd/system/saslauthd.service; enabled)
Active: failed (Result: start-limit) since Fre 2014-09-05 15:36:30 CEST;
1min 55s ago
Process: 1692 ExecStop=/bin/kill -TERM $MAINPID (code=exited,
status=1/FAILURE)
Process: 1688 ExecStart=/usr/sbin/saslauthd (code=exited, status=0/SUCCESS)
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From gjn at gjn.priv.at Fri Sep 5 09:03:08 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Fri, 05 Sep 2014 17:03:08 +0200
Subject: [sles-beta] cron.d script
Message-ID: <3014610.gt1Y6yYpd4@gjn.priv.at>
Hello,
can any help me to configure this for SLES 12 with SLES 11 this is working.
I have in /etc/cron.d a file kerberos.initial, inside
@reboot root /sbin/sleep 60 && /usr/bin/kinit -k host/xxx.xxxx.xxx
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From meissner at suse.de Fri Sep 5 09:05:25 2014
From: meissner at suse.de (Marcus Meissner)
Date: Fri, 5 Sep 2014 17:05:25 +0200
Subject: [sles-beta] cron.d script
In-Reply-To: <3014610.gt1Y6yYpd4@gjn.priv.at>
References: <3014610.gt1Y6yYpd4@gjn.priv.at>
Message-ID: <20140905150525.GH543@suse.de>
On Fri, Sep 05, 2014 at 05:03:08PM +0200, G?nther J. Niederwimmer wrote:
> Hello,
>
> can any help me to configure this for SLES 12 with SLES 11 this is working.
>
> I have in /etc/cron.d a file kerberos.initial, inside
>
> @reboot root /sbin/sleep 60 && /usr/bin/kinit -k host/xxx.xxxx.xxx
/sbin/sleep sounds wrong.
Ciao, Marcus
From mpost at suse.com Fri Sep 5 10:56:57 2014
From: mpost at suse.com (Mark Post)
Date: Fri, 05 Sep 2014 10:56:57 -0600
Subject: [sles-beta] SLES12 RC2 x86_64 Login possible even though
autoyast init-script is still runing
In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0F9D2DFB@HXMB12.pnet.ch>
References: <40637DBB36AF3941B243A286A432CA0B0F9D2BF6@HXMB12.pnet.ch>
<20140826133145.GA29287@suse.de>
<20140826153700.506936f1@dhcp150.suse.cz>
<40637DBB36AF3941B243A286A432CA0B0F9D2C39@HXMB12.pnet.ch>
<20140826155728.76851414@dhcp150.suse.cz>
<40637DBB36AF3941B243A286A432CA0B0F9D2DFB@HXMB12.pnet.ch>
Message-ID: <5409B3190200006D0016FBEB@prv-mh.provo.novell.com>
>>> On 8/27/2014 at 04:38 AM, wrote:
> Aug 27 08:13:59 h05cnh systemd[1]: Started Login Service.
> Aug 27 08:13:59 h05cnh systemd-logind[10059]: New seat seat0.
> Aug 27 08:13:59 h05cnh systemd-logind[10059]: Watching system buttons on
> /dev/input/event2 (Power Button)
> + systemctl disable systemd-logind
> + systemctl stop systemd-logind
> +sleep 300
> + systemctl enable systemd-logind
> The unit files have no [Install] section. They are not meant to be enabled
> using systemctl.
> Possible reasons for having this kind of units are:
> 1) A unit may be statically enabled by being symlinked from another unit's
> .wants/ or .requires/ directory.
> 2) A unit's purpose may be to act as a helper for some other unit which has
> a requirement dependency on it.
> 3) A unit may be started when needed via activation (socket, path, timer,
> D-Bus, udev, scripted systemctl call, ...).
There is a class of service files that are called "static." They cannot be enabled or disabled, per se. It would be nice if systemctl disable would tell you that. :(
You _can_ mask/unmask them, however. So, try this:
systemctl mask systemd-logind.service
systemctl stop systemd-logind.service
systemctl unmask systemd-logind.service
systemctl start systemd-logind.service
Mark Post
From gsu at axway.com Fri Sep 5 11:46:24 2014
From: gsu at axway.com (Guang Su)
Date: Fri, 5 Sep 2014 17:46:24 +0000
Subject: [sles-beta] RC2 PXE imaging error
In-Reply-To: <20140905093322.007e6adb@linux-5mqx.site>
References:
<20140905093322.007e6adb@linux-5mqx.site>
Message-ID:
Hi Josef,
Both installation source and profiles are stored on NFS server. It looks like the nfs shares were not mount by autoyast.
Pxelinx.cfg
default linux
prompt 0
label linux
kernel vmlinuz-SLES12-x86_64
append load_ramdisk=1 initrd=initrd-SLES12-x86_64 install=nfs://10.x.x.x/exports/appliance-os/sles-12/x86_64/ autoyast=nfs://10.x.x.x/appimgs/test/pxe.0A823CAD/ textmode=1 biosdevname=1 net.ifnames=0 namescheme="" doscsirename=1 brokenmodules=qla2xxx,qla2400,usb-storage y2confirm
The content of /exports/appliance-os/sles-12/x86_64
ls -l /exports/appliance-os/sles-12/x86_64/
-r--r--r-- 1 root root 5251769 2014-08-21 07:06 ARCHIVES.gz
dr-xr-xr-x 3 root root 4096 2014-08-21 07:06 boot
-r--r--r-- 1 root root 18091062 2014-08-21 07:04 ChangeLog
-r--r--r-- 1 root root 11093 2014-08-21 07:06 content
-r--r--r-- 1 root root 481 2014-08-21 07:06 content.asc
-r--r--r-- 1 root root 972 2014-08-21 07:06 content.key
-r--r--r-- 1 root root 48337 2014-08-05 12:31 control.xml
-r--r--r-- 1 root root 17992 2014-08-21 06:09 COPYING
-r--r--r-- 1 root root 25733 2014-08-21 06:09 COPYING.de
-r--r--r-- 1 root root 1455 2014-08-21 06:09 COPYRIGHT
-r--r--r-- 1 root root 1620 2014-08-21 06:09 COPYRIGHT.de
-r--r--r-- 1 root root 275 2014-08-21 07:06 directory.yast
dr-xr-xr-x 2 root root 4096 2014-08-21 07:00 docu
dr-xr-xr-x 3 root root 4096 2014-08-21 07:00 EFI
-r--r--r-- 1 root root 955 2014-08-21 06:09 gpg-pubkey-39db7c82-510a966b.asc
-r--r--r-- 1 root root 975 2014-08-21 06:09 gpg-pubkey-50a3dd1c-50f35137.asc
-r--r--r-- 1 root root 39973 2014-08-21 07:06 INDEX.gz
-r--r--r-- 1 root root 7280 2014-08-21 06:09 license.tar.gz
-r--r--r-- 1 root root 64709 2014-08-21 07:06 ls-lR.gz
dr-xr-xr-x 2 root root 4096 2014-08-21 07:06 media.1
-r--r--r-- 1 root root 124083 2014-08-21 06:09 NEWS
-r--r--r-- 1 root root 1288 2014-08-21 06:09 pubring.gpg
-r--r--r-- 1 root root 2910 2014-01-15 00:26 README
-r--r--r-- 1 root root 547 2014-08-21 07:04 README.BETA
dr-xr-xr-x 5 root root 4096 2014-08-21 07:00 suse
Thanks
--Guang
-----Original Message-----
From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Josef Reidinger
Sent: Friday, September 5, 2014 12:33 AM
To: sles-beta at lists.suse.com
Subject: Re: [sles-beta] RC2 PXE imaging error
On Thu, 4 Sep 2014 22:07:57 +0000
"Guang Su" wrote:
> Hi,
>
> I tried SLES12 RC2 PXE installation on Dell PowerEdge R620 server and
> saw this YaST error. Has anyone seen this error before? I did not see
> this issue in beta testing. See attached y2log from the server.
> [cid:image001.png at 01CFC851.B8CE0790]
>
> Thanks
>
> --Guang
Hi Guang,
this error said that yast have problem to find any product in installation repository. I see you use PXE boot, what repository do you use as base for such installation?
Josef
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta
From gjn at gjn.priv.at Sat Sep 6 01:36:44 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Sat, 06 Sep 2014 09:36:44 +0200
Subject: [sles-beta] cron.d script
In-Reply-To: <20140905150525.GH543@suse.de>
References: <3014610.gt1Y6yYpd4@gjn.priv.at> <20140905150525.GH543@suse.de>
Message-ID: <7350490.rDk7Jl5Rv8@gjn.priv.at>
Hello Marcus and all,
Thanks for the answer, but ..
Am Freitag, 5. September 2014, 17:05:25 schrieb Marcus Meissner:
> On Fri, Sep 05, 2014 at 05:03:08PM +0200, G?nther J. Niederwimmer wrote:
> > Hello,
> >
> > can any help me to configure this for SLES 12 with SLES 11 this is
> > working.
> >
> > I have in /etc/cron.d a file kerberos.initial, inside
> >
> > @reboot root /sbin/sleep 60 && /usr/bin/kinit -k host/xxx.xxxx.xxx
>
> /sbin/sleep sounds wrong.
you are right, the path have change, but is it possible that I have to
configure this on a other place ?
I mean the special parameters not longer working with cron!
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From gjn at gjn.priv.at Sat Sep 6 09:59:55 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Sat, 06 Sep 2014 17:59:55 +0200
Subject: [sles-beta] YaST2 + Ldap + Mirrormode
Message-ID: <5347779.7gbrKqiqjK@gjn.priv.at>
Hello,
have any tested, set up a ldap MirrorMode server and have afterward a running
system ?
I gamble now three Days but I don't have a running system :-(
I make the ground configuration with YaST2 and afterward with slapcat / slapadd
the rest , ldapmodify is not working for the DB hdb
Please test it ,and say afterward it is my mistake ;)
Thanks for a answer.
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer
From gjn at gjn.priv.at Sun Sep 7 11:31:32 2014
From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer)
Date: Sun, 07 Sep 2014 19:31:32 +0200
Subject: [sles-beta] YaST DNS-Server Module
Message-ID: <24744487.WQlCy5EsUd@gjn.priv.at>
Hello,
for witch config File search the DNS-Server Module, when I like to store the
DNS-Server in ldap. Or must I have a extra ldap server installed?
I can't this with yast2 not configure.
Thanks for a answer,
--
mit freundlichen Gr??en / best Regards,
G?nther J. Niederwimmer