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: images/NetBSD-9.99.81-amd64-live
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 xen
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 trouble
Emmanuel Dreyfus wrote:
> port 3 addr 4: high speed, self powered, config 1, ZTE WCDMA
> Technologies MSM(0
> x0117), ZTE,Incorporated(0x19d2), rev 0.00(0x), serial
> MF1900BYTD01
I had some success with ZTE MF112 by just telling umass to not attach it
using umass_quirks (patch below).
As may be obvious to some by now my original proof-of-concept patch was
not exactly complete or even near correct.
This is the actual patch I've been testing (though it's collected from
places in a cvs-examine emacs buffer so may be incomplete).
I've restored some of the code that does actual ent
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 "probl
