Hi Dan,
On 1/31/23 7:38 AM, Dan Connolly wrote:
On Mon, Jan 30, 2023 at 2:08 PM Alexander Boettcher
wrote:
[...]
In your vbox6 configuration file, you have to use one VMDK per Block device. So
in your case it would be 3 different VMDK files.
Really?
On Tue, Jan 31, 2023 at 12:38 AM Dan Connolly wrote:
> On Mon, Jan 30, 2023 at 2:08 PM Alexander Boettcher
> wrote:
> [...]
> > In the runtime file there are 3 places, at the head, at the vfs node and in
> > the routing rules (end of file). According to your posted link, at the end
> > you
On Mon, Jan 30, 2023 at 2:08 PM Alexander Boettcher
wrote:
[...]
> In your vbox6 configuration file, you have to use one VMDK per Block device.
> So in your case it would be 3 different VMDK files.
Really?
https://genodians.org/jschlatow/2021-04-23-start-existing-linux-from-sculpt
seems to
Hi Dan,
On 30.01.23 16:09, Dan Connolly wrote:
On Mon, Jan 30, 2023 at 2:52 AM Alexander Boettcher
wrote:
You may rewrite the label to your actual Block provider, e.g. as an example
(taken from my setup):
Yes, my config is like that (with 1 rather than 7), and now that I
restart this
On Mon, Jan 30, 2023 at 2:52 AM Alexander Boettcher
wrote:
> You may rewrite the label to your actual Block provider, e.g. as an example
> (taken from my setup):
>
> label="7"/>
Yes, my config is like that (with 1 rather than 7), and now that I
restart this morning, I don't see the "no
Hello Dan,
On 30.01.23 01:37, Dan Connolly wrote:
I'm struggling to understand how to configure the vbox6-block component.
All seems to go well until...
[runtime -> ahci-0.part_block] Warning: no policy defined for label
'vbox6-block -> block0'
You may rewrite the label to your actual
I'm struggling to understand how to configure the vbox6-block component.
All seems to go well until...
[runtime -> ahci-0.part_block] Warning: no policy defined for label
'vbox6-block -> block0'
I read up on component configuration; I have a better understanding of it now.
https://geno
