From schubi at suse.de Mon Jul 21 00:54:53 2014 From: schubi at suse.de (Stefan Schubert) Date: Mon, 21 Jul 2014 08:54:53 +0200 Subject: [sles-beta] SLES 12 Beta 10 leaves autoinst.xml file which installs smaller set of rpms than manual install In-Reply-To: References: Message-ID: <53CCB93D.9070805@suse.de> Yes, that's a known issue: https://bugzilla.novell.com/show_bug.cgi?id=887118 The problem is, that libzypp does save the current state of the package only: E.g. The user selects a package for installation. So the package has the state will be installed and is selected by the user for the installation. After the installation the package has the state: is installed by the system/libzypp. Which is also true but the previous information has been lost. At that point the /root/autoinst.xml will be generated. So the generated autoinst.xml via the button in the installation overview (before starting the real installation) produce a valid package selection. Yes, I know there is an inconsistency but we are working on it to find a better solution for. :-) Greetings Stefan Am 18.07.2014 21:12, schrieb Harold Longley: > SLES 12 Beta 10 installs manually, but the /root/autoinst.xml file > which is left behind is not sufficient to duplicate the system. Using > that autoinst.xml file to do an install leaves a system where the set > of rpms installed is smaller by 184 rpms than the manual install. > > For the manual install, no rpms were added to the default set. > > %wc -l rpmlist.stock12Beta10 rpmlist.stock12Beta10.defaultautoinst > 1586 rpmlist.stock12Beta10 > 1402 rpmlist.stock12Beta10.defaultautoinst > > > > Opened SR 10902235641 with the detailed rpm list and the generated > autoinst.xml file. > > Harold Longley > Cray Inc. > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- ******************************************************************************* Stefan Schubert e-mail: schubi at suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From Klaus.Gmeinwieser at oce.com Tue Jul 22 05:56:40 2014 From: Klaus.Gmeinwieser at oce.com (Klaus Gmeinwieser) Date: Tue, 22 Jul 2014 13:56:40 +0200 Subject: [sles-beta] Japanese Input Message-ID: <53CE5178.6040401@oce.com> Hi SUSE team, I tested an install of SLES12 in Japanaese which seems to work faily good (Japanese character output used in the F1-F6 terminals remain cubes for e.g. df -h command)... The main Problem for me now, is to get Japanese Input system (ibus) to work. Is there any documentation available from SUSE on how to setup (if necessary), use and switch between the keyboard layouts? Some documenation is available for Arch and Ubuntu, but I assume this not to apply for the SUSE branding of Gnome.... Could you please give me some information on "howto" or "where to find", as I need to do this also for Korean and Chinese and need to add the results to our documentation - as it is not totally austomatic and "self explaining" like scim with KDE was. Please advise Thanks a lot & Best Regards Klaus -- Klaus Gmeinwieser T +49 (0)8121 72 4358 F +49 (0)8121 72 3173 E klaus.gmeinwieser at oce.com W www.oce.com Oc? Printing Systems GmbH & Co. KG ? A Canon Group Company P.O. Box 1260 ? 85581 Poing Siemensallee 2 ? 85586 Poing ? Germany Oc? enables its customers to manage their documents efficiently and effectively by offering innovative print and document management products and services for professional environments. Oc? Printing Systems GmbH & Co. KG The company is a limited partnership with its registered office in Poing ? Trade Register HRA 100955 (Amtsgericht M?nchen) ? WEEE-Reg.-No. DE 888 05 443 General Partner: Oc? Printing Systems Gesch?ftsf?hrungsgesellschaft mbH Registered Office: Poing ? Trade Register HRB 206480 (Amtsgericht M?nchen) Executive Officer: Andr? Mittelsteiner This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation. From fcrozat at suse.com Tue Jul 22 06:03:12 2014 From: fcrozat at suse.com (Frederic Crozat) Date: Tue, 22 Jul 2014 14:03:12 +0200 Subject: [sles-beta] Japanese Input In-Reply-To: <53CE5178.6040401@oce.com> References: <53CE5178.6040401@oce.com> Message-ID: <1406030592.7728.3.camel@par-r81vxc7.par.novell.com> Le mardi 22 juillet 2014 ? 13:56 +0200, Klaus Gmeinwieser a ?crit : > Hi SUSE team, > > I tested an install of SLES12 in Japanaese which seems to work faily > good (Japanese character output used in the F1-F6 terminals remain cubes > for e.g. df -h command)... > > The main Problem for me now, is to get Japanese Input system (ibus) to > work. Is there any documentation available from SUSE on how to setup (if > necessary), use and switch between the keyboard layouts? > > Some documenation is available for Arch and Ubuntu, but I assume this > not to apply for the SUSE branding of Gnome.... The "Arch" documentation should apply to our GNOME version. You just need to go to GNOME Control Center (The settings icon on the bottom right system menu), "Region and Languages" and "Add input source". It should be the same for other languages such as Korean and Chinese. -- Frederic Crozat Project Manager Enterprise Desktop SUSE From gbonazzoli at technogym.com Tue Jul 22 07:25:32 2014 From: gbonazzoli at technogym.com (Bonazzoli Giandomenico - Technogym SPA) Date: Tue, 22 Jul 2014 13:25:32 +0000 Subject: [sles-beta] Oracle 11.2.0.4 On SLES 12 Message-ID: Oracle 11.2.0.4 is working fine on SLES 12. You only need to launch the installer with : ./runInstaller -ignorePrereq By the way, the package rpms that the installer is searching are completely different both in name and in version since SLES 11. In your experience how many day it will need to be certified by Oracle after the definitive SLES 12 version is released ? From Klaus.Gmeinwieser at oce.com Tue Jul 22 08:33:10 2014 From: Klaus.Gmeinwieser at oce.com (Klaus Gmeinwieser) Date: Tue, 22 Jul 2014 16:33:10 +0200 Subject: [sles-beta] Japanese Input In-Reply-To: <1406030592.7728.3.camel@par-r81vxc7.par.novell.com> References: <53CE5178.6040401@oce.com> <1406030592.7728.3.camel@par-r81vxc7.par.novell.com> Message-ID: <53CE7626.9030804@oce.com> Hi Frederic, thanks for the quick answer. I did the settings in the GCC (added Japanese in addition to English) and got a en/ja entry in the system tray. Unfortunately the settings do not work, as I can change settings to ja but the keyboard remains fully English - also the "show keyboard" shows a US Intl. layout. Did I miss something to configure? The automatic configuration for any Asian/Cyrillic/??? install to include the keyboard layout automatically is definitely gone? Thanks in advance & Rgds Klaus Am 22.07.2014 14:03, schrieb Frederic Crozat: > Le mardi 22 juillet 2014 ? 13:56 +0200, Klaus Gmeinwieser a ?crit : >> Hi SUSE team, >> >> I tested an install of SLES12 in Japanaese which seems to work faily >> good (Japanese character output used in the F1-F6 terminals remain cubes >> for e.g. df -h command)... >> >> The main Problem for me now, is to get Japanese Input system (ibus) to >> work. Is there any documentation available from SUSE on how to setup (if >> necessary), use and switch between the keyboard layouts? >> >> Some documenation is available for Arch and Ubuntu, but I assume this >> not to apply for the SUSE branding of Gnome.... > > The "Arch" documentation should apply to our GNOME version. You just > need to go to GNOME Control Center (The settings icon on the bottom > right system menu), "Region and Languages" and "Add input source". > > It should be the same for other languages such as Korean and Chinese. > -- Klaus Gmeinwieser T +49 (0)8121 72 4358 F +49 (0)8121 72 3173 E klaus.gmeinwieser at oce.com W www.oce.com Oc? Printing Systems GmbH & Co. KG ? A Canon Group Company P.O. Box 1260 ? 85581 Poing Siemensallee 2 ? 85586 Poing ? Germany Oc? enables its customers to manage their documents efficiently and effectively by offering innovative print and document management products and services for professional environments. Oc? Printing Systems GmbH & Co. KG The company is a limited partnership with its registered office in Poing ? Trade Register HRA 100955 (Amtsgericht M?nchen) ? WEEE-Reg.-No. DE 888 05 443 General Partner: Oc? Printing Systems Gesch?ftsf?hrungsgesellschaft mbH Registered Office: Poing ? Trade Register HRB 206480 (Amtsgericht M?nchen) Executive Officer: Andr? Mittelsteiner This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation. From Arun.Singh at suse.com Tue Jul 22 08:45:35 2014 From: Arun.Singh at suse.com (Arun Singh) Date: Tue, 22 Jul 2014 08:45:35 -0600 Subject: [sles-beta] Oracle 11.2.0.4 On SLES 12 In-Reply-To: References: Message-ID: <53CE24AF02000042000953DF@prv-mh.provo.novell.com> Hi Bonazzoli, >>> On 7/22/2014 at 6:25 AM, Bonazzoli Giandomenico - Technogym SPA wrote: > Oracle 11.2.0.4 is working fine on SLES 12. Good to hear. > > You only need to launch the installer with : ./runInstaller -ignorePrereq > > By the way, the package rpms that the installer is searching are completely > different both in name and in version since SLES 11. This is due to that fact that Oracle OUI doesn't understand SLES12. Please use following workaround: Edit "database/stage/cvu/cv/admin/cvu_config" and change "CV_ASUME_DISTID=SUSE11" to avoid above OUI trouble: > > In your experience how many day it will need to be certified by Oracle after > the definitive SLES 12 version is released ? > It's takes couple of months after product is released. Thanks, Arun From fcrozat at suse.com Tue Jul 22 08:52:28 2014 From: fcrozat at suse.com (Frederic Crozat) Date: Tue, 22 Jul 2014 16:52:28 +0200 Subject: [sles-beta] Japanese Input In-Reply-To: <53CE7626.9030804@oce.com> References: <53CE5178.6040401@oce.com> <1406030592.7728.3.camel@par-r81vxc7.par.novell.com> <53CE7626.9030804@oce.com> Message-ID: <1406040748.7728.7.camel@par-r81vxc7.par.novell.com> Le mardi 22 juillet 2014 ? 16:33 +0200, Klaus Gmeinwieser a ?crit : > Hi Frederic, > > thanks for the quick answer. > > I did the settings in the GCC (added Japanese in addition to English) > and got a en/ja entry in the system tray. Unfortunately the settings do > not work, as I can change settings to ja but the keyboard remains fully > English - also the "show keyboard" shows a US Intl. layout. Did I miss > something to configure? Sorry, my instructions were incomplete (I'm not a specialist in CJK input methods). You need to first install the ibus subpackage for your target language. This should be done is done automatically if you choose the language during install but it won't be done otherwise. Do to so, just run "zypper in locale(ibus:jp)", it will cause zypper to install the "right" ibus component for japanese. Then, you need to logout from the current desktop session, login again and add the input method (you will notice new input method for japanese, Anthy). > The automatic configuration for any Asian/Cyrillic/??? install to > include the keyboard layout automatically is definitely gone? I'm not sure we will be able to have it for GA, since it would rely on gnome-initial-setup which is not part of SLE12. Could you open a SR, just to make sure we track it properly ? -- Frederic Crozat Project Manager Enterprise Desktop SUSE From Klaus.Gmeinwieser at oce.com Tue Jul 22 10:36:01 2014 From: Klaus.Gmeinwieser at oce.com (Klaus Gmeinwieser) Date: Tue, 22 Jul 2014 18:36:01 +0200 Subject: [sles-beta] Japanese Input In-Reply-To: <1406040748.7728.7.camel@par-r81vxc7.par.novell.com> References: <53CE5178.6040401@oce.com> <1406030592.7728.3.camel@par-r81vxc7.par.novell.com> <53CE7626.9030804@oce.com> <1406040748.7728.7.camel@par-r81vxc7.par.novell.com> Message-ID: <53CE92F1.8000607@oce.com> Hi Frederic, I opened SR # 10902791871 on this issue Thanks for your support Klaus Am 22.07.2014 16:52, schrieb Frederic Crozat: > Le mardi 22 juillet 2014 ? 16:33 +0200, Klaus Gmeinwieser a ?crit : >> Hi Frederic, >> >> thanks for the quick answer. >> >> I did the settings in the GCC (added Japanese in addition to English) >> and got a en/ja entry in the system tray. Unfortunately the settings do >> not work, as I can change settings to ja but the keyboard remains fully >> English - also the "show keyboard" shows a US Intl. layout. Did I miss >> something to configure? > > Sorry, my instructions were incomplete (I'm not a specialist in CJK > input methods). > > You need to first install the ibus subpackage for your target language. > This should be done is done automatically if you choose the language > during install but it won't be done otherwise. > > Do to so, just run "zypper in locale(ibus:jp)", it will cause zypper to > install the "right" ibus component for japanese. Then, you need to > logout from the current desktop session, login again and add the input > method (you will notice new input method for japanese, Anthy). > >> The automatic configuration for any Asian/Cyrillic/??? install to >> include the keyboard layout automatically is definitely gone? > > I'm not sure we will be able to have it for GA, since it would rely on > gnome-initial-setup which is not part of SLE12. Could you open a SR, > just to make sure we track it properly ? > -- Klaus Gmeinwieser T +49 (0)8121 72 4358 F +49 (0)8121 72 3173 E klaus.gmeinwieser at oce.com W www.oce.com Oc? Printing Systems GmbH & Co. KG ? A Canon Group Company P.O. Box 1260 ? 85581 Poing Siemensallee 2 ? 85586 Poing ? Germany Oc? enables its customers to manage their documents efficiently and effectively by offering innovative print and document management products and services for professional environments. Oc? Printing Systems GmbH & Co. KG The company is a limited partnership with its registered office in Poing ? Trade Register HRA 100955 (Amtsgericht M?nchen) ? WEEE-Reg.-No. DE 888 05 443 General Partner: Oc? Printing Systems Gesch?ftsf?hrungsgesellschaft mbH Registered Office: Poing ? Trade Register HRB 206480 (Amtsgericht M?nchen) Executive Officer: Andr? Mittelsteiner This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation. From uwedr at suse.com Tue Jul 22 13:21:53 2014 From: uwedr at suse.com (Uwe Drechsel) Date: Tue, 22 Jul 2014 21:21:53 +0200 Subject: [sles-beta] new SLE 12 schedule? In-Reply-To: References: Message-ID: <20140722192153.GA5907@suse.com> On Mon, Jul 21, Wendy Palm wrote: > Now that beta10 released, and RC1 is delayed - is there a new schedule > yet that we can be made aware of? > We are currently working on an updated schedule and will post it here soon. Thanks Uwe -- Uwe Drechsel Project Manager SUSE Linux Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From Dick.Waite at softwareag.com Wed Jul 23 00:55:58 2014 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Wed, 23 Jul 2014 06:55:58 +0000 Subject: [sles-beta] intel_idle Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D538778AF@hqmbx6.eur.ad.sag> Grand Day, When running some SLES11 on X86_64 sites some time ago the "batch" jobs were taking 30-50% more wall clock time. After some time a work-a-round was found to amend the "Intel_Idle" parm. There was some chatter at the time that a "better" fix would be available with a later Linux release. I'm going to visit one of our customers who had this issue in a few weeks time, what news do I have for them? __R Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsmeix at suse.de Wed Jul 23 01:41:46 2014 From: jsmeix at suse.de (Johannes Meixner) Date: Wed, 23 Jul 2014 09:41:46 +0200 (CEST) Subject: [sles-beta] Beta10 - Autoyast In-Reply-To: References: Message-ID: Hello, On Jul 22 13:32 Ronny Pretzsch wrote (excerpt): > Bad News: ... > (3) > We do not install X11 components. > Thus in Stage 2 yast should run in textmode. > But it runs in blank screen mode. > Next thing we see after reboot is the login prompt. FYI: Perhaps this one is somehow related: https://bugzilla.novell.com/show_bug.cgi?id=886488 Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer From schubi at suse.de Wed Jul 23 01:49:04 2014 From: schubi at suse.de (Stefan Schubert) Date: Wed, 23 Jul 2014 09:49:04 +0200 Subject: [sles-beta] Beta10 - Autoyast In-Reply-To: References: Message-ID: <53CF68F0.5060109@suse.de> Am 23.07.2014 09:41, schrieb Johannes Meixner: > > Hello, > > On Jul 22 13:32 Ronny Pretzsch wrote (excerpt): >> Bad News: > ... >> (3) >> We do not install X11 components. >> Thus in Stage 2 yast should run in textmode. >> But it runs in blank screen mode. >> Next thing we see after reboot is the login prompt. > > FYI: Perhaps this one is somehow related: > https://bugzilla.novell.com/show_bug.cgi?id=886488 It seems there is a bug in plymouth. We have made a workaround which is available for RC1. Greetings Stefan -- ******************************************************************************* Stefan Schubert e-mail: schubi at suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From sbahling at suse.com Wed Jul 23 04:09:03 2014 From: sbahling at suse.com (Scott Bahling) Date: Wed, 23 Jul 2014 12:09:03 +0200 Subject: [sles-beta] intel_idle In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D538778AF@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D538778AF@hqmbx6.eur.ad.sag> Message-ID: <1406110143.22894.299.camel@hermano.suse.de> On Wed, 2014-07-23 at 06:55 +0000, Waite, Dick wrote: > Grand Day, > > When running some SLES11 on X86_64 sites some time ago the "batch" > jobs were taking 30-50% more wall clock time. After some time a > work-a-round was found to amend the "Intel_Idle" parm. There was some > chatter at the time that a "better" fix would be available with a > later Linux release. I'm going to visit one of our customers who had > this issue in a few weeks time, what news do I have for them? It depends on the exact tuning ("work-a-round") used. There has been an optimization related to disabling promotion to C1E state so using intel_idle.max_cstate=1 might give better results with SUSE Linux Enterprise Server 12 and remove the need to disable the intel_idle driver completely. It depends on the workload and CPU model in use. Other than that, the intel_idle driver and it's parameters should work the same in 12 as in 11 - meaning if c-states affect your workload, tuning of the intel_idle driver might be necessary. Best Regards, Scott -- Scott Bahling | Technical Account Manager - Team Lead +49 911-74053-121 | Mobile: +49 173-587-6977 | sbahling at suse.com SUSE Linux Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG Nuremberg) From lukas.ocilka at suse.com Wed Jul 23 08:43:43 2014 From: lukas.ocilka at suse.com (Lukas Ocilka) Date: Wed, 23 Jul 2014 16:43:43 +0200 Subject: [sles-beta] SLES12 Beta10 In-Reply-To: References: Message-ID: <53CFCA1F.1080306@suse.com> On 23.7.2014 15:27, Miguel E Rivera wrote: > All, > > Anyone having success Iscsi booting their systems with the new SLES12. > I mysteriously had it working with beta 3 and have not had any success > since then.. > > We diskless boot everything in our environment so this is a big issue > for us? We have HP servers with intel network cards that we flash to be > able to use to iscsi boot from luns we create on our NAS. I was able to > load the system to the iscsi lun with no issues and it loads but once it > reboots or I try to boot it I get the following error. > > ?systemd[1] Failed to insert module ?autofs4? > ... shortened ... > Any help or ideas would be appreciated. > > Mike Rivera Hi Mike, I was just told by the iscsi developer that this will be fixed in RC1, if not, you are kindly asked to open a new bug report. I don't have more info though. Thanks Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader Cloud & Systems Management Department, SUSE Linux From miguel.e.rivera at lmco.com Wed Jul 23 09:12:59 2014 From: miguel.e.rivera at lmco.com (Rivera, Miguel E) Date: Wed, 23 Jul 2014 15:12:59 +0000 Subject: [sles-beta] EXTERNAL: Re: SLES12 Beta10 In-Reply-To: <53CFCA1F.1080306@suse.com> References: <53CFCA1F.1080306@suse.com> Message-ID: Lukas, Thank you for the information. I have opened a bug report but thought I would put it out to the group. Thanks, Mike Rivera -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Lukas Ocilka Sent: Wednesday, July 23, 2014 9:44 AM To: sles-beta at lists.suse.com Subject: EXTERNAL: Re: [sles-beta] SLES12 Beta10 On 23.7.2014 15:27, Miguel E Rivera wrote: > All, > > Anyone having success Iscsi booting their systems with the new SLES12. > I mysteriously had it working with beta 3 and have not had any success > since then.. > > We diskless boot everything in our environment so this is a big issue > for us... We have HP servers with intel network cards that we flash to > be able to use to iscsi boot from luns we create on our NAS. I was > able to load the system to the iscsi lun with no issues and it loads > but once it reboots or I try to boot it I get the following error. > > "systemd[1] Failed to insert module 'autofs4' > ... shortened ... > Any help or ideas would be appreciated. > > Mike Rivera Hi Mike, I was just told by the iscsi developer that this will be fixed in RC1, if not, you are kindly asked to open a new bug report. I don't have more info though. Thanks Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader Cloud & Systems Management Department, SUSE Linux _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From Dick.Waite at softwareag.com Wed Jul 23 10:44:51 2014 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Wed, 23 Jul 2014 16:44:51 +0000 Subject: [sles-beta] intel_idle In-Reply-To: <1406110143.22894.299.camel@hermano.suse.de> References: <46AC8C81C10B8C48820201DF2AE1D76D538778AF@hqmbx6.eur.ad.sag>, <1406110143.22894.299.camel@hermano.suse.de> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D53878776@hqmbx6.eur.ad.sag> Many Thanks for the update Scott. A couple / few of customers did not like the idea of having to amend the boot parm and at the time some words were written about using in a later kernel, syscntl.conf which customers preferred over amending boot as their system providers charged extra... If the parm was not in boot then I think more customers would be willing to amend this value, I wonder how many customer get better results with the default, do you have any numbers? __R ________________________________________ From: Scott Bahling [sbahling at suse.com] Sent: 23 July 2014 12:09 To: Waite, Dick Cc: sles-beta at lists.suse.com Subject: Re: [sles-beta] intel_idle On Wed, 2014-07-23 at 06:55 +0000, Waite, Dick wrote: > Grand Day, > > When running some SLES11 on X86_64 sites some time ago the "batch" > jobs were taking 30-50% more wall clock time. After some time a > work-a-round was found to amend the "Intel_Idle" parm. There was some > chatter at the time that a "better" fix would be available with a > later Linux release. I'm going to visit one of our customers who had > this issue in a few weeks time, what news do I have for them? It depends on the exact tuning ("work-a-round") used. There has been an optimization related to disabling promotion to C1E state so using intel_idle.max_cstate=1 might give better results with SUSE Linux Enterprise Server 12 and remove the need to disable the intel_idle driver completely. It depends on the workload and CPU model in use. Other than that, the intel_idle driver and it's parameters should work the same in 12 as in 11 - meaning if c-states affect your workload, tuning of the intel_idle driver might be necessary. Best Regards, Scott -- Scott Bahling | Technical Account Manager - Team Lead +49 911-74053-121 | Mobile: +49 173-587-6977 | sbahling at suse.com SUSE Linux Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG Nuremberg) Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From Dick.Waite at softwareag.com Wed Jul 23 10:53:49 2014 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Wed, 23 Jul 2014 16:53:49 +0000 Subject: [sles-beta] Beta10 - Autoyast In-Reply-To: References: , Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D538787D3@hqmbx6.eur.ad.sag> Grand Day, Could you give us access to this bug please. ===> You are not authorized to access bug #886488 <==== I have been having X11 issues and a blank screen, very often reported and SR created but no answers, I would to see if this bugzilla could apply to me. I would have thought giving all of the Beta testers access to SLE12 Beta bugzilla's would be a friendly this to do, we are al sort-of under an NDA... __R ________________________________________ From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Johannes Meixner [jsmeix at suse.de] Sent: 23 July 2014 09:41 To: Ronny Pretzsch Cc: sles-beta at lists.suse.com Subject: Re: [sles-beta] Beta10 - Autoyast Hello, On Jul 22 13:32 Ronny Pretzsch wrote (excerpt): > Bad News: ... > (3) > We do not install X11 components. > Thus in Stage 2 yast should run in textmode. > But it runs in blank screen mode. > Next thing we see after reboot is the login prompt. FYI: Perhaps this one is somehow related: https://bugzilla.novell.com/show_bug.cgi?id=886488 Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From gjn at gjn.priv.at Wed Jul 23 11:57:15 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Wed, 23 Jul 2014 19:57:15 +0200 Subject: [sles-beta] Registration server Message-ID: <2014090.1Pmik5Nq0Z@gjn.priv.at> Hello, I have a Timed Out Error when I make a test Installation? -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From gregg at ricis.com Wed Jul 23 12:25:00 2014 From: gregg at ricis.com (Gregory D. Rosenberg) Date: Wed, 23 Jul 2014 13:25:00 -0500 Subject: [sles-beta] Registration server In-Reply-To: <2014090.1Pmik5Nq0Z@gjn.priv.at> References: <2014090.1Pmik5Nq0Z@gjn.priv.at> Message-ID: <25E89D7E-BAE0-4DBF-8EEA-19708E0DD3F6@ricis.com> Good afternoon G?nther, I can get the login page on SuSE?s Customer Center, but when I try to login it never completes the process. I think they use Net IQ for authentication, so it may be an issue that has to get fixed on the back-end. Uwe, is some one aware of this issue. Do we need to open SRs? Are you registering via YaST or using command line tools to register. In theory you can use SCC now instead of NCC. All NCC accounts were ported to SCC. It actually is a much nicer experience. https://scc.suse.com/login. In case it is of interest here are a couple of interesting links relating to the SCC APIs. http://www.rubydoc.info/github/SUSE/connect/frames/SUSE/Connect/Client https://github.com/SUSE/connect/wiki/SCC-API-RFC-(Draft) On Jul 23, 2014, at 12:57 CDT, G?nther J. Niederwimmer wrote: > Hello, > > I have a Timed Out Error when I make a test Installation? > > -- > mit freundlichen Gr??en / best Regards, > > G?nther J. Niederwimmer > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://cp.mcafee.com/d/1jWVIi4wUgdEInshpujoodTdETjsohuu7f6QrFKc8CzB5xASztwQsFCzBUQsI6zASztdNYQsFIcLCOcv8Agl6lFkVsT6lFkVsSMYettIO_R-oK-qerCzBDHTbELLnVN6WrX37bnhIyCGyyDOEuvkzaT0QSyrhdTdTdw0PVkDjGdQ_BY4RtxxYGjB1SKkf-xsxYZdQf-xsxYZbAaJMJZ0kvaAWthKDYKrppLsSqmW7_gKg-uCBQQg0LOcGjzIVlwq8av4PYjra9J0-AYab55LFI 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) From uwedr at suse.com Wed Jul 23 14:18:47 2014 From: uwedr at suse.com (Uwe Drechsel) Date: Wed, 23 Jul 2014 22:18:47 +0200 Subject: [sles-beta] Beta10 - Autoyast In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D538787D3@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D538787D3@hqmbx6.eur.ad.sag> Message-ID: <20140723201847.GL7429@suse.com> On Wed, Jul 23, Dick Waite wrote: > Grand Day, > > Could you give us access to this bug please. > ===> You are not authorized to access bug #886488 <==== > I have been having X11 issues and a blank screen, very often reported > and SR created but no answers, I would to see if this bugzilla could > apply to me. I would have thought giving all of the Beta testers > access to SLE12 Beta bugzilla's would be a friendly this to do, we are > al sort-of under an NDA... > Bugzillas access management is one of the not so usable things, especially in the currently used setup. Allowing all of you testers an easier access is something I have on the agenda for the next bigger beta test. So, sorry, for now the access is given individually by the support engineer who picks up the Service Request. And I just added you to this bug, please understand that I don't scale with adding everyone to every bug manually ;-) Thanks Uwe -- Uwe Drechsel Project Manager SUSE Linux Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From darrent at akurit.com.au Wed Jul 23 14:40:37 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Thu, 24 Jul 2014 06:40:37 +1000 Subject: [sles-beta] Beta10 - Autoyast In-Reply-To: <20140723201847.GL7429@suse.com> References: <46AC8C81C10B8C48820201DF2AE1D76D538787D3@hqmbx6.eur.ad.sag> <20140723201847.GL7429@suse.com> Message-ID: /Joke alert may I suggest photo copying yourself, my employer seems to think it solves all his staff scalability issues.... /Joke alert off On 24 July 2014 06:18, Uwe Drechsel wrote: > On Wed, Jul 23, Dick Waite wrote: > > > Grand Day, > > > > Could you give us access to this bug please. > > ===> You are not authorized to access bug #886488 <==== > > I have been having X11 issues and a blank screen, very often reported > > and SR created but no answers, I would to see if this bugzilla could > > apply to me. I would have thought giving all of the Beta testers > > access to SLE12 Beta bugzilla's would be a friendly this to do, we are > > al sort-of under an NDA... > > > > Bugzillas access management is one of the not so usable things, > especially in the currently used setup. Allowing all of you testers an > easier access is something I have on the agenda for the next bigger beta > test. > > So, sorry, for now the access is given individually by the support > engineer who picks up the Service Request. And I just added you to this > bug, please understand that I don't scale with adding everyone to every > bug manually ;-) > > > Thanks > Uwe > > -- > Uwe Drechsel > Project Manager > SUSE Linux Products GmbH > 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 > -- 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 -------------- 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 Dick.Waite at softwareag.com Thu Jul 24 00:43:49 2014 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Thu, 24 Jul 2014 06:43:49 +0000 Subject: [sles-beta] Problems installing SLES12 under VMware Workstation - Which Tools to use. Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D53878B5C@hqmbx6.eur.ad.sag> Yet Another grand Hot Day in Darmstadt, I have been asked by SUSE support to provide /var/log/Xorg.0.log. The virtual machine is not available to me at the moment so I had a look at a log from a clone of that type of QE machine. It has a lot of interaction with VMware Workstation and the grand Tools. Support can upgrade a KVM machine, I ran an upgrade on an old physical machine I "found" and that ran Okay. I am getting a much stronger feeling in my water that this one is going to come down to "VMware / Workstation / Tools" - interfacing with SLE12 I have not seen many words on the list, bar my own, about VMware / Workstation /Tools, could we have a show of hands on who is using this enviroment? Same question to SUSE I asked some time back. Which "Tools" should I use with SLE 12. Before the upgrade its happy running SLE11-SP3, VMware Workstation 10.0.3 and the Tools that go with that. We run the Update and have SLE12 with the same VMware Workstation but one see it wants to "refresh" the tools. What does one do..., the Tools are the same, or should I now use openSUSE tools? I understand VMware is a good business partner of SUSE, so I would have thought they are also part of this Beta, can they offer some words of wisdom here. It would be grand to have a SLE12 enviroment running before the first RC, then I can run some SAG Apps and create lots of SR's and check out the CUPS stuff the good SUSE gent was asking about. On zlinux we can not access "yast" after an update, that chap and many more will start their holidays on Friday, it?s the Start of the Hessen School holidays.... Any other good people on the list have a SLE11 update to SLE 12 running on zLinux. I do mean update not new_install. __R ___________________________________________ Dick Waite Senior R&D Consultant Phone: +49 6151 92-1505 Mobile: +49 171 8393 769 Software AG Uhlandstr. 12 | 64297 Darmstadt | Germany www.softwareag.com ___________________________________________ -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Simon Flood Sent: Thursday, July 17, 2014 1:57 PM To: 'sles-beta at lists.suse.com' Subject: Re: [sles-beta] Problems installing SLES12 under VMware Player On 17/07/2014 12:28, Waite, Dick wrote: > If I run a new install it's also grand, works as expected, it's only on an Upgrade I get the X11 / display issues with mice and keyboard, but it's Updates I need to get my Apps ready for testing. I'll try installing a basic SLES11 SP3 server then upgrading it. Whilst I normally install my servers as text-only I'll add a GUI. > While we are chatting, VMware Tools Update, when do you run this? Do you push the refresh button or run from the command line or? I have a feeling in the water something is not quite right in this area. The VMware log has quite a lot to say in a -ve way about what is going on. When you say VMware Tools Update do you mean the older VMware-provided Tools or the open-vm-tools that come with SLES12? I've not been doing anything special with my test VMs so currently my Beta 10 VM (under Player) has open-vm-tools automagically installed which Player seems happy with as the menu option is "Reinstall VMware Tools...". I'm guessing this is because the open-vm-tools are "later" than the VMware Tools - remember Player et al won't know about (i.e. support) SLES12 as it's beta and too new (perhaps support will be added with Workstation 11, Fusion 7, etc.?). HTH, Simon -- Simon Flood Senior Systems Specialist University of Cambridge United Kingdom Novell/SUSE/NetIQ Knowledge Partner _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From okir at suse.de Thu Jul 24 01:57:53 2014 From: okir at suse.de (Olaf Kirch) Date: Thu, 24 Jul 2014 09:57:53 +0200 Subject: [sles-beta] Beta10 - Autoyast In-Reply-To: References: <20140723201847.GL7429@suse.com> Message-ID: <201407240957.53952.okir@suse.de> On Wednesday 23 July 2014 22:40:37 Darren Thompson wrote: > may I suggest photo copying yourself, my employer seems to think it > solves all his staff scalability issues.... I tried that with a couple of people here at SUSE, but they wouldn't let me. And now you're telling me this doesn't work at all?!?! Bummer. Regards, Olaf -- Olaf Kirch - Director SUSE Linux Enterprise; R&D (okir at suse.com) SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From uwedr at suse.com Thu Jul 24 02:32:22 2014 From: uwedr at suse.com (Uwe Drechsel) Date: Thu, 24 Jul 2014 10:32:22 +0200 Subject: [sles-beta] Beta10 - Autoyast In-Reply-To: <201407240957.53952.okir@suse.de> References: <20140723201847.GL7429@suse.com> <201407240957.53952.okir@suse.de> Message-ID: <20140724083222.GP7429@suse.com> On Thu, Jul 24, Olaf Kirch wrote: > On Wednesday 23 July 2014 22:40:37 Darren Thompson wrote: > > may I suggest photo copying yourself, my employer seems to think it > > solves all his staff scalability issues.... > > I tried that with a couple of people here at SUSE, but they wouldn't > let me. And now you're telling me this doesn't work at all?!?! > Hm, maybe it *did* work? ;-) -Uwe -- ?There is a theory which states that if ever anyone discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable. There is another theory which states that this has already happened.? D. Adams From lmb at suse.com Thu Jul 24 02:37:53 2014 From: lmb at suse.com (Lars Marowsky-Bree) Date: Thu, 24 Jul 2014 10:37:53 +0200 Subject: [sles-beta] Problems with XFS over Logical Volume In-Reply-To: References: Message-ID: <20140724083753.GD32013@suse.de> On 2014-07-23T16:01:39, Bonazzoli Giandomenico - Technogym SPA wrote: > I think that very is a huge hole in SLES 12 beta10 using XFS over a logical volume: > > This is the vmstat that shows performance problems, and it happens also that the server need to bee rebooted because after some minutes the file system hangs. What disks are you using? Are you writing to the same disk you're reading from? USB, iSCSI, ...? > P.S. : The "terrible" load is generated by a simple gzip -d edwh.dmp.gz How big is that file? How does it perform if you instead write the output to "nowhere" (gzip -dc edwu.dmp.gz >/dev/null)? 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 wstephenson at suse.de Thu Jul 24 03:00:19 2014 From: wstephenson at suse.de (Will Stephenson) Date: Thu, 24 Jul 2014 11:00:19 +0200 Subject: [sles-beta] Registration server In-Reply-To: <25E89D7E-BAE0-4DBF-8EEA-19708E0DD3F6@ricis.com> References: <2014090.1Pmik5Nq0Z@gjn.priv.at> <25E89D7E-BAE0-4DBF-8EEA-19708E0DD3F6@ricis.com> Message-ID: <2710533.SbpGL0KamM@whistler.site> On Wednesday 23 Jul 2014 13:25:00 Gregory D. Rosenberg wrote: > I can get the login page on SuSE?s Customer Center, but when I try to login > it never completes the process. I think they use Net IQ for authentication, > so it may be an issue that has to get fixed on the back-end. > > Uwe, is some one aware of this issue. Do we need to open SRs? Gregory, can you login to other 'netiq'-authenticated sites, eg bugzilla.novell.com? When you say 'never', does that signify this is not a transient error when logging in to scc.suse.com? Will (SCC Engineer) From wstephenson at suse.de Thu Jul 24 03:01:20 2014 From: wstephenson at suse.de (Will Stephenson) Date: Thu, 24 Jul 2014 11:01:20 +0200 Subject: [sles-beta] Registration server In-Reply-To: <2014090.1Pmik5Nq0Z@gjn.priv.at> References: <2014090.1Pmik5Nq0Z@gjn.priv.at> Message-ID: <4485932.nE4oneL9Q8@whistler.site> On Wednesday 23 Jul 2014 19:57:15 G?nther J. Niederwimmer wrote: > I have a Timed Out Error when I make a test Installation? If this isn't a transient error, please make a bug report. Will From gbonazzoli at technogym.com Thu Jul 24 03:17:54 2014 From: gbonazzoli at technogym.com (Bonazzoli Giandomenico - Technogym SPA) Date: Thu, 24 Jul 2014 09:17:54 +0000 Subject: [sles-beta] R: Problems with XFS over Logical Volume In-Reply-To: <20140724083753.GD32013@suse.de> References: <20140724083753.GD32013@suse.de> Message-ID: Q: What disks are you using? It is an hardware raid5 group of 4 SAS disks 15.000 rpm Q: Are you writing to the same disk you're reading from? YES Q: USB, iSCSI, ...? SAS Q: How big is that file? Uncompressed 108511993856 Q: How does it perform if you instead write the output to "nowhere" (gzip -dc edwu.dmp.gz >/dev/null)? I gave the following command instead: cat edwh.dmp > /dev/null # OK 400MB/s and the file system esponds well cat edwh.dmp > a.a # 20MB/s in write and the file system is extremely slow to espond dd if=edwh.dmp of=a.a bs=8192 # 18066702336 bytes (18 GB) copied, 55,8945 s, 323 MB/s .... but file system doesn't respond well cat edwh.dmp | gzip -c > a.a # hangs... it takes minutes to process Control-C -----Messaggio originale----- Da: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Per conto di Lars Marowsky-Bree Inviato: gioved? 24 luglio 2014 10:38 A: sles-beta at lists.suse.com Oggetto: Re: [sles-beta] Problems with XFS over Logical Volume On 2014-07-23T16:01:39, Bonazzoli Giandomenico - Technogym SPA wrote: > I think that very is a huge hole in SLES 12 beta10 using XFS over a logical volume: > > This is the vmstat that shows performance problems, and it happens also that the server need to bee rebooted because after some minutes the file system hangs. What disks are you using? Are you writing to the same disk you're reading from? USB, iSCSI, ...? > P.S. : The "terrible" load is generated by a simple gzip -d > edwh.dmp.gz How big is that file? How does it perform if you instead write the output to "nowhere" (gzip -dc edwu.dmp.gz >/dev/null)? 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 _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From martin.wilck at ts.fujitsu.com Thu Jul 24 03:45:17 2014 From: martin.wilck at ts.fujitsu.com (Martin Wilck) Date: Thu, 24 Jul 2014 11:45:17 +0200 Subject: [sles-beta] Activating IPMI devices /dev/ipmi0 etc. automatically Message-ID: <53D0D5AD.6080503@ts.fujitsu.com> What is the preferred method of activating IPMI devices in SLES12? Do the ipmitool and/or freeipmi packages need to be installed? Is it necessary to enable any of the services provided by these packagese manually? On some other distros, I have seen is the following code allowing automatic activation of IPMI-capable hardware via udev: /etc/modprobe.d/ipmi.conf alias acpi:IPI000*:* ipmi_si alias acpi:IPI000*:* ipmi_devintf alias acpi:IPI000*:* ipmi_msghandler Is there anything similar on SLES12? Martin -- Dr. Martin Wilck PRIMERGY System Software Engineer x86 Server Engineering FUJITSU Fujitsu Technology Solutions GmbH Heinz-Nixdorf-Ring 1 33106 Paderborn, Germany Phone: ++49 5251 525 2796 Fax: ++49 5251 525 2820 Email: martin.wilck at ts.fujitsu.com Internet: http://ts.fujitsu.com Company Details: http://ts.fujitsu.com/imprint From sbahling at suse.com Thu Jul 24 06:01:02 2014 From: sbahling at suse.com (Scott Bahling) Date: Thu, 24 Jul 2014 14:01:02 +0200 Subject: [sles-beta] intel_idle In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D53878776@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D538778AF@hqmbx6.eur.ad.sag> ,<1406110143.22894.299.camel@hermano.suse.de> <46AC8C81C10B8C48820201DF2AE1D76D53878776@hqmbx6.eur.ad.sag> Message-ID: <1406203262.22894.323.camel@hermano.suse.de> On Wed, 2014-07-23 at 16:44 +0000, Waite, Dick wrote: > Many Thanks for the update Scott. A couple / few of customers did not > like the idea of having to amend the boot parm and at the time some > words were written about using in a later kernel, syscntl.conf which > customers preferred over amending boot as their system providers > charged extra... Starting with SLES 11 SP3 (latest updates) the cpupower command will allow to dynamically control the idle states via command line at run time. This is a better option than the kernel parameter. It's recommended to test with disabling only the highest c-states until the desired performance/latency is achieved. Disabling too many c-states can have adverse affects. > If the parm was not in boot then I think more customers would be > willing to amend this value, I wonder how many customer get better > results with the default, do you have any numbers? I'm not sure what kind of numbers you mean. Better results depends on workload requirements related to latency and performance/watt. The results depend on the exact hardware in use as each CPU and platform comes with it's own power vs performance features and behavioral profiles. For instance, disabling certain c-states can disable turbo-boost functionality in modern CPUs which could rob some workloads of a potential performance boost. For a majority of workloads out there, the defaults should be just fine. For those workloads that need extra attention to either performance or power efficiency, tuning is necessary. -Scott > __R > ________________________________________ > From: Scott Bahling [sbahling at suse.com] > Sent: 23 July 2014 12:09 > To: Waite, Dick > Cc: sles-beta at lists.suse.com > Subject: Re: [sles-beta] intel_idle > > On Wed, 2014-07-23 at 06:55 +0000, Waite, Dick wrote: > > Grand Day, > > > > When running some SLES11 on X86_64 sites some time ago the "batch" > > jobs were taking 30-50% more wall clock time. After some time a > > work-a-round was found to amend the "Intel_Idle" parm. There was some > > chatter at the time that a "better" fix would be available with a > > later Linux release. I'm going to visit one of our customers who had > > this issue in a few weeks time, what news do I have for them? > > It depends on the exact tuning ("work-a-round") used. > > There has been an optimization related to disabling promotion to C1E > state so using intel_idle.max_cstate=1 might give better results with > SUSE Linux Enterprise Server 12 and remove the need to disable the > intel_idle driver completely. It depends on the workload and CPU model > in use. > > Other than that, the intel_idle driver and it's parameters should work > the same in 12 as in 11 - meaning if c-states affect your workload, > tuning of the intel_idle driver might be necessary. > > Best Regards, > > Scott > > -- > Scott Bahling | Technical Account Manager - Team Lead > +49 911-74053-121 | Mobile: +49 173-587-6977 | sbahling at suse.com > SUSE Linux Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG Nuremberg) > > > Software AG Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com > From wstephenson at suse.de Thu Jul 24 06:07:37 2014 From: wstephenson at suse.de (Will Stephenson) Date: Thu, 24 Jul 2014 14:07:37 +0200 Subject: [sles-beta] Registration server In-Reply-To: <2710533.SbpGL0KamM@whistler.site> References: <2014090.1Pmik5Nq0Z@gjn.priv.at> <25E89D7E-BAE0-4DBF-8EEA-19708E0DD3F6@ricis.com> <2710533.SbpGL0KamM@whistler.site> Message-ID: <6216558.lqCBbLqjRn@whistler.site> On Thursday 24 Jul 2014 11:00:19 Will Stephenson wrote: > On Wednesday 23 Jul 2014 13:25:00 Gregory D. Rosenberg wrote: > > I can get the login page on SuSE?s Customer Center, but when I try to > > login > > it never completes the process. I think they use Net IQ for > > authentication, > > so it may be an issue that has to get fixed on the back-end. > > > > Uwe, is some one aware of this issue. Do we need to open SRs? > > Gregory, can you login to other 'netiq'-authenticated sites, eg > bugzilla.novell.com? > > When you say 'never', does that signify this is not a transient error when > logging in to scc.suse.com? > Is it this error? " Error:Unable to complete request at this time. (SAML Subject NameIdentifier missing required NameIdentifier value-****) " Will From gjn at gjn.priv.at Thu Jul 24 08:28:42 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Thu, 24 Jul 2014 16:28:42 +0200 Subject: [sles-beta] Registration server In-Reply-To: <6216558.lqCBbLqjRn@whistler.site> References: <2014090.1Pmik5Nq0Z@gjn.priv.at> <2710533.SbpGL0KamM@whistler.site> <6216558.lqCBbLqjRn@whistler.site> Message-ID: <2782143.x8bZjniZAU@gjn.priv.at> Hello, Am Donnerstag, 24. Juli 2014, 14:07:37 schrieb Will Stephenson: > On Thursday 24 Jul 2014 11:00:19 Will Stephenson wrote: > > On Wednesday 23 Jul 2014 13:25:00 Gregory D. Rosenberg wrote: > > > I can get the login page on SuSE?s Customer Center, but when I try to > > > login > > > it never completes the process. I think they use Net IQ for > > > authentication, > > > so it may be an issue that has to get fixed on the back-end. > > > > > > Uwe, is some one aware of this issue. Do we need to open SRs? > > > > Gregory, can you login to other 'netiq'-authenticated sites, eg > > bugzilla.novell.com? > > > > When you say 'never', does that signify this is not a transient error when > > logging in to scc.suse.com? > > Is it this error? > > " > Error:Unable to complete request at this time. (SAML Subject NameIdentifier > missing required NameIdentifier value-****) > " Today I can register again. -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From gjn at gjn.priv.at Thu Jul 24 08:21:18 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Thu, 24 Jul 2014 16:21:18 +0200 Subject: [sles-beta] Init3 Init5 broken again Message-ID: <1847787.hloxxQZ05N@gjn.priv.at> Hello, is this known in Beta 10 is graphic / multi-user broken again by the installation? -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From kukuk at suse.de Thu Jul 24 08:32:45 2014 From: kukuk at suse.de (Thorsten Kukuk) Date: Thu, 24 Jul 2014 16:32:45 +0200 Subject: [sles-beta] Init3 Init5 broken again In-Reply-To: <1847787.hloxxQZ05N@gjn.priv.at> References: <1847787.hloxxQZ05N@gjn.priv.at> Message-ID: <20140724143245.GA29870@suse.de> On Thu, Jul 24, G?nther J. Niederwimmer wrote: > Hello, > > is this known in Beta 10 is graphic / multi-user broken again by the > installation? Don't know what you mean with graphic/multi-user broken again, init 3, init 5, etc works fine for me on Beta10. 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 Dick.Waite at softwareag.com Thu Jul 24 08:58:26 2014 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Thu, 24 Jul 2014 14:58:26 +0000 Subject: [sles-beta] Problems Updateing SLES11 to SLES12 under VMware Workstation - Tools Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D53878FC4@hqmbx6.eur.ad.sag> Grand Sunny Afternoon, I think we are getting somewhere... Support asked me to give them the /var/log/Xorg.... logs Having a look inside the logs there is a real old fight going on about the vmware mouse and keyboard. There are not acceptable to the SLE12 system, but happy as Larry with SLE11... I'm very surprised the VMware Beta testers did not have these issues... Anyway maybe there is light at then end of this tunnel. I think it's going to be too late to get are APPs tested with SLE12-SP0, but it does give us something to work on for SLE12-SP1. Seem support is happy with the files, always grand to keep support happy. __R ________________________________________ From: Waite, Dick Sent: 17 July 2014 13:28 To: 'Simon Flood'; 'sles-beta at lists.suse.com' Subject: RE: [sles-beta] Problems installing SLES12 under VMware Player Hi Simon, If I run a new install it's also grand, works as expected, it's only on an Upgrade I get the X11 / display issues with mice and keyboard, but it's Updates I need to get my Apps ready for testing. While we are chatting, VMware Tools Update, when do you run this? Do you push the refresh button or run from the command line or? I have a feeling in the water something is not quite right in this area. The VMware log has quite a lot to say in a -ve way about what is going on. __R ___________________________________________ Dick Waite Senior R&D Consultant Phone: +49 6151 92-1505 Mobile: +49 171 8393 769 Software AG Uhlandstr. 12 | 64297 Darmstadt | Germany www.softwareag.com ___________________________________________ -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Simon Flood Sent: Thursday, July 17, 2014 1:22 PM To: sles-beta at lists.suse.com Subject: Re: [sles-beta] Problems installing SLES12 under VMware Player On 20/06/2014 14:54, Simon Flood wrote: > Odd. Very odd. Just thought I'd report that Beta 10 seems to be okay under VMware Player 6.0.3 - I've installed it then restarted and shut down, making a few small changes in between, and it's behaved correctly. Now to try a few things out. Thanks, Simon -- Simon Flood Senior Systems Specialist University of Cambridge United Kingdom Novell/SUSE/NetIQ Knowledge Partner _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com From gjn at gjn.priv.at Thu Jul 24 09:16:49 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Thu, 24 Jul 2014 17:16:49 +0200 Subject: [sles-beta] Init3 Init5 broken again In-Reply-To: <20140724143245.GA29870@suse.de> References: <1847787.hloxxQZ05N@gjn.priv.at> <20140724143245.GA29870@suse.de> Message-ID: <1801296.7EV9jHHxCq@gjn.priv.at> Hello, Am Donnerstag, 24. Juli 2014, 16:32:45 schrieb Thorsten Kukuk: > On Thu, Jul 24, G?nther J. Niederwimmer wrote: > > Hello, > > > > is this known in Beta 10 is graphic / multi-user broken again by the > > installation? > > Don't know what you mean with graphic/multi-user broken > again, init 3, init 5, etc works fine for me on Beta10. When I Install a new system and select multi-user in the YaST2 config, after reboot the system boot into graphic (init 5) mode -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From gregg at ricis.com Thu Jul 24 10:04:14 2014 From: gregg at ricis.com (Gregory D. Rosenberg) Date: Thu, 24 Jul 2014 11:04:14 -0500 Subject: [sles-beta] Registration server In-Reply-To: <2710533.SbpGL0KamM@whistler.site> References: <2014090.1Pmik5Nq0Z@gjn.priv.at> <25E89D7E-BAE0-4DBF-8EEA-19708E0DD3F6@ricis.com> <2710533.SbpGL0KamM@whistler.site> Message-ID: <1C42A201-A4DF-4296-B4C7-C55A585ADD67@ricis.com> On Jul 24, 2014, at 04:00 CDT, Will Stephenson wrote: > On Wednesday 23 Jul 2014 13:25:00 Gregory D. Rosenberg wrote: >> I can get the login page on SuSE?s Customer Center, but when I try to login >> it never completes the process. I think they use Net IQ for authentication, >> so it may be an issue that has to get fixed on the back-end. >> >> Uwe, is some one aware of this issue. Do we need to open SRs? > > Gregory, can you login to other 'netiq'-authenticated sites, eg > bugzilla.novell.com? Yes I can login to buzilla, in fact this morning I am able to get into SCC as well. > > When you say 'never', does that signify this is not a transient error when > logging in to scc.suse.com? > > Will > > (SCC Engineer) > 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) From gjn at gjn.priv.at Thu Jul 24 11:05:45 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Thu, 24 Jul 2014 19:05:45 +0200 Subject: [sles-beta] Warning: cpu 0 offline? Message-ID: <2086359.KzpLVZsq9Z@gjn.priv.at> Hello, I have found this in my messages log mcelog[1716]: mcelog: Warning: cpu 0 offline?, imc_log not set Is this a "normal" message or a bug ? -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From darrent at akurit.com.au Thu Jul 24 16:08:10 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Fri, 25 Jul 2014 08:08:10 +1000 Subject: [sles-beta] Init3 Init5 broken again In-Reply-To: <1801296.7EV9jHHxCq@gjn.priv.at> References: <1847787.hloxxQZ05N@gjn.priv.at> <20140724143245.GA29870@suse.de> <1801296.7EV9jHHxCq@gjn.priv.at> Message-ID: G?nther/team I was not sure it had been fixed yet. Here is the bug report https://bugzilla.novell.com/show_bug.cgi?id=882886 Darren On 25 July 2014 01:16, G?nther J. wrote: > Hello, > > Am Donnerstag, 24. Juli 2014, 16:32:45 schrieb Thorsten Kukuk: > > On Thu, Jul 24, G?nther J. Niederwimmer wrote: > > > Hello, > > > > > > is this known in Beta 10 is graphic / multi-user broken again by the > > > installation? > > > > Don't know what you mean with graphic/multi-user broken > > again, init 3, init 5, etc works fine for me on Beta10. > > When I Install a new system and select multi-user in the YaST2 config, > after > reboot the system boot into graphic (init 5) mode > > -- > 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 > -- 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 -------------- 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 darrent at akurit.com.au Thu Jul 24 16:16:27 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Fri, 25 Jul 2014 08:16:27 +1000 Subject: [sles-beta] Changing "run level" post built (Going from Graphical to text and vice versa) Message-ID: Team I posted this some time ago. The process to change run levels from "graphical" (init 5) to "Multi-user (init 3) in a server "post build". I still have not successfully "built" a server that install/starts in "Muti-user" mode. Darren On 18 June 2014 18:13, Darren Thompson wrote: > Frederic > > Good Point... > > Team, do it the way he says... ;-) > > e.g. > > 1. Login to graphical console as root user. > 2. run a "terminal" session (the yast service manager process is currently > broken, it would be Best/easier to just run that). > 3. systemctl set-default --force multi-user.target > - This will "tell" systemd that you want to run in "multi-user" mode (e.g. > the old init 3 level, without a X-server/GUI). > *** reboot *** > 4 shutdown -r now > (you can achieve the same result by typing: 'init 3' if you prefer not to > reboot). > > > If you want to reverse this and run the full "graphical" (X) console again > 1. Login to test console as root user. > 2. systemctl set-default --force graphical.target > - This will "tell" systemd that you want to run in "Graphical" mode (e.g. > the old init 5 level, with a X-server/GUI). > *** reboot *** > 4 shutdown -r now > (you can achieve the same result by typing: 'init 5' if you prefer not to > reboot). > > I hope this is found to be helpful. > > Darren > > > > > > > > > > On 18 June 2014 17:52, Frederic Crozat wrote: > >> Le mercredi 18 juin 2014 ? 10:50 +1000, Darren Thompson a ?crit : >> > Team >> > >> > >> > I have been doing some testing on getting a "default graphical build" >> > SLES12B8 server to become a "multi-user" server. >> > >> > >> > It's harder than you would think, mainly due to the way >> > display-server.service seems to be erroneously activated, even on >> > multi-user target boots. >> > >> > >> > I have found this process works: >> > 1. Login to graphical console as root user. >> > 2. run a "terminal" session (the yast service manager process is >> > currently broken, it would be Bets/easier to just run that). >> > 3. cd /etc/systemd/system >> > 4. rm default.target >> > 5. ln -s /usr/lib/systemd/system/multi-user.target default.target >> > 6. cd /usr/lib/systemd/user >> > 7. rm default.target >> > 8. ln -s /usr/lib/systemd/system/multi-user.target default.target >> > 9. cd /usr/lib/systemd/system >> > 10. rm default.target >> > 11. ln -s /usr/lib/systemd/system/multi-user.target default.target >> > **** I have no idea why default.target is in these three locations, I >> > would expect 2 of them are redundant but am not familiar enough with >> > systemd to guess which **** >> >> Sorry but you are doing this the wrong way. >> >> NEVER ever change stuff in /usr/lib/systemd/system. /etc/systemd/system >> has ALWAYS precedence over /usr/lib/systemd/system, which means file >> with the same name in /etc/systemd/system will "hide" the one >> in /usr/lib/systemd/system. >> >> The proper way to do it is : >> run as root: systemctl set-default --force multi-user.target >> >> (or if you want to do it manually: ln -s >> -f /usr/lib/systemd/system/multi-user.target >> /etc/systemd/system/default.target) >> >> That's it. >> >> -- >> Frederic Crozat >> Project Manager Enterprise Desktop >> SUSE >> >> _______________________________________________ >> sles-beta mailing list >> sles-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sles-beta >> > > > > -- > > 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 > -- 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 -------------- 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 jsavanyo at vmware.com Thu Jul 24 18:45:09 2014 From: jsavanyo at vmware.com (John Savanyo) Date: Fri, 25 Jul 2014 00:45:09 +0000 Subject: [sles-beta] Problems installing SLES12 under VMware Workstation - Which Tools to use. In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D53878B5C@hqmbx6.eur.ad.sag> Message-ID: VMware is in the process of transitioning to a fully open-source model for drivers and tools and distribution of same through OS distros. You can read more about details in these KB articles: http://kb.vmware.com/kb/2073803 http://kb.vmware.com/kb/2073804 Compared to SLES 11 SP3, SLES 12 adds 3 additional kernel modules/drivers (vmwgfx, vmci and vsock) and also adds open-vm-tools (OVT). SLES 12 now includes the full set of 6 kernel and 2 xorg drivers supported by vSphere/ESXi. (Workstation/Fusion products have an additional kernel driver vmhgfs, but is not used on vSphere/ESXi) We recommend using open-vm-tools and the drivers distributed by SUSE in SLES12. Although, during the transition period you can also use the legacy Vmware tools that are bundled with each Vmware product if you find that they work better for you. If you are mostly working on server workloads, then SLES12 should include all the drivers and tools (OVT) you should need. If you are using Workstation/Fusion and require a more rich desktop experience, then you likely will need to wait for a future release of Workstation/Fusion that publishes support for SLES12 and try to use the legacy bundled tools bundled with that product. -John On 7/23/14, 11:43 PM, "Waite, Dick" wrote: >Yet Another grand Hot Day in Darmstadt, > >I have been asked by SUSE support to provide /var/log/Xorg.0.log. The >virtual machine is not available to me at the moment so I had a look at a >log from a clone of that type of QE machine. It has a lot of interaction >with VMware Workstation and the grand Tools. > >Support can upgrade a KVM machine, I ran an upgrade on an old physical >machine I "found" and that ran Okay. I am getting a much stronger feeling >in my water that this one is going to come down to "VMware / Workstation >/ Tools" - interfacing with SLE12 > >I have not seen many words on the list, bar my own, about VMware / >Workstation /Tools, could we have a show of hands on who is using this >enviroment? > >Same question to SUSE I asked some time back. Which "Tools" should I use >with SLE 12. Before the upgrade its happy running SLE11-SP3, VMware >Workstation 10.0.3 and the Tools that go with that. We run the Update and >have SLE12 with the same VMware Workstation but one see it wants to >"refresh" the tools. What does one do..., the Tools are the same, or >should I now use openSUSE tools? > >I understand VMware is a good business partner of SUSE, so I would have >thought they are also part of this Beta, can they offer some words of >wisdom here. It would be grand to have a SLE12 enviroment running before >the first RC, then I can run some SAG Apps and create lots of SR's and >check out the CUPS stuff the good SUSE gent was asking about. > >On zlinux we can not access "yast" after an update, that chap and many >more will start their holidays on Friday, it?s the Start of the Hessen >School holidays.... Any other good people on the list have a SLE11 update >to SLE 12 running on zLinux. I do mean update not new_install. > >__R > >___________________________________________ >Dick Waite >Senior R&D Consultant >Phone: +49 6151 92-1505 >Mobile: +49 171 8393 769 >Software AG >Uhlandstr. 12 | 64297 Darmstadt | Germany >www.softwareag.com >___________________________________________ > > > > >-----Original Message----- >From: sles-beta-bounces at lists.suse.com >[mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Simon Flood >Sent: Thursday, July 17, 2014 1:57 PM >To: 'sles-beta at lists.suse.com' >Subject: Re: [sles-beta] Problems installing SLES12 under VMware Player > >On 17/07/2014 12:28, Waite, Dick wrote: > >> If I run a new install it's also grand, works as expected, it's only on >>an Upgrade I get the X11 / display issues with mice and keyboard, but >>it's Updates I need to get my Apps ready for testing. > >I'll try installing a basic SLES11 SP3 server then upgrading it. Whilst I >normally install my servers as text-only I'll add a GUI. > >> While we are chatting, VMware Tools Update, when do you run this? Do >>you push the refresh button or run from the command line or? I have a >>feeling in the water something is not quite right in this area. The >>VMware log has quite a lot to say in a -ve way about what is going on. > >When you say VMware Tools Update do you mean the older VMware-provided >Tools or the open-vm-tools that come with SLES12? > >I've not been doing anything special with my test VMs so currently my >Beta 10 VM (under Player) has open-vm-tools automagically installed which >Player seems happy with as the menu option is "Reinstall VMware >Tools...". I'm guessing this is because the open-vm-tools are "later" >than the VMware Tools - remember Player et al won't know about (i.e. >support) SLES12 as it's beta and too new (perhaps support will be added >with Workstation 11, Fusion 7, etc.?). > >HTH, >Simon >-- >Simon Flood >Senior Systems Specialist >University of Cambridge >United Kingdom > >Novell/SUSE/NetIQ Knowledge Partner >_______________________________________________ >sles-beta mailing list >sles-beta at lists.suse.com >http://lists.suse.com/mailman/listinfo/sles-beta > >Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, >Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - >Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), >Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of >the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com > >_______________________________________________ >sles-beta mailing list >sles-beta at lists.suse.com >http://lists.suse.com/mailman/listinfo/sles-beta From darrent at akurit.com.au Thu Jul 24 19:09:45 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Fri, 25 Jul 2014 11:09:45 +1000 Subject: [sles-beta] Changing "run level" post built (Going from Graphical to text and vice versa) In-Reply-To: References: Message-ID: Gregory Thanks for replying. I'm aware that both init 3 and init 5 are "multi-user" Since SLES12 is now using systemd as the 'init' system, the old "run levels, e.g. Init 3, init 5 etc" do no longer actually exist. Instead there are now "target run levels" The "fully graphical" target level (functionally equivalent to the old init 5 level) is now called "GUI.target" The "fully networked but command shell only" target level (functionally equivilent to the old init 3 level) in now called "muti-user.target" It is in this context that I use the terms "GUI" and "Muti-user" The previous email was the process to change the default "target run level" But in any case, the build process for a machine that is installed/run only at "multi-user" target level is still not correct 9I have not fully tested SLES12B10 yet so this could have changed). I centrainly could not get a reliable "muli-user target: build running with autoyast. Regards Darren On 25 July 2014 09:53, Gregory D. Rosenberg wrote: > Darren, > > Even graphical mode is still multi-user. It is just multi-user with > X-windows. All my servers are running in run level 3. I can?t say that I > have tried to build one from scratch to start in run level 3. We have > certainly done that with SLES 11 SP3 using autoyast. I will take a closer > look at the installer tomorrow and see what I can discover and let you know. > > On Jul 24, 2014, at 17:16 CDT, Darren Thompson > wrote: > > Team > > I posted this some time ago. The process to change run levels from > "graphical" (init 5) to "Multi-user (init 3) in a server "post build". > > I still have not successfully "built" a server that install/starts in > "Muti-user" mode. > > Darren > > > On 18 June 2014 18:13, Darren Thompson wrote: > >> Frederic >> >> Good Point... >> >> Team, do it the way he says... ;-) >> >> e.g. >> >> 1. Login to graphical console as root user. >> 2. run a "terminal" session (the yast service manager process is currently >> broken, it would be Best/easier to just run that). >> 3. systemctl set-default --force multi-user.target >> - This will "tell" systemd that you want to run in "multi-user" mode >> (e.g. the old init 3 level, without a X-server/GUI). >> *** reboot *** >> 4 shutdown -r now >> (you can achieve the same result by typing: 'init 3' if you prefer not to >> reboot). >> >> >> If you want to reverse this and run the full "graphical" (X) console again >> 1. Login to test console as root user. >> 2. systemctl set-default --force graphical.target >> - This will "tell" systemd that you want to run in "Graphical" mode (e.g. >> the old init 5 level, with a X-server/GUI). >> *** reboot *** >> 4 shutdown -r now >> (you can achieve the same result by typing: 'init 5' if you prefer not to >> reboot). >> >> I hope this is found to be helpful. >> >> Darren >> >> >> >> >> >> >> >> >> >> On 18 June 2014 17:52, Frederic Crozat wrote: >> >>> Le mercredi 18 juin 2014 ? 10:50 +1000, Darren Thompson a ?crit : >>> > Team >>> > >>> > >>> > I have been doing some testing on getting a "default graphical build" >>> > SLES12B8 server to become a "multi-user" server. >>> > >>> > >>> > It's harder than you would think, mainly due to the way >>> > display-server.service seems to be erroneously activated, even on >>> > multi-user target boots. >>> > >>> > >>> > I have found this process works: >>> > 1. Login to graphical console as root user. >>> > 2. run a "terminal" session (the yast service manager process is >>> > currently broken, it would be Bets/easier to just run that). >>> > 3. cd /etc/systemd/system >>> > 4. rm default.target >>> > 5. ln -s /usr/lib/systemd/system/multi-user.target default.target >>> > 6. cd /usr/lib/systemd/user >>> > 7. rm default.target >>> > 8. ln -s /usr/lib/systemd/system/multi-user.target default.target >>> > 9. cd /usr/lib/systemd/system >>> > 10. rm default.target >>> > 11. ln -s /usr/lib/systemd/system/multi-user.target default.target >>> > **** I have no idea why default.target is in these three locations, I >>> > would expect 2 of them are redundant but am not familiar enough with >>> > systemd to guess which **** >>> >>> Sorry but you are doing this the wrong way. >>> >>> NEVER ever change stuff in /usr/lib/systemd/system. /etc/systemd/system >>> has ALWAYS precedence over /usr/lib/systemd/system, which means file >>> with the same name in /etc/systemd/system will "hide" the one >>> in /usr/lib/systemd/system. >>> >>> The proper way to do it is : >>> run as root: systemctl set-default --force multi-user.target >>> >>> (or if you want to do it manually: ln -s >>> -f /usr/lib/systemd/system/multi-user.target >>> /etc/systemd/system/default.target) >>> >>> That's it. >>> >>> -- >>> Frederic Crozat >>> Project Manager Enterprise Desktop >>> SUSE >>> >>> _______________________________________________ >>> sles-beta mailing list >>> sles-beta at lists.suse.com >>> http://lists.suse.com/mailman/listinfo/sles-beta >>> >>> >> >> >> >> -- >> >> 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 >> >> > > > > -- > > 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 > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > > http://cp.mcafee.com/d/k-Kr40USyNtNdyXZQPtPqdQT64nDxPNJ6Wrz29EVhopdETod7apEVud7b1EVdETjsvd7ar3bVIz7O945hBqlendNBqlendLKKf8EcLZvANPX3zbfnKnjphsVxdeZXzKmKzp5dmZQul3PWApmU6CQjq9KVKVI06vaAWthKDYLwCHIcfBisEeROx_QbAfDFKx_QbAfDFsxlK5LE2zVkDjGdQ_BPqqrapEVdCBKx_QbAfDFFtd40AjS16k29Ewd4kmU6y0_PfDCy8QgblFcQg46V7Pd41EE2lpg8Cy1Sdljh04EWIjBrjPh1eFEwDUvcQgr10Qg6pmYQg6vzjjhirud79Jd3V > > > > > 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) > > > > -- 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 -------------- 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 darrent at akurit.com.au Thu Jul 24 19:12:44 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Fri, 25 Jul 2014 11:12:44 +1000 Subject: [sles-beta] Changing "run level" post built (Going from Graphical to text and vice versa) In-Reply-To: References: Message-ID: Dolt Please allow for typos etc.... also factual error, when I said "GUI.target" I actually meant "Graphical.target" I really should start proof reading before clicking the "send button" ;-) Darren On 25 July 2014 11:09, Darren Thompson wrote: > Gregory > > Thanks for replying. > > I'm aware that both init 3 and init 5 are "multi-user" > > Since SLES12 is now using systemd as the 'init' system, the old "run > levels, e.g. Init 3, init 5 etc" do no longer actually exist. Instead > there are now "target run levels" > > The "fully graphical" target level (functionally equivalent to the old > init 5 level) is now called "GUI.target" > The "fully networked but command shell only" target level (functionally > equivilent to the old init 3 level) in now called "muti-user.target" > > It is in this context that I use the terms "GUI" and "Muti-user" > > The previous email was the process to change the default "target run level" > > But in any case, the build process for a machine that is installed/run > only at "multi-user" target level is still not correct 9I have not fully > tested SLES12B10 yet so this could have changed). I centrainly could not > get a reliable "muli-user target: build running with autoyast. > > Regards > Darren > > > > On 25 July 2014 09:53, Gregory D. Rosenberg wrote: > >> Darren, >> >> Even graphical mode is still multi-user. It is just multi-user with >> X-windows. All my servers are running in run level 3. I can?t say that I >> have tried to build one from scratch to start in run level 3. We have >> certainly done that with SLES 11 SP3 using autoyast. I will take a closer >> look at the installer tomorrow and see what I can discover and let you know. >> >> On Jul 24, 2014, at 17:16 CDT, Darren Thompson >> wrote: >> >> Team >> >> I posted this some time ago. The process to change run levels from >> "graphical" (init 5) to "Multi-user (init 3) in a server "post build". >> >> I still have not successfully "built" a server that install/starts in >> "Muti-user" mode. >> >> Darren >> >> >> On 18 June 2014 18:13, Darren Thompson wrote: >> >>> Frederic >>> >>> Good Point... >>> >>> Team, do it the way he says... ;-) >>> >>> e.g. >>> >>> 1. Login to graphical console as root user. >>> 2. run a "terminal" session (the yast service manager process is currently >>> broken, it would be Best/easier to just run that). >>> 3. systemctl set-default --force multi-user.target >>> - This will "tell" systemd that you want to run in "multi-user" mode >>> (e.g. the old init 3 level, without a X-server/GUI). >>> *** reboot *** >>> 4 shutdown -r now >>> (you can achieve the same result by typing: 'init 3' if you prefer not >>> to reboot). >>> >>> >>> If you want to reverse this and run the full "graphical" (X) console >>> again >>> 1. Login to test console as root user. >>> 2. systemctl set-default --force graphical.target >>> - This will "tell" systemd that you want to run in "Graphical" mode >>> (e.g. the old init 5 level, with a X-server/GUI). >>> *** reboot *** >>> 4 shutdown -r now >>> (you can achieve the same result by typing: 'init 5' if you prefer not >>> to reboot). >>> >>> I hope this is found to be helpful. >>> >>> Darren >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> On 18 June 2014 17:52, Frederic Crozat wrote: >>> >>>> Le mercredi 18 juin 2014 ? 10:50 +1000, Darren Thompson a ?crit : >>>> > Team >>>> > >>>> > >>>> > I have been doing some testing on getting a "default graphical build" >>>> > SLES12B8 server to become a "multi-user" server. >>>> > >>>> > >>>> > It's harder than you would think, mainly due to the way >>>> > display-server.service seems to be erroneously activated, even on >>>> > multi-user target boots. >>>> > >>>> > >>>> > I have found this process works: >>>> > 1. Login to graphical console as root user. >>>> > 2. run a "terminal" session (the yast service manager process is >>>> > currently broken, it would be Bets/easier to just run that). >>>> > 3. cd /etc/systemd/system >>>> > 4. rm default.target >>>> > 5. ln -s /usr/lib/systemd/system/multi-user.target default.target >>>> > 6. cd /usr/lib/systemd/user >>>> > 7. rm default.target >>>> > 8. ln -s /usr/lib/systemd/system/multi-user.target default.target >>>> > 9. cd /usr/lib/systemd/system >>>> > 10. rm default.target >>>> > 11. ln -s /usr/lib/systemd/system/multi-user.target default.target >>>> > **** I have no idea why default.target is in these three locations, I >>>> > would expect 2 of them are redundant but am not familiar enough with >>>> > systemd to guess which **** >>>> >>>> Sorry but you are doing this the wrong way. >>>> >>>> NEVER ever change stuff in /usr/lib/systemd/system. /etc/systemd/system >>>> has ALWAYS precedence over /usr/lib/systemd/system, which means file >>>> with the same name in /etc/systemd/system will "hide" the one >>>> in /usr/lib/systemd/system. >>>> >>>> The proper way to do it is : >>>> run as root: systemctl set-default --force multi-user.target >>>> >>>> (or if you want to do it manually: ln -s >>>> -f /usr/lib/systemd/system/multi-user.target >>>> /etc/systemd/system/default.target) >>>> >>>> That's it. >>>> >>>> -- >>>> Frederic Crozat >>>> Project Manager Enterprise Desktop >>>> SUSE >>>> >>>> _______________________________________________ >>>> sles-beta mailing list >>>> sles-beta at lists.suse.com >>>> http://lists.suse.com/mailman/listinfo/sles-beta >>>> >>>> >>> >>> >>> >>> -- >>> >>> 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 >>> >>> >> >> >> >> -- >> >> 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 >> >> _______________________________________________ >> sles-beta mailing list >> sles-beta at lists.suse.com >> >> http://cp.mcafee.com/d/k-Kr40USyNtNdyXZQPtPqdQT64nDxPNJ6Wrz29EVhopdETod7apEVud7b1EVdETjsvd7ar3bVIz7O945hBqlendNBqlendLKKf8EcLZvANPX3zbfnKnjphsVxdeZXzKmKzp5dmZQul3PWApmU6CQjq9KVKVI06vaAWthKDYLwCHIcfBisEeROx_QbAfDFKx_QbAfDFsxlK5LE2zVkDjGdQ_BPqqrapEVdCBKx_QbAfDFFtd40AjS16k29Ewd4kmU6y0_PfDCy8QgblFcQg46V7Pd41EE2lpg8Cy1Sdljh04EWIjBrjPh1eFEwDUvcQgr10Qg6pmYQg6vzjjhirud79Jd3V >> >> >> >> >> 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) >> >> >> >> > > > -- > > 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 > -- 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 -------------- 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 Dick.Waite at softwareag.com Thu Jul 24 22:33:51 2014 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Fri, 25 Jul 2014 04:33:51 +0000 Subject: [sles-beta] Problems installing SLES12 under VMware Workstation - Which Tools to use. In-Reply-To: References: <46AC8C81C10B8C48820201DF2AE1D76D53878B5C@hqmbx6.eur.ad.sag>, Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D53879334@hqmbx6.eur.ad.sag> Grand Morning John, Many thanks for the good words. Its looking more likely my issues are due to a SUSE packaging issue when running Update. It seems not many on the Beta use Update, seems it was just me. The issues did not show if one ran a new install. I'll take a look at the URL's you have posted. Maybe if VMware had tested with update and not new I would not have seen the issues and been able to test SAG's Apps. Still that's water under bridge now, lets look forward to SLE12-SP1. __R ________________________________________ From: John Savanyo [jsavanyo at vmware.com] Sent: 25 July 2014 02:45 To: Waite, Dick; 'sles-beta at lists.suse.com' Subject: Re: [sles-beta] Problems installing SLES12 under VMware Workstation - Which Tools to use. VMware is in the process of transitioning to a fully open-source model for drivers and tools and distribution of same through OS distros. You can read more about details in these KB articles: http://kb.vmware.com/kb/2073803 http://kb.vmware.com/kb/2073804 Compared to SLES 11 SP3, SLES 12 adds 3 additional kernel modules/drivers (vmwgfx, vmci and vsock) and also adds open-vm-tools (OVT). SLES 12 now includes the full set of 6 kernel and 2 xorg drivers supported by vSphere/ESXi. (Workstation/Fusion products have an additional kernel driver vmhgfs, but is not used on vSphere/ESXi) We recommend using open-vm-tools and the drivers distributed by SUSE in SLES12. Although, during the transition period you can also use the legacy Vmware tools that are bundled with each Vmware product if you find that they work better for you. If you are mostly working on server workloads, then SLES12 should include all the drivers and tools (OVT) you should need. If you are using Workstation/Fusion and require a more rich desktop experience, then you likely will need to wait for a future release of Workstation/Fusion that publishes support for SLES12 and try to use the legacy bundled tools bundled with that product. -John On 7/23/14, 11:43 PM, "Waite, Dick" wrote: >Yet Another grand Hot Day in Darmstadt, > >I have been asked by SUSE support to provide /var/log/Xorg.0.log. The >virtual machine is not available to me at the moment so I had a look at a >log from a clone of that type of QE machine. It has a lot of interaction >with VMware Workstation and the grand Tools. > >Support can upgrade a KVM machine, I ran an upgrade on an old physical >machine I "found" and that ran Okay. I am getting a much stronger feeling >in my water that this one is going to come down to "VMware / Workstation >/ Tools" - interfacing with SLE12 > >I have not seen many words on the list, bar my own, about VMware / >Workstation /Tools, could we have a show of hands on who is using this >enviroment? > >Same question to SUSE I asked some time back. Which "Tools" should I use >with SLE 12. Before the upgrade its happy running SLE11-SP3, VMware >Workstation 10.0.3 and the Tools that go with that. We run the Update and >have SLE12 with the same VMware Workstation but one see it wants to >"refresh" the tools. What does one do..., the Tools are the same, or >should I now use openSUSE tools? > >I understand VMware is a good business partner of SUSE, so I would have >thought they are also part of this Beta, can they offer some words of >wisdom here. It would be grand to have a SLE12 enviroment running before >the first RC, then I can run some SAG Apps and create lots of SR's and >check out the CUPS stuff the good SUSE gent was asking about. > >On zlinux we can not access "yast" after an update, that chap and many >more will start their holidays on Friday, it?s the Start of the Hessen >School holidays.... Any other good people on the list have a SLE11 update >to SLE 12 running on zLinux. I do mean update not new_install. > >__R > >___________________________________________ >Dick Waite >Senior R&D Consultant >Phone: +49 6151 92-1505 >Mobile: +49 171 8393 769 >Software AG >Uhlandstr. 12 | 64297 Darmstadt | Germany >www.softwareag.com >___________________________________________ > > > > >-----Original Message----- >From: sles-beta-bounces at lists.suse.com >[mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Simon Flood >Sent: Thursday, July 17, 2014 1:57 PM >To: 'sles-beta at lists.suse.com' >Subject: Re: [sles-beta] Problems installing SLES12 under VMware Player > >On 17/07/2014 12:28, Waite, Dick wrote: > >> If I run a new install it's also grand, works as expected, it's only on >>an Upgrade I get the X11 / display issues with mice and keyboard, but >>it's Updates I need to get my Apps ready for testing. > >I'll try installing a basic SLES11 SP3 server then upgrading it. Whilst I >normally install my servers as text-only I'll add a GUI. > >> While we are chatting, VMware Tools Update, when do you run this? Do >>you push the refresh button or run from the command line or? I have a >>feeling in the water something is not quite right in this area. The >>VMware log has quite a lot to say in a -ve way about what is going on. > >When you say VMware Tools Update do you mean the older VMware-provided >Tools or the open-vm-tools that come with SLES12? > >I've not been doing anything special with my test VMs so currently my >Beta 10 VM (under Player) has open-vm-tools automagically installed which >Player seems happy with as the menu option is "Reinstall VMware >Tools...". I'm guessing this is because the open-vm-tools are "later" >than the VMware Tools - remember Player et al won't know about (i.e. >support) SLES12 as it's beta and too new (perhaps support will be added >with Workstation 11, Fusion 7, etc.?). > >HTH, >Simon >-- >Simon Flood >Senior Systems Specialist >University of Cambridge >United Kingdom > >Novell/SUSE/NetIQ Knowledge Partner >_______________________________________________ >sles-beta mailing list >sles-beta at lists.suse.com >http://lists.suse.com/mailman/listinfo/sles-beta > >Software AG ? Sitz/Registered office: Uhlandstra?e 12, 64297 Darmstadt, >Germany ? Registergericht/Commercial register: Darmstadt HRB 1562 - >Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), >Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of >the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com > >_______________________________________________ >sles-beta mailing list >sles-beta at lists.suse.com >http://lists.suse.com/mailman/listinfo/sles-beta From Dick.Waite at softwareag.com Thu Jul 24 23:02:37 2014 From: Dick.Waite at softwareag.com (Waite, Dick) Date: Fri, 25 Jul 2014 05:02:37 +0000 Subject: [sles-beta] intel_idle In-Reply-To: <1406203262.22894.323.camel@hermano.suse.de> References: <46AC8C81C10B8C48820201DF2AE1D76D538778AF@hqmbx6.eur.ad.sag> ,<1406110143.22894.299.camel@hermano.suse.de> <46AC8C81C10B8C48820201DF2AE1D76D53878776@hqmbx6.eur.ad.sag>, <1406203262.22894.323.camel@hermano.suse.de> Message-ID: <46AC8C81C10B8C48820201DF2AE1D76D538793B5@hqmbx6.eur.ad.sag> Grand New Day Scott, Very good news, "cpupower" sounds a lot better the boot parm. Could you give me a URL for the SLE12 Docu for this please. We will not change the SLE11 running, leave sleeping dogs lie. When the new Intel driver bashfully came on the scene, we only run major check with a new version, SLE10, SLE11 and now SLE12, we don't expect a major driver change, with little Docu or readme's on a SP, but now we know better. The customers found their batch night work running 30% - 50% longer, the night shift was too short... We did work with SUSE on this and got the boot fix. Now with SLE12 it sounds like using the "cpupower" command the customers or in most cases the service provider, in one case that is IBM, can "tune" for best use. When running a "normal" Adabas load during the day with or without the "fix" the performance did not seem any different, it was only running Utility work during the night shift the issues were seen. http://www.novell.com/support/kb/doc.php?id=7011982 The URL from Novell gives an outline of the issues and the cpupower command. I'm sure there are some grand words of wisdom on how to best use this. So with this set "correctly" to run Utility at night, would you expect the daily database performance to improve as at the moment it's switched off with the boot fix? Again many thanks for the update. One of the customers is not from Neuerburg, maybe you would like to pop over when they have SLE12 running and see your work in a customers environment. I know from my own development work, it's grand to see it running in a "real world" environment. __R ________________________________________ From: Scott Bahling [sbahling at suse.com] Sent: 24 July 2014 14:01 To: Waite, Dick Cc: sles-beta at lists.suse.com Subject: Re: [sles-beta] intel_idle On Wed, 2014-07-23 at 16:44 +0000, Waite, Dick wrote: > Many Thanks for the update Scott. A couple / few of customers did not > like the idea of having to amend the boot parm and at the time some > words were written about using in a later kernel, syscntl.conf which > customers preferred over amending boot as their system providers > charged extra... Starting with SLES 11 SP3 (latest updates) the cpupower command will allow to dynamically control the idle states via command line at run time. This is a better option than the kernel parameter. It's recommended to test with disabling only the highest c-states until the desired performance/latency is achieved. Disabling too many c-states can have adverse affects. > If the parm was not in boot then I think more customers would be > willing to amend this value, I wonder how many customer get better > results with the default, do you have any numbers? I'm not sure what kind of numbers you mean. Better results depends on workload requirements related to latency and performance/watt. The results depend on the exact hardware in use as each CPU and platform comes with it's own power vs performance features and behavioral profiles. For instance, disabling certain c-states can disable turbo-boost functionality in modern CPUs which could rob some workloads of a potential performance boost. For a majority of workloads out there, the defaults should be just fine. For those workloads that need extra attention to either performance or power efficiency, tuning is necessary. -Scott > __R > ________________________________________ > From: Scott Bahling [sbahling at suse.com] > Sent: 23 July 2014 12:09 > To: Waite, Dick > Cc: sles-beta at lists.suse.com > Subject: Re: [sles-beta] intel_idle > > On Wed, 2014-07-23 at 06:55 +0000, Waite, Dick wrote: > > Grand Day, > > > > When running some SLES11 on X86_64 sites some time ago the "batch" > > jobs were taking 30-50% more wall clock time. After some time a > > work-a-round was found to amend the "Intel_Idle" parm. There was some > > chatter at the time that a "better" fix would be available with a > > later Linux release. I'm going to visit one of our customers who had > > this issue in a few weeks time, what news do I have for them? > > It depends on the exact tuning ("work-a-round") used. > > There has been an optimization related to disabling promotion to C1E > state so using intel_idle.max_cstate=1 might give better results with > SUSE Linux Enterprise Server 12 and remove the need to disable the > intel_idle driver completely. It depends on the workload and CPU model > in use. > > Other than that, the intel_idle driver and it's parameters should work > the same in 12 as in 11 - meaning if c-states affect your workload, > tuning of the intel_idle driver might be necessary. > > Best Regards, > > Scott > > -- > Scott Bahling | Technical Account Manager - Team Lead > +49 911-74053-121 | Mobile: +49 173-587-6977 | sbahling at suse.com > SUSE Linux Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend??rffer, HRB 16746 (AG Nuremberg) > > > Software AG Sitz/Registered office: Uhlandstra??e 12, 64297 Darmstadt, Germany Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. Wolfram Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com > From schubi at suse.de Fri Jul 25 00:41:59 2014 From: schubi at suse.de (Stefan Schubert) Date: Fri, 25 Jul 2014 08:41:59 +0200 Subject: [sles-beta] Init3 Init5 broken again In-Reply-To: <1801296.7EV9jHHxCq@gjn.priv.at> References: <1847787.hloxxQZ05N@gjn.priv.at> <20140724143245.GA29870@suse.de> <1801296.7EV9jHHxCq@gjn.priv.at> Message-ID: <53D1FC37.7020608@suse.de> Am 24.07.2014 17:16, schrieb G?nther J. Niederwimmer: > Hello, > > Am Donnerstag, 24. Juli 2014, 16:32:45 schrieb Thorsten Kukuk: >> On Thu, Jul 24, G?nther J. Niederwimmer wrote: >>> Hello, >>> >>> is this known in Beta 10 is graphic / multi-user broken again by the >>> installation? >> Don't know what you mean with graphic/multi-user broken >> again, init 3, init 5, etc works fine for me on Beta10. > When I Install a new system and select multi-user in the YaST2 config, after > reboot the system boot into graphic (init 5) mode > Please open a new Bug Report and attach the logfiles, autoinst.xml I am currently working in that area and will have a look. Thanks ! Greetings Stefan -- ******************************************************************************* Stefan Schubert e-mail: schubi at suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From schubi at suse.de Fri Jul 25 00:53:41 2014 From: schubi at suse.de (Stefan Schubert) Date: Fri, 25 Jul 2014 08:53:41 +0200 Subject: [sles-beta] Changing "run level" post built (Going from Graphical to text and vice versa) In-Reply-To: References: Message-ID: <53D1FEF5.8040307@suse.de> Yes, I am aware of that but and have made a fix regarding package selection and with that fix this has worked quite will. Maybe there is another reason for. Please report it again via a new Bugzilla entry. Thanks ! Greetings Stefan Schubert Am 25.07.2014 00:16, schrieb Darren Thompson: > Team > > I posted this some time ago. The process to change run levels from > "graphical" (init 5) to "Multi-user (init 3) in a server "post build". > > I still have not successfully "built" a server that install/starts in > "Muti-user" mode. > > Darren > > > On 18 June 2014 18:13, Darren Thompson > wrote: > > Frederic > > Good Point... > > Team, do it the way he says... ;-) > > e.g. > > 1. Login to graphical console as root user. > 2. run a "terminal" session (the yast service manager process is > currently broken, it would be Best/easier to just run that). > 3. systemctl set-default --force multi-user.target > - This will "tell" systemd that you want to run in "multi-user" > mode (e.g. the old init 3 level, without a X-server/GUI). > *** reboot *** > 4 shutdown -r now > (you can achieve the same result by typing: 'init 3' if you prefer > not to reboot). > > > If you want to reverse this and run the full "graphical" (X) > console again > 1. Login to test console as root user. > 2. systemctl set-default --force graphical.target > - This will "tell" systemd that you want to run in "Graphical" > mode (e.g. the old init 5 level, with a X-server/GUI). > *** reboot *** > 4 shutdown -r now > (you can achieve the same result by typing: 'init 5' if you prefer > not to reboot). > > I hope this is found to be helpful. > > Darren > > > > > > > > > > On 18 June 2014 17:52, Frederic Crozat > wrote: > > Le mercredi 18 juin 2014 ? 10:50 +1000, Darren Thompson a ?crit : > > Team > > > > > > I have been doing some testing on getting a "default > graphical build" > > SLES12B8 server to become a "multi-user" server. > > > > > > It's harder than you would think, mainly due to the way > > display-server.service seems to be erroneously activated, > even on > > multi-user target boots. > > > > > > I have found this process works: > > 1. Login to graphical console as root user. > > 2. run a "terminal" session (the yast service manager process is > > currently broken, it would be Bets/easier to just run that). > > 3. cd /etc/systemd/system > > 4. rm default.target > > 5. ln -s /usr/lib/systemd/system/multi-user.target > default.target > > 6. cd /usr/lib/systemd/user > > 7. rm default.target > > 8. ln -s /usr/lib/systemd/system/multi-user.target > default.target > > 9. cd /usr/lib/systemd/system > > 10. rm default.target > > 11. ln -s /usr/lib/systemd/system/multi-user.target > default.target > > **** I have no idea why default.target is in these three > locations, I > > would expect 2 of them are redundant but am not familiar > enough with > > systemd to guess which **** > > Sorry but you are doing this the wrong way. > > NEVER ever change stuff in /usr/lib/systemd/system. > /etc/systemd/system > has ALWAYS precedence over /usr/lib/systemd/system, which > means file > with the same name in /etc/systemd/system will "hide" the one > in /usr/lib/systemd/system. > > The proper way to do it is : > run as root: systemctl set-default --force multi-user.target > > (or if you want to do it manually: ln -s > -f /usr/lib/systemd/system/multi-user.target > /etc/systemd/system/default.target) > > That's it. > > -- > Frederic Crozat > Project Manager Enterprise Desktop > SUSE > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > > > > > -- > > 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 > > > > > -- > > 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 > > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- ******************************************************************************* Stefan Schubert e-mail: schubi at suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From wstephenson at suse.de Fri Jul 25 01:15:47 2014 From: wstephenson at suse.de (Will Stephenson) Date: Fri, 25 Jul 2014 09:15:47 +0200 Subject: [sles-beta] Registration server In-Reply-To: <1C42A201-A4DF-4296-B4C7-C55A585ADD67@ricis.com> References: <2014090.1Pmik5Nq0Z@gjn.priv.at> <2710533.SbpGL0KamM@whistler.site> <1C42A201-A4DF-4296-B4C7-C55A585ADD67@ricis.com> Message-ID: <1587834.Y3QqjuvyNb@whistler.site> On Thursday 24 Jul 2014 11:04:14 you wrote: > On Jul 24, 2014, at 04:00 CDT, Will Stephenson wrote: > > On Wednesday 23 Jul 2014 13:25:00 Gregory D. Rosenberg wrote: > >> I can get the login page on SuSE?s Customer Center, but when I try to > >> login > >> it never completes the process. I think they use Net IQ for > >> authentication, > >> so it may be an issue that has to get fixed on the back-end. > >> > >> Uwe, is some one aware of this issue. Do we need to open SRs? > > > > Gregory, can you login to other 'netiq'-authenticated sites, eg > > bugzilla.novell.com? > > Yes I can login to buzilla, in fact this morning I am able to get into SCC > as well. Ok, I'll regard this as a glitch for now. From uwedr at suse.com Fri Jul 25 01:30:12 2014 From: uwedr at suse.com (Uwe Drechsel) Date: Fri, 25 Jul 2014 09:30:12 +0200 Subject: [sles-beta] Beta schedule Message-ID: <20140725073012.GB7429@suse.com> Dear beta participants, after we have released Beta 10 instead of RC1 last week, we have received many questions regarding a change in the schedule. We are currently working hard to make the next milestone meet our quality criteria. We are confident that it'll be at a level so that we can call it RC1, and keep the announced first customer shipment date. Your SUSE Linux Enterprise Team From schubi at suse.de Fri Jul 25 01:41:40 2014 From: schubi at suse.de (Stefan Schubert) Date: Fri, 25 Jul 2014 09:41:40 +0200 Subject: [sles-beta] Beta10 - Autoyast In-Reply-To: References: Message-ID: <53D20A34.3070606@suse.de> Hello, thanks for the feedback Am 22.07.2014 15:32, schrieb Ronny Pretzsch: > Hello, > > Thank you for the new beta 10. > > Good news first: > ================ > (1) > Manual installation: Early Network config works. > SMT registration works. > (although there pops up a failure, see below) > > (2) > Autoyast works in general, chroot- and post-scripts are executed > > (3) > Autoyast network config is functional. > > (4) > The suse firewall is configured according to autoyast.xml There is still an open issue regarding generating the settings: Bug 887406 - Build0559: AutoYaST doesn't clone firewall settings So "yast clone_system" generates the right one :-) > > (5) > Tmpfs is exported to /root/autoinst.xml There has been a bug which is fixed for RC1. In some cases following wrong entry will be generated. /dev/tmpfs true CT_TMPFS all Please remove it manually for testing. > > > Bad News: > ========= > (1) > First try with our autoyast.xml failed: The system did not reboot into stage 2. > The reason was that the /boot Partition was not activated. > I already reported this here some weeks ago. > > A workaround is to set "activate" explicitly in autoyast.xml: > > > true > true > true > > grub2 > > > > In SLES11 "activate" was obviously true by default. Why not in SLES12? > In the manual Yast GUI it is pre-selected, so it should be default in autoyast. > (We do not use btrfs, we use LVM, ext-filesystems and a separate boot partition) > But we can live with it. > But please open a bug report for it. > (2) > The network config from autoyast.xml is not applied in Stage 1. > Thus the system would register to the customer center or SMT with wrong Hostname, IP, ... > In our case it is even impossible to register due firewall / proxy settings. > We mentioned this before on the list and on bug reports, too. Could you please point us to the bugzilla entry ? > > (3) > We do not install X11 components. Thus in Stage 2 yast should run in textmode. > But it runs in blank screen mode. > Next thing we see after reboot is the login prompt. This is fixed now. > (3) > The resulting /root/autoinst.xml does not contain the previously configured > SMT Server. Could you please open a bug report ? Thanks again for detailed report. Greetings Stefan Schubert -- ******************************************************************************* Stefan Schubert e-mail: schubi at suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From schubi at suse.de Fri Jul 25 02:04:14 2014 From: schubi at suse.de (Stefan Schubert) Date: Fri, 25 Jul 2014 10:04:14 +0200 Subject: [sles-beta] beta10 autoYast SMT / CC Registration In-Reply-To: <8103bf353fdf48eea981a4d21837bad9@LGNMSXA01.prod.bk.dfs> References: <8103bf353fdf48eea981a4d21837bad9@LGNMSXA01.prod.bk.dfs> Message-ID: <53D20F7E.6020403@suse.de> Hello, thanks for the feedback. Am 24.07.2014 10:30, schrieb Ronny Pretzsch: > Hello, > > I have some questions about the early registration to SMT or Customer Center (CC) feature in SLES12. > > When installing manually Yast offers the ability to register before actually installing. > This is useful as updates can be installed immediately. > Since Beta10 one can choose a local registration server (SMT) on the Yast gui. > Thank you for this feature. > > Can anybody post a functioning autoyast.xml extract which does exactly this registering in Autoyast? > (Please no "that SHOULD work" stuff) > Or send a (public) link to the current SLES *12* Autoyast Documentation? > > After registering the question pops up if updates shall be installed immediately. > How is this question answered in autoyast.xml? > Again please post a piece of working xml here. Registration with autoyast is currently still in developing mode. E.g. Bug 888168 - cloned autoinst.xml doesn't contain entry for registration We will post on the list, when there is a working version available. > > I tried to manually install and early-register. The resulting /root/autoinst.xml does not contain anything related to registering. There seems to be some work left. > > When installing manually the Yast Registration Page comes before the Yast Add-On Product Page. My question is if an Add-On Product (e.g. SDK) gets correctly registered at the SMT / CC as it is added after the registration. I myself found it more straight forward if Yast first does the add-on stuff and then the registering. Otherwise Yast would have to register again (in the background) after adding add-ons which makes the total installation process slower. > I could not test this yet but I am going to with manual installation. I will ask the responsible person for. > > And once again: Autoyast must apply the network setting and the proxy setting *before* registering to SMT/CC. Or make it configurable in the xml file. > > As this yast installation stuff cannot be fixed per maintenance update it must perfectly work when releasing SLES12. ;-) Yes, you are completely right ! :-) Greetings Stefan Schubert > > > Regards, > Ronny Pretzsch > > DFS Deutsche Flugsicherung GmbH > > > DFS Deutsche Flugsicherung GmbH > Am DFS-Campus > D - 63225 Langen > > Tel.: +49-(0)6103-707-0 > > Sitz der Gesellschaft: Langen/Hessen > Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977 > Vorsitzender des Aufsichtsrates: Michael Odenwald > Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann > > Internet: http://www.dfs.de > Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- ******************************************************************************* Stefan Schubert e-mail: schubi at suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany From jreidinger at suse.com Fri Jul 25 02:16:10 2014 From: jreidinger at suse.com (Josef Reidinger) Date: Fri, 25 Jul 2014 10:16:10 +0200 Subject: [sles-beta] Beta10 - Autoyast In-Reply-To: References: Message-ID: <20140725101610.466650c4@dhcp150.suse.cz> On Tue, 22 Jul 2014 13:32:21 +0000 "Ronny Pretzsch" wrote: > Hello, > > Thank you for the new beta 10. > > > Bad News: > ========= > (1) > First try with our autoyast.xml failed: The system did not reboot > into stage 2. The reason was that the /boot Partition was not > activated. I already reported this here some weeks ago. > > A workaround is to set "activate" explicitly in autoyast.xml: > > > true > true > true > > grub2 > > > > In SLES11 "activate" was obviously true by default. Why not in SLES12? > In the manual Yast GUI it is pre-selected, so it should be default in > autoyast. (We do not use btrfs, we use LVM, ext-filesystems and a > separate boot partition) But we can live with it. > > Please report this problem. Looks like wrong proposal in case of missing part of autoyast profile. In SLES11 it was not by default active, but according to storage if it is needed. Josef > > > Regards, > > Ronny Pretzsch > > Deutsche Flugsicherung GmbH From jreidinger at suse.com Fri Jul 25 02:29:34 2014 From: jreidinger at suse.com (Josef Reidinger) Date: Fri, 25 Jul 2014 10:29:34 +0200 Subject: [sles-beta] beta10 autoYast SMT / CC Registration In-Reply-To: <8103bf353fdf48eea981a4d21837bad9@LGNMSXA01.prod.bk.dfs> References: <8103bf353fdf48eea981a4d21837bad9@LGNMSXA01.prod.bk.dfs> Message-ID: <20140725102934.77396270@dhcp150.suse.cz> On Thu, 24 Jul 2014 08:30:16 +0000 "Ronny Pretzsch" wrote: > Hello, > > I have some questions about the early registration to SMT or Customer > Center (CC) feature in SLES12. > > When installing manually Yast offers the ability to register before > actually installing. This is useful as updates can be installed > immediately. Since Beta10 one can choose a local registration server > (SMT) on the Yast gui. Thank you for this feature. > > Can anybody post a functioning autoyast.xml extract which does > exactly this registering in Autoyast? (Please no "that SHOULD work" > stuff) Or send a (public) link to the current SLES *12* Autoyast > Documentation? Hi Ronny, as question regarding registration in autoyast environment appear, I try to capture example snippet - https://github.com/yast/yast-registration/blob/master/README.md If something do not work or something is not clear, do not hesitate to ask, I will try to improve such snippet or documentation of registration part. Josef > > After registering the question pops up if updates shall be installed > immediately. How is this question answered in autoyast.xml? > Again please post a piece of working xml here. > > I tried to manually install and early-register. The > resulting /root/autoinst.xml does not contain anything related to > registering. There seems to be some work left. > > When installing manually the Yast Registration Page comes before the > Yast Add-On Product Page. My question is if an Add-On Product (e.g. > SDK) gets correctly registered at the SMT / CC as it is added after > the registration. I myself found it more straight forward if Yast > first does the add-on stuff and then the registering. Otherwise Yast > would have to register again (in the background) after adding add-ons > which makes the total installation process slower. I could not test > this yet but I am going to with manual installation. > > And once again: Autoyast must apply the network setting and the proxy > setting *before* registering to SMT/CC. Or make it configurable in > the xml file. > > As this yast installation stuff cannot be fixed per maintenance > update it must perfectly work when releasing SLES12. ;-) > > > Regards, > Ronny Pretzsch > > DFS Deutsche Flugsicherung GmbH From kkaempf at suse.de Fri Jul 25 02:31:02 2014 From: kkaempf at suse.de (Klaus Kaempf) Date: Fri, 25 Jul 2014 10:31:02 +0200 Subject: [sles-beta] beta10 autoYast SMT / CC Registration In-Reply-To: <8103bf353fdf48eea981a4d21837bad9@LGNMSXA01.prod.bk.dfs> References: <8103bf353fdf48eea981a4d21837bad9@LGNMSXA01.prod.bk.dfs> Message-ID: <20140725083102.GA8716@heron.suse.de> * Ronny Pretzsch [Jul 24. 2014 10:30]: > > When installing manually the Yast Registration Page comes before the > Yast Add-On Product Page. My question is if an Add-On Product (e.g. > SDK) gets correctly registered at the SMT / CC as it is added after > the registration. I myself found it more straight forward if Yast > first does the add-on stuff and then the registering. Otherwise Yast > would have to register again (in the background) after adding add-ons > which makes the total installation process slower. The list of possible extensions/modules (new SLES 12 terminology for 'addons') is dynamically generated as part of the registration process. Adding a module is quick with SUSE Customer Center (SCC) since only one http request is needed to add the respective zypper service. Hth, Klaus -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5, 90409 N?rnberg, Germany From michael.baensch at dfs.de Fri Jul 25 04:09:29 2014 From: michael.baensch at dfs.de (Michael Baensch) Date: Fri, 25 Jul 2014 10:09:29 +0000 Subject: [sles-beta] Beta10 - Autoyast In-Reply-To: <53D20A34.3070606@suse.de> References: <53D20A34.3070606@suse.de> Message-ID: Hello Stephan, thanks, we will open SRs/Bugs. Concerning (2) we found no Bug No, so we will open one too. Best regards Michael -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Stefan Schubert Gesendet: Freitag, 25. Juli 2014 09:42 An: sles-beta at lists.suse.com Betreff: Re: [sles-beta] Beta10 - Autoyast Hello, thanks for the feedback Am 22.07.2014 15:32, schrieb Ronny Pretzsch: > > > > Bad News: > ========= > (1) > First try with our autoyast.xml failed: The system did not reboot into stage 2. > The reason was that the /boot Partition was not activated. > I already reported this here some weeks ago. > > A workaround is to set "activate" explicitly in autoyast.xml: > > > true > true > true > > grub2 > > > > In SLES11 "activate" was obviously true by default. Why not in SLES12? > In the manual Yast GUI it is pre-selected, so it should be default in autoyast. > (We do not use btrfs, we use LVM, ext-filesystems and a separate boot > partition) But we can live with it. > But please open a bug report for it. > (2) > The network config from autoyast.xml is not applied in Stage 1. > Thus the system would register to the customer center or SMT with wrong Hostname, IP, ... > In our case it is even impossible to register due firewall / proxy settings. > We mentioned this before on the list and on bug reports, too. Could you please point us to the bugzilla entry ? > > (3) > We do not install X11 components. Thus in Stage 2 yast should run in textmode. > But it runs in blank screen mode. > Next thing we see after reboot is the login prompt. This is fixed now. > (3) > The resulting /root/autoinst.xml does not contain the previously > configured SMT Server. Could you please open a bug report ? Thanks again for detailed report. Greetings Stefan Schubert -- ******************************************************************************* Stefan Schubert e-mail: schubi at suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5 90409 N?rnberg Germany _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta DFS Deutsche Flugsicherung GmbH Am DFS-Campus D - 63225 Langen Tel.: +49-(0)6103-707-0 Sitz der Gesellschaft: Langen/Hessen Zust?ndiges Registergericht: AG Offenbach am Main, HRB 34977 Vorsitzender des Aufsichtsrates: Michael Odenwald Gesch?ftsf?hrer: Prof. Klaus-Dieter Scheurle (Vors.), Robert Schickling, Dr. Michael Hann Internet: http://www.dfs.de Public-Key der DFS: http://www.dfs.de/dfs/public_key.asc From gjn at gjn.priv.at Fri Jul 25 04:18:25 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Fri, 25 Jul 2014 12:18:25 +0200 Subject: [sles-beta] Init3 Init5 broken again In-Reply-To: <53D1FC37.7020608@suse.de> References: <1847787.hloxxQZ05N@gjn.priv.at> <1801296.7EV9jHHxCq@gjn.priv.at> <53D1FC37.7020608@suse.de> Message-ID: <1528198.p6eTXXvYof@gjn.priv.at> Am Freitag, 25. Juli 2014, 08:41:59 schrieb Stefan Schubert: > Am 24.07.2014 17:16, schrieb G?nther J. Niederwimmer: > > Hello, > > > > Am Donnerstag, 24. Juli 2014, 16:32:45 schrieb Thorsten Kukuk: > >> On Thu, Jul 24, G?nther J. Niederwimmer wrote: > >>> Hello, > >>> > >>> is this known in Beta 10 is graphic / multi-user broken again by the > >>> installation? > >> > >> Don't know what you mean with graphic/multi-user broken > >> again, init 3, init 5, etc works fine for me on Beta10. > > > > When I Install a new system and select multi-user in the YaST2 config, > > after reboot the system boot into graphic (init 5) mode > > Please open a new Bug Report and attach the logfiles, autoinst.xml > I am currently working in that area and will have a look. I have created #SR 10903323781 and attache the files Thanks -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From abonilla at suse.com Fri Jul 25 08:37:43 2014 From: abonilla at suse.com (Alejandro Bonilla) Date: Fri, 25 Jul 2014 10:37:43 -0400 Subject: [sles-beta] [ANNOUNCE] Docker in SLES 12 In-Reply-To: References: Message-ID: Hi Darren, Could you comment on your use case for Docker and HA? Thanks On Thu, Jun 19, 2014 at 4:26 AM, Darren Thompson wrote: > Team > > Excellent work, is there any documentation or install/configure etc > available yet? > > Is there a Cluster HA OCF template for Docker (Or am I just getting too > far ahead of myself)? > > Regards > Darren > > > On 19 June 2014 18:24, Michal Svec wrote: > >> >> Dear Beta participants, >> >> we are happy to announce that SUSE will include Docker as a part of SLES >> 12. For those not familiar with Docker yet, it is an open-source project >> that automates the deployment of applications inside software containers. >> It builds on top of Linux Containers, which we have had in SLES since quite >> some time (SLES 11 SP2) already and adds another layer allowing for easy >> image deployment and management. >> >> Starting with SLES 12 Beta8 Docker is now included on the SLES >> installation media, for now as a Technology Preview, feel free to give it a >> try and let us know how it works! >> >> Thanks in advance for all your testing >> >> Your SUSE Linux Enterprise Team >> >> Regards >> Michal >> >> -- >> Michal Svec >> Senior Product Manager >> SUSE Linux Enterprise, Virtualization >> SUSE, www.suse.com >> >> _______________________________________________ >> sles-beta mailing list >> sles-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sles-beta >> > > > > -- > > 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 > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > > -- Alejandro Bonilla Sales Engineer ABonilla at suse.com Mobile: +1 484 426 7722 -------------- 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 gjn at gjn.priv.at Fri Jul 25 10:36:24 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Fri, 25 Jul 2014 18:36:24 +0200 Subject: [sles-beta] YaSt2 control center qt Version Message-ID: <2097315.W3rLlWAO2M@gjn.priv.at> Hello, is the qt version from yast2 a problem child ? I have big Problems with yast2. I don't install Gnome and like the "old" Version. But I have ongoing 2 Icon for runlevel I have crashes on start YaS2T. ibGL error: failed to load driver: swrast libGL error: Try again with LIBGL_DEBUG=verbose for more details. QXcbConnection: XCB error: 2 (BadValue), sequence: 457, resource id: 680, major code: 131 (Unknown), minor code: 3 QXcbConnection: XCB error: 2 (BadValue), sequence: 462, resource id: 680, major code: 131 (Unknown), minor code: 3 QXcbConnection: XCB error: 2 (BadValue), sequence: 463, resource id: 680, major code: 131 (Unknown), minor code: 3 I have no windows when I open a module .... usw. -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From gjn at gjn.priv.at Fri Jul 25 11:24:41 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Fri, 25 Jul 2014 19:24:41 +0200 Subject: [sles-beta] Security Problem / question Message-ID: <1457396.CXZtGF0diF@gjn.priv.at> Hello, I have a problem understanding the root key system normal when I install the system new and go later with ssh -X ... to this system I have to delete the old Key from the ssh system. With SLES 12 I mean I have always the same key ? ssh have no problem to connect ? -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From kukuk at suse.de Fri Jul 25 12:16:20 2014 From: kukuk at suse.de (Thorsten Kukuk) Date: Fri, 25 Jul 2014 20:16:20 +0200 Subject: [sles-beta] YaSt2 control center qt Version In-Reply-To: <2097315.W3rLlWAO2M@gjn.priv.at> References: <2097315.W3rLlWAO2M@gjn.priv.at> Message-ID: <20140725181620.GA554@suse.de> Hi, On Fri, Jul 25, G?nther J. Niederwimmer wrote: > Hello, > > is the qt version from yast2 a problem child ? There is nothing known. > I have big Problems with yast2. I don't install Gnome and like the "old" > Version. But Do you see the same issues if you deinstall yast2-control-center-qt and install yast2-control-center-gnome? > I have ongoing 2 Icon for runlevel > > I have crashes on start YaS2T. > > ibGL error: failed to load driver: swrast > libGL error: Try again with LIBGL_DEBUG=verbose for more details. > QXcbConnection: XCB error: 2 (BadValue), sequence: 457, resource id: 680, > major code: 131 (Unknown), minor code: 3 > QXcbConnection: XCB error: 2 (BadValue), sequence: 462, resource id: 680, > major code: 131 (Unknown), minor code: 3 > QXcbConnection: XCB error: 2 (BadValue), sequence: 463, resource id: 680, > major code: 131 (Unknown), minor code: 3 Do you start yast2 on the local system or remote via ssh? This sounds like you are doing a ssh from a x86-64 box to a s390x box? 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 Jul 25 12:39:32 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Fri, 25 Jul 2014 20:39:32 +0200 Subject: [sles-beta] YaSt2 control center qt Version In-Reply-To: <20140725181620.GA554@suse.de> References: <2097315.W3rLlWAO2M@gjn.priv.at> <20140725181620.GA554@suse.de> Message-ID: <3911024.23Sdc3gVRQ@gjn.priv.at> Hello, Am Freitag, 25. Juli 2014, 20:16:20 schrieb Thorsten Kukuk: > On Fri, Jul 25, G?nther J. Niederwimmer wrote: > > Hello, > > > > is the qt version from yast2 a problem child ? > > There is nothing known. > > > I have big Problems with yast2. I don't install Gnome and like the "old" > > Version. But > > Do you see the same issues if you deinstall yast2-control-center-qt > and install yast2-control-center-gnome? There are other issues with gnome to big windows only 1 runlevel Icon ;-). > > I have ongoing 2 Icon for runlevel > > > > I have crashes on start YaS2T. > > > > ibGL error: failed to load driver: swrast > > libGL error: Try again with LIBGL_DEBUG=verbose for more details. > > QXcbConnection: XCB error: 2 (BadValue), sequence: 457, resource id: 680, > > major code: 131 (Unknown), minor code: 3 > > QXcbConnection: XCB error: 2 (BadValue), sequence: 462, resource id: 680, > > major code: 131 (Unknown), minor code: 3 > > QXcbConnection: XCB error: 2 (BadValue), sequence: 463, resource id: 680, > > major code: 131 (Unknown), minor code: 3 > > Do you start yast2 on the local system or remote via ssh? > This sounds like you are doing a ssh from a x86-64 box to a > s390x box? This is a x86-64 13.1 and a x86-64 sles 12 > Thorsten -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From darrent at akurit.com.au Fri Jul 25 19:37:28 2014 From: darrent at akurit.com.au (Darren Thompson) Date: Sat, 26 Jul 2014 11:37:28 +1000 Subject: [sles-beta] [ANNOUNCE] Docker in SLES 12 In-Reply-To: References: Message-ID: Alejandro I do not have a specific "use case for Docker" at this time. I'm currently a big user of HA with either XEN and LXC. I was wanting to test what extra functionality I get over LXC since they have a common root but "Docker" seems to be more evolved. If docker does not have HA capability then I will stick with XEN and LXC for now, although both have a more convoluted and manual setup process (Docker seems to have a growing repoo "virtual appliances" which would save a lot of the manual work). Regards Darren On 26 July 2014 00:37, Alejandro Bonilla wrote: > Hi Darren, > > Could you comment on your use case for Docker and HA? > > Thanks > > > On Thu, Jun 19, 2014 at 4:26 AM, Darren Thompson > wrote: > >> Team >> >> Excellent work, is there any documentation or install/configure etc >> available yet? >> >> Is there a Cluster HA OCF template for Docker (Or am I just getting too >> far ahead of myself)? >> >> Regards >> Darren >> >> >> On 19 June 2014 18:24, Michal Svec wrote: >> >>> >>> Dear Beta participants, >>> >>> we are happy to announce that SUSE will include Docker as a part of SLES >>> 12. For those not familiar with Docker yet, it is an open-source project >>> that automates the deployment of applications inside software containers. >>> It builds on top of Linux Containers, which we have had in SLES since quite >>> some time (SLES 11 SP2) already and adds another layer allowing for easy >>> image deployment and management. >>> >>> Starting with SLES 12 Beta8 Docker is now included on the SLES >>> installation media, for now as a Technology Preview, feel free to give it a >>> try and let us know how it works! >>> >>> Thanks in advance for all your testing >>> >>> Your SUSE Linux Enterprise Team >>> >>> Regards >>> Michal >>> >>> -- >>> Michal Svec >>> Senior Product Manager >>> SUSE Linux Enterprise, Virtualization >>> SUSE, www.suse.com >>> >>> _______________________________________________ >>> sles-beta mailing list >>> sles-beta at lists.suse.com >>> http://lists.suse.com/mailman/listinfo/sles-beta >>> >> >> >> >> -- >> >> 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 >> >> _______________________________________________ >> sles-beta mailing list >> sles-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sles-beta >> >> > > > -- > Alejandro Bonilla > Sales Engineer > ABonilla at suse.com > Mobile: +1 484 426 7722 > -- 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 -------------- 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 meissner at suse.de Sat Jul 26 02:08:06 2014 From: meissner at suse.de (Marcus Meissner) Date: Sat, 26 Jul 2014 10:08:06 +0200 Subject: [sles-beta] Security Problem / question In-Reply-To: <1457396.CXZtGF0diF@gjn.priv.at> References: <1457396.CXZtGF0diF@gjn.priv.at> Message-ID: <20140726080806.GB16732@suse.de> On Fri, Jul 25, 2014 at 07:24:41PM +0200, G?nther J. Niederwimmer wrote: > Hello, > > I have a problem understanding the root key system > > normal when I install the system new and go later with ssh -X ... to this > system I have to delete the old Key from the ssh system. > > With SLES 12 I mean I have always the same key ? > > ssh have no problem to connect ? So you are installing fresh and the hostkey does not change? Or do you update? This would be bad actually. Ciao, Marcus From gjn at gjn.priv.at Sat Jul 26 02:24:11 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Sat, 26 Jul 2014 10:24:11 +0200 Subject: [sles-beta] Security Problem / question In-Reply-To: <20140726080806.GB16732@suse.de> References: <1457396.CXZtGF0diF@gjn.priv.at> <20140726080806.GB16732@suse.de> Message-ID: <2641214.edgJEuDVbI@gjn.priv.at> Hello Marcus, Am Samstag, 26. Juli 2014, 10:08:06 schrieb Marcus Meissner: > On Fri, Jul 25, 2014 at 07:24:41PM +0200, G?nther J. Niederwimmer wrote: > > Hello, > > > > I have a problem understanding the root key system > > > > normal when I install the system new and go later with ssh -X ... to this > > system I have to delete the old Key from the ssh system. > > > > With SLES 12 I mean I have always the same key ? > > > > ssh have no problem to connect ? > > So you are installing fresh and the hostkey does not change? > Or do you update? The old installation are a Beta 9, the new fresh installation is Beta 10 I have the same IP name usw. > This would be bad actually. I do install three KVM Instance and the hostkey are not change ? I can go with ssh -X to the client, without change the hostkey? OK, now i understand his is a BUG :-) -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From kukuk at suse.de Sat Jul 26 03:41:37 2014 From: kukuk at suse.de (Thorsten Kukuk) Date: Sat, 26 Jul 2014 11:41:37 +0200 Subject: [sles-beta] Security Problem / question In-Reply-To: <20140726080806.GB16732@suse.de> References: <1457396.CXZtGF0diF@gjn.priv.at> <20140726080806.GB16732@suse.de> Message-ID: <20140726094137.GA32592@suse.de> On Sat, Jul 26, Marcus Meissner wrote: > On Fri, Jul 25, 2014 at 07:24:41PM +0200, G?nther J. Niederwimmer wrote: > > Hello, > > > > I have a problem understanding the root key system > > > > normal when I install the system new and go later with ssh -X ... to this > > system I have to delete the old Key from the ssh system. > > > > With SLES 12 I mean I have always the same key ? > > > > ssh have no problem to connect ? > > So you are installing fresh and the hostkey does not change? > Or do you update? > > This would be bad actually. To my knowledge: if you "overwrite" an old installation, ssh key and /home partition are preserved if 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 meissner at suse.de Sat Jul 26 03:57:07 2014 From: meissner at suse.de (Marcus Meissner) Date: Sat, 26 Jul 2014 11:57:07 +0200 Subject: [sles-beta] Security Problem / question In-Reply-To: <20140726094137.GA32592@suse.de> References: <1457396.CXZtGF0diF@gjn.priv.at> <20140726080806.GB16732@suse.de> <20140726094137.GA32592@suse.de> Message-ID: <20140726095707.GF16732@suse.de> On Sat, Jul 26, 2014 at 11:41:37AM +0200, Thorsten Kukuk wrote: > On Sat, Jul 26, Marcus Meissner wrote: > > > On Fri, Jul 25, 2014 at 07:24:41PM +0200, G?nther J. Niederwimmer wrote: > > > Hello, > > > > > > I have a problem understanding the root key system > > > > > > normal when I install the system new and go later with ssh -X ... to this > > > system I have to delete the old Key from the ssh system. > > > > > > With SLES 12 I mean I have always the same key ? > > > > > > ssh have no problem to connect ? > > > > So you are installing fresh and the hostkey does not change? > > Or do you update? > > > > This would be bad actually. > > To my knowledge: if you "overwrite" an old installation, ssh key > and /home partition are preserved if possible. Yes, there is code to auto-import those in various upgrade scenarios. Ciao, Marcus From gjn at gjn.priv.at Sat Jul 26 05:41:44 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Sat, 26 Jul 2014 13:41:44 +0200 Subject: [sles-beta] Security Problem / question In-Reply-To: <20140726094137.GA32592@suse.de> References: <1457396.CXZtGF0diF@gjn.priv.at> <20140726080806.GB16732@suse.de> <20140726094137.GA32592@suse.de> Message-ID: <3359138.kEgd7sPiSX@gjn.priv.at> Hello, Am Samstag, 26. Juli 2014, 11:41:37 schrieb Thorsten Kukuk: > On Sat, Jul 26, Marcus Meissner wrote: > > On Fri, Jul 25, 2014 at 07:24:41PM +0200, G?nther J. Niederwimmer wrote: > > > Hello, > > > > > > I have a problem understanding the root key system > > > > > > normal when I install the system new and go later with ssh -X ... to > > > this > > > system I have to delete the old Key from the ssh system. > > > > > > With SLES 12 I mean I have always the same key ? > > > > > > ssh have no problem to connect ? > > > > So you are installing fresh and the hostkey does not change? > > Or do you update? > > > > This would be bad actually. > > To my knowledge: if you "overwrite" an old installation, ssh key > and /home partition are preserved if possible. NO,i format the Installation Partition with Btrfs "/"and I mean this is a default, the KVM clients are also with fresh format Partitions installed ? I make a #SR OK ? -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From gjn at gjn.priv.at Sat Jul 26 05:51:03 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Sat, 26 Jul 2014 13:51:03 +0200 Subject: [sles-beta] Security Problem / question In-Reply-To: <20140726095707.GF16732@suse.de> References: <1457396.CXZtGF0diF@gjn.priv.at> <20140726094137.GA32592@suse.de> <20140726095707.GF16732@suse.de> Message-ID: <1900577.aqopyW4071@gjn.priv.at> Hello, Am Samstag, 26. Juli 2014, 11:57:07 schrieb Marcus Meissner: > On Sat, Jul 26, 2014 at 11:41:37AM +0200, Thorsten Kukuk wrote: > > On Sat, Jul 26, Marcus Meissner wrote: > > > On Fri, Jul 25, 2014 at 07:24:41PM +0200, G?nther J. Niederwimmer wrote: > > > > Hello, > > > > > > > > I have a problem understanding the root key system > > > > > > > > normal when I install the system new and go later with ssh -X ... to > > > > this > > > > system I have to delete the old Key from the ssh system. > > > > > > > > With SLES 12 I mean I have always the same key ? > > > > > > > > ssh have no problem to connect ? > > > > > > So you are installing fresh and the hostkey does not change? > > > Or do you update? > > > > > > This would be bad actually. > > > > To my knowledge: if you "overwrite" an old installation, ssh key > > and /home partition are preserved if possible. > > Yes, there is code to auto-import those in various upgrade scenarios. Could it be the SSH is broken on the client (13.1) so now I make a Test with a KVM Client and format the "Raw Partition" before I instal and use it with the client ?l -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From gjn at gjn.priv.at Sat Jul 26 06:42:02 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Sat, 26 Jul 2014 14:42:02 +0200 Subject: [sles-beta] Security Problem / question In-Reply-To: <1900577.aqopyW4071@gjn.priv.at> References: <1457396.CXZtGF0diF@gjn.priv.at> <20140726095707.GF16732@suse.de> <1900577.aqopyW4071@gjn.priv.at> Message-ID: <8903764.kXrO6LXIug@gjn.priv.at> Am Samstag, 26. Juli 2014, 13:51:03 schrieb G?nther J. Niederwimmer: > Hello, > > Am Samstag, 26. Juli 2014, 11:57:07 schrieb Marcus Meissner: > > On Sat, Jul 26, 2014 at 11:41:37AM +0200, Thorsten Kukuk wrote: > > > On Sat, Jul 26, Marcus Meissner wrote: > > > > On Fri, Jul 25, 2014 at 07:24:41PM +0200, G?nther J. Niederwimmer wrote: > > > > > Hello, > > > > > > > > > > I have a problem understanding the root key system > > > > > > > > > > normal when I install the system new and go later with ssh -X ... to > > > > > this > > > > > system I have to delete the old Key from the ssh system. > > > > > > > > > > With SLES 12 I mean I have always the same key ? > > > > > > > > > > ssh have no problem to connect ? > > > > > > > > So you are installing fresh and the hostkey does not change? > > > > Or do you update? > > > > > > > > This would be bad actually. > > > > > > To my knowledge: if you "overwrite" an old installation, ssh key > > > and /home partition are preserved if possible. > > > > Yes, there is code to auto-import those in various upgrade scenarios. > > Could it be the SSH is broken on the client (13.1) > > so now I make a Test with a KVM Client and format the "Raw Partition" before > I instal and use it with the client ?l I have now format the Partition with XFS before installation and now I have a correct changed hostkey @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! But I mean it is something wrong with the Btrfs Filesystem when I format new and have the old hostkey? -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From kukuk at suse.de Sat Jul 26 07:12:59 2014 From: kukuk at suse.de (Thorsten Kukuk) Date: Sat, 26 Jul 2014 15:12:59 +0200 Subject: [sles-beta] Security Problem / question In-Reply-To: <8903764.kXrO6LXIug@gjn.priv.at> References: <1457396.CXZtGF0diF@gjn.priv.at> <20140726095707.GF16732@suse.de> <1900577.aqopyW4071@gjn.priv.at> <8903764.kXrO6LXIug@gjn.priv.at> Message-ID: <20140726131259.GA16409@suse.de> On Sat, Jul 26, G?nther J. Niederwimmer wrote: > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! > > But I mean it is something wrong with the Btrfs Filesystem when I format new > and have the old hostkey? What happend during fresh installation, if the fresh installation replaces an older installtion: - Save ssh keys - Find /home partition - format filesystem - Install - Readd /home - copy back ssh keys 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 Sat Jul 26 08:23:37 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Sat, 26 Jul 2014 16:23:37 +0200 Subject: [sles-beta] Security Problem / question In-Reply-To: <20140726131259.GA16409@suse.de> References: <1457396.CXZtGF0diF@gjn.priv.at> <8903764.kXrO6LXIug@gjn.priv.at> <20140726131259.GA16409@suse.de> Message-ID: <3304007.hbPkfGkh6s@gjn.priv.at> Hallo Thorsten, Am Samstag, 26. Juli 2014, 15:12:59 schrieb Thorsten Kukuk: > On Sat, Jul 26, G?nther J. Niederwimmer wrote: > > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > > @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ > > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! > > > > But I mean it is something wrong with the Btrfs Filesystem when I format > > new and have the old hostkey? > > What happend during fresh installation, if the fresh installation > replaces an older installtion: > - Save ssh keys > - Find /home partition > - format filesystem > - Install > - Readd /home > - copy back ssh keys > I have a Problem when I do Find /home partition format filesystem Install Readd /home ;-) and I have the same hostkey then before? -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From gjn at gjn.priv.at Sat Jul 26 08:41:24 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Sat, 26 Jul 2014 16:41:24 +0200 Subject: [sles-beta] wicked & openvswitch Message-ID: <1836253.NTgZCXi9QK@gjn.priv.at> Hello, when I install and configure openvswitch wicked crash In YaST2 Network Setting I found Network setting method with Wicked service Network Service disabled Mean Network Service disabled the old configuration Method, or is all networking disabled Should I can configure openvswitch with wicked or not? -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer From S.M.Flood at ucs.cam.ac.uk Sat Jul 26 15:50:09 2014 From: S.M.Flood at ucs.cam.ac.uk (Simon Flood) Date: Sat, 26 Jul 2014 22:50:09 +0100 Subject: [sles-beta] Security Problem / question In-Reply-To: <1457396.CXZtGF0diF@gjn.priv.at> References: <1457396.CXZtGF0diF@gjn.priv.at> Message-ID: On 25 July 2014 18:24:41 BST, "G?nther J. Niederwimmer" wrote: >I have a problem understanding the root key system > >normal when I install the system new and go later with ssh -X ... to >this >system I have to delete the old Key from the ssh system. > >With SLES 12 I mean I have always the same key ? > >ssh have no problem to connect ? Whilst you may have noticed it with SLES12 beta it's not new with SLES12 as it exists with SLES11 - see https://forums.suse.com/showthread.php?2565-ssh-host-keys-kept-despite-of-fresh-installation&p=12609#post12609 HTH, Simon Simon Flood Senior Systems Specialist University of Cambridge United Kingdom Novell/SUSE/NetIQ Knowledge Partner From gjn at gjn.priv.at Sun Jul 27 07:54:20 2014 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Sun, 27 Jul 2014 15:54:20 +0200 Subject: [sles-beta] Question UEFI Boot Update Message-ID: <10906504.9rLhCgaS1g@gjn.priv.at> Hello, What is the best way to update the configuration when a new Bios Update the UEFi Boot tables deleted? Without new Installation ;-). -- mit freundlichen Gr??en / best Regards, G?nther J. Niederwimmer