February 2017 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] Adding update for kernel module
by Dr. Peer-Joachim Koch 23 Feb '17

23 Feb '17

Hi, I've to install SLES11SP3 on some newer DELL hardware (R730, R330). Problem: the module for the perc controller is to old, so the system won't see a, hard disk. I patched the initrd with a newer kernel module - installation works fine. The problem is now the installed kernel-rpm does not contain the new driver and the system will not boot. So what is the best way to add this additional rpm before the system is booting the first time, but after installing the kernel ? -- Bye, Peer ________________________________________________________ Max-Planck-Institut für Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705

1 1

Re: [opensuse-autoinstall] autoyast installation in Xen DomUs -- defining /etc/fstab ?
by lssl＠ssl-mail.com 14 Feb '17

14 Feb '17

Hi On Tue, Feb 14, 2017, at 05:19 AM, Erico Mendonça wrote: > Remember, in AutoYaST, less is more. 'less' is good. Trying to get to the most straightfwd way to build, configure & deploy Xen guests withOUT excess. For Opensuse at least pretty sure AY is part of the equation. > Where in that case would I set the 'proc', 'sysfs', debugfs', & 'devpts' > > mounts? They're not *additional* partitions, and from the docs, for a > > given partition I can only have one <mount>...</mount>. > > <snip> > > You shouldn't need it. IIRC, AutoYaST already adds these by default. It adds them by default, but what if I change the default fstopts for those mounts, e.g.? Or add an additional mount? Atm, adding changes to the Guest's /etc/fstab, then creating/examining a reference profile show no trace of my change. E.g., after adding /home/test/JUNK /mnt/JUNK none bind 0 0 to /etc/fstab, and re-creating a all-selected reference profile, I see no mention of the mount in the autoyast profile output. Unclear whether I've missed something in the profile generation, or it's simply not dealt with. > The easiest way would be to install the package yast2-autoyast on a machine > that already has these entries defined in /etc/fstab. Then run "yast2 > autoyast", select "Hardware", "Partitioning", then hit "Clone". > > You should be able to edit and export a valid XML. Kindof cheating, rather than rtfm'in up-front, by hey -- it works! Once I figure out the fstab bits ... -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 0

[opensuse-autoinstall] autoyast installation in Xen DomUs -- defining /etc/fstab ?
by lssl＠ssl-mail.com 14 Feb '17

14 Feb '17

I'm setting up autoyast for autoinstall of Xen DomUs. Both Xen Host & Guests run Opensuse Leap 42.2. >From my Dom0 I pass pre-formatted, but not yet populated, LVMs as disks to the DomU config guest.cfg ... disk = [ 'phy:/dev/VG0/EFI,xvda,w','phy:/dev/VG0/ROOT,xvde,w'] ... I want my Guest /etc/fstab to end up as UUID=AAAA-BBBB /boot/efi vfat [ ... efi fstab options ... ] 0 2 UUID=111...111 / ext4 [ ... root fstab options ... ] 1 1 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 My question is how 'best' to set the 'proc', 'sysfs', debugfs', 'devpts' mounts & their respective fstopts? In the autoyast.xml that'll get passed to the xen.cfg, IIUC, I can use <partitioning> for the passed-in devices, with 'initialize', 'create' & 'format' all == "false", <partitioning config:type="list"> <drive> <device>/dev/xvda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean" >false</create> <format config:type="boolean">false</format> <mount>/boot/efi</mount> <mountby config:type="symbol">uuid</mountby> <fstopt>[ ... efi fstab options ... ]</fstopt> <size>max</size> <filesystem config:type="symbol">vfat</filesystem> <partition_nr config:type="integer">1</partition_nr> </partition> </partitions> </drive> <drive> <device>/dev/xvde</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean" >false</create> <format config:type="boolean">false</format> <mount>/</mount> <mountby config:type="symbol">uuid</mountby> <fstopt>[ ... root fstab options ... ]</fstopt> <size>max</size> <filesystem config:type="symbol">ext4</filesystem> <partition_nr config:type="integer">1</partition_nr> </partition> </partitions> </drive> </partitioning> Where in that case would I set the 'proc', 'sysfs', debugfs', & 'devpts' mounts? They're not *additional* partitions, and from the docs, for a given partition I can only have one <mount>...</mount>. One option would be to use a postpartitioning script <scripts> <postpartitioning-scripts config:type="list"> <script> cat EOF >> /etc/fstab ( ... fstab entries for 'proc', 'sysfs', debugfs', & 'devpts' ... ) EOF </script> </postpartitioning-scripts> </scripts> , modifying the just-created-fstab immediately after the <partitioning> step. That's doable, but seems messy. What's the recommended way to get to a completely defined fstab in the Xen-DomU-install case above? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 3