Mailinglist Archive: opensuse-buildservice (251 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] loop module in qemu-kvm of build service
- From: Adrian Schröter <adrian@xxxxxxx>
- Date: Wed, 1 Sep 2010 10:54:53 +0200
- Message-id: <201009011054.53422.adrian@xxxxxxx>
On Wednesday 01 September 2010 00:05:34 Praveen_Paladugu@xxxxxxxx wrote:
I suppose you speak about the use case of XEN/kvm using and inside of it qemu ?
For XEN I solved this by defining the loop module as to be loaded as default in
initrd.
We still use the kernel and initrd from the worker host and not the kernel from
the build target.
(The reason for this is that most of our build targets don't have a good enough
working kernel in VM).
bye
adrian
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian@xxxxxxx
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
Kiwi image builds require loop devices in the qemu virtual Machine used by
OBS server.
But the kernel that qemu boots into doesn't seem to have "loop" built in. It
is compiled as a module.=20
I tried to load the loop module in init_buildsystem (with modprobe loop)
script which is run by the kernel during boot. =20
Since the modules.dep file is not available, this will not work.
How else can I load "loop" module into the kernel in the VM for the kiwi
builds to work?
Following are the versions of packages I am using:
I suppose you speak about the use case of XEN/kvm using and inside of it qemu ?
For XEN I solved this by defining the loop module as to be loaded as default in
initrd.
We still use the kernel and initrd from the worker host and not the kernel from
the build target.
(The reason for this is that most of our build targets don't have a good enough
working kernel in VM).
bye
adrian
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian@xxxxxxx
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |