8
Vote

Does not boot on Hyper-V

description

I have built Singularity and now i'm trying to boot it on Hyper-V (Windows Server 2008 x64)
I boot from World.Prototype.LegacyPC.MarkSweep.Min.MarkSweep.iso. It writes 1a2345 and nothing else.

On Virtual PC it boots correctly.

Is it possible to launch this OS on Hyper-V?

file attachments

comments

ohodson wrote Mar 6, 2008 at 12:04 AM

We've had a similar report on XEN and I noticed that VM Fusion and Bochs fail in a similar way.

zstengel wrote Mar 6, 2008 at 3:53 AM

We've had a similar report on XEN
This may be more appropriate for a new thread, but in my experience, booting from the ISO image on Xen fails well before "1a2345" gets written. This string gets written (as individual characters) inside of BootPhase1() in singldr.cpp. When booting on Xen, I don't even get that far. The initial boot loader (Etfs_BS.asm) fails, printing only the following to the screen:

S≡S

After digging into Etfs_BS.asm, I found that the problem is the boot loader cannot find the Supplementary Volume Descriptor (i.e. never jumps to the FoundSVD: label), and eventually jumps to SVDError:, which outputs the above error, instead of the intended "S Error". I don't know why this would fail in Xen but work in VPC, though.

GVL wrote Mar 6, 2008 at 12:24 PM

I got the same result on VMWare: it writes 1a2345 and hangs.

wrote Mar 6, 2008 at 1:36 PM

wrote Mar 7, 2008 at 8:07 PM

some1 wrote Mar 9, 2008 at 7:04 PM

I think I have a fix for the "1a2345" that at least works in VMWare. The problem is with functions in base\boot\Singldr\debug.cpp:
  1. It sets i8253 to the wrong mode (BCD one shot instead of binary periodic) according to my doc.
  2. It reads the timer value wrong -- the code assumes that the left operand to '+' is evaluated before the right, but that's not guarantied.
Diff attached.

wrote Mar 9, 2008 at 7:04 PM

wrote Mar 10, 2008 at 5:25 AM

mcnster wrote Mar 10, 2008 at 12:38 PM

Attached is "Etfs_BS.asm.diff" fixing the

S≡S

problem. The issue lies with some BIOS' loading the bootsector at 07c0:0 (which works ok without the patch),
and other BIOS' loading at 0000:7c00 (with gives the above error and fails--fixed by the patch).

wrote Mar 10, 2008 at 12:38 PM

artyom_kr wrote Mar 10, 2008 at 5:40 PM

Thanks, I applyed debug.diff - and now it boots on Hyper-V

Fabian030 wrote May 9, 2008 at 7:31 PM

How do I use the Etfs_BS.asm.diff to fix the issue with the S≡S error?
encountered that, too, on VirtualBox and vPC 2007

some1 wrote May 18, 2008 at 8:02 PM

You'll need a patch utility (e.g. http://gnuwin32.sourceforge.net/packages/patch.htm). Use it to apply .diff to the source code file in base/boot/BootSectors folder.
But actually this patch is quite trivial so you can just apply the changes by hands (just open the file in notepad, it's quite selfexplaining).

wrote Aug 18, 2008 at 9:25 PM

dcoetzee wrote Sep 17, 2008 at 4:31 AM

This is now internal bug 34.

wrote Nov 26, 2008 at 2:54 AM

ryanman wrote Nov 26, 2008 at 3:03 AM

I attempted to boot 17067 on 2 seperate Amd64 systems under hyper-v. I get a system hang with the following displayed on the screen:



DebugPort: 0000
KdInitialize! [CpuMaxCount=1]
No debugger.
Boot Time:
Booting from CD in drive 0xEF

Reading distro files ... 424 /424 165759822 /165759822
Debugger OFF
Allocated kernel stack at 0x0000000021BA5000
MM: Physical Region:
MM: BIOS
MM: SINGULARITY
MM: KERNEL_IMAGE
...
MM: BOOT_LOADER

BL: kernel=[00c1000 ... 00EF7FFF]
BL: entry = 00DD6060

wrote Nov 26, 2008 at 3:03 AM

wrote Feb 2, 2013 at 11:36 PM

mklemarczyk wrote Feb 2, 2013 at 11:40 PM

(Hyper-V in Windows 8 Pro x64)

I have an error:
BL: Unrecognized kill action 0xFFFFFFFF!
BL: Halt! blsingularity.cpp(720)

What does it mean?

sandit27 wrote Feb 6, 2013 at 6:41 PM

I'm facing same issue as mklemarczyk.

On Windows 8 Pro (Hyper-v), I'm getting the following error:
BL: Unrecognized kill action 0xFFFFFFFF!
BL: Halt! blsingularity.cpp(720)

What's the issue here?

wrote Feb 6, 2013 at 6:52 PM

wrote Feb 14, 2013 at 8:42 PM