On the other hand NetBSD's own .img files work OK.
However interestingly there's a small, but apparently insignificant
(because it works OK) difference between how fdisk sees the disk image
and the vnd0 device:
# fdisk -F images/NetBSD-9.99.81-amd64-live.img
Disk:
At Sat, 10 Apr 2021 18:44:32 -0700, Brian Buhrow wrote:
Subject: Re: I think I've found why Xen domUs can't mount some file-backed disk
images! (vnd(4) hides labels!)
>
> hello. This must be some kind of regression that's ben around a
> while. I'm runing a xen dom0 with NetBSD-5.2 and
hello. This must be some kind of regression that's ben around a
while. I'm runing a xen
dom0 with NetBSD-5.2 and xen-3.3.2, very old, but vnd(4) does expose the entire
file to the
domu's including FreeBSD 11 and 12 without any corruption or booting issues.
Do you know when this
The NetBSD-current/i386 build is working again.
Between the last failed build and the successful build, a total of
7130 revisions were committed, by the following developers:
mrg
rillig
wiz
The first of these commits was made on CVS date 2021.04.10.22.09.16,
and the last on
Martin Husemann writes:
> On Sat, Apr 10, 2021 at 04:12:55PM +1000, matthew green wrote:
> > Martin Husemann writes:
> > > On Sat, Apr 10, 2021 at 08:38:39AM +1000, matthew green wrote:
> > > > for a quick fix, this is OK, but long term, these are built
> > > > for sparc64 compat32 as well, and
I think I've found why Xen domUs can't mount some file-backed disk images!
This realization must have come to my unconscious as I was sleeping,
since just as I awoke I realised what must be happening.
The clue I needed was from back in the early March discussion with
Michael van Elst about
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2021.04.10.18.36.27.
An extract from the build.sh output follows:
--- print.lo ---
*** [print.lo] Error code 1
On Sat, Apr 10, 2021 at 04:12:55PM +1000, matthew green wrote:
> Martin Husemann writes:
> > On Sat, Apr 10, 2021 at 08:38:39AM +1000, matthew green wrote:
> > > for a quick fix, this is OK, but long term, these are built
> > > for sparc64 compat32 as well, and benefit from having this
> > > code
Martin Husemann writes:
> On Sat, Apr 10, 2021 at 08:38:39AM +1000, matthew green wrote:
> > for a quick fix, this is OK, but long term, these are built
> > for sparc64 compat32 as well, and benefit from having this
> > code in place.
>
> I have seen that (and the previous modes.inc
On Sat, Apr 10, 2021 at 08:38:39AM +1000, matthew green wrote:
> for a quick fix, this is OK, but long term, these are built
> for sparc64 compat32 as well, and benefit from having this
> code in place.
I have seen that (and the previous modes.inc conditionalizing it), but I
do not understand how
10 matches
Mail list logo
