Mailinglist Archive: opensuse-autoinstall (56 mails)

< Previous Next >
SLES9 on z/VM, autoyast and <dasd> section
  • From: Kai Dusek <kai.dusek@xxxxxxxxxx>
  • Date: Mon, 10 Apr 2006 16:55:43 +0000 (UTC)
  • Message-id: <OF598B1282.0FDD5701-ONC125714C.005B48C7-C125714C.005CFC6C@xxxxxxxxxx>
Dear all,

We're trying to setup an SLES9 SP3 system on a z/VM guest with autoyast.
We would like to pre-defined an autoinst.xml file.

It looks like the <dasd>...</dasd> section is mandatory since autoyast
does not get the dasd hardware settings "on the fly". Unfortunately we
don't know the mdisk id a priori, so that we currently are modifying the
autoinst.xml file manually for every system with a different mdisk id.

Replacing the autoinst.xml file with a new one during the pre-installation
step (as described in the SLES documentation) does not work since hardware
detection is done before pre-installation. Simply omiting the
<dasd>...</dasd> section did not work since yast stops working after
hardware detection since it does not detect any disk to install the system
on. I tried to add a dasd= (resp. DASD=) parameter to the parmfile but it
doesn't help detecting the disks.

Does anybody know what we could do to omit that <dasd>...</dasd> section
from the autoinst.xml file? Can we specify the mdisk id in that section
with a placeholder? Or has it really to be hardcoded in the autoinst.xml
file?

[...]
<dasd>
<devices config:type="list">
<listentry>
<channel_id>0.0.0150</channel_id>
<diag config:type="boolean">false</diag>
<format config:type="boolean">true</format>
</listentry>
</devices>
</dasd>
[...]


Mit freundlichen Gruessen/Kind regards

Kai Dusek
< Previous Next >
Follow Ups