OPERATIONAL DEFECT DATABASE
...
...
Image uploads and deploys successfully.After deployment, the virtual machine fails to boot and displays a repair or blue screen error.In this specific case, the issue is reproducible when the original image was installed using a SATA controller but deployed on NativeEdge with Virtio. It can happen with any images if the storage controller used during the original OS installation differs from the controller configured during deployment.Sometimes, converting the image to QCOW2 format resolves the issue, but conversion is only required if the image fails to boot.
Windows operating systems installed using a SATA controller do not include Virtio drivers by default.When the image is deployed on NativeEdge with Virtio as the storage controller, the OS cannot detect the disk and fails to boot.Changing the storage controller after OS installation is not supported because operating systems do not dynamically switch storage drivers postinstallation.
Workaround: Redeploy the virtual machine using the same storage controller type as the original installation (for example, SATA for Windows images created on Hyper-V).If boot still fails, convert the image to QCOW2 format using the virt-v2v tool on Linux: sudo apt-get install -y virt-v2v mkdir -p /var/tmp/v2v-out sudo virt-v2v -v -x -i disk <image>.vhd -o local -os /var/tmp/v2v-out -of qcow2 mv /var/tmp/v2v-out/<generated-file>.vhd-sda /var/tmp/v2v-out/<generated-file>.qcow2 Best Practice: Ensure that the correct storage controller is selected during initial OS installation.Avoid changing the storage controller after installation.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
