On Fri, Dec 09, 2022 at 08:18:25PM +0200, Andreas Gustafsson wrote:
> And all but the most recent versions of qemu really do have a nasty
> habit of accessing the wrong part of the disk when running NetBSD
> guests, because of a bug that was finally fixed in this commit:
>
>
On Fri, Dec 09, 2022 at 05:14:58PM +, Mr Roooster wrote:
> It does seem to be possible to boot QEMU off the host disk under Linux
> (by pointing it at the block device rather than a partition), but you
> could really set yourself up for problems. (Qemu writing to the wrong
> bit of your disk
Mr Roooster wrote:
> It does seem to be possible to boot QEMU off the host disk under Linux
> (by pointing it at the block device rather than a partition), but you
> could really set yourself up for problems. (Qemu writing to the wrong
> bit of your disk may end badly. :D )
And all but the most
On Mon, 5 Dec 2022 at 12:48, Mayuresh wrote:
>
> On Sat, Dec 03, 2022 at 02:50:00PM +0100, Martin Husemann wrote:
> > I would not go via the VM detour, but instead:
>
> Just curious, what can go wrong this way.
>
I have installed OSs (Not NetBSD) using this method in the past,
giving the VM full
On Sun, Dec 04, 2022 at 08:17:46PM +0530, Mayuresh wrote:
> Thanks. If I got it right from one of your replies, -current installer is
> not recommended to install 9.2/9.3 sets. Right?
Yes, that will not work very well. I didn't test the netbsd-9 installer
because I didn't have it handy, but will
On Sat, Dec 03, 2022 at 02:50:00PM +0100, Martin Husemann wrote:
> I would not go via the VM detour, but instead:
Just curious, what can go wrong this way.
Booting configuration - yes, but it's a pain either way.
Besides, may be some amount of manual reconfiguration?
Or is there more mess it
On Sun, Dec 04, 2022 at 01:45:40PM +0100, Martin Husemann wrote:
> On Sun, Dec 04, 2022 at 09:32:56AM +0100, Martin Husemann wrote:
> > That sounds like a bug.
>
> I just tested with the installer from -current and a fake setup trying
> to mimic parts of your environment.
Thanks. If I got it
On Sun, Dec 04, 2022 at 09:32:56AM +0100, Martin Husemann wrote:
> That sounds like a bug.
I just tested with the installer from -current and a fake setup trying
to mimic parts of your environment. I used labels for the NetBSD partitions
to make their identification easier later.
Before:
# gpt
On Sat, Dec 03, 2022 at 08:37:33AM +0530, Mayuresh wrote:
> I am running into several problems described on previous title of this
> thread, on GPT partitioned disk and with UEFI boot.
As a last resort I tried installation on to a USB stick. Things went fine
till configuration stage. When setting
On Sun, Dec 04, 2022 at 12:10:02PM +0530, Mayuresh wrote:
> > 2) install (e.g. from the USB install image) by selecting "preconfigured
> > wedges (dk(4))" in the target disk selection and picking the root
> > partition you added in (1)
I forgot - this is slightly different in -current,
On Sat, Dec 03, 2022 at 02:50:00PM +0100, Martin Husemann wrote:
> 1) add partition(s) for NetBSD (root mandatory, swap optional)
> - you can do this manually from any other OS if it allows you to
> force a specific GPT type for the partition
> - you can do this from the install
On Sat, Dec 03, 2022 at 08:37:33AM +0530, Mayuresh wrote:
> On the same disk I have Void Linux and Windows installations.
The installer is not very smart when you create multi-boot installations
(unless you have a disk per OS).
I would not go via the VM detour, but instead:
1) add partition(s)
On Sat, Dec 03, 2022 at 08:37:33AM +0530, Mayuresh wrote:
> I'll use qemu/virtualbox on Linux to boot the installation image and
> select the physical partition on which I was trying to install NetBSD as
> the installation partition.
>
> Will this work, or are there things to watch out if I try
13 matches
Mail list logo
