Boot stuck with version 2.4.1

[guyschaos]

Hi @ailispaw ,

Just test your latest release, v2.4.1. Can not boot with Hyper-V. Here is the screen capture.

I've tried 3 isos.

1. Your local test build for Hyper-V config. -- pass
2. My local test build for Hyper-V config. -- pass
3. v2.4.1 -- stuck

[ailispaw]

Hmm.
The differences from v2.4.1-dev are
kernel: Add CONFIG_X86_X2APIC 1ddf696
and
Upgrade kernel to v4.9.15 1ddf696 .

I guess it's not big different.

[ailispaw]

Hyper-V doesn't support x2APIC?

[guyschaos]

I have no idea. Maybe I can revert the commit and build on my local machine.

[ailispaw]

@guyschaos Which version of Windows do you use?

[guyschaos]

Is there any quick guide for building Barge with docker ? Vagrant will not be an option for me on my windows computer, because Hyper-V conflicts with VirtualBox,

[guyschaos]

@ailispaw Windows 10 pro.

[ailispaw]

What you are trying to build is same as #36 (comment) except the version number 2.4.1-dev.

BTW,
Asking for cache data failed things are just a warning message and I can see in
#36 (comment) as well.
There is something wrong somewhere else.

[guyschaos]

I've created a fresh VM, it could boot without "Asking for cache data failed". I am confused...

[ailispaw]

I have never try this way, but it will work for you.

$ git clone https://github.com/bargees/barge-os.git
$ cd barge-os
<checkout a commit you want to build>
$ docker build -t barge-builder .
$ docker run --privileged --name barge-built barge-builder
$ docker cp barge-built:/build/buildroot/output/images/barge.iso .

[ailispaw]

I've created a fresh VM, it could boot without "Asking for cache data failed". I am confused...

Ah..
It's strange...

[ailispaw]

I guess there may be some wrong cache in somewhere of Virtual HDD...

[guyschaos]

Yes, looks Virtual HDD related after doing some tests.
Exist VM:

1. boot with your local build , Physic HDD as Virtual HDD , pass
2. boot with your v2.4.1, Physic HDD as Virtual HDD , stuck
3. boot with your v2.4.1, Physic HDD as Virtual HDD and add a new Virtual HDD , pass... !!!

So, workaround is -- add a new Virtual HDD (will never be used.)...

[ailispaw]

Hmm.
There might be something wrong to umount the disks on shutdown.
Your shutdown process looks normal on Hyper-V?

[ailispaw]

Im not sure it's caused by x2APIC or kernel v4.9.15.
Can you disable x2APIC on Hyper-V VM to test?

[guyschaos]

Try to compile with docker. Vagrant only works on my Mac at home. Will tell you the test result ASAP.

[guyschaos]

@ailispaw
After long long time of building, I got the iso of commit "Add CONFIG_X86_X2APIC ".
Remove my "New added fake Virtual HDD" , select the iso, boot the VM, every thing looks good.
Then, I tested the version 2.4.1, boot pass too.
That's weird. I have not change any thing else.
Maybe you can close this issue first. I will observe the Hyper-V barge-os behavior on my WIndows 10/WIndows Server 2012R2 these days.
Anyway, thanks for your support.

[ailispaw]

I found something.
Linux guest graceful shutdown in Hyper-V - Server Fault
http://serverfault.com/questions/747247/linux-guest-graceful-shutdown-in-hyper-v

We may need modprobe hv_utils and something (a user daemon).
I will try to create an ISO for that there. bargees/barge-packer#11

Stay tuned.

[guyschaos]

All the iso (your local build, my local build, version 2.4.1 and so on) can boot without any workaround. And I have tested version 2.4.1 on my Hp Microserver gen8 (Windows server 2012 R2), everything looks good.
I cannot reproduce the "Asking for cache data failed" any more. Maybe, there is a mistake with my physic hdd.
The Hyper-V KVP daemon looks useful for Hyper-V users. I can test your build with KVP feature. Where is the download link ?

[ailispaw]

@guyschaos Thank you for the confirmation.

Here it is.
bargees/barge-packer#12