Attempting to create a windows 10 image

Community Support Storage
1

Hello i’ve been trying to create a windows 10 image but i am stuck i and keep on getting the “Windows cannot be installed to this disk. This computer’s hardware may not support booting to this disk. Ensure that the disk’s controller is enabled in the computer’s BIOS menu.” message in choosing the storage.

image
image1011×872 74.6 KB

here’s my vm template

TEMPLATE 15 INFORMATION
ID             : 15
NAME           : win10template
USER           : oneadmin
GROUP          : oneadmin
LOCK           : None
REGISTER TIME  : 03/08 10:54:43

PERMISSIONS
OWNER          : um-
GROUP          : ---
OTHER          : ---

TEMPLATE CONTENTS
CONTEXT=[
  NETWORK="YES",
  SSH_PUBLIC_KEY="$USER[SSH_PUBLIC_KEY]" ]
CPU="0.5"
CPU_COST="0.5"
DISK=[
  IMAGE="win 10 iot enterprise ltsc iso",
  IMAGE_UNAME="oneadmin",
  READONLY="NO" ]
DISK=[
  IMAGE="one-context",
  IMAGE_UNAME="oneadmin" ]
DISK=[
  IMAGE="virtio-01266",
  IMAGE_UNAME="oneadmin" ]
DISK=[
  DEV_PREFIX="vd",
  IMAGE="os-disk-osi-persistent",
  IMAGE_UNAME="oneadmin" ]
DISK=[
  DEV_PREFIX="vd",
  IMAGE="os-disk-datablock-persistent",
  IMAGE_UNAME="oneadmin" ]
DISK_COST="0.00048828125"
GRAPHICS=[
  LISTEN="0.0.0.0",
  TYPE="VNC" ]
HOT_RESIZE=[
  CPU_HOT_ADD_ENABLED="NO",
  MEMORY_HOT_ADD_ENABLED="NO" ]
HYPERVISOR="kvm"
INPUT=[
  BUS="usb",
  TYPE="tablet" ]
MEMORY="4096"
MEMORY_COST="0.5"
MEMORY_RESIZE_MODE="HOTPLUG"
MEMORY_SLOTS="2"
MEMORY_UNIT_COST="MB"
NIC=[
  NETWORK="vnet-bridged-public",
  NETWORK_UID="0",
  NETWORK_UNAME="oneadmin" ]
NIC_DEFAULT=[
  MODEL="virtio" ]
OS=[
  BOOT="disk0",
  FIRMWARE="BIOS",
  FIRMWARE_SECURE="NO" ]
SCHED_DS_RANK="FREE_MB"
SCHED_DS_REQUIREMENTS="ID=\"102\""
SCHED_RANK="FREE_CPU"
SCHED_REQUIREMENTS="ID=\"0\" | CLUSTER_ID=\"0\""
VCPU="4"

i have already done the following:

  • using the latest virtio drivers and making sure that the drivers are meant for windows 10
  • DEV_PREFIX = vd in the persistent storage image

and i just dont know what to do anymore, i already followed the guides here How to Build an Image for Windows Virtual Machines – OpenNebula Customer Portal and also watched the youtube video for it

2

i have found out the reason. apparently you have to also check the the disk that you created in setting up the boot order so windows would recognize it as a bootable disk - something that is unforunately not specified in the guide: How to Build an Image for Windows Virtual Machines – OpenNebula Customer Portal

image
image1283×474 16.4 KB

1 Like