> --- Original message ---
> From: "Rodney W. Grimes"
> Date: 27 February 2018, 10:28:37
> > > --- Original message ---
> > > From: "Rodney W. Grimes"
> > > Date: 27 February 2018, 09:13:56
> > > > ...
> > > >
> > > > > > Boot Failed? So windows never started.
> > > > > > Your not having a shutdown problem your having a start up failure.
> > > > > >
> > > > > > What is the output of:
> > > > > > file /vm/img/disk1.raw
> > > > > > file /VM/distro/null.iso
Your command in the original email had these 2 strings, please correct that
error in your command. VM != vm in unix world.
> > > > > > And do you really have /vm and /VM? Or is that a typo?
> > > >
> > > >
> > > > You have not answered these 3 questions
> > > > what is output of "file /vm/img/disk1.raw"
> > > > what is output of "file /VM/distro/null.iso"
> > > >
> > > > Is there a possible typo here in your command line??? vm vs VM?
> > >
> > > This files are present and without typo as I have copied path and
> > > filenames via clipboard.
> > > Next I will try with sysutils/uefi-edk2-bhyve-csm.
> >
> > It would still be helpful to know what the host system thinks of
> > these files, please output of:
> > file /vm/img/disk1.raw
> > file /VM/distory/null.iso
>
> Ok,
>
> # file ./null.iso
> ./null.iso: empty
>
> # file ./disk1.raw
> ./disk1.raw: DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163
> "Invalid partition table" at offset 0x17b "Error loading operating system" at
> offset 0x19a "Missing operating system", disk signature 0xbaf010d7; partition
> 1 : ID=0x7, active, start-CHS (0x0,32,33), end-CHS (0xc,223,19), startsector
> 2048, 204800 sectors; partition 2 : ID=0x7, start-CHS (0xc,223,20), end-CHS
> (0x3ff,254,63), startsector 206848, 253745152 sectors; partition 3 : ID=0x7,
> start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 253953468,
> 722810844 sectors
Ok so infact these 2 files are in the same directory, that needs to be spelled
exactly the same
on the command line of bhyyve.
But I think the bigger problem is that this is an MBR disk with Windows 7 in
it, I
do not believe that bhyve can run Windows 7 at this time.
> May be I incorrect have converted this image?...
The results above look ok, though the alignment is a bit odd.
You man want to play with mdconfig and fusefs to see if you
can read the converted image:
pkg install fusefs-ntfs
mdconfig -f disk1.raw
ntfs-3g /dev/md0s1 /mnt
find /mnt
That should atleast validate the file system a little.
> I have just tested with UEFI_CSM.
> I am able manage BHYVE UEFI via F2 key pressing and there are Legacy CD-ROM
> and Legacy Hard Drive options. If choosing HDD and continue to booting just
> black screen...
Peter pointed out to us that UEFI_CSM does not work with windows.
I think the bigger problem here is this appears to be a windows 7 image?
--
Rod Grimes rgri...@freebsd.org
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"