From behlert at suse.de Fri Mar 1 01:09:13 2013 From: behlert at suse.de (Stefan Behlert) Date: Fri, 1 Mar 2013 09:09:13 +0100 Subject: [sles-beta] beta2 questions In-Reply-To: References: Message-ID: <20130301080913.GB27370@suse.de> Hi Greg, On Mar 01, 13 05:33:58 +0000, Greg.Lehmann at csiro.au wrote: > Is the 2nd beta of the SDK going to appear? I've got SLES iso's already. You should see them meanwhile. The images are synced to the download servers with the main products being prioritized, and afterwards the SDK images are made available. And then an official announcement is sent after we have made some spot tests. Of course, if you look at the right time you will see the downloads before the announcement, but only after the annoucne ment is out you should expect everything to be present. (I expect the announcement for SLES soon, I'm currently finalizing the one for SLED.) ciao, Stefan > > Greg Lehmann > Unix Lead, Server Operations > CSIRO Information Management and Technology -- Stefan Behlert, SUSE LINUX Project Manager Enterprise Desktop Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE LINUX Products GmbH, Nuernberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuernberg) From Klaus.Gmeinwieser at oce.com Fri Mar 1 04:20:44 2013 From: Klaus.Gmeinwieser at oce.com (Klaus Gmeinwieser) Date: Fri, 1 Mar 2013 12:20:44 +0100 Subject: [sles-beta] Issues I saw after several installs and some configuration In-Reply-To: <512F9171.2000604@ts.fujitsu.com> References: <512F6E35.3010109@oce.com> <512F9171.2000604@ts.fujitsu.com> Message-ID: <51308F0C.5050600@oce.com> Hallo Herr Wilck, das passiert auch bei Verwendung des USB Stick alleine. Bei "normalen" Maschinen ist der angegebene Workaround verwendbar, bei fest verkabelten Servern ist das in der Weise nicht machbar. Problem ist, dass das erste sichtbare USB Medium als erste Festplatte gesehen/verwendet und damit SLES auch dorthin installiert wird (was wegen mangelndem Plattenplatz nat?rlich schief geht). Der KVM-Switch sollte hier nicht das Problem sein... Gru? Klaus Gmeinwieser Am 28.02.2013 18:18, schrieb Martin Wilck: > Hallo Herr Gmeinwieser, > >> Most annoying issue was impossible unattended installation of my rack >> systems connected to a Fujitsu KVM s4-1622. This KVM is emulating USB >> remote storage and YaST wants to install the system on this USB media if >> using "autoyast=usb" to import the control file from a USB media. >> >> The only possibility to get SLES installed is to disconnect the switch >> and to directly connect keyboard and mouse and to use a workaround to >> connect the USB stick earliest after YaST asks for it. > > Eine Frage dazu: Passiert das nur mit dem KVM S4, oder auch zB mit einer > direkten angesteckten USB Platte oder USB Stick? > > Gru? > Martin Wilck > -- Klaus Gmeinwieser email: klaus.gmeinwieser at oce.com voice: +49 8121 72 4358 Oc? Printing System GmbH - A Canon Group Company 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 mge at suse.com Fri Mar 1 04:37:34 2013 From: mge at suse.com (Matthias G. Eckermann) Date: Fri, 1 Mar 2013 12:37:34 +0100 Subject: [sles-beta] Issues I saw after several installs and some configuration In-Reply-To: <51308F0C.5050600@oce.com> References: <512F6E35.3010109@oce.com> <512F9171.2000604@ts.fujitsu.com> <51308F0C.5050600@oce.com> Message-ID: <20130301113734.GB31347@suse.com> Summarizing the german discussion: there are issues with installing via USB Media, which are not limited to the Fujitsu KVM s4-1622, but also occur with USB in general. The situation is worse thouhg with a KVM, as it cannot be "removed" manually (as a stick could). I suggest that you open a Service Request about this general issue. While I am not sure, if we can fix it for all situations (there is some interaction with BIOS, sort orders, ...), we should at least document in the Release Notes, how this could be workarounded. Thanks in advance! so long - MgE On 2013-03-01 T 12:20 +0100 Klaus Gmeinwieser wrote: > Hallo Herr Wilck, > > das passiert auch bei Verwendung des USB Stick alleine. Bei > "normalen" Maschinen ist der angegebene Workaround verwendbar, bei > fest verkabelten Servern ist das in der Weise nicht machbar. > > Problem ist, dass das erste sichtbare USB Medium als erste Festplatte > gesehen/verwendet und damit SLES auch dorthin installiert wird (was > wegen mangelndem Plattenplatz nat?rlich schief geht). > > Der KVM-Switch sollte hier nicht das Problem sein... > > Gru? > Klaus Gmeinwieser > > Am 28.02.2013 18:18, schrieb Martin Wilck: > >Hallo Herr Gmeinwieser, > > > >>Most annoying issue was impossible unattended installation of my rack > >>systems connected to a Fujitsu KVM s4-1622. This KVM is emulating USB > >>remote storage and YaST wants to install the system on this USB media if > >>using "autoyast=usb" to import the control file from a USB media. > >> > >>The only possibility to get SLES installed is to disconnect the switch > >>and to directly connect keyboard and mouse and to use a workaround to > >>connect the USB stick earliest after YaST asks for it. > > > >Eine Frage dazu: Passiert das nur mit dem KVM S4, oder auch zB mit einer > >direkten angesteckten USB Platte oder USB Stick? > > > >Gru? > >Martin Wilck > > > > -- > Klaus Gmeinwieser > > email: klaus.gmeinwieser at oce.com > voice: +49 8121 72 4358 > > Oc? Printing System GmbH - A Canon Group Company > > 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. > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From martin.wilck at ts.fujitsu.com Fri Mar 1 04:41:39 2013 From: martin.wilck at ts.fujitsu.com (Martin Wilck) Date: Fri, 01 Mar 2013 12:41:39 +0100 Subject: [sles-beta] Issues I saw after several installs and some configuration In-Reply-To: <20130301113734.GB31347@suse.com> References: <512F6E35.3010109@oce.com> <512F9171.2000604@ts.fujitsu.com> <51308F0C.5050600@oce.com> <20130301113734.GB31347@suse.com> Message-ID: <513093F3.4040705@ts.fujitsu.com> On 03/01/2013 12:37 PM, Matthias G. Eckermann wrote: > Summarizing the german discussion: I am sorry for having posted in German. I erroneously thought I was replying privately, and didn't check the To: header before sending. 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 drahn at suse.com Fri Mar 1 06:26:11 2013 From: drahn at suse.com (Daniel Rahn) Date: Fri, 1 Mar 2013 14:26:11 +0100 Subject: [sles-beta] Issues I saw after several installs and some configuration In-Reply-To: <51308F0C.5050600@oce.com> References: <512F6E35.3010109@oce.com> <512F9171.2000604@ts.fujitsu.com> <51308F0C.5050600@oce.com> Message-ID: <20130301132611.GE9568@suse.com> Hi Klaus, can you please start off the installation using this additinal parameter: SCSIBeforeUSB=1 Please let us know if that changes the behavior. Thanks, Daniel -- Daniel Rahn (????????), Senior Tech. Account Manager Product Management, SUSE LINUX Products GmbH Maxfeldstrasse 5, 90409 Nuernberg, Germany P: +49 (0) 911 74053 351 - F: +49 (0) 911 74053 679 M: +49 (0) 179 2320786 - HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer From Klaus.Gmeinwieser at oce.com Fri Mar 1 08:22:48 2013 From: Klaus.Gmeinwieser at oce.com (Klaus Gmeinwieser) Date: Fri, 1 Mar 2013 16:22:48 +0100 Subject: [sles-beta] Issues I saw after several installs and some configuration In-Reply-To: <20130301132611.GE9568@suse.com> References: <512F6E35.3010109@oce.com> <512F9171.2000604@ts.fujitsu.com> <51308F0C.5050600@oce.com> <20130301132611.GE9568@suse.com> Message-ID: <5130C7C8.9070501@oce.com> Hello Daniel, this does not change the behaviour of the system. The USB media is still identified as /dev/sda (sfdisk -l) and YaST stops for 56603MB missing space on my harddisk... I recognized some additional messages at boot up, but did not watch in detail. Is there some information needed, and if so - how should I provide? System is a standard Fujitsu TX150S5 with LSI Logic 1068 MPT SAS controller. If necessary, I can try on more (newer) systems, but need to install a new set of disks before SP3 installation... please let me know. Thanks & Regards Klaus Am 01.03.2013 14:26, schrieb Daniel Rahn: > Hi Klaus, > > can you please start off the installation using this additinal > parameter: > > SCSIBeforeUSB=1 > > Please let us know if that changes the behavior. > > Thanks, > > Daniel > -- Klaus Gmeinwieser email: klaus.gmeinwieser at oce.com voice: +49 8121 72 4358 Oc? Printing System GmbH - A Canon Group Company 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 Greg.Lehmann at csiro.au Fri Mar 1 18:50:33 2013 From: Greg.Lehmann at csiro.au (Greg.Lehmann at csiro.au) Date: Sat, 2 Mar 2013 01:50:33 +0000 Subject: [sles-beta] Issues I saw after several installs and some configuration In-Reply-To: <20130301132611.GE9568@suse.com> References: <512F6E35.3010109@oce.com> <512F9171.2000604@ts.fujitsu.com> <51308F0C.5050600@oce.com>,<20130301132611.GE9568@suse.com> Message-ID: It did not help with my HP microserver N40L either. While it can boot from the USB drive to start the install as soon as it gets itself going it can no longer find the USB/CD drive. Console 3 summary: reading driver update: disk:/?blah rescaninng devices url mount: trying disk:/?blah...-part1 Partition: 32.GB.iso9660, SLES... No new driver updates found. repository: looking for cd:/ rescanning devices repository: not found No SUSE Linux Enterprise Server 11 repository found automatic setup not possible If I back up and pick installation from hard disk and pick the USB drive the install continues. It also gets the boot loader install wrong. It picks separate boot partition rather than MBR. Manually fixing that allows the install to complete. ________________________________________ From: sles-beta-bounces at lists.suse.com [sles-beta-bounces at lists.suse.com] on behalf of Daniel Rahn [drahn at suse.com] Sent: Friday, March 01, 2013 11:26 PM To: sles-beta at lists.suse.com Subject: Re: [sles-beta] Issues I saw after several installs and some configuration Hi Klaus, can you please start off the installation using this additinal parameter: SCSIBeforeUSB=1 Please let us know if that changes the behavior. Thanks, Daniel -- Daniel Rahn (????????), Senior Tech. Account Manager Product Management, SUSE LINUX Products GmbH Maxfeldstrasse 5, 90409 Nuernberg, Germany P: +49 (0) 911 74053 351 - F: +49 (0) 911 74053 679 M: +49 (0) 179 2320786 - HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From urs.frey at post.ch Mon Mar 4 02:57:15 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Mon, 4 Mar 2013 09:57:15 +0000 Subject: [sles-beta] Problems with mcelog on HP-Proliant Server with AMD Opteron processors Message-ID: <40637DBB36AF3941B243A286A432CA0B0E226BBF@HXMB12.pnet.ch> Hi Installation of SLES11-SP3 beta2 works smoothly. I am testing on: HP Proliant DL385-G5 HP Proliant BL465c-G7 Blade: AMD Opteron(tm) Processor 6172 HP Proliant BL465c-Gen8 Blade : AMD Opteron(TM) Processor 6220 HP Proliant BL460c-Gen8 Blade : Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz The only thing which irritates me, is that mcelog failed message on my console: On all AMD Opteron Processors models I get this failure: "CPU is unsupported" h04syy:/etc/init.d # /etc/init.d/mcelog start Starting mcelog... CPU is unsupported startproc: exit status of parent of /usr/sbin/mcelog: 1 failed h04syy:/etc/init.d # I mean under SLES11-SP2 mcelog works with no failure. On SLES11-SP2 there is an older release of mcelog h04wwl:~ # uname -a Linux h04wwl 3.0.58-0.6.6-default #1 SMP Tue Feb 19 11:07:00 UTC 2013 (1576ecd) x86_64 x86_64 x86_64 GNU/Linux h04wwl:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 2 h04wwl:~ # h04wwl:~ # cat /proc/cpuinfo | grep "model name" model name : AMD Opteron(tm) Processor 6172 h04wwl:~ # ps -ef | grep mcelog root 5603 1 0 Feb27 ? 00:00:00 /usr/sbin/mcelog --daemon --config-file /etc/mcelog/mcelog.conf root 31534 31503 0 10:27 pts/0 00:00:00 grep mcelog h04wwl:~ # cat /var/run/mcelog.pid 5603 h04wwl:~ # freyu at h04wwl:~> rpm -q --changelog mcelog-1.0.2011.06.08-0.11.1 | less * Tue Apr 17 2012 trenn at suse.de - Add Ivy Bridge support (bnc#748484) - Add forgotten CPU model 0x25 (bnc#742716) On Intel mcelog works on SLES11-SP3 beta2 model name : Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz h05cni:~ # h05cni:~ # uname -a Linux h05cni 3.0.65-0.9-default #1 SMP Mon Feb 25 07:21:23 UTC 2013 (055263a) x86_64 x86_64 x86_64 GNU/Linux h05cni:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 3 h05cni:~ # ps -ef | grep mcelog | grep -v grep root 4949 1 0 10:33 ? 00:00:00 /usr/sbin/mcelog --daemon --config-file /etc/mcelog/mcelog.conf h05cni:~ # cat /var/run/mcelog.pid 4949 h05cni:~ # But on AMD processors mcelog does not work anymore on SLES11-SP3 beta2 model name : AMD Opteron(TM) Processor 6220 h05cnh:~ # ps -ef | grep mcelog | grep -v grep h05cnh:~ # uname -a Linux h05cnh 3.0.65-0.9-default #1 SMP Mon Feb 25 07:21:23 UTC 2013 (055263a) x86_64 x86_64 x86_64 GNU/Linux h05cnh:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 3 h05cnh:~ # With SLES11-SP3 a new release of mcelog has been included: This is new in the RPM changelog: h05cnh:~ # rpm -qa | grep mcelog mcelog-1.0.2013.01.18-0.7.7 h05cnh:~ # rpm -q --changelog mcelog-1.0.2013.01.18-0.7.7 | less * Mon Jan 21 2013 trenn at suse.de - Updated to latest git state (2013-01-18) (fate#313746) and removed patches which went upstream meanwhile (for example enabling ivybridge, fate#313745). This one has latest IvyBridge EX/EP CPU decoding support - Removed wrongly used getdomainname call and replaced it with a dnslookup call as done in factory for a while QUESTION: Is there now a special configuration needed for AMD Opteron processors? When I diff /etc/mcelog/mcelog.conf from SLES11-SP2 and SLES11-SP3 there is no difference at all. So why is there the message "CPU is unsupported" only on Amd Opteron processors? Can it be, that with the removal of patches, some AMD specific code has been removed? Thanks for your feedback Best regards Urs Frey Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX : ++41 (0)58 667 30 07 E-Mail: urs.frey at post.ch From Maximilian.Decker at cancom.de Mon Mar 4 07:39:41 2013 From: Maximilian.Decker at cancom.de (Decker Maximilian) Date: Mon, 4 Mar 2013 15:39:41 +0100 Subject: [sles-beta] few things to note after my first install In-Reply-To: References: <20130221103545.GC24104@suse.de> Message-ID: Dear SuSE, please, any official comment on why there is no ext4 support in SLES 11, even in SP3 ? This question is asked quite a lot by our customers, and I am running out of arguments here. Especially when it comes to "but in RHEL there is .... " To some degree I could understand that for 11, it was missing from the beginning. But what are the odds that we see ext4 in 12 ? Btw - you know that reiserfs (v3) has some serious stability issues as of post-2.6.35 kernels, right ? The BKL replacements somehow rendered reiserfs prone to deadlocking in a more or less frequent manner. These issues seem to exist up to at least the current 3.8 kernels. So (in theory) also SLE >= SP2 (i.e. 3.0.x) kernels might be affected. But the good thing is - I cannot tell for sure as none of our maintained SLES 11 installations is on reiserfs. (same with btrfs) However, anything regarding ext4 would be highly appreciated. thanks - Maximilian -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Swartz, Patrick H Gesendet: Sonntag, 24. Februar 2013 19:57 An: 'SUSE Linux Enterprise Server Authorized Beta Program' Betreff: Re: [sles-beta] few things to note after my first install To add to that, we can't/won't be able to use BTRFS until it can support /boot. Our SLES11 deployment model is based on using Atomic updates, which requires the first 2 partitions to be dedicated to Atomic. So, that means that /boot is therefore incorporated into the root partition. The ability to roll back patches and upgrades is critical, but not being able to roll back a kernel makes BTRFS useless for us. Just my 2cents worth from the field... Patrick Swartz -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Decker Maximilian Sent: Sunday, February 24, 2013 11:25 AM To: 'SUSE Linux Enterprise Server Authorized Beta Program' Subject: Re: [sles-beta] few things to note after my first install Hi list, regarding the lack of (supported) ext4, just out of curiosity - what exactly is SuSE's reason behind obviously abandoning ext4, which by now is a well known, fast and proven evolution to ext3 ? Of course, BTRFS really is the cool new stuff, and it seems like it will become an amazing alternative. But to be honest none of our SLES customers is actually running BTRFS in their datacenters yet. Some lab or testing installations do exist, though, however bottom line is - for production systems we are effectively stuck with ext3. (sometimes even due to missing support from 3rd party SW vendors) If I understand correctly ext4 might also be missing in SLES 12. And I know there are plenty of discussions on this matter all around the internet, but hey, I hope with the current Beta maybe SuSE can shed some official light on that. Really would be great to know. Please don't get me wrong, I know there are quite a bunch of brilliant developers at SuSE that are giving their blessings to the current state of BTRFS, and we also got official SuSE support on that, but it just does not help "in the field".... people still consider it beta. thanks, - Maximilian > -----Original Message----- > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta- > bounces at lists.suse.com] On Behalf Of Thorsten Kukuk > Sent: Thursday, 21 February 2013 8:36 PM > To: SUSE Linux Enterprise Server Authorized Beta Program > Subject: Re: [sles-beta] few things to note after my first install > > On Thu, Feb 21, Greg.Lehmann at csiro.au wrote: > <---& -----> > > > 2. I can't believe we have btrfs as a filesystem option but no > ext4 - again SLES 12 hopefully. > > I don't think that this will change. > _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent 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 First Data immediately by replying to this message and deleting it from your computer. _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From Greg.Lehmann at csiro.au Tue Mar 5 00:07:17 2013 From: Greg.Lehmann at csiro.au (Greg.Lehmann at csiro.au) Date: Tue, 5 Mar 2013 07:07:17 +0000 Subject: [sles-beta] Problems with mcelog on HP-Proliant Server with AMD Opteron processors In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0E226BBF@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0E226BBF@HXMB12.pnet.ch> Message-ID: I noticed this on a AMD server too but since I had not installed SP2 on there before, I didn't know it had changed. Greg > -----Original Message----- > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta- > bounces at lists.suse.com] On Behalf Of urs.frey at post.ch > Sent: Monday, 4 March 2013 7:57 PM > To: sles-beta at lists.suse.com > Subject: [sles-beta] Problems with mcelog on HP-Proliant Server with > AMD Opteron processors > > Hi > > Installation of SLES11-SP3 beta2 works smoothly. > I am testing on: > HP Proliant DL385-G5 > HP Proliant BL465c-G7 Blade: AMD Opteron(tm) Processor 6172 > HP Proliant BL465c-Gen8 Blade : AMD Opteron(TM) Processor 6220 > HP Proliant BL460c-Gen8 Blade : Intel(R) Xeon(R) CPU E5-2660 0 @ > 2.20GHz > > The only thing which irritates me, is that mcelog failed message on my > console: > > On all AMD Opteron Processors models I get this failure: "CPU is > unsupported" > > h04syy:/etc/init.d # /etc/init.d/mcelog start > Starting mcelog... CPU is unsupported > startproc: exit status of parent of /usr/sbin/mcelog: 1 > failed > h04syy:/etc/init.d # > > I mean under SLES11-SP2 mcelog works with no failure. > On SLES11-SP2 there is an older release of mcelog > > h04wwl:~ # uname -a > Linux h04wwl 3.0.58-0.6.6-default #1 SMP Tue Feb 19 11:07:00 UTC 2013 > (1576ecd) x86_64 x86_64 x86_64 GNU/Linux > h04wwl:~ # cat /etc/SuSE-release > SUSE Linux Enterprise Server 11 (x86_64) > VERSION = 11 > PATCHLEVEL = 2 > h04wwl:~ # > h04wwl:~ # cat /proc/cpuinfo | grep "model name" > model name : AMD Opteron(tm) Processor 6172 > h04wwl:~ # ps -ef | grep mcelog > root 5603 1 0 Feb27 ? 00:00:00 /usr/sbin/mcelog -- > daemon --config-file /etc/mcelog/mcelog.conf > root 31534 31503 0 10:27 pts/0 00:00:00 grep mcelog > h04wwl:~ # cat /var/run/mcelog.pid > 5603 > h04wwl:~ # > freyu at h04wwl:~> rpm -q --changelog mcelog-1.0.2011.06.08-0.11.1 | less > * Tue Apr 17 2012 trenn at suse.de > - Add Ivy Bridge support (bnc#748484) > - Add forgotten CPU model 0x25 (bnc#742716) > > On Intel mcelog works on SLES11-SP3 beta2 > model name : Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz > h05cni:~ # > h05cni:~ # uname -a > Linux h05cni 3.0.65-0.9-default #1 SMP Mon Feb 25 07:21:23 UTC 2013 > (055263a) x86_64 x86_64 x86_64 GNU/Linux > h05cni:~ # cat /etc/SuSE-release > SUSE Linux Enterprise Server 11 (x86_64) > VERSION = 11 > PATCHLEVEL = 3 > h05cni:~ # ps -ef | grep mcelog | grep -v grep > root 4949 1 0 10:33 ? 00:00:00 /usr/sbin/mcelog -- > daemon --config-file /etc/mcelog/mcelog.conf > h05cni:~ # cat /var/run/mcelog.pid > 4949 > h05cni:~ # > > But on AMD processors mcelog does not work anymore on SLES11-SP3 beta2 > model name : AMD Opteron(TM) Processor 6220 > h05cnh:~ # ps -ef | grep mcelog | grep -v grep > h05cnh:~ # uname -a > Linux h05cnh 3.0.65-0.9-default #1 SMP Mon Feb 25 07:21:23 UTC 2013 > (055263a) x86_64 x86_64 x86_64 GNU/Linux > h05cnh:~ # cat /etc/SuSE-release > SUSE Linux Enterprise Server 11 (x86_64) > VERSION = 11 > PATCHLEVEL = 3 > h05cnh:~ # > > > With SLES11-SP3 a new release of mcelog has been included: This is new > in the RPM changelog: > h05cnh:~ # rpm -qa | grep mcelog > mcelog-1.0.2013.01.18-0.7.7 > h05cnh:~ # rpm -q --changelog mcelog-1.0.2013.01.18-0.7.7 | less > * Mon Jan 21 2013 trenn at suse.de > - Updated to latest git state (2013-01-18) (fate#313746) > and removed patches which went upstream meanwhile (for example > enabling ivybridge, fate#313745). This one has latest IvyBridge EX/EP > CPU decoding support > - Removed wrongly used getdomainname call and replaced it with > a dnslookup call as done in factory for a while > > QUESTION: > Is there now a special configuration needed for AMD Opteron processors? > When I diff /etc/mcelog/mcelog.conf from SLES11-SP2 and SLES11-SP3 > there is no difference at all. > > So why is there the message "CPU is unsupported" only on Amd Opteron > processors? > Can it be, that with the removal of patches, some AMD specific code has > been removed? > > Thanks for your feedback > Best regards > > Urs Frey > Die Schweizerische Post > Services > Informationstechnologie > Webergutstrasse 12 > 3030 Bern (Zollikofen) > Telefon : ++41 (0)58 338 58 70 > FAX : ++41 (0)58 667 30 07 > E-Mail: urs.frey at post.ch > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta From mkrapp at suse.com Tue Mar 5 03:06:08 2013 From: mkrapp at suse.com (Michael Krapp) Date: Tue, 5 Mar 2013 11:06:08 +0100 Subject: [sles-beta] Problems with mcelog on HP-Proliant Server with AMD Opteron processors In-Reply-To: References: <40637DBB36AF3941B243A286A432CA0B0E226BBF@HXMB12.pnet.ch> Message-ID: <20130305100608.GA30714@wawa.suse.de> Hi, newer AMD processors, family 16 and greater, do not support mcelog, on SP2 mcelog was just missing the check and the errormessage. The message is not really helpful at the moment since we don't ship edac_mce_amd with the SLES kernel. For now, please just disable mcelog. OTOH, no harm is done if mcelog starts on AMD systems, it will just bail out with that message, nothing else is affected. We're tracking that with bnc#807336, AMD is involved. -- Kind regards / Mit freundlichen Gr??en Michael Krapp, Technical Support Engineer Worldwide Support Services Linux SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 21284 (AG N?rnberg) Maxfeldstr. 5, D-90409 N?rnberg T: +49-911-74053-0 F: +49-911-74053-679 * Greg.Lehmann at csiro.au schrieb 20130305 08:08: > I noticed this on a AMD server too but since I had not installed SP2 on there before, I didn't know it had changed. > > Greg > > > -----Original Message----- > > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta- > > bounces at lists.suse.com] On Behalf Of urs.frey at post.ch > > Sent: Monday, 4 March 2013 7:57 PM > > To: sles-beta at lists.suse.com > > Subject: [sles-beta] Problems with mcelog on HP-Proliant Server with > > AMD Opteron processors > > > > Hi > > > > Installation of SLES11-SP3 beta2 works smoothly. > > I am testing on: > > HP Proliant DL385-G5 > > HP Proliant BL465c-G7 Blade: AMD Opteron(tm) Processor 6172 > > HP Proliant BL465c-Gen8 Blade : AMD Opteron(TM) Processor 6220 > > HP Proliant BL460c-Gen8 Blade : Intel(R) Xeon(R) CPU E5-2660 0 @ > > 2.20GHz > > > > The only thing which irritates me, is that mcelog failed message on my > > console: > > > > On all AMD Opteron Processors models I get this failure: "CPU is > > unsupported" > > > > h04syy:/etc/init.d # /etc/init.d/mcelog start > > Starting mcelog... CPU is unsupported > > startproc: exit status of parent of /usr/sbin/mcelog: 1 > > failed > > h04syy:/etc/init.d # > > > > I mean under SLES11-SP2 mcelog works with no failure. > > On SLES11-SP2 there is an older release of mcelog > > > > h04wwl:~ # uname -a > > Linux h04wwl 3.0.58-0.6.6-default #1 SMP Tue Feb 19 11:07:00 UTC 2013 > > (1576ecd) x86_64 x86_64 x86_64 GNU/Linux > > h04wwl:~ # cat /etc/SuSE-release > > SUSE Linux Enterprise Server 11 (x86_64) > > VERSION = 11 > > PATCHLEVEL = 2 > > h04wwl:~ # > > h04wwl:~ # cat /proc/cpuinfo | grep "model name" > > model name : AMD Opteron(tm) Processor 6172 > > h04wwl:~ # ps -ef | grep mcelog > > root 5603 1 0 Feb27 ? 00:00:00 /usr/sbin/mcelog -- > > daemon --config-file /etc/mcelog/mcelog.conf > > root 31534 31503 0 10:27 pts/0 00:00:00 grep mcelog > > h04wwl:~ # cat /var/run/mcelog.pid > > 5603 > > h04wwl:~ # > > freyu at h04wwl:~> rpm -q --changelog mcelog-1.0.2011.06.08-0.11.1 | less > > * Tue Apr 17 2012 trenn at suse.de > > - Add Ivy Bridge support (bnc#748484) > > - Add forgotten CPU model 0x25 (bnc#742716) > > > > On Intel mcelog works on SLES11-SP3 beta2 > > model name : Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20GHz > > h05cni:~ # > > h05cni:~ # uname -a > > Linux h05cni 3.0.65-0.9-default #1 SMP Mon Feb 25 07:21:23 UTC 2013 > > (055263a) x86_64 x86_64 x86_64 GNU/Linux > > h05cni:~ # cat /etc/SuSE-release > > SUSE Linux Enterprise Server 11 (x86_64) > > VERSION = 11 > > PATCHLEVEL = 3 > > h05cni:~ # ps -ef | grep mcelog | grep -v grep > > root 4949 1 0 10:33 ? 00:00:00 /usr/sbin/mcelog -- > > daemon --config-file /etc/mcelog/mcelog.conf > > h05cni:~ # cat /var/run/mcelog.pid > > 4949 > > h05cni:~ # > > > > But on AMD processors mcelog does not work anymore on SLES11-SP3 beta2 > > model name : AMD Opteron(TM) Processor 6220 > > h05cnh:~ # ps -ef | grep mcelog | grep -v grep > > h05cnh:~ # uname -a > > Linux h05cnh 3.0.65-0.9-default #1 SMP Mon Feb 25 07:21:23 UTC 2013 > > (055263a) x86_64 x86_64 x86_64 GNU/Linux > > h05cnh:~ # cat /etc/SuSE-release > > SUSE Linux Enterprise Server 11 (x86_64) > > VERSION = 11 > > PATCHLEVEL = 3 > > h05cnh:~ # > > > > > > With SLES11-SP3 a new release of mcelog has been included: This is new > > in the RPM changelog: > > h05cnh:~ # rpm -qa | grep mcelog > > mcelog-1.0.2013.01.18-0.7.7 > > h05cnh:~ # rpm -q --changelog mcelog-1.0.2013.01.18-0.7.7 | less > > * Mon Jan 21 2013 trenn at suse.de > > - Updated to latest git state (2013-01-18) (fate#313746) > > and removed patches which went upstream meanwhile (for example > > enabling ivybridge, fate#313745). This one has latest IvyBridge EX/EP > > CPU decoding support > > - Removed wrongly used getdomainname call and replaced it with > > a dnslookup call as done in factory for a while > > > > QUESTION: > > Is there now a special configuration needed for AMD Opteron processors? > > When I diff /etc/mcelog/mcelog.conf from SLES11-SP2 and SLES11-SP3 > > there is no difference at all. > > > > So why is there the message "CPU is unsupported" only on Amd Opteron > > processors? > > Can it be, that with the removal of patches, some AMD specific code has > > been removed? > > > > Thanks for your feedback > > Best regards > > > > Urs Frey > > Die Schweizerische Post > > Services > > Informationstechnologie > > Webergutstrasse 12 > > 3030 Bern (Zollikofen) > > Telefon : ++41 (0)58 338 58 70 > > FAX : ++41 (0)58 667 30 07 > > E-Mail: urs.frey at post.ch > > > > > > _______________________________________________ > > sles-beta mailing list > > sles-beta at lists.suse.com > > http://lists.suse.com/mailman/listinfo/sles-beta > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Michael Abschmecken ist feige... From mail at marcusmoeller.ch Tue Mar 5 05:18:26 2013 From: mail at marcusmoeller.ch (Marcus Moeller) Date: Tue, 05 Mar 2013 13:18:26 +0100 Subject: [sles-beta] Submit SR Message-ID: <5135E292.6010202@marcusmoeller.ch> Hi all, one of you has mentioned in the first Beta Call, that it will be possible to submit Service Requests through the SR-Portal. Sadly I cannot see an beta-entitlement to associate with. Greets Marcus From uwedr at suse.com Tue Mar 5 05:50:56 2013 From: uwedr at suse.com (Uwe Drechsel) Date: Tue, 5 Mar 2013 13:50:56 +0100 Subject: [sles-beta] Submit SR In-Reply-To: <5135E292.6010202@marcusmoeller.ch> References: <5135E292.6010202@marcusmoeller.ch> Message-ID: <20130305125056.GM26394@suse.de> Hi Marcus, please send me your support contact ID, which can be found/changed at the bottome of the page to open a SR. I'll check. If someoneelse should have similar problems, please also let me know at beta-programs at suse.de Thanks Uwe -- Uwe Drechsel SUSE Linux Beta Program Manager SUSE Linux Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) On Tue, Mar 05, Marcus Moeller wrote: > Hi all, > > one of you has mentioned in the first Beta Call, that it will be > possible to submit Service Requests through the SR-Portal. Sadly I > cannot see an beta-entitlement to associate with. > > Greets > Marcus > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > From behlert at suse.de Wed Mar 6 18:50:22 2013 From: behlert at suse.de (Stefan Behlert) Date: Thu, 7 Mar 2013 02:50:22 +0100 Subject: [sles-beta] hw driver wacom tablet In-Reply-To: References: <5135E292.6010202@marcusmoeller.ch> Message-ID: <20130307015022.GD28232@suse.de> Hi, On Mar 05, 13 13:39:09 +0100, michael.baensch at dfs.de wrote: > Hello, > > there is a seperation of kernel driver (included since kernel 3.0) and X11 > input driver (x11 input wacom comes with SLED). > Maybe one of the SUSE people know, if there was an driver update, because > there are/were new wacom tablets (HD Models) last year. The answer depends a little bit on the type of device. If it's an USB device, there's a good chance that it's suported in the kernel. If it's a serial device, then it's most likely not supported - we had no update of x11-waco,mm, which would be required for that. The problem with updating linuxwacom is that the most recent releases require an update of the xorg server to something higher than 1.6 (which we currently have). And an update of that is no option for a Service Pack. I hope this helps, let me know if there's a specific device you see issues with, so we can check if there's something we can/need to do. Stefan > > Thanks > Michael > > DFS Deutsche Flugsicherung GmbH > Am DFS-Campus 10 > 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 Behlert, SUSE LINUX Project Manager Enterprise Desktop Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE LINUX Products GmbH, Nuernberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuernberg) From Glenn.Andersson at ostersund.se Wed Mar 6 18:50:33 2013 From: Glenn.Andersson at ostersund.se (Glenn Andersson sf) Date: Thu, 07 Mar 2013 02:50:33 +0100 Subject: [sles-beta] hw driver wacom tablet Message-ID: Hej, ?r ledig men ?ter m?ndag. Vid br?dskande ?renden kontakta kundservice p? 063-140600. M V H Glenn Andersson Datacenter ?stersunds Kommun -------------- next part -------------- An HTML attachment was scrubbed... URL: From john.dallman at siemens.com Thu Mar 7 03:19:51 2013 From: john.dallman at siemens.com (Dallman, John) Date: Thu, 7 Mar 2013 10:19:51 +0000 Subject: [sles-beta] GCC 4.7? Message-ID: I'm mostly interested in SLES11sp3 as a platform for C++11 development with GCC 4.7. My sysadmin can't find GCC 4.7 on the first SDK DVD from Beta 1. The second DVD one is a little more fiddly to access, because it needs dual-layer drives and media, and we'd expect that to be sources anyway. Is GCC 4.7 provided with beta 1? Beta 2? thanks, -- John Dallman ----------------- Siemens Industry Software Limited is a limited company registered in England and Wales. Registered number: 3476850. Registered office: Faraday House, Sir William Siemens Square, Frimley, Surrey, GU16 8QD. From aj at suse.com Thu Mar 7 03:40:12 2013 From: aj at suse.com (Andreas Jaeger) Date: Thu, 07 Mar 2013 11:40:12 +0100 Subject: [sles-beta] GCC 4.7? In-Reply-To: References: Message-ID: <51386E8C.3010709@suse.com> On 03/07/2013 11:19 AM, Dallman, John wrote: > I'm mostly interested in SLES11sp3 as a platform for C++11 development > with GCC 4.7. My sysadmin can't find GCC 4.7 on the first SDK DVD from > Beta 1. The second DVD one is a little more fiddly to access, because > it needs dual-layer drives and media, and we'd expect that to be sources > anyway. > > Is GCC 4.7 provided with beta 1? Beta 2? It should be on the first SDK DVD: aj at byrd:/SLE-11-SP3-SDK-Beta2/x86_64/DVD1/suse/x86_64> l gcc47-* -rw-r--r-- 1 nobody nobody 2226581 Feb 22 20:37 gcc47-32bit-4.7.2_20130108-0.15.10.x86_64.rpm -rw-r--r-- 1 nobody nobody 6909767 Feb 22 20:37 gcc47-4.7.2_20130108-0.15.10.x86_64.rpm -rw-r--r-- 1 nobody nobody 5006392 Feb 22 20:37 gcc47-c++-4.7.2_20130108-0.15.10.x86_64.rpm -rw-r--r-- 1 nobody nobody 1405476 Feb 22 20:37 gcc47-fortran-32bit-4.7.2_20130108-0.15.10.x86_64.rpm -rw-r--r-- 1 nobody nobody 6228716 Feb 22 20:37 gcc47-fortran-4.7.2_20130108-0.15.10.x86_64.rpm -rw-r--r-- 1 nobody nobody 1429816 Feb 22 20:37 gcc47-info-4.7.2_20130108-0.15.10.x86_64.rpm -rw-r--r-- 1 nobody nobody 1918047 Feb 22 20:37 gcc47-locale-4.7.2_20130108-0.15.10.x86_64.rpm The libraries are there as well. Please ask your sysadmin to install the package gcc47-c++ (with its dependencies) for C++ development. Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imend?rffer,HRB16746 (AG N?rnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From kukuk at suse.de Thu Mar 7 03:41:02 2013 From: kukuk at suse.de (Thorsten Kukuk) Date: Thu, 7 Mar 2013 11:41:02 +0100 Subject: [sles-beta] GCC 4.7? In-Reply-To: References: Message-ID: <20130307104102.GA18882@suse.de> On Thu, Mar 07, Dallman, John wrote: > I'm mostly interested in SLES11sp3 as a platform for C++11 development > with GCC 4.7. My sysadmin can't find GCC 4.7 on the first SDK DVD from > Beta 1. The second DVD one is a little more fiddly to access, because > it needs dual-layer drives and media, and we'd expect that to be sources > anyway. > > Is GCC 4.7 provided with beta 1? Beta 2? GCC 4.7 is on the first SDK DVD. Most of the needed packages have a "gcc47" prefix. I have no clue how someboday can not find it ... Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From john.dallman at siemens.com Thu Mar 7 03:54:56 2013 From: john.dallman at siemens.com (Dallman, John) Date: Thu, 7 Mar 2013 10:54:56 +0000 Subject: [sles-beta] GCC 4.7? In-Reply-To: <20130307104102.GA18882@suse.de> References: <20130307104102.GA18882@suse.de> Message-ID: Thorsten Kukuk wrote: > GCC 4.7 is on the first SDK DVD. Most of the needed packages have > a "gcc47" prefix. I have no clue how someboday can not find it ... Andreas Jaeger [aj at suse.com] wrote: > aj at byrd:/SLE-11-SP3-SDK-Beta2/x86_64/DVD1/suse/x86_64> l gcc47-* > -rw-r--r-- 1 nobody nobody 2226581 Feb 22 20:37 gcc47-32bit-4.7.2_20130108-0.15.10.x86_64.rpm > -rw-r--r-- 1 nobody nobody 6909767 Feb 22 20:37 gcc47-4.7.2_20130108-0.15.10.x86_64.rpm > -rw-r--r-- 1 nobody nobody 5006392 Feb 22 20:37 gcc47-c++-4.7.2_20130108-0.15.10.x86_64.rpm ... Thanks, I'll grab Beta 2 and tell them to look properly. -- John Dallman ----------------- Siemens Industry Software Limited is a limited company registered in England and Wales. Registered number: 3476850. Registered office: Faraday House, Sir William Siemens Square, Frimley, Surrey, GU16 8QD. From martin.wilck at ts.fujitsu.com Thu Mar 7 11:18:09 2013 From: martin.wilck at ts.fujitsu.com (Martin Wilck) Date: Thu, 07 Mar 2013 19:18:09 +0100 Subject: [sles-beta] UEFI + PXE Message-ID: <5138D9E1.40005@ts.fujitsu.com> Is there documentation somewhere how to configure a server to boot the SLES11 SP3 installation via UEFI + PXE? - What boot loader EFI binary should be used for PXE? - How should the configuration look like for the boot loader? - Can I use the ordinary "linux" and "initrd" files from the ISO image? - anything else? Currently I am using a GRUB1 bootloader with a config file looking like this: title SLES11-SP3 root (nd) kernel /sles11-sp3/boot/x86_64/loader/linux install=http://192.168.253.5/install/suse/ix86/sles11-sp3 initrd /sles11-sp3/boot/x86_64/loader/initrd I see that kernel and initrd are loaded by GRUB, but then, nothing happens. With a Fedora 18 kernel + initrd, the installation starts. 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 urs.frey at post.ch Mon Mar 11 08:56:13 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Mon, 11 Mar 2013 14:56:13 +0000 Subject: [sles-beta] Problem with facter BUG in SLES11 facter version 1.5.2 Message-ID: <40637DBB36AF3941B243A286A432CA0B0E22877D@HXMB12.pnet.ch> Dear all We do have an issue with the facter version in SLES11-SP2 & SLES11-SP3 facter-1.5.2-1.20 h04szd:~ # uname -a Linux h04szd 3.0.65-0.9-default #1 SMP Mon Feb 25 07:21:23 UTC 2013 (055263a) x86_64 x86_64 x86_64 GNU/Linux h04szd:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 3 h04szd:~ # rpm -qa | grep facter facter-1.5.2-1.20 h04szd:~ # It is a known bug , known by puppetlabs and documented here: http://projects.puppetlabs.com/issues/7039 When declaring several facts in a single file, Facter won't pick them up properly: It is easy to reproduce: h04szd:~ # cat test_facts.rb # test_facts.rb Facter.add(:test_fact1) do setcode do "test fact 1" end end Facter.add(:test_fact2) do setcode do "test fact 2" end end h04szd:~ # h04szd:~ # export FACTERLIB=/root/ h04szd:~ # facter | grep test test_fact1 => test fact 1 test_fact2 => test fact 2 h04szd:~ # Now when trying to retrieve one of these facts, facter does not work h04szd:~ # facter --version 1.5.2 h04szd:~ # facter test_fact1 h04szd:~ # facter test_fact2 facter does not work with several facts declared, because the declaration file needs to be named exactly the way the fact is called in this existing version of facter on SLES11: If I have only one fact declared in one file: h04szd:~ # ll test_fact1.rb -rw-r--r-- 1 root root 92 Mar 11 15:34 test_fact1.rb h04szd:~ # cat test_fact1.rb # test_facts.rb Facter.add(:test_fact1) do setcode do "test fact 1" end end h04szd:~ # facter test_fact1 test fact 1 h04szd:~ # When doing the very same test on a newer facter version this multi declaration of facts in only one file works [root at vtst1a ~]# cat test_facts.rb # test_facts.rb Facter.add(:test_fact1) do setcode do "test fact 1" end end Facter.add(:test_fact2) do setcode do "test fact 2" end end [root at vtst1a ~]# [root at vtst1a ~]# facter --version 1.6.4 [root at vtst1a ~]# facter test_fact1 test fact 1 [root at vtst1a ~]# facter test_fact2 test fact 2 [root at vtst1a ~]# Would there be a lot of work, if I ask kindly to update, or fix this bug, by an appropriate backport? For us here it would save us a lot of work in creating our own private facter-RPM and update the entire platform of several hundred servers to our own private RPM package. I mean , we would need to create updates for the entire private puppet packages and the find a way to remotely remove the SLES facter package and install the newly created private facter package. Thanks for considering this problem Best regards Urs Frey Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX : ++41 (0)58 667 30 07 E-Mail: urs.frey at post.ch From kukuk at suse.de Wed Mar 13 03:28:37 2013 From: kukuk at suse.de (Thorsten Kukuk) Date: Wed, 13 Mar 2013 10:28:37 +0100 Subject: [sles-beta] Apache2 version obviously from SP1 and not from SP2 and GCC4.7 libs are missing. In-Reply-To: References: Message-ID: <20130313092837.GA13268@suse.de> Hi, On Wed, Mar 13, Huenteler, Thomas wrote: > Hi, > > we detected that Apache2 in SP3 BETA2 is not the latest one. > > In SP3 contain Apache: apache2-2.2.12-1.30.1.x86_64 > > Latest SP2 update contains apache2-2.2.12-1.36.1.x86_64 Correct, updates, which where released after we mastered Beta2, cannot be part of Beta2. > Furthermore the following libs are missing > > nothing provides libgcc47 > nothing provides libstdc++47 > > for the gcc47 I have no problems to install gcc47 and yast/zypper are both able to resolve all dependencys. How did you try to install gcc47? Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From mge at suse.com Wed Mar 13 09:56:34 2013 From: mge at suse.com (Matthias G. Eckermann) Date: Wed, 13 Mar 2013 16:56:34 +0100 Subject: [sles-beta] few things to note after my first install In-Reply-To: References: <20130221103545.GC24104@suse.de> Message-ID: <20130313155633.GC23874@suse.com> Hello Maximilian and all, sorry for not responding more quickly: I was traveling. So, we have two questions here (at least): 1. ext4: why not fully supported yet? SLES 12? 2. reiserfs quality On 2013-03-04 T 15:39 +0100 Decker Maximilian wrote: > please, any official comment on why there is no ext4 > support in SLES 11, even in SP3 ? This question is asked > quite a lot by our customers, and I am running out of > arguments here. Especially when it comes to "but in RHEL > there is .... " To some degree I could understand that for > 11, it was missing from the beginning. But what are the > odds that we see ext4 in 12? 1. There are several reasons, why we do not support ext4 in read-write-mode yet (we do support it in read-only-mode), as you may know from studying the release notes. For more details I probably will provide a longer E-Mail or even a public blog in the comming days. To give you an idea already, about why we are not supporting it yet: * Missing Scalability, specifically compared to XFS. As you know, we do support XFS in SLES for 8+ years already without extra costs. * Questions about ext4's reliability specifically on multi-disk backends (there should be some public information about this). As far as I know that's the reason, why another Linux distributor is using XFS underneath their storage product and not ext4, even if ext4 is their default filesystem. That should tell us something, ... * Supporting a filesystem needs more than just support for the Kernel module, but integration, QA, certifications, ... For SUSE Linux Enterprise 12 we plan to follow the upstream development in the Kernel area, and as you may know, ext3 and ext4 are now served by one Kernel module. > Btw - you know that reiserfs (v3) has some serious > stability issues as of post-2.6.35 kernels, right ? The > BKL replacements somehow rendered reiserfs prone to > deadlocking in a more or less frequent manner. These > issues seem to exist up to at least the current 3.8 > kernels. So (in theory) also SLE >= SP2 (i.e. 3.0.x) > kernels might be affected. But the good thing is - I > cannot tell for sure as none of our maintained SLES 11 > installations is on reiserfs. (same with btrfs) 2. Where does your information about ReiserFS come from? Are you sure that this information is valid for SUSE Linux Enterprise Kernels? We certainly do have additional patches in ReiserFS in the SUSE Linux Enterprise Kernel, which might not yet have been accepted / shiped upstream. I checked back with our Kernel team, and we do not have any reports or issues open with ReiserFS currently. Do you see ReiserFS issues with SUSE Linux Enterprise in your environment? -- In that case, please open an SR. so long - MgE > -----Urspr?ngliche Nachricht----- > Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Swartz, Patrick H > Gesendet: Sonntag, 24. Februar 2013 19:57 > An: 'SUSE Linux Enterprise Server Authorized Beta Program' > Betreff: Re: [sles-beta] few things to note after my first install > To add to that, we can't/won't be able to use BTRFS > until it can support /boot. Our SLES11 deployment model > is based on using Atomic updates, which requires the > first 2 partitions to be dedicated to Atomic. So, that > means that /boot is therefore incorporated into the root > partition. The ability to roll back patches and > upgrades is critical, but not being able to roll back a > kernel makes BTRFS useless for us. Just my 2cents worth > from the field... > Patrick Swartz > > -----Original Message----- > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Decker Maximilian > Sent: Sunday, February 24, 2013 11:25 AM > To: 'SUSE Linux Enterprise Server Authorized Beta Program' > Subject: Re: [sles-beta] few things to note after my first install > Hi list, > > regarding the lack of (supported) ext4, just out of > curiosity - what exactly is SuSE's reason behind > obviously abandoning ext4, which by now is a well known, > fast and proven evolution to ext3 ? > > Of course, BTRFS really is the cool new stuff, and it > seems like it will become an amazing alternative. But to > be honest none of our SLES customers is actually running > BTRFS in their datacenters yet. Some lab or testing > installations do exist, though, however bottom line is - > for production systems we are effectively stuck with > ext3. (sometimes even due to missing support from 3rd > party SW vendors) > > If I understand correctly ext4 might also be missing in > SLES 12. And I know there are plenty of discussions on > this matter all around the internet, but hey, I hope > with the current Beta maybe SuSE can shed some official > light on that. Really would be great to know. > > Please don't get me wrong, I know there are quite a > bunch of brilliant developers at SuSE that are giving > their blessings to the current state of BTRFS, and we > also got official SuSE support on that, but it just does > not help "in the field".... people still consider it > beta. > > > thanks, > > - Maximilian > > -----Original Message----- > > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta- > > bounces at lists.suse.com] On Behalf Of Thorsten Kukuk > > Sent: Thursday, 21 February 2013 8:36 PM > > To: SUSE Linux Enterprise Server Authorized Beta Program > > Subject: Re: [sles-beta] few things to note after my first install > > > > On Thu, Feb 21, Greg.Lehmann at csiro.au wrote: > > > <---& -----> > > > > > 2. I can't believe we have btrfs as a filesystem option but no > > ext4 - again SLES 12 hopefully. > > > > I don't think that this will change. > -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From Maximilian.Decker at cancom.de Wed Mar 13 10:56:29 2013 From: Maximilian.Decker at cancom.de (Decker Maximilian) Date: Wed, 13 Mar 2013 17:56:29 +0100 Subject: [sles-beta] few things to note after my first install In-Reply-To: <20130313155633.GC23874@suse.com> References: <20130221103545.GC24104@suse.de> <20130313155633.GC23874@suse.com> Message-ID: Hi MgE, thanks a bunch for your feedback, I almost gave up hope... So it seems like there is a chance for getting fully supported r/w ext4 in SLES 12, well that would be great. And I know it might not be the best filesystem to choose for every scenario, but (IMHO) at least for the local filesystems it is quite superior to ext3 (and yes, many different reasons and opinions here ... we can skip that ;-) At least, if we are able to select ext4, many discussions will be avoided, whether or not we actually use ext4 then. Anyway, regarding my reiserfs3 comments - I was referring to this long-standing-but-still-stuck bug report: https://bugzilla.kernel.org/show_bug.cgi?id=29162 As I said, I do not have SLES 11 SP2 systems running on reiserfs3, so I cannot tell if SLES is affected here. But I guess it is. There even is a @suse mail address involved (CC on bugzilla), so if there were any SuSE specific fixes to that I think they would have been committed upstream already. Really looking forward to your mentioned blog post. thanks - Maximilian -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Matthias G. Eckermann Gesendet: Mittwoch, 13. M?rz 2013 16:57 An: SUSE Linux Enterprise Server Authorized Beta Program Betreff: Re: [sles-beta] few things to note after my first install Hello Maximilian and all, sorry for not responding more quickly: I was traveling. So, we have two questions here (at least): 1. ext4: why not fully supported yet? SLES 12? 2. reiserfs quality On 2013-03-04 T 15:39 +0100 Decker Maximilian wrote: > please, any official comment on why there is no ext4 support in SLES > 11, even in SP3 ? This question is asked quite a lot by our customers, > and I am running out of arguments here. Especially when it comes to > "but in RHEL there is .... " To some degree I could understand that > for 11, it was missing from the beginning. But what are the odds that > we see ext4 in 12? 1. There are several reasons, why we do not support ext4 in read-write-mode yet (we do support it in read-only-mode), as you may know from studying the release notes. For more details I probably will provide a longer E-Mail or even a public blog in the comming days. To give you an idea already, about why we are not supporting it yet: * Missing Scalability, specifically compared to XFS. As you know, we do support XFS in SLES for 8+ years already without extra costs. * Questions about ext4's reliability specifically on multi-disk backends (there should be some public information about this). As far as I know that's the reason, why another Linux distributor is using XFS underneath their storage product and not ext4, even if ext4 is their default filesystem. That should tell us something, ... * Supporting a filesystem needs more than just support for the Kernel module, but integration, QA, certifications, ... For SUSE Linux Enterprise 12 we plan to follow the upstream development in the Kernel area, and as you may know, ext3 and ext4 are now served by one Kernel module. > Btw - you know that reiserfs (v3) has some serious stability issues as > of post-2.6.35 kernels, right ? The BKL replacements somehow rendered > reiserfs prone to deadlocking in a more or less frequent manner. These > issues seem to exist up to at least the current 3.8 kernels. So (in > theory) also SLE >= SP2 (i.e. 3.0.x) kernels might be affected. But > the good thing is - I cannot tell for sure as none of our maintained > SLES 11 installations is on reiserfs. (same with btrfs) 2. Where does your information about ReiserFS come from? Are you sure that this information is valid for SUSE Linux Enterprise Kernels? We certainly do have additional patches in ReiserFS in the SUSE Linux Enterprise Kernel, which might not yet have been accepted / shiped upstream. I checked back with our Kernel team, and we do not have any reports or issues open with ReiserFS currently. Do you see ReiserFS issues with SUSE Linux Enterprise in your environment? -- In that case, please open an SR. so long - MgE > -----Urspr?ngliche Nachricht----- > Von: sles-beta-bounces at lists.suse.com > [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Swartz, > Patrick H > Gesendet: Sonntag, 24. Februar 2013 19:57 > An: 'SUSE Linux Enterprise Server Authorized Beta Program' > Betreff: Re: [sles-beta] few things to note after my first install > To add to that, we can't/won't be able to use BTRFS until it can > support /boot. Our SLES11 deployment model is based on using Atomic > updates, which requires the first 2 partitions to be dedicated to > Atomic. So, that means that /boot is therefore incorporated into the > root partition. The ability to roll back patches and upgrades is > critical, but not being able to roll back a kernel makes BTRFS useless > for us. Just my 2cents worth from the field... > Patrick Swartz > > -----Original Message----- > From: sles-beta-bounces at lists.suse.com > [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Decker > Maximilian > Sent: Sunday, February 24, 2013 11:25 AM > To: 'SUSE Linux Enterprise Server Authorized Beta Program' > Subject: Re: [sles-beta] few things to note after my first install > Hi list, > > regarding the lack of (supported) ext4, just out of curiosity - what > exactly is SuSE's reason behind obviously abandoning ext4, which by > now is a well known, fast and proven evolution to ext3 ? > > Of course, BTRFS really is the cool new stuff, and it seems like it > will become an amazing alternative. But to be honest none of our SLES > customers is actually running BTRFS in their datacenters yet. Some > lab or testing installations do exist, though, however bottom line is > - for production systems we are effectively stuck with ext3. > (sometimes even due to missing support from 3rd party SW vendors) > > If I understand correctly ext4 might also be missing in SLES 12. And > I know there are plenty of discussions on this matter all around the > internet, but hey, I hope with the current Beta maybe SuSE can shed > some official light on that. Really would be great to know. > > Please don't get me wrong, I know there are quite a bunch of brilliant > developers at SuSE that are giving their blessings to the current > state of BTRFS, and we also got official SuSE support on that, but it > just does not help "in the field".... people still consider it beta. > > > thanks, > > - Maximilian > > -----Original Message----- > > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta- > > bounces at lists.suse.com] On Behalf Of Thorsten Kukuk > > Sent: Thursday, 21 February 2013 8:36 PM > > To: SUSE Linux Enterprise Server Authorized Beta Program > > Subject: Re: [sles-beta] few things to note after my first install > > > > On Thu, Feb 21, Greg.Lehmann at csiro.au wrote: > > > <---& -----> > > > > > 2. I can't believe we have btrfs as a filesystem option but no > > ext4 - again SLES 12 hopefully. > > > > I don't think that this will change. > -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From mge at suse.com Wed Mar 13 16:49:57 2013 From: mge at suse.com (Matthias G. Eckermann) Date: Wed, 13 Mar 2013 23:49:57 +0100 Subject: [sles-beta] few things to note after my first install In-Reply-To: References: <20130221103545.GC24104@suse.de> <20130313155633.GC23874@suse.com> Message-ID: <20130313224957.GA25368@suse.com> Hello Maximilan and all, On 2013-03-13 T 17:56 +0100 Decker Maximilian wrote: > thanks a bunch for your feedback, I almost gave up hope... > > So it seems like there is a chance for getting fully > supported r/w ext4 in SLES 12, well that would be great. > And I know it might not be the best filesystem to choose > for every scenario, but (IMHO) at least for the local > filesystems it is quite superior to ext3 (and yes, many > different reasons and opinions here ... we can skip that > ;-) At least, if we are able to select ext4, many > discussions will be avoided, whether or not we actually > use ext4 then. This is understood. > Anyway, regarding my reiserfs3 comments - I was referring > to this long-standing-but-still-stuck bug report: > https://bugzilla.kernel.org/show_bug.cgi?id=29162 Ah, good to have some data points. > As I said, I do not have SLES 11 SP2 systems running on > reiserfs3, so I cannot tell if SLES is affected here. But > I guess it is. There even is a @suse mail address involved > (CC on bugzilla), so if there were any SuSE specific fixes > to that I think they would have been committed upstream > already. I will ask in our development team. so long - MgE > Really looking forward to your mentioned blog post. > -----Urspr?ngliche Nachricht----- > Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Matthias G. Eckermann > Gesendet: Mittwoch, 13. M?rz 2013 16:57 > An: SUSE Linux Enterprise Server Authorized Beta Program > Betreff: Re: [sles-beta] few things to note after my first install > > Hello Maximilian and all, > > sorry for not responding more quickly: I was traveling. > > So, we have two questions here (at least): > 1. ext4: why not fully supported yet? SLES 12? > 2. reiserfs quality > > On 2013-03-04 T 15:39 +0100 Decker Maximilian wrote: > > > please, any official comment on why there is no ext4 support in SLES > > 11, even in SP3 ? This question is asked quite a lot by our customers, > > and I am running out of arguments here. Especially when it comes to > > "but in RHEL there is .... " To some degree I could understand that > > for 11, it was missing from the beginning. But what are the odds that > > we see ext4 in 12? > > 1. There are several reasons, why we do not support ext4 in > read-write-mode yet (we do support it in read-only-mode), > as you may know from studying the release notes. > > For more details I probably will provide a longer E-Mail > or even a public blog in the comming days. To give you an > idea already, about why we are not supporting it yet: > > * Missing Scalability, specifically compared to XFS. > As you know, we do support XFS in SLES for 8+ years > already without extra costs. > > * Questions about ext4's reliability specifically on > multi-disk backends (there should be some public > information about this). As far as I know that's the > reason, why another Linux distributor is using > XFS underneath their storage product and not ext4, > even if ext4 is their default filesystem. That should > tell us something, ... > > * Supporting a filesystem needs more than just support > for the Kernel module, but integration, QA, > certifications, ... > > For SUSE Linux Enterprise 12 we plan to follow the > upstream development in the Kernel area, and as you may > know, ext3 and ext4 are now served by one Kernel module. > > > Btw - you know that reiserfs (v3) has some serious stability issues as > > of post-2.6.35 kernels, right ? The BKL replacements somehow rendered > > reiserfs prone to deadlocking in a more or less frequent manner. These > > issues seem to exist up to at least the current 3.8 kernels. So (in > > theory) also SLE >= SP2 (i.e. 3.0.x) kernels might be affected. But > > the good thing is - I cannot tell for sure as none of our maintained > > SLES 11 installations is on reiserfs. (same with btrfs) > > 2. Where does your information about ReiserFS come from? > > Are you sure that this information is valid for > SUSE Linux Enterprise Kernels? > > We certainly do have additional patches in ReiserFS > in the SUSE Linux Enterprise Kernel, which might > not yet have been accepted / shiped upstream. > > I checked back with our Kernel team, and we do not > have any reports or issues open with ReiserFS currently. > > Do you see ReiserFS issues with SUSE Linux Enterprise > in your environment? -- In that case, please open an SR. > > > so long - > MgE > > > > -----Urspr?ngliche Nachricht----- > > Von: sles-beta-bounces at lists.suse.com > > [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Swartz, > > Patrick H > > Gesendet: Sonntag, 24. Februar 2013 19:57 > > An: 'SUSE Linux Enterprise Server Authorized Beta Program' > > Betreff: Re: [sles-beta] few things to note after my first install > > > To add to that, we can't/won't be able to use BTRFS until it can > > support /boot. Our SLES11 deployment model is based on using Atomic > > updates, which requires the first 2 partitions to be dedicated to > > Atomic. So, that means that /boot is therefore incorporated into the > > root partition. The ability to roll back patches and upgrades is > > critical, but not being able to roll back a kernel makes BTRFS useless > > for us. Just my 2cents worth from the field... > > > Patrick Swartz > > > > -----Original Message----- > > From: sles-beta-bounces at lists.suse.com > > [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Decker > > Maximilian > > Sent: Sunday, February 24, 2013 11:25 AM > > To: 'SUSE Linux Enterprise Server Authorized Beta Program' > > Subject: Re: [sles-beta] few things to note after my first install > > > Hi list, > > > > regarding the lack of (supported) ext4, just out of curiosity - what > > exactly is SuSE's reason behind obviously abandoning ext4, which by > > now is a well known, fast and proven evolution to ext3 ? > > > > Of course, BTRFS really is the cool new stuff, and it seems like it > > will become an amazing alternative. But to be honest none of our SLES > > customers is actually running BTRFS in their datacenters yet. Some > > lab or testing installations do exist, though, however bottom line is > > - for production systems we are effectively stuck with ext3. > > (sometimes even due to missing support from 3rd party SW vendors) > > > > If I understand correctly ext4 might also be missing in SLES 12. And > > I know there are plenty of discussions on this matter all around the > > internet, but hey, I hope with the current Beta maybe SuSE can shed > > some official light on that. Really would be great to know. > > > > Please don't get me wrong, I know there are quite a bunch of brilliant > > developers at SuSE that are giving their blessings to the current > > state of BTRFS, and we also got official SuSE support on that, but it > > just does not help "in the field".... people still consider it beta. > > > > > > thanks, > > > > - Maximilian > > > > -----Original Message----- > > > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta- > > > bounces at lists.suse.com] On Behalf Of Thorsten Kukuk > > > Sent: Thursday, 21 February 2013 8:36 PM > > > To: SUSE Linux Enterprise Server Authorized Beta Program > > > Subject: Re: [sles-beta] few things to note after my first install > > > > > > On Thu, Feb 21, Greg.Lehmann at csiro.au wrote: > > > > > <---& -----> > > > > > > > 2. I can't believe we have btrfs as a filesystem option but no > > > ext4 - again SLES 12 hopefully. > > > > > > I don't think that this will change. > > > > -- > Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise > Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com > SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From urs.frey at post.ch Thu Mar 14 08:54:41 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Thu, 14 Mar 2013 14:54:41 +0000 Subject: [sles-beta] Problem with facter, when using LXC containers : veth2: error fetching interface information: Device not found Message-ID: <40637DBB36AF3941B243A286A432CA0B0E22911F@HXMB12.pnet.ch> Dear all During tests with SLES11-SP3 Beta2 x86_64 I decided by the way to have a closer look at LXC container feature delivered with SLES11. Lightweight virtualization seems to be a very good way when hosting some small applications on a platform. As we do system configuration using puppet & facter with it , I noticed the following error message when invoking facter delivered with SLES11-SP3: vethuU2: error fetching interface information: Device not found veth2: error fetching interface information: Device not found vethuU2: error fetching interface information: Device not found vethuU2: error fetching interface information: Device not found veth2: error fetching interface information: Device not found veth2: error fetching interface information: Device not found architecture => x86_64 So obviously there is something missing in facter, as I do not see similar messages when running XEN or virtualizing with KVM On XEN facter recognizes vif devices : interfaces => bond0,br0,br1,eth0,eth1,tap4.0,tap5.0,tap9.0,tap14.0,vif1.0,vif2.0,vif3.0,vif4.0,vif5.0,vif6.0,vif6.1,vif7.0,vif8.0,vif9.0,vif11.0,vif12.0,vlan1143 On KVM facter recognizes vnet devices: interfaces => br0,eth0,eth1,vnet0,vnet1,vnet2,vnet3 I assume that there is something missing in facter to handle LCX virtualization the correct way What is your opinion? Thanks for feedback h04szd:~ # uname -a Linux h04szd 3.0.65-0.9-default #1 SMP Mon Feb 25 07:21:23 UTC 2013 (055263a) x86_64 x86_64 x86_64 GNU/Linux h04szd:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 3 h04szd:~ # /etc/init.d/lxc list Listing LXC containers... c04szo RUNNING c04szp RUNNING h04szd:~ # netstat -i Kernel Interface table Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg bond0 1500 0 84723 0 13682 0 25951 0 0 0 BMmRU br0 1500 0 54913 0 0 0 7196 0 0 0 BMRU eth0 1500 0 71041 0 0 0 25951 0 0 0 BMsRU eth1 1500 0 13682 0 13682 0 0 0 0 0 BMsRU eth2 1500 0 0 0 0 0 0 0 0 0 BMU eth4 1500 0 0 0 0 0 0 0 0 0 BMRU lo 16436 0 16308 0 0 0 16308 0 0 0 LRU veth2IbtvO 1500 0 6745 0 0 0 53987 0 0 0 BMRU vethuU2VTT 1500 0 6835 0 0 0 53470 0 0 0 BMRU h04szd:~ # facter vethuU2: error fetching interface information: Device not found veth2: error fetching interface information: Device not found vethuU2: error fetching interface information: Device not found vethuU2: error fetching interface information: Device not found veth2: error fetching interface information: Device not found veth2: error fetching interface information: Device not found architecture => x86_64 domain => pnet.ch facterversion => 1.5.2 fqdn => h04szd.pnet.ch hardwaremodel => x86_64 hostname => h04szd interfaces => bond0,br0,eth0,eth1,eth2,eth3,eth4,eth5,veth2,vethuU2 ipaddress => 138.191.39.23 ipaddress_br0 => 138.191.39.23 ipaddress_eth2 => 172.25.96.51 ipaddress_eth4 => 10.226.128.16 kernel => Linux kernelrelease => 3.0.65-0.9-default kernelversion => 3.0.65 macaddress_bond0 => 00:21:5A:C9:2A:0E macaddress_br0 => 00:21:5A:C9:2A:0E macaddress_eth0 => 00:21:5A:C9:2A:0E macaddress_eth1 => 00:21:5A:C9:2A:0E macaddress_eth2 => 00:26:55:D4:55:58 macaddress_eth3 => 00:26:55:D4:55:59 macaddress_eth4 => 00:1B:78:58:A6:E2 macaddress_eth5 => 00:1B:78:58:A6:E3 manufacturer => HP best regards Urs Frey Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX : ++41 (0)58 667 30 07 E-Mail: urs.frey at post.ch From mge at suse.com Thu Mar 14 09:03:06 2013 From: mge at suse.com (Matthias G. Eckermann) Date: Thu, 14 Mar 2013 16:03:06 +0100 Subject: [sles-beta] Intel_Idel - Apci_Idel - Slow Wall Clock time SP1 to SP2 what about SP3? In-Reply-To: <46AC8C81C10B8C48820201DF2AE1D76D01512A@hqmbx6.eur.ad.sag> References: <46AC8C81C10B8C48820201DF2AE1D76D01512A@hqmbx6.eur.ad.sag> Message-ID: <20130314150306.GD31999@suse.com> Hello Dick and all, On 2013-03-14 T 09:55 +0000 Waite, Dick wrote: > Second run with boot parameters set to > intel_idle.max_cstate=0 processor.max_cstate=0 idle=mwait > I have a pretty nasty heads-up. If you have > hardware using an Intel XEON and a newer Linux > kernel, you may be experiencing very high CPU > latency. You can check yourself: > > cat /sys/devices/system/cpu/cpuidle/current_driver > > If it says intel_idle, the Linux kernel will > *aggressively* put your CPU to sleep. We > definitely noticed this, and it's pretty darn > painful. But it's *more* painful in your > asynchronous, standby, or otherwise less busy > nodes. Why? > > As you can imagine, the secondary nodes don't get > much activity, so spend most of their time > sleeping. Now the CPU has a lot more sleep time, > and wake latency while trying to copy data or > process new WAL traffic. we are aware of this issue and are working on an analysis together with our hardware partners. We do not know yet, if this issue can be fixed in sw, or if requires firmware updates on the hw side. We will keep you posted. so long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From mkraft at suse.com Thu Mar 14 10:51:49 2013 From: mkraft at suse.com (Marcus Kraft) Date: Thu, 14 Mar 2013 17:51:49 +0100 Subject: [sles-beta] Upcoming SLE 11 SP3 beta 3 release with a short delay Message-ID: <201303141751.49778.mkraft@suse.com> Dear beta test participants, please stay turned for the upcoming SLE 11 SP3 beta 3 release while we are working on resolving issues found late during our pre-release quality assurance test. We expect a new set of tested images for download during or shortly after the weekend, and we will notify you on the resepective mailing list if they are ready for download. Best regards, your SUSE beta team. -- Marcus Kraft Senior Product Manager - SUSE Linux Enterprise SUSE mkraft at suse.com (P) +49 911 74053-171 (F) +49 911 74053-483 SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Maxfeldstra?e 5, 90409 N?rnberg, Germany "We Adapt. You Succeed" www.suse.com Follow us at twitter.com/SLE4Systemz From Maximilian.Decker at cancom.de Fri Mar 15 06:47:42 2013 From: Maximilian.Decker at cancom.de (Decker Maximilian) Date: Fri, 15 Mar 2013 13:47:42 +0100 Subject: [sles-beta] SLES Storage / MD RAID feature Message-ID: Hi list, maybe someone at SuSE is also able to give some comments on this one. Background is: When migrating Unix-Systems to the Linux platform, especially with HP-UX being the source, there seems to be one very specific drawback concerning LVM and logical disk mirrors. Let's say if I wanted to have LVM'ed filesystems (non-clustered, i.e. like ext3) and want them deployed as RAID 1 mirror at two dedicated storage systems (or even datacenters), one option would be to use host based RAID 1 instead of a more expensive und less flexible storage mirror. (with flexible I mean "not to be vendor locked with future upgrades") General recommendation in Linux land (AFAIK) sees LVM for just the volume pools and MD as the RAID layer (so no LVM RAID). Syncing (esp. re-syncing) the mirror has improved dramatically with the introduction of the write-intent bitmap. But there is one thing that would be really nice to have, and I wonder if there are any plans for SLES to actually provide that in the future: With lvdisplay -v on HP-UX you can get the full list of all the logical extents showing their state, which can be "current" or "stale". In case of a "stale" extent, re-sycing that specific extent is possible. In any case, you get a great and detailed overview on the status of the RAID mirror. Of course the system has to keep track of that list, meaning some kind of database is needed, thus resulting in a bit of performance penalty. (->/etc/lvmconf/* on HP-UX) So, long story short - something like this already on the SLES roadmap ? Or maybe already there and I just missed it ? (/proc/mdstat only shows a very generic form of status display here) And yes, if not, well it actually is some kind of feature request then ;-) thanks, - Maximilian From lmb at suse.com Fri Mar 15 08:58:47 2013 From: lmb at suse.com (Lars Marowsky-Bree) Date: Fri, 15 Mar 2013 15:58:47 +0100 Subject: [sles-beta] SLES Storage / MD RAID feature In-Reply-To: References: Message-ID: <20130315145847.GE7949@suse.de> On 2013-03-15T13:47:42, Decker Maximilian wrote: Hi Maximilian, > General recommendation in Linux land (AFAIK) sees LVM for just the volume pools and MD as the > RAID layer (so no LVM RAID). Yes. For non-clustered mirrors, this is preferrable. > So, long story short - something like this already on the SLES roadmap ? > Or maybe already there and I just missed it ? > (/proc/mdstat only shows a very generic form of status display here) I don't have access to a non-Linux system, so I'm not sure what you're asking. Are you asking for something to show you which regions in the md bitmap are dirty? (The MD device always syncs as a whole, you don't get to pick which parts to sync exclusively. This will not change.) 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 RWipfel at fusionio.com Fri Mar 15 09:24:35 2013 From: RWipfel at fusionio.com (Robert Wipfel) Date: Fri, 15 Mar 2013 09:24:35 -0600 Subject: [sles-beta] SLES Storage / MD RAID feature In-Reply-To: <20130315145847.GE7949@suse.de> Message-ID: Not sure if SUSE is picking up the upstream patches for SP3, but MD is now also block layer DISCARD (TRIM) aware, so works better with SSDs. -- Robert On 3/15/13 8:58 AM, "Lars Marowsky-Bree" wrote: >On 2013-03-15T13:47:42, Decker Maximilian >wrote: > >Hi Maximilian, > >> General recommendation in Linux land (AFAIK) sees LVM for just the >>volume pools and MD as the >> RAID layer (so no LVM RAID). > >Yes. For non-clustered mirrors, this is preferrable. > >> So, long story short - something like this already on the SLES roadmap ? >> Or maybe already there and I just missed it ? >> (/proc/mdstat only shows a very generic form of status display here) > >I don't have access to a non-Linux system, so I'm not sure what you're >asking. > >Are you asking for something to show you which regions in the md bitmap >are dirty? > >(The MD device always syncs as a whole, you don't get to pick which parts >to sync exclusively. This will not change.) > > >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 This e-mail (and any attachments) is confidential and may be privileged. Any unauthorized use, copying, disclosure or dissemination of this communication is prohibited. If you are not the intended recipient, please notify the sender immediately and delete all copies of the message and its attachments. From Maximilian.Decker at cancom.de Fri Mar 15 09:48:23 2013 From: Maximilian.Decker at cancom.de (Decker Maximilian) Date: Fri, 15 Mar 2013 16:48:23 +0100 Subject: [sles-beta] SLES Storage / MD RAID feature In-Reply-To: <20130315145847.GE7949@suse.de> References: <20130315145847.GE7949@suse.de> Message-ID: Hi Lars, first of all thanks for your answer. I'm talking about some sort of visually dumping the bitmap including the PVs involved. So, you are right, I am basically asking for a way to show which regions in the md bitmap are marked dirty. On HP-UX, this looks something like: (sample taken from host based RAID 1 over two datacenters) <.....> --- Logical extents --- LE PV1 PE1 Status 1 PV2 PE2 Status 2 00000000 /dev/disk/disk84 00000018 current /dev/disk/disk86 00000018 current 00000001 /dev/disk/disk85 00000018 current /dev/disk/disk87 00000018 current 00000002 /dev/disk/disk84 00000019 current /dev/disk/disk86 00000019 current <.....> This way you can see that e.g. logical extent No. 0 (LE) is on PV disk84 and disk86 and this specific extent is in sync ("current"). On large volumes you get quite a long list here, but that is on purpose. It really is a cool way so actually "see" the status and physical location of each extent. Especially if a LV is spread among lots of PVs this information is quite vital. Also, you can get a transparent view on how far a re-sync progress already finished. IMHO the ability to manually re-sync parts of the RAID or specific extents is not really necessary as with a md bitmap in use only the dirty parts are re-synced automatically, providing a decent nice solution here. Ok and we cannot really compare the two platforms here as they differ quite a lot behind the scenes, but I think some way of getting such detailed information out of the md bitmap should be possible. - Maximilian -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Lars Marowsky-Bree Gesendet: Freitag, 15. M?rz 2013 15:59 An: SUSE Linux Enterprise Server Authorized Beta Program Betreff: Re: [sles-beta] SLES Storage / MD RAID feature On 2013-03-15T13:47:42, Decker Maximilian wrote: Hi Maximilian, > General recommendation in Linux land (AFAIK) sees LVM for just the > volume pools and MD as the RAID layer (so no LVM RAID). Yes. For non-clustered mirrors, this is preferrable. > So, long story short - something like this already on the SLES roadmap ? > Or maybe already there and I just missed it ? > (/proc/mdstat only shows a very generic form of status display here) I don't have access to a non-Linux system, so I'm not sure what you're asking. Are you asking for something to show you which regions in the md bitmap are dirty? (The MD device always syncs as a whole, you don't get to pick which parts to sync exclusively. This will not change.) 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 julien.foltier at laposte.fr Mon Mar 18 04:12:08 2013 From: julien.foltier at laposte.fr (FOLTIER Julien) Date: Mon, 18 Mar 2013 10:12:08 +0000 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <20130318100802.GA11230@suse.de> References: <20130318100802.GA11230@suse.de> Message-ID: <02954CD80554BB4AA0977E7110B60C722356BC40@RPN00152.melposte.log.intra.laposte.fr> Hi, There's no download available in my beta page, links have disappeared. Regards, Julien FOLTIER -----Message d'origine----- De?: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] De la part de Thorsten Kukuk Envoy??: lundi 18 mars 2013 11:08 ??: sles-beta at lists.suse.com Objet?: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released Subject: [ANNOUNCE] SLES 11 SP3 Beta3 available Dear Beta Tester, we are happy to announce SUSE Linux Enterprise Server 11 SP3 Beta3 ISO images are now available for download now. Please go to http://www.novell.com/beta and select "View my beta page". Here you should see all Beta's you are part of. We offer 3 DVD ISOs: DVD1 contains the binaries, the second DVD the sources and the third DVD the debuginfo packages. The final product will not contain the debuginfo packages on the media. Please verify the md5sum of the ISO using the MD5SUMS file, which can be found in the same directory on the download servers. Known issues: - libpfm4 was removed. Please deinstall this package, too, to avoid update problems from a previous beta. - papi update was reverted to SLE11 SP2 version. This results in a package downgrade, please make sure that the correct *papi* packages are installed after an update from a previous beta. - Splash screen not shown when system startup and shutdown on some machines [bnc#809090] Thanks in advance for all your testing Your SUSE Linux Enterprise Team -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) Post-scriptum La Poste Ce message est confidentiel. Sous reserve de tout accord conclu par ecrit entre vous et La Poste, son contenu ne represente en aucun cas un engagement de la part de La Poste. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee prealablement. Si vous n'etes pas destinataire de ce message, merci d'en avertir immediatement l'expediteur. From Klaus.Gmeinwieser at oce.com Mon Mar 18 04:25:20 2013 From: Klaus.Gmeinwieser at oce.com (Klaus Gmeinwieser) Date: Mon, 18 Mar 2013 11:25:20 +0100 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <02954CD80554BB4AA0977E7110B60C722356BC40@RPN00152.melposte.log.intra.laposte.fr> References: <20130318100802.GA11230@suse.de> <02954CD80554BB4AA0977E7110B60C722356BC40@RPN00152.melposte.log.intra.laposte.fr> Message-ID: <5146EB90.2010405@oce.com> Hi, same for me, no downloads available at all :( Regards Klaus Am 18.03.2013 11:12, schrieb FOLTIER Julien: > Hi, > > There's no download available in my beta page, links have disappeared. > > > Regards, > > Julien FOLTIER > > > -----Message d'origine----- > De : sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] De la part de Thorsten Kukuk > Envoy? : lundi 18 mars 2013 11:08 > ? : sles-beta at lists.suse.com > Objet : [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released > > Subject: [ANNOUNCE] SLES 11 SP3 Beta3 available > > Dear Beta Tester, > > we are happy to announce > > SUSE Linux Enterprise Server 11 SP3 Beta3 > > > ISO images are now available for download now. Please go to http://www.novell.com/beta and select "View my beta page". > Here you should see all Beta's you are part of. > > We offer 3 DVD ISOs: DVD1 contains the binaries, the second DVD the sources and the third DVD the debuginfo packages. > The final product will not contain the debuginfo packages on the media. > > Please verify the md5sum of the ISO using the MD5SUMS file, which can be found in the same directory on the download servers. > > Known issues: > - libpfm4 was removed. Please deinstall this package, too, to avoid > update problems from a previous beta. > - papi update was reverted to SLE11 SP2 version. This results in a > package downgrade, please make sure that the correct *papi* packages > are installed after an update from a previous beta. > - Splash screen not shown when system startup and > shutdown on some machines [bnc#809090] > > > Thanks in advance for all your testing > > Your SUSE Linux Enterprise Team > > -- > Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg > GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) > > Post-scriptum La Poste > > Ce message est confidentiel. Sous reserve de tout accord conclu par > ecrit entre vous et La Poste, son contenu ne represente en aucun cas un > engagement de la part de La Poste. Toute publication, utilisation ou > diffusion, meme partielle, doit etre autorisee prealablement. Si vous > n'etes pas destinataire de ce message, merci d'en avertir immediatement > l'expediteur. > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > -- Klaus Gmeinwieser email: klaus.gmeinwieser at oce.com voice: +49 8121 72 4358 Oc? Printing Systems GmbH - A Canon Group Company 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 Mon Mar 18 04:35:04 2013 From: uwedr at suse.com (Uwe Drechsel) Date: Mon, 18 Mar 2013 11:35:04 +0100 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <5146EB90.2010405@oce.com> References: <20130318100802.GA11230@suse.de> <02954CD80554BB4AA0977E7110B60C722356BC40@RPN00152.melposte.log.intra.laposte.fr> <5146EB90.2010405@oce.com> Message-ID: <20130318103504.GO11019@suse.de> Hi, On Mon, Mar 18, Klaus Gmeinwieser wrote: > same for me, no downloads available at all :( Am 18.03.2013 11:12, schrieb FOLTIER Julien: >Hi, > >There's no download available in my beta page, links have disappeared. > Both of you are entitled for downloads, please try again in a few hours and let me know, if there are still issues then. Sorry for the inconvenience. Thanks Uwe -- Uwe Drechsel SUSE Linux Beta Program Manager SUSE Linux Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From Falco.Lee at gigabyte.com Mon Mar 18 06:16:00 2013 From: Falco.Lee at gigabyte.com (=?utf-8?B?RmFsY28uTGVlICjmnY7mmI7li7Mp?=) Date: Mon, 18 Mar 2013 12:16:00 +0000 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <20130318103504.GO11019@suse.de> References: <20130318100802.GA11230@suse.de> <02954CD80554BB4AA0977E7110B60C722356BC40@RPN00152.melposte.log.intra.laposte.fr> <5146EB90.2010405@oce.com> <20130318103504.GO11019@suse.de> Message-ID: Hi Uwe, I also can't see the link in SLES beta page, but SLED link is available. Best regards, Falco -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Uwe Drechsel Sent: Monday, March 18, 2013 6:35 PM To: sles-beta at lists.suse.com Subject: Re: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released Hi, On Mon, Mar 18, Klaus Gmeinwieser wrote: > same for me, no downloads available at all :( Am 18.03.2013 11:12, schrieb FOLTIER Julien: >Hi, > >There's no download available in my beta page, links have disappeared. > Both of you are entitled for downloads, please try again in a few hours and let me know, if there are still issues then. Sorry for the inconvenience. Thanks Uwe -- Uwe Drechsel SUSE Linux Beta Program 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 From lawton.silva at siemens-enterprise.com Mon Mar 18 06:21:15 2013 From: lawton.silva at siemens-enterprise.com (Lawton Bonnevialle) Date: Mon, 18 Mar 2013 09:21:15 -0300 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: References: <20130318100802.GA11230@suse.de> <02954CD80554BB4AA0977E7110B60C722356BC40@RPN00152.melposte.log.intra.laposte.fr> <5146EB90.2010405@oce.com> <20130318103504.GO11019@suse.de> Message-ID: <514706BB.4040807@siemens-enterprise.com> Too... On 03/18/2013 09:16 AM, Falco.Lee (???) wrote: > Hi Uwe, > > I also can't see the link in SLES beta page, but SLED link is available. > > Best regards, > Falco > -----Original Message----- > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Uwe Drechsel > Sent: Monday, March 18, 2013 6:35 PM > To: sles-beta at lists.suse.com > Subject: Re: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released > > Hi, > > On Mon, Mar 18, Klaus Gmeinwieser wrote: > >> same for me, no downloads available at all :( > > Am 18.03.2013 11:12, schrieb FOLTIER Julien: >> Hi, >> >> There's no download available in my beta page, links have disappeared. >> > Both of you are entitled for downloads, please try again in a few hours and let me know, if there are still issues then. > > Sorry for the inconvenience. > > > Thanks > Uwe > > -- > Uwe Drechsel > SUSE Linux Beta Program 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 > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta From msvec at suse.com Tue Mar 19 03:59:39 2013 From: msvec at suse.com (Michal Svec) Date: Tue, 19 Mar 2013 10:59:39 +0100 (CET) Subject: [sles-beta] [ANNOUNCE] VMDP 2.1 Beta available Message-ID: Dear Beta Tester, we are happy to announce SUSE Linux Enterprise Virtual Machine Driver Pack 2.1 Beta SUSE Linux Enterprise Virtual Machine Driver Pack (VMDP) contains disk and network device drivers for Microsoft Windows Operating Systems that enable the high performance hosting of the unmodified guests on top of SUSE Linux Enterprise Server. Supported host operating systems are SUSE Linux Enterprise Server 10 SP4 and SUSE Linux Enterprise Server 11 SP2 or later. SUSE Linux Enterprise Virtual Machine Driver Pack contains paravirtualized drivers for both KVM and Xen hypervisors, available as part of our SUSE Linux Enterprise Server product. The key updates in version 2.1 are: - Support for SUSE Linux Enterprise Server 11 SP3 - Support for new Microsoft Windows releases: - Microsoft Windows Server 2012 - Microsoft Windows 8 - SCSI pass-through support The files are now available for download. Please go to http://www.novell.com/beta and select "View My Beta Page". Here you should see all Beta's you are part of. The SUSE Linux Enterprise Virtual Machine Driver Pack downloads are in the same directory as SUSE Linux Enterprise Server 11 SP3, please select the respective Beta in order to download it. The SUSE Linux Enterprise Virtual Machine Driver Pack is available for download in three formats: - Windows self-extracting zip file (.exe) - virtual floppy disk (.vfd) for Windows XP and 2003 - ISO image (.iso) for Windows 2008 and newer Please verify the md5sum of the downloaded files using the md5 files, which can be found in the same directory on the download servers. Thanks in advance for all your testing Your SUSE Linux Enterprise Team -------------------------------------------------------------- From Klaus.Gmeinwieser at oce.com Wed Mar 20 04:06:06 2013 From: Klaus.Gmeinwieser at oce.com (Klaus Gmeinwieser) Date: Wed, 20 Mar 2013 11:06:06 +0100 Subject: [sles-beta] Beta Update/Upgrade Question Message-ID: <51498A0E.9030802@oce.com> Hi, I have now downloaded the Beta3 iso. As I upgraded/installed several of our Application test servers with Beta2 I need to know, which is the recommended procedure to "update" from Beta2 to Beta3 (or 3->4,4->5,...). A fresh reinstallation of all of the servers with Beta3 and a complete reconfiguraton of all services is not possible for me. Please advise, what is possible on this issue. Thanks a lot in advance & Best Regards Klaus -- Klaus Gmeinwieser email: klaus.gmeinwieser at oce.com voice: +49 8121 72 4358 Oc? Printing Systems GmbH - A Canon Group Company 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 jrd at netlab1.oucs.ox.ac.uk Wed Mar 20 04:35:14 2013 From: jrd at netlab1.oucs.ox.ac.uk (jrd) Date: Wed, 20 Mar 2013 10:35:14 +0000 Subject: [sles-beta] Beta Update/Upgrade Question In-Reply-To: <51498A0E.9030802@oce.com> References: <51498A0E.9030802@oce.com> Message-ID: <514990E2.5080806@netlab1.oucs.ox.ac.uk> On 20/03/2013 10:06, Klaus Gmeinwieser wrote: > Hi, > > I have now downloaded the Beta3 iso. As I upgraded/installed several of > our Application test servers with Beta2 I need to know, which is the > recommended procedure to "update" from Beta2 to Beta3 (or > 3->4,4->5,...). A fresh reinstallation of all of the servers with Beta3 > and a complete reconfiguraton of all services is not possible for me. > > Please advise, what is possible on this issue. > > Thanks a lot in advance & Best Regards > Klaus ----------- A non-authoritative answer is you can employ an in-place upgrade. I encountered the same puzzle when working with my test HA cluster, not wanting to recreate everything again. Lars suggested quietly that an in-place upgrade would be a good idea. He was correct; it worked perfectly for me. Joe D. From Klaus.Gmeinwieser at oce.com Wed Mar 20 04:44:38 2013 From: Klaus.Gmeinwieser at oce.com (Klaus Gmeinwieser) Date: Wed, 20 Mar 2013 11:44:38 +0100 Subject: [sles-beta] Beta Update/Upgrade Question In-Reply-To: <514990E2.5080806@netlab1.oucs.ox.ac.uk> References: <51498A0E.9030802@oce.com> <514990E2.5080806@netlab1.oucs.ox.ac.uk> Message-ID: <51499316.5080606@oce.com> Hi Joe, thanks for your answer. If this works (as you tested already) - this would be very very nice for me :) Klaus Am 20.03.2013 11:35, schrieb jrd: > On 20/03/2013 10:06, Klaus Gmeinwieser wrote: >> Hi, >> >> I have now downloaded the Beta3 iso. As I upgraded/installed several of >> our Application test servers with Beta2 I need to know, which is the >> recommended procedure to "update" from Beta2 to Beta3 (or >> 3->4,4->5,...). A fresh reinstallation of all of the servers with Beta3 >> and a complete reconfiguraton of all services is not possible for me. >> >> Please advise, what is possible on this issue. >> >> Thanks a lot in advance & Best Regards >> Klaus > ----------- > A non-authoritative answer is you can employ an in-place upgrade. I > encountered the same puzzle when working with my test HA cluster, not > wanting to recreate everything again. Lars suggested quietly that an > in-place upgrade would be a good idea. He was correct; it worked > perfectly for me. > Joe D. > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > -- Klaus Gmeinwieser email: klaus.gmeinwieser at oce.com voice: +49 8121 72 4358 Oc? Printing Systems GmbH - A Canon Group Company 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 kukuk at suse.de Wed Mar 20 04:49:26 2013 From: kukuk at suse.de (Thorsten Kukuk) Date: Wed, 20 Mar 2013 11:49:26 +0100 Subject: [sles-beta] Beta Update/Upgrade Question In-Reply-To: <51499316.5080606@oce.com> References: <51498A0E.9030802@oce.com> <514990E2.5080806@netlab1.oucs.ox.ac.uk> <51499316.5080606@oce.com> Message-ID: <20130320104926.GA23753@suse.de> On Wed, Mar 20, Klaus Gmeinwieser wrote: > Hi Joe, > > thanks for your answer. If this works (as you tested already) - this would > be very very nice for me :) At least with the update from Beta2 to Beta3 you can run into dependency problems, see the Beta3 known issues list. Normally any update method should work, but we don't test and we don't fix any BetaX -> BetaY issues. Thorsten > Am 20.03.2013 11:35, schrieb jrd: >> On 20/03/2013 10:06, Klaus Gmeinwieser wrote: >>> Hi, >>> >>> I have now downloaded the Beta3 iso. As I upgraded/installed several of >>> our Application test servers with Beta2 I need to know, which is the >>> recommended procedure to "update" from Beta2 to Beta3 (or >>> 3->4,4->5,...). A fresh reinstallation of all of the servers with Beta3 >>> and a complete reconfiguraton of all services is not possible for me. >>> >>> Please advise, what is possible on this issue. >>> >>> Thanks a lot in advance & Best Regards >>> Klaus >> ----------- >> A non-authoritative answer is you can employ an in-place upgrade. I >> encountered the same puzzle when working with my test HA cluster, not >> wanting to recreate everything again. Lars suggested quietly that an >> in-place upgrade would be a good idea. He was correct; it worked >> perfectly for me. >> Joe D. >> _______________________________________________ >> sles-beta mailing list >> sles-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sles-beta >> > > -- > Klaus Gmeinwieser > > email: klaus.gmeinwieser at oce.com > voice: +49 8121 72 4358 > > Oc? Printing Systems GmbH - A Canon Group Company > > 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. > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Thorsten Kukuk, Project Manager/Release Manager SLES 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 Wed Mar 20 06:11:07 2013 From: gjn at gjn.priv.at (=?ISO-8859-1?Q?G=FCnther_J=2E?= Niederwimmer) Date: Wed, 20 Mar 2013 13:11:07 +0100 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <20130318100802.GA11230@suse.de> References: <20130318100802.GA11230@suse.de> Message-ID: <54578646.LlXhJ63i42@techz> Am Montag, 18. M?rz 2013, 11:08:02 schrieb Thorsten Kukuk: > Subject: [ANNOUNCE] SLES 11 SP3 Beta3 available > > Dear Beta Tester, > > we are happy to announce > > SUSE Linux Enterprise Server 11 SP3 Beta3 > can any download the Beta 3? -- mit freundlichen Gr??en / best Regards. G?nther J. Niederwimmer From jason.kinninger at westernsouthernlife.com Wed Mar 20 06:20:07 2013 From: jason.kinninger at westernsouthernlife.com (Kinninger, Jason) Date: Wed, 20 Mar 2013 08:20:07 -0400 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <54578646.LlXhJ63i42@techz> References: <20130318100802.GA11230@suse.de> <54578646.LlXhJ63i42@techz> Message-ID: I've been trying for the last few hours and nada. An error occurred while processing your request. Reference #97.85e23f17.1363781995.4442b55 -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of G?nther J. Niederwimmer Sent: Wednesday, March 20, 2013 8:11 AM To: sles-beta at lists.suse.com Subject: Re: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released Am Montag, 18. M?rz 2013, 11:08:02 schrieb Thorsten Kukuk: > Subject: [ANNOUNCE] SLES 11 SP3 Beta3 available > > Dear Beta Tester, > > we are happy to announce > > SUSE Linux Enterprise Server 11 SP3 Beta3 > can any download the Beta 3? -- mit freundlichen Gr??en / best Regards. G?nther J. Niederwimmer _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From pczanik at genesi-usa.com Wed Mar 20 06:21:42 2013 From: pczanik at genesi-usa.com (Peter Czanik) Date: Wed, 20 Mar 2013 13:21:42 +0100 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <54578646.LlXhJ63i42@techz> References: <20130318100802.GA11230@suse.de> <54578646.LlXhJ63i42@techz> Message-ID: <5149A9D6.7020601@genesi-usa.com> On 03/20/2013 01:11 PM, G?nther J. Niederwimmer wrote: > Am Montag, 18. M?rz 2013, 11:08:02 schrieb Thorsten Kukuk: >> Subject: [ANNOUNCE] SLES 11 SP3 Beta3 available >> >> Dear Beta Tester, >> >> we are happy to announce >> >> SUSE Linux Enterprise Server 11 SP3 Beta3 >> > > can any download the Beta 3? No. With firefox I get a blank page when I click the download button, with wget after many redirects I get a short piece of javascript... Bye, CzP From Klaus.Gmeinwieser at oce.com Wed Mar 20 06:21:50 2013 From: Klaus.Gmeinwieser at oce.com (Klaus Gmeinwieser) Date: Wed, 20 Mar 2013 13:21:50 +0100 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: References: <20130318100802.GA11230@suse.de> <54578646.LlXhJ63i42@techz> Message-ID: <5149A9DE.6000004@oce.com> For me the download works fine today at 10 am German time, got about 3,4 Mbit/s... Am 20.03.2013 13:20, schrieb Kinninger, Jason: > I've been trying for the last few hours and nada. > > An error occurred while processing your request. > > Reference #97.85e23f17.1363781995.4442b55 > > > -----Original Message----- > From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of G?nther J. Niederwimmer > Sent: Wednesday, March 20, 2013 8:11 AM > To: sles-beta at lists.suse.com > Subject: Re: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released > > Am Montag, 18. M?rz 2013, 11:08:02 schrieb Thorsten Kukuk: >> Subject: [ANNOUNCE] SLES 11 SP3 Beta3 available >> >> Dear Beta Tester, >> >> we are happy to announce >> >> SUSE Linux Enterprise Server 11 SP3 Beta3 >> > > > can any download the Beta 3? > -- Klaus Gmeinwieser email: klaus.gmeinwieser at oce.com voice: +49 8121 72 4358 Oc? Printing Systems GmbH - A Canon Group Company 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 lawton.silva at siemens-enterprise.com Wed Mar 20 06:25:58 2013 From: lawton.silva at siemens-enterprise.com (Lawton Bonnevialle) Date: Wed, 20 Mar 2013 09:25:58 -0300 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <5149A9DE.6000004@oce.com> References: <20130318100802.GA11230@suse.de> <54578646.LlXhJ63i42@techz> <5149A9DE.6000004@oce.com> Message-ID: <5149AAD6.90203@siemens-enterprise.com> I can't complete the download, max 36Mb! On 03/20/2013 09:21 AM, Klaus Gmeinwieser wrote: > For me the download works fine today at 10 am German time, got about > 3,4 Mbit/s... > > Am 20.03.2013 13:20, schrieb Kinninger, Jason: >> I've been trying for the last few hours and nada. >> >> An error occurred while processing your request. >> >> Reference #97.85e23f17.1363781995.4442b55 >> >> >> -----Original Message----- >> From: sles-beta-bounces at lists.suse.com >> [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of G?nther J. >> Niederwimmer >> Sent: Wednesday, March 20, 2013 8:11 AM >> To: sles-beta at lists.suse.com >> Subject: Re: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released >> >> Am Montag, 18. M?rz 2013, 11:08:02 schrieb Thorsten Kukuk: >>> Subject: [ANNOUNCE] SLES 11 SP3 Beta3 available >>> >>> Dear Beta Tester, >>> >>> we are happy to announce >>> >>> SUSE Linux Enterprise Server 11 SP3 Beta3 >>> >> >> >> can any download the Beta 3? >> > From andrew.foulsham at imm.ox.ac.uk Wed Mar 20 06:37:02 2013 From: andrew.foulsham at imm.ox.ac.uk (Andrew Foulsham) Date: Wed, 20 Mar 2013 12:37:02 +0000 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <5149AAD6.90203@siemens-enterprise.com> References: <20130318100802.GA11230@suse.de> <54578646.LlXhJ63i42@techz> <5149A9DE.6000004@oce.com> <5149AAD6.90203@siemens-enterprise.com> Message-ID: <1363783022.24979.4.camel@falcon.imm.ox.ac.uk> I'm finding problems downloading Beta3 ISOs from here in Oxford. I get 8MB downloading using firefox, and then the connection fails. When I try using wget (using the CDN URL that the download page eventually redirects to) it says: "Filename too long". Best wishes, Andrew Foulsham On Wed, 2013-03-20 at 09:25 -0300, Lawton Bonnevialle wrote: > I can't complete the download, max 36Mb! > > > On 03/20/2013 09:21 AM, Klaus Gmeinwieser wrote: > > For me the download works fine today at 10 am German time, got about > > 3,4 Mbit/s... > > > > Am 20.03.2013 13:20, schrieb Kinninger, Jason: > >> I've been trying for the last few hours and nada. > >> > >> An error occurred while processing your request. > >> > >> Reference #97.85e23f17.1363781995.4442b55 > >> > >> > >> -----Original Message----- > >> From: sles-beta-bounces at lists.suse.com > >> [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of G?nther J. > >> Niederwimmer > >> Sent: Wednesday, March 20, 2013 8:11 AM > >> To: sles-beta at lists.suse.com > >> Subject: Re: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released > >> > >> Am Montag, 18. M?rz 2013, 11:08:02 schrieb Thorsten Kukuk: > >>> Subject: [ANNOUNCE] SLES 11 SP3 Beta3 available > >>> > >>> Dear Beta Tester, > >>> > >>> we are happy to announce > >>> > >>> SUSE Linux Enterprise Server 11 SP3 Beta3 > >>> > >> > >> > >> can any download the Beta 3? > >> > > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Andrew Foulsham, Systems & Networks Manager, Weatherall Institute of Molecular Medicine, University of Oxford 01865 222618 andrew.foulsham at imm.ox.ac.uk From Falco.Lee at gigabyte.com Wed Mar 20 06:38:32 2013 From: Falco.Lee at gigabyte.com (=?utf-8?B?RmFsY28uTGVlICjmnY7mmI7li7Mp?=) Date: Wed, 20 Mar 2013 12:38:32 +0000 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <5149AAD6.90203@siemens-enterprise.com> References: <20130318100802.GA11230@suse.de> <54578646.LlXhJ63i42@techz> <5149A9DE.6000004@oce.com> <5149AAD6.90203@siemens-enterprise.com> Message-ID: 8~12 hours ago download is no problem, but last few hours during downloading files connection would be lost. -----Original Message----- From: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of Lawton Bonnevialle Sent: Wednesday, March 20, 2013 8:26 PM To: SUSE Linux Enterprise Server Authorized Beta Program Subject: Re: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released I can't complete the download, max 36Mb! On 03/20/2013 09:21 AM, Klaus Gmeinwieser wrote: > For me the download works fine today at 10 am German time, got about > 3,4 Mbit/s... > > Am 20.03.2013 13:20, schrieb Kinninger, Jason: >> I've been trying for the last few hours and nada. >> >> An error occurred while processing your request. >> >> Reference #97.85e23f17.1363781995.4442b55 >> >> >> -----Original Message----- >> From: sles-beta-bounces at lists.suse.com >> [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of G?nther J. >> Niederwimmer >> Sent: Wednesday, March 20, 2013 8:11 AM >> To: sles-beta at lists.suse.com >> Subject: Re: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released >> >> Am Montag, 18. M?rz 2013, 11:08:02 schrieb Thorsten Kukuk: >>> Subject: [ANNOUNCE] SLES 11 SP3 Beta3 available >>> >>> Dear Beta Tester, >>> >>> we are happy to announce >>> >>> SUSE Linux Enterprise Server 11 SP3 Beta3 >>> >> >> >> can any download the Beta 3? >> > _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From mge at suse.com Wed Mar 20 06:46:19 2013 From: mge at suse.com (Matthias G. Eckermann) Date: Wed, 20 Mar 2013 13:46:19 +0100 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <1363783022.24979.4.camel@falcon.imm.ox.ac.uk> References: <20130318100802.GA11230@suse.de> <54578646.LlXhJ63i42@techz> <5149A9DE.6000004@oce.com> <5149AAD6.90203@siemens-enterprise.com> <1363783022.24979.4.camel@falcon.imm.ox.ac.uk> Message-ID: <20130320124619.GA6955@suse.com> Hello all, I also had seen those / similar issues here from my home office in Berlin today morning (I am connected via regular DSL from Deutsche Telekom). It seems to be resolved though since a few minutes ago. In any case, please make sure that your DNS resolving works properly: we are distributing via Akamai, and this uses dynamic DNS answers. Please check again! so long - MgE On 2013-03-20 T 12:37 +0000 Andrew Foulsham wrote: > I'm finding problems downloading Beta3 ISOs from here in Oxford. I get > 8MB downloading using firefox, and then the connection fails. > > When I try using wget (using the CDN URL that the download page > eventually redirects to) it says: > "Filename too long". > > Best wishes, > > Andrew Foulsham > > On Wed, 2013-03-20 at 09:25 -0300, Lawton Bonnevialle wrote: > > I can't complete the download, max 36Mb! > > > > > > On 03/20/2013 09:21 AM, Klaus Gmeinwieser wrote: > > > For me the download works fine today at 10 am German time, got about > > > 3,4 Mbit/s... > > > > > > Am 20.03.2013 13:20, schrieb Kinninger, Jason: > > >> I've been trying for the last few hours and nada. > > >> > > >> An error occurred while processing your request. > > >> > > >> Reference #97.85e23f17.1363781995.4442b55 > > >> > > >> > > >> -----Original Message----- > > >> From: sles-beta-bounces at lists.suse.com > > >> [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of G?nther J. > > >> Niederwimmer > > >> Sent: Wednesday, March 20, 2013 8:11 AM > > >> To: sles-beta at lists.suse.com > > >> Subject: Re: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released > > >> > > >> Am Montag, 18. M?rz 2013, 11:08:02 schrieb Thorsten Kukuk: > > >>> Subject: [ANNOUNCE] SLES 11 SP3 Beta3 available > > >>> > > >>> Dear Beta Tester, > > >>> > > >>> we are happy to announce > > >>> > > >>> SUSE Linux Enterprise Server 11 SP3 Beta3 > > >>> > > >> > > >> > > >> can any download the Beta 3? > > >> > > > > > > > _______________________________________________ > > sles-beta mailing list > > sles-beta at lists.suse.com > > http://lists.suse.com/mailman/listinfo/sles-beta > > > -- > Andrew Foulsham, Systems & Networks Manager, > Weatherall Institute of Molecular Medicine, University of Oxford > 01865 222618 > andrew.foulsham at imm.ox.ac.uk > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From jrd at netlab1.oucs.ox.ac.uk Wed Mar 20 07:34:41 2013 From: jrd at netlab1.oucs.ox.ac.uk (jrd) Date: Wed, 20 Mar 2013 13:34:41 +0000 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <20130320124619.GA6955@suse.com> References: <20130318100802.GA11230@suse.de> <54578646.LlXhJ63i42@techz> <5149A9DE.6000004@oce.com> <5149AAD6.90203@siemens-enterprise.com> <1363783022.24979.4.camel@falcon.imm.ox.ac.uk> <20130320124619.GA6955@suse.com> Message-ID: <5149BAF1.6070205@netlab1.oucs.ox.ac.uk> I let the transfer run overnight and yesterday morning the whole SLES SP3 Beta 3 iso was present. I have not brought it up yet to check on things, nor run the md5sum. Perhaps the quiet time at night helped a little. Joe D. On 20/03/2013 12:46, Matthias G. Eckermann wrote: > Hello all, > > I also had seen those / similar issues here from my home > office in Berlin today morning (I am connected via > regular DSL from Deutsche Telekom). > > It seems to be resolved though since a few minutes ago. > > In any case, please make sure that your DNS resolving > works properly: we are distributing via Akamai, and this > uses dynamic DNS answers. > > Please check again! > > so long - > MgE > > On 2013-03-20 T 12:37 +0000 Andrew Foulsham wrote: >> I'm finding problems downloading Beta3 ISOs from here in Oxford. I get >> 8MB downloading using firefox, and then the connection fails. >> >> When I try using wget (using the CDN URL that the download page >> eventually redirects to) it says: >> "Filename too long". >> >> Best wishes, >> >> Andrew Foulsham >> >> On Wed, 2013-03-20 at 09:25 -0300, Lawton Bonnevialle wrote: >>> I can't complete the download, max 36Mb! >>> >>> >>> On 03/20/2013 09:21 AM, Klaus Gmeinwieser wrote: >>>> For me the download works fine today at 10 am German time, got about >>>> 3,4 Mbit/s... >>>> >>>> Am 20.03.2013 13:20, schrieb Kinninger, Jason: >>>>> I've been trying for the last few hours and nada. >>>>> >>>>> An error occurred while processing your request. >>>>> >>>>> Reference #97.85e23f17.1363781995.4442b55 >>>>> >>>>> >>>>> -----Original Message----- >>>>> From: sles-beta-bounces at lists.suse.com >>>>> [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of G?nther J. >>>>> Niederwimmer >>>>> Sent: Wednesday, March 20, 2013 8:11 AM >>>>> To: sles-beta at lists.suse.com >>>>> Subject: Re: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released >>>>> >>>>> Am Montag, 18. M?rz 2013, 11:08:02 schrieb Thorsten Kukuk: >>>>>> Subject: [ANNOUNCE] SLES 11 SP3 Beta3 available >>>>>> >>>>>> Dear Beta Tester, >>>>>> >>>>>> we are happy to announce >>>>>> >>>>>> SUSE Linux Enterprise Server 11 SP3 Beta3 >>>>>> >>>>> >>>>> >>>>> can any download the Beta 3? >>>>> >>>> >>> >>> _______________________________________________ >>> sles-beta mailing list >>> sles-beta at lists.suse.com >>> http://lists.suse.com/mailman/listinfo/sles-beta >> >> >> -- >> Andrew Foulsham, Systems & Networks Manager, >> Weatherall Institute of Molecular Medicine, University of Oxford >> 01865 222618 >> andrew.foulsham at imm.ox.ac.uk >> >> _______________________________________________ >> sles-beta mailing list >> sles-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sles-beta > From pczanik at genesi-usa.com Wed Mar 20 07:39:13 2013 From: pczanik at genesi-usa.com (Peter Czanik) Date: Wed, 20 Mar 2013 14:39:13 +0100 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <20130320124619.GA6955@suse.com> References: <20130318100802.GA11230@suse.de> <54578646.LlXhJ63i42@techz> <5149A9DE.6000004@oce.com> <5149AAD6.90203@siemens-enterprise.com> <1363783022.24979.4.camel@falcon.imm.ox.ac.uk> <20130320124619.GA6955@suse.com> Message-ID: <5149BC01.9020504@genesi-usa.com> On 03/20/2013 01:46 PM, Matthias G. Eckermann wrote: > Hello all, > > I also had seen those / similar issues here from my home > office in Berlin today morning (I am connected via > regular DSL from Deutsche Telekom). > > It seems to be resolved though since a few minutes ago. > > In any case, please make sure that your DNS resolving > works properly: we are distributing via Akamai, and this > uses dynamic DNS answers. > > Please check again! I did, but still no luck. Even restarted the browsers and the local DNS server... Bye, CzP From lawton.silva at siemens-enterprise.com Wed Mar 20 08:07:36 2013 From: lawton.silva at siemens-enterprise.com (Lawton Bonnevialle) Date: Wed, 20 Mar 2013 11:07:36 -0300 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <20130320124619.GA6955@suse.com> References: <20130318100802.GA11230@suse.de> <54578646.LlXhJ63i42@techz> <5149A9DE.6000004@oce.com> <5149AAD6.90203@siemens-enterprise.com> <1363783022.24979.4.camel@falcon.imm.ox.ac.uk> <20130320124619.GA6955@suse.com> Message-ID: <5149C2A8.2080605@siemens-enterprise.com> For me, nothing.... I'm using firefox 17.0.3. The download down in ~ 38Mb. On 03/20/2013 09:46 AM, Matthias G. Eckermann wrote: > Hello all, > > I also had seen those / similar issues here from my home > office in Berlin today morning (I am connected via > regular DSL from Deutsche Telekom). > > It seems to be resolved though since a few minutes ago. > > In any case, please make sure that your DNS resolving > works properly: we are distributing via Akamai, and this > uses dynamic DNS answers. > > Please check again! > > so long - > MgE > > On 2013-03-20 T 12:37 +0000 Andrew Foulsham wrote: >> I'm finding problems downloading Beta3 ISOs from here in Oxford. I get >> 8MB downloading using firefox, and then the connection fails. >> >> When I try using wget (using the CDN URL that the download page >> eventually redirects to) it says: >> "Filename too long". >> >> Best wishes, >> >> Andrew Foulsham >> >> On Wed, 2013-03-20 at 09:25 -0300, Lawton Bonnevialle wrote: >>> I can't complete the download, max 36Mb! >>> >>> >>> On 03/20/2013 09:21 AM, Klaus Gmeinwieser wrote: >>>> For me the download works fine today at 10 am German time, got about >>>> 3,4 Mbit/s... >>>> >>>> Am 20.03.2013 13:20, schrieb Kinninger, Jason: >>>>> I've been trying for the last few hours and nada. >>>>> >>>>> An error occurred while processing your request. >>>>> >>>>> Reference #97.85e23f17.1363781995.4442b55 >>>>> >>>>> >>>>> -----Original Message----- >>>>> From: sles-beta-bounces at lists.suse.com >>>>> [mailto:sles-beta-bounces at lists.suse.com] On Behalf Of G?nther J. >>>>> Niederwimmer >>>>> Sent: Wednesday, March 20, 2013 8:11 AM >>>>> To: sles-beta at lists.suse.com >>>>> Subject: Re: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released >>>>> >>>>> Am Montag, 18. M?rz 2013, 11:08:02 schrieb Thorsten Kukuk: >>>>>> Subject: [ANNOUNCE] SLES 11 SP3 Beta3 available >>>>>> >>>>>> Dear Beta Tester, >>>>>> >>>>>> we are happy to announce >>>>>> >>>>>> SUSE Linux Enterprise Server 11 SP3 Beta3 >>>>>> >>>>> >>>>> can any download the Beta 3? >>>>> >>> _______________________________________________ >>> sles-beta mailing list >>> sles-beta at lists.suse.com >>> http://lists.suse.com/mailman/listinfo/sles-beta >> >> -- >> Andrew Foulsham, Systems & Networks Manager, >> Weatherall Institute of Molecular Medicine, University of Oxford >> 01865 222618 >> andrew.foulsham at imm.ox.ac.uk >> >> _______________________________________________ >> sles-beta mailing list >> sles-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/sles-beta From urs.frey at post.ch Wed Mar 20 08:11:27 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Wed, 20 Mar 2013 14:11:27 +0000 Subject: [sles-beta] Experience with SLES11-SP3 beta3 x86_64 Message-ID: <40637DBB36AF3941B243A286A432CA0B0E232763@HXMB12.pnet.ch> Hello I downloaded SLES-11-SP3-DVD-x86_64-Beta3-DVD1.iso & SLE-11-SP3-SDK-DVD-x86_64-Beta3-DVD1.iso succesfully yesterday morning CET. Now I am testing on HP Proliant DL385-G5, BL465cG7, BL460c-Gen8 and VMware Installation runs smoothly. I always do a fresh installation using autoyast and network install server via http:80 BUG with mcelog, not supporting AMD Opteron CPUs still open. ([Bug 807336] mcelog: AMD Processor family 21: Please load edac_mce_amd module) I did already an update from SLES11-SP2 to SLES11-SP3 using zypper --non-interactive dist-upgrade --auto-agree-with-licenses What I notice is a problem, when updating postfix: Installing: rsync-3.0.4-2.45.40 [.done] Installing: postfix-2.9.4-0.9.25 [..done] Additional rpm output: warning: /etc/postfix/main.cf created as /etc/postfix/main.cf.rpmnew warning: /etc/postfix/master.cf created as /etc/postfix/master.cf.rpmnew executing upgrade-configuration /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix Editing /etc/postfix/master.cf, adding missing entry for tlsmgr service Editing /etc/postfix/master.cf, adding missing entry for postscreen TCP service Editing /etc/postfix/master.cf, adding missing entry for smtpd unix-domain service Editing /etc/postfix/master.cf, adding missing entry for dnsblog unix-domain service Editing /etc/postfix/master.cf, adding missing entry for tlsproxy unix-domain service Note: the following files or directories still exist but are no longer part of Postfix: /etc/postfix/postfix-files /etc/postfix/postfix-script /etc/postfix/post-install /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix Updating etc/sysconfig/postfix... Updating etc/sysconfig/mail... /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix Installing: openssh-6.1p1-0.9.12 [.done] Postfix is working afterwards, but also in the /var/log/boot.msg I get this warning from postfix on my console: -------------------------------- postfix start Starting mail service (Postfix)done 'postfix start' exits with status 0 cron start /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix Starting CRON daemon ---------------------------------- Of course I can disable the line by editing /etc/postfix/mani.cf #program_directory = /usr/lib/postfix and then this warning no longer appears. It would be great, if there is no need to edit manually after an Upgrade Thank you for feedback Best regards Urs Frey Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX : ++41 (0)58 667 30 07 E-Mail: urs.frey at post.ch From dboyes at sinenomine.net Wed Mar 20 08:49:15 2013 From: dboyes at sinenomine.net (David Boyes) Date: Wed, 20 Mar 2013 14:49:15 +0000 Subject: [sles-beta] [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <20130320124619.GA6955@suse.com> References: <20130318100802.GA11230@suse.de> <54578646.LlXhJ63i42@techz> <5149A9DE.6000004@oce.com> <5149AAD6.90203@siemens-enterprise.com> <1363783022.24979.4.camel@falcon.imm.ox.ac.uk> <20130320124619.GA6955@suse.com> Message-ID: <2748AD71D96C2B42B7E5176021026FC3079BF390@ORD2MBX03A.mex05.mlsrvr.com> None of the non-Intel architectures seem to be downloadable, error "File not found:" when clicked on for POWER and System z. 8-( From uwedr at suse.com Wed Mar 20 08:54:04 2013 From: uwedr at suse.com (Uwe Drechsel) Date: Wed, 20 Mar 2013 15:54:04 +0100 Subject: [sles-beta] Download issues / Re: [ANNOUNCE] SLES 11 SP3 Beta3 released In-Reply-To: <2748AD71D96C2B42B7E5176021026FC3079BF390@ORD2MBX03A.mex05.mlsrvr.com> References: <20130318100802.GA11230@suse.de> <54578646.LlXhJ63i42@techz> <5149A9DE.6000004@oce.com> <5149AAD6.90203@siemens-enterprise.com> <1363783022.24979.4.camel@falcon.imm.ox.ac.uk> <20130320124619.GA6955@suse.com> <2748AD71D96C2B42B7E5176021026FC3079BF390@ORD2MBX03A.mex05.mlsrvr.com> Message-ID: <20130320145404.GW11019@suse.de> Hi, as many of you have noticed, there currently is a problem with the download infrastructure. The server team is currently looking into it. Sorry for the inconvenience. Thanks Uwe -- Uwe Drechsel SUSE Linux Beta Program Manager SUSE Linux Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From swehnert at suse.com Wed Mar 20 10:20:58 2013 From: swehnert at suse.com (Sascha Wehnert) Date: Wed, 20 Mar 2013 17:20:58 +0100 Subject: [sles-beta] Intel_Idel - Apci_Idel - Slow Wall Clock time SP1 to SP2 what about SP3? In-Reply-To: <3CBFA7CC2505A74B9C172B35128B8863020B636D@YLAV4460.INETPSA.com> References: <46AC8C81C10B8C48820201DF2AE1D76D01512A@hqmbx6.eur.ad.sag> <3CBFA7CC2505A74B9C172B35128B8863020B636D@YLAV4460.INETPSA.com> Message-ID: <5149E1EA.6090005@suse.com> Hi Lo?c, On 03/20/2013 04:41 PM, LOIC DEVULDER wrote: > I have found this TID concerning the slow wall clock problem: > https://www.suse.com/support/kb/doc.php?id=7011982 > > But be careful, this TID is not correct: ?intel_idle_max_cstate=0? is > not the only option needed! ?Processor.max_cstate=0? is also needed (I > have made test). For each TID in our knowledge base you have the possibility to leave feedback which will get routed to the author. Please use the link at the bottom "Did this document solve your problem? Provide Feedback" to do so, we always appreciate feedback to the documents we release. I checked back with the author and he suggested to open a service request so we can investigate this in mode depth. [...] Kind regards Sascha Wehnert -- Sascha Andree Wehnert, Technical Support Engineer Email: swehnert at suse.com Novell GmbH, N?rdlicher Zubringer 9-11, 40470 D?sseldorf GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer HRB 202401 (AG M?nchen) From behlert at suse.de Thu Mar 21 08:17:34 2013 From: behlert at suse.de (Stefan Behlert) Date: Thu, 21 Mar 2013 15:17:34 +0100 Subject: [sles-beta] Issues I saw after several installs and some configuration In-Reply-To: <512F6E35.3010109@oce.com> References: <512F6E35.3010109@oce.com> Message-ID: <20130321141734.GL4525@suse.de> Hi, On Feb 28, 13 15:48:21 +0100, Klaus Gmeinwieser wrote: > Hello all, > > I did several installs/updates of Beta 1 on about 5 servers. > > The installation itself works smooth on every Fujitsu TX server I tried > (TX150 / TX300 SAS systems) also for installation on ESX4/5 systems as > guest. > > Upgrades from installed SP2 to SP3 Beta1 also works seamlessly. > > Very good :) > > But I found some minor but annoying issues: > > - in KDE Control Center, configuration of the Screen Saver is not possible > as the Control Center crashes immediately (100% reproducible) > > - The "KDE Root Shell" Icon in the KDE Menu does not work as I always get a > regular user shell instead of a "root shell" Be so kind to open SRs for those two - I tested it on SLED, and could not reproduce it with Beta3. So it could be something special to SLES or your hardware (in the screensaver case). thanks, Stefan -- Stefan Behlert, SUSE LINUX Project Manager Enterprise Desktop Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE LINUX Products GmbH, Nuernberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuernberg) From mkrapp at suse.com Thu Mar 21 08:56:06 2013 From: mkrapp at suse.com (Michael Krapp) Date: Thu, 21 Mar 2013 15:56:06 +0100 Subject: [sles-beta] Issues I saw after several installs and some configuration In-Reply-To: <20130321141734.GL4525@suse.de> References: <512F6E35.3010109@oce.com> <20130321141734.GL4525@suse.de> Message-ID: <20130321145606.GA28773@wawa.suse.de> * Stefan Behlert schrieb 20130321 15:16: > Hi, > > On Feb 28, 13 15:48:21 +0100, Klaus Gmeinwieser wrote: > > But I found some minor but annoying issues: > > > > - in KDE Control Center, configuration of the Screen Saver is not possible > > as the Control Center crashes immediately (100% reproducible) https://bugzilla.novell.com/show_bug.cgi?id=810783 > > - The "KDE Root Shell" Icon in the KDE Menu does not work as I always get a > > regular user shell instead of a "root shell" https://bugzilla.novell.com/show_bug.cgi?id=808061 > Be so kind to open SRs for those two - I tested it on SLED, and could not > reproduce it with Beta3. Already done for Beta2 :) > So it could be something special to SLES or your hardware (in the > screensaver case). Both are reproducible on SLES in a Beta 3 VM as well. Stefan, if you want to have a look yourself, let me know. Regards, Michael > thanks, > Stefan > > -- > Stefan Behlert, SUSE LINUX > Project Manager Enterprise Desktop > > Maxfeldstr. 5, D-90409 Nuernberg, Germany > Phone +49-911-74053-173 > SUSE LINUX Products GmbH, Nuernberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuernberg) > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Kind regards / Mit freundlichen Gr??en Michael Krapp, Technical Support Engineer Worldwide Support Services Linux SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 21284 (AG N?rnberg) Maxfeldstr. 5, D-90409 N?rnberg T: +49-911-74053-0 F: +49-911-74053-679 From behlert at suse.de Thu Mar 21 09:08:19 2013 From: behlert at suse.de (Stefan Behlert) Date: Thu, 21 Mar 2013 16:08:19 +0100 Subject: [sles-beta] Issues I saw after several installs and some configuration In-Reply-To: <20130321145606.GA28773@wawa.suse.de> References: <512F6E35.3010109@oce.com> <20130321141734.GL4525@suse.de> <20130321145606.GA28773@wawa.suse.de> Message-ID: <20130321150819.GP4525@suse.de> Hi, On Mar 21, 13 15:56:06 +0100, Michael Krapp wrote: > * Stefan Behlert schrieb 20130321 15:16: > > Hi, > > > > On Feb 28, 13 15:48:21 +0100, Klaus Gmeinwieser wrote: > > > But I found some minor but annoying issues: > > > > > > - in KDE Control Center, configuration of the Screen Saver is not possible > > > as the Control Center crashes immediately (100% reproducible) > > https://bugzilla.novell.com/show_bug.cgi?id=810783 > > > > - The "KDE Root Shell" Icon in the KDE Menu does not work as I always get a > > > regular user shell instead of a "root shell" > > https://bugzilla.novell.com/show_bug.cgi?id=808061 > > > Be so kind to open SRs for those two - I tested it on SLED, and could not > > reproduce it with Beta3. > > Already done for Beta2 :) Thanks! Somehow I missed them on my radar :( > > > So it could be something special to SLES or your hardware (in the > > screensaver case). > > Both are reproducible on SLES in a Beta 3 VM as well. Stefan, if you want to > have a look yourself, let me know. I'll let the experts handle it, thanks for the offer. ciao, Stefan > > Regards, > > Michael > > > thanks, > > Stefan > > > > -- > > Stefan Behlert, SUSE LINUX > > Project Manager Enterprise Desktop > > > > Maxfeldstr. 5, D-90409 Nuernberg, Germany > > Phone +49-911-74053-173 > > SUSE LINUX Products GmbH, Nuernberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuernberg) > > _______________________________________________ > > sles-beta mailing list > > sles-beta at lists.suse.com > > http://lists.suse.com/mailman/listinfo/sles-beta > > -- > Kind regards / Mit freundlichen Gr??en > > Michael Krapp, Technical Support Engineer > Worldwide Support Services Linux > SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 21284 (AG N?rnberg) > Maxfeldstr. 5, D-90409 N?rnberg > T: +49-911-74053-0 F: +49-911-74053-679 > > > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta -- Stefan Behlert, SUSE LINUX Project Manager Enterprise Desktop Maxfeldstr. 5, D-90409 Nuernberg, Germany Phone +49-911-74053-173 SUSE LINUX Products GmbH, Nuernberg; GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuernberg) From mge at suse.com Fri Mar 22 09:45:08 2013 From: mge at suse.com (Matthias G. Eckermann) Date: Fri, 22 Mar 2013 16:45:08 +0100 Subject: [sles-beta] SLES for VMware & vmware-tools In-Reply-To: References: <40637DBB36AF3941B243A286A432CA0B0E232F6A@HXMB12.pnet.ch> Message-ID: <20130322154508.GB20488@suse.com> Hello Maximilian and all, On 2013-03-22 T 15:33 +0100 Decker Maximilian wrote: > yes that indeed is a nice and easy solution - as long > as you consider the kernel ABI 100% unchanged ;-) The rule for SUSE Linux Enterprise is that the Kernel ABI does not incopmatibly change during the lifetime of a Service Pack. Our Kernel team as automated checks in place to enforce this. As this rule or guideline applies for the whole Kernel ABI, SUSE's policy in this aspect is stricter than the one of other Linux distributions. > But there are patches that might possibly influence > here. As the linux kernel is monolithic, the > communication (binary) interface to drivers is prone > to changes with each and every update. So, especially > for production systems, I prefer kernel modules built > against exactly the same kernel version, just to be > sure there are no glitches that might have passed the > compatibility check by mistake ... You are free to not trust our team -- however, please do not complain about additional work in that case! :-) [...] > Now we see there are lots of different ways and > opinions here, and that is exactly why I would love to > see officially supported vmware tools (and kernel > modules) as part of the base installation. I think, Mark and Kai have listed a number of convincing reasons why this can not be achieved as easily and quickly as we all wanted, ... So long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From Maximilian.Decker at cancom.de Fri Mar 22 10:44:17 2013 From: Maximilian.Decker at cancom.de (Decker Maximilian) Date: Fri, 22 Mar 2013 17:44:17 +0100 Subject: [sles-beta] SLES for VMware & vmware-tools In-Reply-To: <20130322154508.GB20488@suse.com> References: <40637DBB36AF3941B243A286A432CA0B0E232F6A@HXMB12.pnet.ch> <20130322154508.GB20488@suse.com> Message-ID: Well if that is an official statement from SuSE then I would be happy to rely on the ABI being stable within service packs ;-) I was not aware of that, thanks for clarifying. However I remember we once had an issue with a changed ABI within SLES 11 SP1, according to my notes it was bnc#625674 that broke things a bit around ixgbe (fiber nic). It was a quite special case, though, and I can't tell if that one might have had affected vmware modules at all, but things like that just make me prefer a bit of a conservative approach here... But I'm starting to get off topic, never mind. Just better start finding solutions to include vmware-tools instead of reasons against ;-) (no offense, more like a glimmer of hope) And thanks to the list in general, really was quite informative on that specific topic. - Maximilian -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Matthias G. Eckermann Gesendet: Freitag, 22. M?rz 2013 16:45 An: SUSE Linux Enterprise Server Authorized Beta Program Betreff: Re: [sles-beta] SLES for VMware & vmware-tools Hello Maximilian and all, On 2013-03-22 T 15:33 +0100 Decker Maximilian wrote: > yes that indeed is a nice and easy solution - as long as you consider > the kernel ABI 100% unchanged ;-) The rule for SUSE Linux Enterprise is that the Kernel ABI does not incopmatibly change during the lifetime of a Service Pack. Our Kernel team as automated checks in place to enforce this. As this rule or guideline applies for the whole Kernel ABI, SUSE's policy in this aspect is stricter than the one of other Linux distributions. > But there are patches that might possibly influence here. As the > linux kernel is monolithic, the communication (binary) interface to > drivers is prone to changes with each and every update. So, > especially for production systems, I prefer kernel modules built > against exactly the same kernel version, just to be sure there are no > glitches that might have passed the compatibility check by mistake ... You are free to not trust our team -- however, please do not complain about additional work in that case! :-) [...] > Now we see there are lots of different ways and opinions here, and > that is exactly why I would love to see officially supported vmware > tools (and kernel > modules) as part of the base installation. I think, Mark and Kai have listed a number of convincing reasons why this can not be achieved as easily and quickly as we all wanted, ... So long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From simon.rowe at eu.citrix.com Tue Mar 26 03:56:50 2013 From: simon.rowe at eu.citrix.com (Simon Rowe) Date: Tue, 26 Mar 2013 09:56:50 +0000 Subject: [sles-beta] SR turn around time? Message-ID: <515170E2.9070305@eu.citrix.com> How long should I expect for a reply to an SR? I opened 10820471581 nearly two weeks ago and haven't received a response yet. Simon From urs.frey at post.ch Tue Mar 26 04:02:47 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Tue, 26 Mar 2013 10:02:47 +0000 Subject: [sles-beta] SR turn around time? In-Reply-To: <515170E2.9070305@eu.citrix.com> References: <515170E2.9070305@eu.citrix.com> Message-ID: <40637DBB36AF3941B243A286A432CA0B0E233F35@HXMB12.pnet.ch> Same here SUMMARY OF SR # 10821644381 (20-Mar-2013) * SR Severity Level: Medium * SR Product: * SR Brief Description: SLES11-SP3-Beta3: postconf: warning: main.cf: unused parameter: program_directory SUMMARY OF SR # 10820890071 (15-Mar-2013) * SR Severity Level: Medium * SR Product: * SR Brief Description: SLES11-SP3-beta2 problem facter witch LXC: veth2: error fetching interface information It seems that some SR are taken By Novell people USA and then seem to be blocked for SuSE people. Mine are blocked by Jim Petersen , Novell Best regards Urs Frey????????????????????????????????????????????? Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX???? : ++41 (0)58 667 30 07 E-Mail:?? urs.frey at post.ch -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Simon Rowe Gesendet: Tuesday, March 26, 2013 10:57 AM An: sles-beta at lists.suse.com Betreff: [sles-beta] SR turn around time? How long should I expect for a reply to an SR? I opened 10820471581 nearly two weeks ago and haven't received a response yet. Simon _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From sarsene at suse.com Tue Mar 26 04:04:56 2013 From: sarsene at suse.com (Simona Arsene) Date: Tue, 26 Mar 2013 11:04:56 +0100 Subject: [sles-beta] SR turn around time? In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0E233F35@HXMB12.pnet.ch> References: <515170E2.9070305@eu.citrix.com> <40637DBB36AF3941B243A286A432CA0B0E233F35@HXMB12.pnet.ch> Message-ID: <515180D8020000220013D174@smtp.nue.novell.com> Hi, thank you for reporting the issue. We'll have a look at the incidents and contact you directly. Simona >>> On 3/26/2013 at 11:02 AM, in message <40637DBB36AF3941B243A286A432CA0B0E233F35 at HXMB12.pnet.ch>, wrote: > Same here > > SUMMARY OF SR # 10821644381 (20-Mar-2013) > * SR Severity Level: Medium > * SR Product: > * SR Brief Description: SLES11-SP3-Beta3: postconf: warning: main.cf: > unused parameter: program_directory > > SUMMARY OF SR # 10820890071 (15-Mar-2013) > * SR Severity Level: Medium > * SR Product: > * SR Brief Description: SLES11-SP3-beta2 problem facter witch LXC: veth2: > error fetching interface information > > It seems that some SR are taken By Novell people USA and then seem to be > blocked for SuSE people. > Mine are blocked by Jim Petersen , Novell > > Best regards > > Urs Frey > Die Schweizerische Post > Services > Informationstechnologie > Webergutstrasse 12 > 3030 Bern (Zollikofen) > Telefon : ++41 (0)58 338 58 70 > FAX : ++41 (0)58 667 30 07 > E-Mail: urs.frey at post.ch > > -----Urspr?ngliche Nachricht----- > Von: sles-beta-bounces at lists.suse.com > [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Simon Rowe > Gesendet: Tuesday, March 26, 2013 10:57 AM > An: sles-beta at lists.suse.com > Betreff: [sles-beta] SR turn around time? > > How long should I expect for a reply to an SR? I opened 10820471581 > nearly two weeks ago and haven't received a response yet. > > Simon > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta From uwedr at suse.com Tue Mar 26 04:20:48 2013 From: uwedr at suse.com (Uwe Drechsel) Date: Tue, 26 Mar 2013 11:20:48 +0100 Subject: [sles-beta] SR turn around time? In-Reply-To: <515170E2.9070305@eu.citrix.com> References: <515170E2.9070305@eu.citrix.com> Message-ID: <20130326102048.GB18400@suse.de> On Tue, Mar 26, Simon Rowe wrote: > How long should I expect for a reply to an SR? I opened 10820471581 > nearly two weeks ago and haven't received a response yet. > The target is 3 days. I'll check with the Support team. Thanks Uwe -- Uwe Drechsel SUSE Linux Beta Program Manager SUSE Linux Products GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From urs.frey at post.ch Tue Mar 26 10:49:57 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Tue, 26 Mar 2013 16:49:57 +0000 Subject: [sles-beta] Experience with SLES11-SP3 beta3 x86_64 In-Reply-To: <5151D0B0.2090603@suse.com> References: <40637DBB36AF3941B243A286A432CA0B0E232763@HXMB12.pnet.ch> <5151D0B0.2090603@suse.com> Message-ID: <40637DBB36AF3941B243A286A432CA0B0E235064@HXMB12.pnet.ch> Hello Kai SR already opened 20-Mar-2013 SUMMARY OF SR # 10821644381 * SR Severity Level: Medium * SR Product: * SR Brief Description: SLES11-SP3-Beta3: postconf: warning: main.cf: unused parameter: program_directory SR is blocked on status pending by Jim Petersen, Novell Best regards Urs Frey????????????????????????????????????????????? Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX???? : ++41 (0)58 667 30 07 E-Mail:?? urs.frey at post.ch -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Kai Dupke Gesendet: Tuesday, March 26, 2013 5:46 PM An: sles-beta at lists.suse.com Betreff: Re: [sles-beta] Experience with SLES11-SP3 beta3 x86_64 Urs, please open an SR for this issue. greetings kai On 03/20/2013 03:11 PM, urs.frey at post.ch wrote: > Hello > > I downloaded SLES-11-SP3-DVD-x86_64-Beta3-DVD1.iso & SLE-11-SP3-SDK-DVD-x86_64-Beta3-DVD1.iso succesfully yesterday morning CET. > Now I am testing on HP Proliant DL385-G5, BL465cG7, BL460c-Gen8 and VMware > > Installation runs smoothly. I always do a fresh installation using autoyast and network install server via http:80 > > BUG with mcelog, not supporting AMD Opteron CPUs still open. > ([Bug 807336] mcelog: AMD Processor family 21: Please load edac_mce_amd module) > > I did already an update from SLES11-SP2 to SLES11-SP3 using zypper --non-interactive dist-upgrade --auto-agree-with-licenses > What I notice is a problem, when updating postfix: > > Installing: rsync-3.0.4-2.45.40 [.done] > Installing: postfix-2.9.4-0.9.25 [..done] > Additional rpm output: > warning: /etc/postfix/main.cf created as /etc/postfix/main.cf.rpmnew > warning: /etc/postfix/master.cf created as /etc/postfix/master.cf.rpmnew > executing upgrade-configuration > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > Editing /etc/postfix/master.cf, adding missing entry for tlsmgr service > Editing /etc/postfix/master.cf, adding missing entry for postscreen TCP service > Editing /etc/postfix/master.cf, adding missing entry for smtpd unix-domain service > Editing /etc/postfix/master.cf, adding missing entry for dnsblog unix-domain service > Editing /etc/postfix/master.cf, adding missing entry for tlsproxy unix-domain service > > Note: the following files or directories still exist but are no > longer part of Postfix: > > /etc/postfix/postfix-files /etc/postfix/postfix-script > /etc/postfix/post-install > > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > Updating etc/sysconfig/postfix... > Updating etc/sysconfig/mail... > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > > > Installing: openssh-6.1p1-0.9.12 [.done] > > > Postfix is working afterwards, but also in the /var/log/boot.msg I get this warning from postfix on my console: > -------------------------------- > > postfix start > > Starting mail service (Postfix)done > > 'postfix start' exits with status 0 > > > cron start > > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix > Starting CRON daemon > > ---------------------------------- > > Of course I can disable the line by editing /etc/postfix/mani.cf > #program_directory = /usr/lib/postfix > and then this warning no longer appears. > It would be great, if there is no need to edit manually after an Upgrade > > > Thank you for feedback > > > Best regards > > > Urs Frey > Die Schweizerische Post > Services > Informationstechnologie > Webergutstrasse 12 > 3030 Bern (Zollikofen) > Telefon : ++41 (0)58 338 58 70 > FAX : ++41 (0)58 667 30 07 > E-Mail: urs.frey at post.ch > > > _______________________________________________ > sles-beta mailing list > sles-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/sles-beta > > > Kai Dupke Senior Product Manager Server Product Line -- Phone: +49-(0)5102-9310828 Mail: kai.dupke at suse.com Mobile: +49-(0)173-5876766 WWW: www.suse.com SUSE Linux Products GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany) GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG Nurnberg) From kukuk at suse.de Tue Mar 26 12:05:55 2013 From: kukuk at suse.de (Thorsten Kukuk) Date: Tue, 26 Mar 2013 19:05:55 +0100 Subject: [sles-beta] Experience with SLES11-SP3 beta3 x86_64 In-Reply-To: <5151D0B0.2090603@suse.com> References: <40637DBB36AF3941B243A286A432CA0B0E232763@HXMB12.pnet.ch> <5151D0B0.2090603@suse.com> Message-ID: <20130326180555.GA27079@suse.de> On Tue, Mar 26, Kai Dupke wrote: > Urs, please open an SR for this issue. The problem is already fixed. -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From urs.frey at post.ch Tue Mar 26 12:08:04 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Tue, 26 Mar 2013 18:08:04 +0000 Subject: [sles-beta] Experience with SLES11-SP3 beta3 x86_64 In-Reply-To: <20130326180555.GA27079@suse.de> References: <40637DBB36AF3941B243A286A432CA0B0E232763@HXMB12.pnet.ch> <5151D0B0.2090603@suse.com> <20130326180555.GA27079@suse.de> Message-ID: <40637DBB36AF3941B243A286A432CA0B0E2350CD@HXMB12.pnet.ch> > Urs, please open an SR for this issue. > The problem is already fixed. Great! Thank you very much. Urs Frey????????????????????????????????????????????? Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX???? : ++41 (0)58 667 30 07 E-Mail:?? urs.frey at post.ch -----Urspr?ngliche Nachricht----- Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Thorsten Kukuk Gesendet: Tuesday, March 26, 2013 7:06 PM An: sles-beta at lists.suse.com Betreff: Re: [sles-beta] Experience with SLES11-SP3 beta3 x86_64 On Tue, Mar 26, Kai Dupke wrote: > Urs, please open an SR for this issue. The problem is already fixed. -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) _______________________________________________ sles-beta mailing list sles-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/sles-beta From urs.frey at post.ch Wed Mar 27 10:45:56 2013 From: urs.frey at post.ch (urs.frey at post.ch) Date: Wed, 27 Mar 2013 16:45:56 +0000 Subject: [sles-beta] Question concerning IPv6 Message-ID: <40637DBB36AF3941B243A286A432CA0B0E2355C0@HXMB12.pnet.ch> Hi As IPv6 becomes more and more important I wonder if there is also an IPv6 implementation within autoyast. I mean we here do have already IPv6 implemented in the Network Access DMZ. But IPv6 configuration has to be done using Shell scripts I googled a bit and got stuck, because I could not really find a solution, where I can place the IPv6 address directly in my autoyast.xml http://users.suse.com/~ug/ Some solutions propose a shell script to configure IPv6 in my ifcfg-eth0 Does somebody have experience with IPv6 LAN configuration when doing automated setup with autoyast? Are there SuSE plans concerning IPv6 full implementation in SLES autoyast? Maybe SLES12? Thank you very much for your feedback Best regards Urs Frey Die Schweizerische Post Services Informationstechnologie Webergutstrasse 12 3030 Bern (Zollikofen) Telefon : ++41 (0)58 338 58 70 FAX : ++41 (0)58 667 30 07 E-Mail: urs.frey at post.ch From mge at suse.com Thu Mar 28 04:31:22 2013 From: mge at suse.com (Matthias G. Eckermann) Date: Thu, 28 Mar 2013 11:31:22 +0100 Subject: [sles-beta] Question concerning IPv6 In-Reply-To: <40637DBB36AF3941B243A286A432CA0B0E2355C0@HXMB12.pnet.ch> References: <40637DBB36AF3941B243A286A432CA0B0E2355C0@HXMB12.pnet.ch> Message-ID: <20130328103122.GB16451@suse.com> Hello Urs and all, On 2013-03-27 T 16:45 +0000 urs.frey at post.ch wrote: > As IPv6 becomes more and more important I wonder if > there is also an IPv6 implementation within autoyast. I > mean we here do have already IPv6 implemented in the > Network Access DMZ. But IPv6 configuration has to be > done using Shell scripts > > I googled a bit and got stuck, because I could not > really find a solution, where I can place the IPv6 > address directly in my autoyast.xml > http://users.suse.com/~ug/ Some solutions propose a > shell script to configure IPv6 in my ifcfg-eth0 > > Does somebody have experience with IPv6 LAN > configuration when doing automated setup with autoyast? > > Are there SuSE plans concerning IPv6 full implementation > in SLES autoyast? Maybe SLES12? > > Thank you very much for your feedback while we have put IPv6 compatibility high on our agenda, and have achieved the "pole position" of Linux Distributions (not to say Operating Systems:-) in terms of IPv6 compliance (search for vendor "Novell"): https://www.iol.unh.edu/services/testing/ipv6/usgv6tested.php and even if I remember discussions about improving linuxrc (that's what is running in the initrd) to become IPv6 compliant, we might have a gap in AutoYaST, meaning that the YaST2-network module is fully IPv6 aware, but the AutoYaST schema is not. I am not sure, how quickly this can be resolved. Nevertheless, please open an SR and let's take it from there. Thanks for finding! As a sidenote: tomorrow (Friday, 2013-03-29) and on Monday (2013-04-01) are public holidays in Germany and other countries. Expect delays in answers from SUSE people. Happy Easter! so long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE? Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 E-Mail: mge at suse.com SUSE LINUX Products GmbH Maxfeldstra?e 5 90409 N?rnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg) From jeff.chapman at pervasive.com Thu Mar 28 10:05:53 2013 From: jeff.chapman at pervasive.com (Jeff Chapman) Date: Thu, 28 Mar 2013 16:05:53 +0000 Subject: [sles-beta] Question concerning IPv6 In-Reply-To: <20130328103122.GB16451@suse.com> References: <40637DBB36AF3941B243A286A432CA0B0E2355C0@HXMB12.pnet.ch> <20130328103122.GB16451@suse.com> Message-ID: <139B79F9D8503B44B649F0D751D8E9B31A9E9C93@PVSWMAIL2010.pervasive.com> We're also doing heavy IPv6 testing. We've had no problems so far with IPv6 in our interfaces or on the wire. I feel that the GUI utilities are not all that intuitive. For example, you have to setup an 'alias' (which is not a true DNS alias) in order to add an IPv6 address to an existing IPv4 configuration. I prefer separate tabs for IPv4 data, IPv6, data and DNS data. However once you realize you must use the 'alias' fields, the GUI utilities for IPv6 work pretty well. We're also testing with earlier editions of SuSE so we resigned ourselves to using post-install logic to setup IPv6 networking. For each Linux distro, it's a real hassle to get working (especially since we use self-administered IPv6 addresses so we can strictly control the scope and membership of QA's IPv6 subnets) and every flavor/release of Linux has different caveats. I realize this might be fairly complicated, but it would be ideal for the IPv6 setup to be standardized as a native part of Auto-YAST. Cheers, Jeff Jeff Chapman QA Architect, Database Division Tel: 512.231.6548 Main: 800.287.4383 Fax: 512.231.6010 Jeff.Chapman at pervasive.com Pervasive Software 12365-B Riata Trace Parkway Austin, TX 78727 http://www.pervasive.com/ NOTICE: All information in and attached to this email may be proprietary, confidential, privileged and otherwise protected from improper or erroneous disclosure. If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message.