Mailinglist Archive: opensuse-buildservice (332 mails)

< Previous Next >
Re: [opensuse-buildservice] Re: [PATCH] added sample how to generate a KVM initrd for OBS worker use
  • From: Martin Mohring <martinmohring@xxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 22 Jul 2010 10:56:04 +0200
  • Message-id: <4C4807A4.2030309@xxxxxxxxxxxxxxxxxxx>
Adrian Schröter wrote:
On Wednesday 21 July 2010 21:04:16 OBS build-service wrote:

From: Martin Mohring <martinmohring@xxxxxxxxxxxxxxxxxxx>

dist/sysconfig.obs-worker | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/dist/sysconfig.obs-worker b/dist/sysconfig.obs-worker
index 5526fd3..815db71 100644
--- a/dist/sysconfig.obs-worker
+++ b/dist/sysconfig.obs-worker
@@ -157,6 +157,12 @@ OBS_VM_KERNEL="none"
## Default: "none"
## Config: OBS
+# for KVM, you have to create with (example for openSUSE 11.2):
+# export rootfstype="ext4"
+# mkinitrd -d /dev/null -m "ext4 binfmt_misc virtio_pci virtio_blk" -k
vmlinuz- -i initrd-
+# a working initrd file which includes virtio and binfmt_misc for OBS in
order to work fine

Why is that needed at all ? We have out-of-the-box working KVM on our
appliances without the need to modify
the system initrd ?

The build script defaults to ext3 anyway and if you don't change the values
in sysconfig the initrd get anyway
replaced again on next kernel update.

So I dislike this hint atm, because it will create problems later.


Then I correct the comment in that sense that:
- if you want or need to use an own kernel with the KVM setup
- then you need to make sure that the initrd contains the modules listed
- and want to default to ext4 in the KVM setup, then you have to make
export rootfstype="ext4"

You say the initrd defaulting in /boot is working. Then I can comment
like that. Let me try it out. Do you suggest that:
- switching on KVM should automagically work
- what about a missing vitio module in the initrd


To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >