Re: install/58507: Weird installer issue in VM

["dev.lenn" <dev.lenn%proton.me@localhost>]

The following reply was made to PR install/58507; it has been noted by GNATS.

From: "dev.lenn" <dev.lenn%proton.me@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: install/58507: Weird installer issue in VM
Date: Wed, 31 Jul 2024 18:41:00 +0000

 G'Day Mr. Gutch,
 
 i've tried to create a NetBSD iso without vmt.=20
 Thatfor i tried the following steps:
 1. compiled Tools
 2. Create "NEW" file in sys/arch/amd64/conf
 =09--> same as "GENERIC" but with "#" in front of the line with "vmt0"
 3. cd sys/arch/amd64/conf
 4. /netbsd/obj/tooldir.Linux-6.1.0-23-amd64-x86_64/bin/nbconfig NEW
 5. /netbsd/obj/tooldir.Linux-6.1.0-23-amd64-x86_64/bin/nbmake-amd64 depend
 6. /netbsd/obj/tooldir.Linux-6.1.0-23-amd64-x86_64/bin/nbmake-amd64
 7. gzip -9 /home/master/netbsd/sys/arch/amd64/compile/NEW/netbsd
 8. Move netbsd.gz to the directory with the extracted NetBSD ISO (./iso_in/=
 cdrom0/)
 9. Remove .gz extension
 10. run "mkisofs -o ~/netbsd_custom.iso -b boot -c boot.catalog -r -J -v -T=
  ./iso_in/cdrom0/"
 
 This has led me to the following error: Size of boot image is 172 sectors -=
 > genisoimage: Error - boot image '/home/master/iso_in/cdrom0/boot' has not=
  an allowable size.
 
 According to the internet and ChatGPT: "This is because the boot file is no=
 t the expected size for an El Torito boot image file."=20
 Which is suprising to me because I haven't changed/modified the boot file
 
 I hope this mail is halfway understandable, i am sorry for my horrible engl=
 ish
 
 Thank you in advance
 Best Greetings
 Lenn
 
 
 
 
 Sent with Proton Mail secure email.
 
 On Monday, July 29th, 2024 at 09:25, Harold Gutch <logix%foobar.franken.de@localhost>=
  wrote:
 
 > The following reply was made to PR install/58507; it has been noted by GN=
 ATS.
 >=20
 > From: Harold Gutch logix%foobar.franken.de@localhost
 >=20
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc:
 > Subject: Re: install/58507: Weird installer issue in VM
 > Date: Mon, 29 Jul 2024 09:24:21 +0200
 >=20
 > Try disabling vmt. In the boot loader (the first thing you see when
 > booting that says "NetBSD/amd64" and counts down to 0), go to the
 > boot prompt and type "userconf disable vmt0", then "boot".
 >=20
 > You'll probably have to do that after the installation too. In order
 > to make the change permanent you can then add this to your /boot.cfg
 > (or compile a kernel without vmt0).
 >=20
 >=20
 > There have been a few updates (in -current) to vmt(4) earlier this
 > year, but I don't use VMWare Workstation and thus don't know if these
 > are relevant to your issue.
 >=20
 >=20
 > Harold