Jump to content











Photo
- - - - -

hyperv in winpe (not winpe in hyperv)

hyperv winpe

  • Please log in to reply
3 replies to this topic

#1 noel

noel

    Frequent Member

  • Advanced user
  • 178 posts
  • Location:nantes
  •  
    France

Posted 15 April 2021 - 08:42 AM

Hi,

I know, it's something useless. But I like to play with winpe.

Yes, you can use VirtualBox or, better, use Linux. No problem ;-))

But after VirtualBox in winpe, i wanted to try hyperV in Winpe.

Much more complicated than VirtualBox. And it's not over yet. But I can create a VM and a Vswitch.

Actually, "someone" ( a driver, a program, a real ghost...) try to create the "virtual Switch" named "default" and immediately destroy this vswitch. I can't find how to stop this loop.

If someone want help me, i'll be happy.

See you soon.

Noel

Attached Files



#2 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 3041 posts
  • Location:Nantes - France
  •  
    France

Posted 18 April 2021 - 12:03 PM

Hi Noel,

 

Nice achievement already (starting vmms.exe as a service under winpe is probably not that easy).

Would be nice to come with a package or how to later on.

What is your base O.S? win10? 

 

About tracing/finding out who/what does create/destroy the default vswitch, have you tried  "process monitor" from (formerly) sysinternals?

It will show you the disk and registry activities of all processes which may give you a hint of who does what.

 

Regards,

Erwan

 

PS : next challenge would be to run the MS cluster service in WinPE so that you can run 2 winpe and use live migration between 2 hypervisors running in WinPE... :)



#3 noel

noel

    Frequent Member

  • Advanced user
  • 178 posts
  • Location:nantes
  •  
    France

Posted 19 April 2021 - 05:21 PM

Hi Erwan,

I'm happy to read you. I try to write without bing translator. But i'm sure you can read a french man writing in english ;-))

 

What is your base O.S? win10?

My Winpe is actually based on a Winpe ADK for 20H2. In hyperV ( into this winpe  host), i launch a same winpe version  in a VM (i don't get other os).

 

Yes, i use intensively Procmon.exe, windbg.exe since many years. And it's not easy to get a first "handler" to get the "one" who initiates the vmswtich destroy.

I play also with WindowsSandBox (WSL2 more later)  FOD. With Sandbox, i get the same issue with vmswitch.

 

 

...a package or how to later on

Actually, adding a FOD ( Feature On Deman with OptionalFeatures.exe) is not too complex.

But there is no futur for this feature itself and also for the creating method.

I use a VHD ( files and keys persistence ( as i described in an other place about FullFlat )

As i said, it needs a long wait to create a Winbuilder script ( i can't and i prefer my horrible PS script ).

 

Only for people who want to challenge with winpe and want to research the origine of the issue, i can put my VHD in a share ( ask me in a PM, and i'll be happy).

 

For the fun...

 

next challenge would be to run the MS cluster service in WinPE

If one day if i understand the concept but i can't without a french documentation. You know that my english is not good.

 

Have a good day.



#4 noel

noel

    Frequent Member

  • Advanced user
  • 178 posts
  • Location:nantes
  •  
    France

Posted 08 June 2021 - 07:58 AM

Hi,

I fixed the VmSwitch and HyperV anomaly in Winpe.

Unfortunately I can't provide the delta between the files/hives of Win10XPE and "my" Winpe.
Because the base of the files/keys of Win10XPE is too different. In Win10XPE, too many files,drivers,services,keys are missing.
Identifying them would take me too long.

I can explain in a few words the method I used to install the FODs. It is necessary to mount the VHD containing Winpe. To use the "DISM /add-feature" command, the target must have all the necessary files/keys so that 'trustedinstaller.exe' can move files and initialize components. "Dism" fills in a log file that allows you to find the missing files. The Component hive of 'install.wim' is required. As I check in Winpe the presence of FODs, you must also install the part 'X:Windowsservicing'.

 

I agree with those who will say that hyperV in Winpe is really useless.
It was a great challenge for me.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users