boot disk not an MBR partition (Hyper-V to AWS)

swbns · Mon Sep 09, 2024 1:05 am

Hi
I am trying to convert a Windows VM from Hyper-V to AWS.

I get all the way through to the output screen (AWS) and press Convert.

I then get the error message 'Boot disk is not an MBR partition'.

Any advice would be appreciated.

thanks.

Mon Sep 09, 2024 1:12 am

Could you please provide the screenshot and the conversion logs from C:\Program Files\StarWind Software\StarWind V2V Converter\logs?

swbns · Mon Sep 09, 2024 1:36 am

: starwind issue1.png (21.91 KiB) Viewed 5340 times

The log file name: 'logs\V2V_Log-20240909-103721.log' (PID 49228)
9/9 10:37:21.677 4278 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
9/9 10:37:21.677 4278 Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.1.509
9/9 10:37:21.681 4278 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
9/9 10:37:21.682 4278 Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
9/9 10:37:21.683 4278 Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 10, MinorVersion 0, BuildNumber 22631
9/9 10:37:21.687 4278 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - 94600000
9/9 10:37:21.687 4278 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - 94600000
9/9 10:37:35.296 4278 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eHYPERVConnection
9/9 10:37:56.833 4278 Facility ???INFO: WrapperHyperV::connect: Host - \\192.168.0.2\root\virtualization\v2
9/9 10:37:59.600 4278 Facility ???INFO: WrapperHyperV::connect: user: administrator
9/9 10:37:59.600 4278 Facility ???WARNING: WrapperHyperV::connect: Domain not found - administrator
9/9 10:38:00.059 4278 Facility ???INFO: WrapperHyperV::connectToCIMV2: user: administrator
9/9 10:38:00.059 4278 Facility ???WARNING: WrapperHyperV::connectToCIMV2: Domain not found - administrator
9/9 10:38:00.274 4278 Facility ???INFO: WrapperHyperV::init_version: HyperV version: 10.0.17763
9/9 10:38:00.280 4278 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eInputVM
9/9 10:38:32.517 4278 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eLocationTo
9/9 10:38:36.505 4278 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - (null)
9/9 10:40:02.417 4278 Facility ???INFO: WrapperAWS::createEC2Client: Created clients to region - ap-southeast-2
9/9 10:40:02.417 4278 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVMSettingsAWS
9/9 10:40:44.873 4278 Facility ???INFO: CVHDXFile::getCurrentHeader: Read header 1.
9/9 10:40:44.874 4278 Facility ???INFO: CVHDXFile::getCurrentHeader: Read header 2.
9/9 10:40:44.875 4278 Facility ???INFO: CVHDXFile::getCurrentHeader: Check correct header 1.
9/9 10:40:44.875 4278 Facility ???INFO: CVHDXFile::getCurrentHeader: Check correct header 2.
9/9 10:40:44.876 4278 Facility ???INFO: CVHDXFile::ParseFile: Log is empty.
9/9 10:40:44.876 4278 Facility ???INFO: CVHDXFile::getRegion: Read region header 1.
9/9 10:40:44.879 4278 Facility ???INFO: CVHDXFile::getRegion: Read region header 1.
9/9 10:40:46.261 4278 Facility ???ERROR: CPPVMSettingsAWS::onNext: Boot disk is not MBR partitioning - 0
9/9 10:49:06.398 4278 Facility ???INFO: CVHDXFile::getCurrentHeader: Read header 1.
9/9 10:49:06.398 4278 Facility ???INFO: CVHDXFile::getCurrentHeader: Read header 2.
9/9 10:49:06.418 4278 Facility ???INFO: CVHDXFile::getCurrentHeader: Check correct header 1.
9/9 10:49:06.418 4278 Facility ???INFO: CVHDXFile::getCurrentHeader: Check correct header 2.
9/9 10:49:06.420 4278 Facility ???INFO: CVHDXFile::ParseFile: Log is empty.
9/9 10:49:06.420 4278 Facility ???INFO: CVHDXFile::getRegion: Read region header 1.
9/9 10:49:06.427 4278 Facility ???INFO: CVHDXFile::getRegion: Read region header 1.
9/9 10:49:18.469 4278 Facility ???ERROR: CPPVMSettingsAWS::onNext: Boot disk is not MBR partitioning - 0

Thu Sep 12, 2024 11:16 pm

Thanks for your update. I will forward the logs to R&D.

Wed Sep 18, 2024 6:25 pm

R&D has found the issue. They are working on resolving it.