From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, xenomai@lists.linux.dev
Subject: Re: [xenomai-images][PATCH 3/3] start-qemu: Start with read-writable rootfs
Date: Wed, 04 Jan 2023 16:57:54 +0100 [thread overview]
Message-ID: <87d836c68358798cf64dfd1264974bd67cb6498b.camel@siemens.com> (raw)
In-Reply-To: <18e4ca3b65ab3881493b4e6a8d019cd62fe5efc8.1672845695.git.jan.kiszka@siemens.com>
On Wed, 2023-01-04 at 16:21 +0100, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> This is needed by systemd to initialize the machine ID on first boot.
I'm not facing any problem regarding the machine-ID here, but the LAVA
tests are failing like this:
2023-01-04T15:10:03 [?2004lmkdir: cannot create directory ‘/lava-6952’: Read-only file system
So, in addition to the qemu-script we might have to update the job
templates for the qemu tests as well.
I already added "rw" to the qemu kernel cmdline in my local branch, but
I updated to Debian 12 here and up to now was sure that this is
something Debian 12 specific. I have no glue what changed in the test
setup / LAVA installation that "rw" is necessary now. Any ideas?
Regards,
Florian
next prev parent reply other threads:[~2023-01-04 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 15:21 [xenomai-images][PATCH 0/3] Version updates, start-qemu fix Jan Kiszka
2023-01-04 15:21 ` [xenomai-images][PATCH 1/3] linux-xenomai: Refresh releases and simplify their maintenance Jan Kiszka
2023-01-04 15:21 ` [xenomai-images][PATCH 2/3] xenomai: Update to latest releases Jan Kiszka
2023-01-04 15:21 ` [xenomai-images][PATCH 3/3] start-qemu: Start with read-writable rootfs Jan Kiszka
2023-01-04 15:57 ` Florian Bezdeka [this message]
2023-01-04 16:25 ` Jan Kiszka
2023-01-04 22:37 ` Florian Bezdeka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d836c68358798cf64dfd1264974bd67cb6498b.camel@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.