May 2009 - openSUSE Autoinstall - openSUSE Mailing Lists

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

3 2

[opensuse-autoinstall] Adding packages to profile triggers error message
by Isaac Hailperin 07 Nov '10

07 Nov '10

Hi, I try to install sles 11 via autoyast. I did an installation from dvd, and pulled an autoyast profile. This profile works, and can be installed via pxe. Now I want to add the following packages: findutils-locate, dhcp-server, bind, apache2, vsftpd, nfs-kernel-server I do this via the gui. I have also tried to do it with an editor, as the gui messed up profiles in sles10sp2. In both cases, after the first reboot, I get the errormessage: "The package resolver run failed. Please check your software section in the aut" [oyast profile] (last part invisible, I guess it should be the software section in my autoyast profile :-)) This a real problem, as I have to confirm this message, thus it stops the autoinstall process. After confirming, the autoinstall process continues. Right bevor I can log in, I get "Could not update ICEauthority file /var/lib/gdm/.ICEauthority" I confirm, and get: "There is a problem with the configuration server. (/usr/lib/GConf/2/gconf-sanity-check-2 exited with status 256)" I confirm, and can log in. Theses messages are presistend after reboot. Its annoying, but not a stopper like the first problem. Why is this? Can I avoid this? Isaac -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] Classes do not work in 11.1 autoyast installation
by mwani＠fkf.mpg.de 06 Oct '09

06 Oct '09

Hi, I want to use classes in my autoyast installation. With the 'autoyast' parameter I'm loading the xml-file: <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <classes config:type="list"> <class> <class_name>default</class_name> <configuration>software.xml</configuration> </class> <class> <class_name>laptop</class_name> <configuration>partitions.xml</configuration> </class> </classes> </profile> I'm booting the client via PXE boot. I can see in the log file of the http server, that the client fetches the xml file. But in contrast the client does not even try to load the class files. I can not see an obvious error in the y2log file. With 10.3 that procedure worked that way. With 11.1 it has broken for me. Any hints are appreciated. thanks, Michael Wanitschek -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 7

[opensuse-autoinstall] Install all packages via autoyast.
by Ajay Mulwani 22 Aug '09

22 Aug '09

Hi, What is the syntax in autoinst.xml to install ALL packages of the media (sles10 and sles11). In RedHat Linux "@Everything" directive in ks.cfg does this job. Is there something similar available? Thanks, Ajay -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

7 9

[opensuse-autoinstall] merging of <package> doesn't work
by Frank Steiner 11 Aug '09

11 Aug '09

Hi, I'm adding two profiles in rules.xml, both contain <packages> and <remove-packages> entries (and addon produtcs). I'm adding the second profile as: <rule> ... <result> <profile>profiles/sled-only.xml</profile> <continue config:type="boolean">true</continue> <dont_merge config:type="list"> <element>listentry</element> <element>package</element> </dont_merge> </result> </rule> Merging of the two add_on_product listentries works fine, but the packages are not merged. E.g. I have <packages config:type="list"> <package>sendmail</package> </packages> in the first profile and <packages config:type="list"> <package>lilo</package> </packages> in the sled-only.xml. But lilo is not added and in y2log I see only "software":$["packages":["sendmail"]] although at some point earlier I find AutoInstallRules.ycp:590 user defined dont_merge for rules found. dontmerge is ["listentry", "package"] When merge the two xml files manually according to your blog, i.e. with /usr/bin/xsltproc --novalid --param replace "'false'" --param dontmerge1 "'package'" --param with "'sled-only.xml'" --output out.xml /usr/share/autoinstall/xslt/merge.xslt lmu.xml then out.xml contains the merge: <ns1:packages config:type="list"> <package>sendmail</package><package>lilo</package> </ns1:packages> Am I doing sth. wrong? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 6

[opensuse-autoinstall] net-udev and bonding
by Michael.Leu＠mgb.ch 04 Jun '09

04 Jun '09

Hi all, (please disregard my previous mail, some things where wrong, sorry.) I am trying to rename and bond two eth with AY while installing over NFS. It fails in the second configure step because it can't setup networking. SLES11 on a HP DL385 G5 with two internal NICs and one additional PCI dual-port NIC. These are the relevant parts of my networking section: <networking> <net-udev config:type="list"> <rule> <name>eth0</name> <rule>ATTR{address}</rule> <value>00:23:7d:25:5f:e4</value> </rule> <rule> <name>eth1</name> <rule>ATTR{address}</rule> <value>00:23:7d:25:5f:e6</value> </rule> </net-udev> <interfaces config:type="list"> <interface> <bonding_master>yes</bonding_master> <bonding_module_opts>mode=1 miimon=100</bonding_module_opts> <bonding_slave0>eth0</bonding_slave0> <bonding_slave1>eth1</bonding_slave1> <bootproto>static</bootproto> <device>bond0</device> <ipaddr>1.2.3.4</ipaddr> <netmask>255.255.255.0</netmask> <prefixlen>24</prefixlen> <startmode>auto</startmode> </interface> <interface> <bootproto>none</bootproto> <device>eth0</device> <startmode>off</startmode> </interface> <interface> <bootproto>none</bootproto> <device>eth1</device> <startmode>off</startmode> </interface> [... snip ...] </networking> Now what happens after the reboot is: Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.8.0 (Aug 14, 2008) vendor=1166 device=0142 bnx2 0000:0c:04.0: PCI INT A -> GSI 40 (level, low) -> IRQ 40 eth0: Broadcom NetXtreme II BCM5706 1000Base-T (A2) PCI-X 64-bit 100MHz found at mem f6000000, IRQ 40, node addr 00:1e:0b:d8:68:68 vendor=1166 device=0142 bnx2 0000:0d:05.0: PCI INT A -> GSI 39 (level, low) -> IRQ 39 eth1: Broadcom NetXtreme II BCM5706 1000Base-T (A2) PCI-X 64-bit 100MHz found at mem f8000000, IRQ 39, node addr 00:1e:0b:d8:68:6a vendor=1166 device=0144 bnx2 0000:04:00.0: PCI INT A -> GSI 41 (level, low) -> IRQ 41 eth2: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f2000000, IRQ 41, node addr 00:23:7d:25:5f:e6 vendor=1166 device=0142 bnx2 0000:42:00.0: PCI INT A -> GSI 34 (level, low) -> IRQ 34 scsi2 : qla2xxx eth3: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem fa000000, IRQ 34, node addr 00:23:7d:25:5f:e4 eth3 renamed to eth3_rename by udevd [2213] eth2 renamed to eth2_rename by udevd [2214] eth1 renamed to eth2 by udevd [2212] eth2_rename renamed to eth1 by udevd [2214] udev: renamed network interface eth1 to eth2 udev: renamed network interface eth2_rename to eth1 eth0 renamed to eth3 by udevd [2211] udev: renamed network interface eth0 to eth3 eth3_rename renamed to eth0 by udevd [2213] udev: renamed network interface eth3_rename to eth0 All looks good. But later it goes: Setting up (localfs) network interfaces: lo lo IP address: 127.0.0.1/8 IP address: 127.0.0.2/8 done eth0 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) No configuration found for eth0 unused eth1 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) No configuration found for eth1 unused eth2 device: Broadcom Corporation NetXtreme II BCM5706 Gigabit Ethernet (rev 02) eth2 Starting DHCP4 client. . . . . . . . eth2 DHCP4 continues in background waiting eth3 device: Broadcom Corporation NetXtreme II BCM5706 Gigabit Ethernet (rev 02) No configuration found for eth3 unused Waiting for mandatory devices: eth2 __NSC__ 11 10 8 7 6 5 3 2 1 eth2 device: Broadcom Corporation NetXtreme II BCM5706 Gigabit Ethernet (rev 02) eth2 DHCP4 client (dhcpcd) is running eth2 . . . but is still waiting for data waiting eth2 interface could not be set up until now failed Setting up service (localfs) network . . . . . . . . . . failed *** Starting YaST2 *** So network cannot be setup for the second stage because 1) eth0/1 are disabled for bonding 2) eth2 is in another VLAN And the final configuration step fails with: Cannot access installation media SUSE-Linux-Enterprise-Server-11 11-0 (Medium 1). Check whether the server is accessible. Am I doing something totally wrong? Or should I open a bugreport with Novell? Thanks, Michael ps: Why bother with renaming? Because not all our servers have additional NICs and for consistency I want the internal ones to always be eth0/1. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 4

[opensuse-autoinstall] Rule based auto-installation without network
by Tomas Rosenthal 02 Jun '09

02 Jun '09

Hi, I'm trying to set up a rule based SLES11 installer that will perform different installations depending on hardware. A requirement is that the installer must be able to run without a network connection. I'm invoking the autoinstaller like this: autoyast=file:///profiles/rules/rules.xml install=cdrom But it doesn't work. It seems it doesn't care about my rules.xml and just launches a generic minimalistic auto-install after validating the rules.xml file. I'm reading this doc: http://www.suse.de/~ug/autoyast_doc/rulesandclass.html "The rules file is retrieved only if no specific control is supplied using the autoyast keyword. For example, if the following is used, the rules file wont be evaluated: autoyast=http://10.10.0.1/profile/test.xml" Does it mean it's impossible the way I'm trying to make it? Should I use pre-install scripts instead? Regards, Tomas -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] net-udev and bonding
by Michael.Leu＠mgb.ch 31 May '09

31 May '09

Hi all, I am trying to rename and bond two eth with AY while installing over NFS. It fails in the second configure step because it can't setup networking. SLES11 on a HP DL385 G5 with two internal NICs and one additional PCI dual-port NIC. These are the relevant parts of my networking section: <networking> <net-udev config:type="list"> <rule> <name>eth0</name> <rule>ATTR{address}</rule> <value>00:23:7d:25:5f:e4</value> </rule> <rule> <name>eth1</name> <rule>ATTR{address}</rule> <value>00:23:7d:25:5f:e6</value> </rule> </net-udev> <interfaces config:type="list"> <interface> <bonding_master>yes</bonding_master> <bonding_module_opts>mode=1 miimon=100</bonding_module_opts> <bonding_slave0>eth0</bonding_slave0> <bonding_slave1>eth1</bonding_slave1> <bootproto>static</bootproto> <device>bond0</device> <ipaddr>1.2.3.4</ipaddr> <netmask>255.255.255.0</netmask> <prefixlen>24</prefixlen> <startmode>auto</startmode> </interface> <interface> <bootproto>none</bootproto> <device>eth0</device> <startmode>off</startmode> </interface> <interface> <bootproto>none</bootproto> <device>eth1</device> <startmode>off</startmode> </interface> [... snip ...] </networking> Now what happens after the reboot is: Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.8.0 (Aug 14, 2008) vendor=1166 device=0142 bnx2 0000:0c:04.0: PCI INT A -> GSI 40 (level, low) -> IRQ 40 eth0: Broadcom NetXtreme II BCM5706 1000Base-T (A2) PCI-X 64-bit 100MHz found at mem f6000000, IRQ 40, node addr 00:1e:0b:d8:68:68 vendor=1166 device=0142 bnx2 0000:0d:05.0: PCI INT A -> GSI 39 (level, low) -> IRQ 39 eth1: Broadcom NetXtreme II BCM5706 1000Base-T (A2) PCI-X 64-bit 100MHz found at mem f8000000, IRQ 39, node addr 00:1e:0b:d8:68:6a vendor=1166 device=0144 bnx2 0000:04:00.0: PCI INT A -> GSI 41 (level, low) -> IRQ 41 eth2: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f2000000, IRQ 41, node addr 00:23:7d:25:5f:e6 vendor=1166 device=0142 bnx2 0000:42:00.0: PCI INT A -> GSI 34 (level, low) -> IRQ 34 eth3: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem fa000000, IRQ 34, node addr 00:23:7d:25:5f:e4 eth2 renamed to eth2_rename by udevd [2613] eth1 renamed to eth2 by udevd [2615] udev: renamed network interface eth1 to eth2 eth2_rename renamed to eth1 by udevd [2613] udev: renamed network interface eth2_rename to eth1 Funny, only eth2 and eth1 get switched. And later it goes: Setting up (localfs) network interfaces: lo lo IP address: 127.0.0.1/8 IP address: 127.0.0.2/8 done eth0 device: Broadcom Corporation NetXtreme II BCM5706 Gigabit Ethernet (rev 02) No configuration found for eth0 unused eth1 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) No configuration found for eth1 unused eth2 device: Broadcom Corporation NetXtreme II BCM5706 Gigabit Ethernet (rev 02) eth2 Starting DHCP4 client. . . . . . . . eth2 DHCP4 continues in background waiting eth3 device: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) No configuration found for eth3 unused Waiting for mandatory devices: eth2 __NSC__ 11 10 8 7 6 4 3 2 1 eth2 device: Broadcom Corporation NetXtreme II BCM5706 Gigabit Ethernet (rev 02) eth2 DHCP4 client (dhcpcd) is running eth2 . . . but is still waiting for data waiting eth2 interface could not be set up until now failed Setting up service (localfs) network . . . . . . . . . . failed *** Starting YaST2 *** So network cannot be setup for the second stage because 1) eth0/1 are disabled for bonding 2) eth2 is in another VLAN And the final configuration step fails with: Cannot access installation media SUSE-Linux-Enterprise-Server-11 11-0 (Medium 1). Check whether the server is accessible. Am I doing something totally wrong? Or should I open a bugreport with Novell? Thanks, Michael ps: Why bother with renaming? Because not all our servers have additional NICs and for consistency I want the internal ones to always be eth0/1. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] use "partitioning_advanced" to define /etc/fstab for an autoyast-install of a clean Xen DomU?
by PGNet Dev 18 May '09

18 May '09

hi, i'm trying to get autoyast to use a defined /etc/fstab to setup a Xen DomU. reading @, "4.4.6. Using existing mount table (fstab)" http://www.suse.de/~ug/autoyast_doc/CreateProfile.Partitioning.html i've created a simple autoyast config, cat test.xml <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <partitioning_advanced> <fstab> <root_partition>/dev/xvdc1</root_partition> <use_existing_fstab config:type="boolean">true</use_existing_fstab> <partitions config:type="list"> <partition> </partition> </partitions> </fstab> </partitioning_advanced> </profile> i've placed, cat /etc/fstab /dev/xvdb1 swap swap defaults 0 0 /dev/xvdc1 / ext3 acl,user_xattr 1 1 /dev/xvda1 /boot ext3 acl,user_xattr 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 onto, /dev/VGU/vroot -> /etc/fstab my DomU cfg contains cat test.cfg ... disk = [ 'phy:/dev/VGU/vboot,xvda1,w', 'phy:/dev/VGU/vswap,xvdb1,w', 'phy:/dev/VGU/vroot,xvdc1,w', ] root = '/dev/xvdc1' extra = 'autoyast=nfs://.../test.xml ...' ... @ domU init/launch, xm create -c test.cfg the installer's invoked, as usual, but i get, "no linux root partition found" @ the link above, i note, "The found partitions will be formatted and mounted as specified in /etc/fstab found on a Linux root partition" since i'm creating a new Xen DomU, there's no clearly _existing_ linux root partition in the DomU how, in autoyast, can i get the DomU installer to mount & use the vfb's phy: devices for the install as defined in "an" /etc/fstab passed to it? thanks. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 5

[opensuse-autoinstall] Using autoyast for an automatic system recovery
by Leonardo L. P. da Mata 15 May '09

15 May '09

Hello, i'm thinking about a new usage of AutoYast (or at least a new in my head), i thinking about building an automatic system recovery for OpenSuse. The idea is to install a system and then create an image of the installed system and store into a partition of the disk. This partition will contain the installer, with an autoyast.xml script that will use this image to automatic restore the installed system (like Sony does in its Notebooks). As conception sounds good, but I need to mature this idea, do you have any suggestions, information or ideas to give? Thanks. -- Leonardo Luiz Padovani da Mata barroca(a)gmail.com "May the force be with you, always" "Nerd Pride... eu tenho. Voce tem?" -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0