MS Server 2016 image KVM boot fail

asked 2017-10-05 11:50:00 +0300

zraffai
1 ●1 ●1 ●1

Hi!

I just created a MS Server 2016 qcow2 image on Windows 8.1 with the cloudbase imaging tools.

When i try to start a new instance in Openstack i get 0xc00000001 error on startup.

I use Virtio version 1.133-2 with these parameters:

New-WindowsOnlineImage -WimFilePath $wimFilePath -ImageName $image.ImageName -WindowsImagePath $windowsImagePath -Type 'KVM' -ExtraFeatures @() -SizeBytes 20GB -CpuCores 4 -Memory 2GB -SwitchName $switchName -ProductKey $productKey -DiskLayout 'BIOS' -VirtioISOPath $virtIOISOPath -InstallUpdates:$false -AdministratorPassword 'Password' ` -PurgeUpdates:$false -DisableSwap:$true

On image creation I have several errors:

BFSVC: SetNamedSecurityInfo failed! Error code = 0x2 BFSVC: SetNamedSecurityInfo failed! Error code = 0x2 BFSVC: SetNamedSecurityInfo failed! Error code = 0x2 BFSVC: SetNamedSecurityInfo failed! Error code = 0x2

WARNING: BCDEdit failed: bootmgr device locate WARNING: BCDEdit failed: default device locate WARNING: BCDEdit failed: default osdevice locate Adding drivers from H: Adding drivers from "H:\WIN8\AMD64" to image "G:\"

Deployment Image Servicing and Management tool Version: 6.3.9600.17031

Error: 50

To service this Windows image requires the latest version of the DISM. See http://go.microsoft.com/fwlink/?LinkI... to find the latest version of DISM,

I tried to start the downloadable MS Server 2012 R2 eval from cloudbase, and it's works. I followed the creation steps from there.

edit retag flag offensive close merge delete

add a comment

Comments

I can't find a way to install newer DISM version to 8.1, I will try to create the image on a Hyper-V virtualized MS Server 2016. I'll back soon with the results. If it won't work I can try it with win 10 at the evening. Thank you, Raffai Zoltán

zraffai ( 2017-10-05 15:41:10 +0300 )edit

I tried it with windows 10 and the DISM error messages are gone and the drivers are installed, however i still get these errors : \GLOBALROOT\Device\HarddiskVolume15\Boot BFSVC: SetNamedSecurityInfo failed! Error code = 0x2

zraffai ( 2017-10-05 20:15:51 +0300 )edit

BFSVC: Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume15\Boot\cs-CZ\bootmgr.exe.mui for read because the file o r path does not exist

zraffai ( 2017-10-05 20:16:02 +0300 )edit

Is the image generation stopping because of those errors? Thanks.

avladu ( 2017-10-05 20:37:26 +0300 )edit

No, but neither with previous errors. I can try the new images(which i did with win10) tomorrow, but these left-over errors confuse me. Is it possible that these boot bootmgr.exe.mui files are not necessary? I tried it with two different ISO now, but the results are same.

zraffai ( 2017-10-05 20:43:21 +0300 )edit

see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

MS Server 2016 image KVM boot fail

1 answer

Comments

Your Answer

Question Tools

Stats

Related questions

MS Server 2016 image KVM boot fail edit

1 answer

Comments

Your Answer

Question Tools

Stats

Related questions

MS Server 2016 image KVM boot fail