vexxhost / vexxhost/migratekit

Windows VM cant be Upgraded via Inplace Upgrade after Migration

Open
#58 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
138
Forks
40
Avg merge
1m
Merged PRs (30d)
1

Description

Windows Machines migrated with migratekit cant be Upgrades "Inplace".

Error:

Matching Profile found: UnknownDriverMigrationFailure - D7541B80-5071-42CE-AD14-FBE8C0C4F7FD

SetupDiag version: 1.7.0.0

System Information:

                Machine Name = Offline

                Manufacturer = OpenStack Foundation

                Model = OpenStack Nova

                HostOSArchitecture = x64

                FirmwareType = UEFI

                BiosReleaseDate = 20150206000000.000000+000

                BiosVendor = 0.0.0

                BiosVersion = 0.0.0

                HostOSVersion = 10.0.17763

                HostOSBuildString = 17763.1.amd64fre.rs5_release.180914-1434

                TargetOSBuildString = 10.0.20348.1 (fe_release.210507-1500)

                HostOSLanguageId = 1033

                HostOSEdition = ServerStandard

                RegisteredAV =

                FilterDrivers = luafv

                UpgradeStartTime = 17.12.2024 12:53:18

                UpgradeEndTime = 17.12.2024 13:27:30

                UpgradeElapsedTime = 00:34:12

                CV = 1EwEI6YflESz0oMG

                ReportId = 7f01e478-60f7-46ae-9d4a-9cc9966b6f39

 

Machines installed via prepared Windows Image are working as intended and can be upgraded inplace.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported migration from VMware to OpenStack and the subsequent Windows in-place upgrade, using the provided SetupDiag output as the failure baseline. Compare the migrated machine with one created from a prepared Windows image; done means the migrated machine completes the in-place upgrade successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cloud, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.