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: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to