I am trying to migrate VM onto the kubernetes cluster, approach i have followed is to upload image onto DataVolume and creating and CR for VirtualMachine , after creating it my VM is stuck in provsioning State , not sure where i am wrong in this
windows-test-vm6 15h Provisioning False
this is descripition, also i am using kubvirt extension and virtctl to execute vm related commands, if this works i will replicate same process onto Open-shift cluster
Name: windows-test-vm6
Namespace: default
Labels: kubevirt.io/vm=vm-alpine-datavolume
Annotations: kubevirt.io/latest-observed-api-version: v1
kubevirt.io/storage-observed-api-version: v1alpha3
API Version: kubevirt.io/v1
Kind: VirtualMachine
Metadata:
Creation Timestamp: 2022-09-14T11:09:56Z
Generation: 6
Managed Fields:
API Version: kubevirt.io/v1alpha3
Fields Type: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.:
f:kubectl.kubernetes.io/last-applied-configuration:
f:labels:
.:
f:kubevirt.io/vm:
f:spec:
.:
f:template:
.:
f:metadata:
.:
f:labels:
.:
f:kubevirt.io/vm:
f:spec:
.:
f:domain:
.:
f:devices:
.:
f:disks:
f:resources:
.:
f:requests:
.:
f:memory:
f:volumes:
Manager: kubectl-client-side-apply
Operation: Update
Time: 2022-09-14T11:09:56Z
API Version: kubevirt.io/v1alpha3
Fields Type: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
f:kubevirt.io/latest-observed-api-version:
f:kubevirt.io/storage-observed-api-version:
f:spec:
f:running:
Manager: Go-http-client
Operation: Update
Time: 2022-09-15T02:32:51Z
API Version: kubevirt.io/v1alpha3
Fields Type: FieldsV1
fieldsV1:
f:status:
.:
f:conditions:
f:created:
f:printableStatus:
f:volumeSnapshotStatuses:
Manager: Go-http-client
Operation: Update
Subresource: status
Time: 2022-09-15T02:33:45Z
Resource Version: 11889192
UID: 3049b3a4-c470-4089-9d8a-7ae93f4fff34
Spec:
Running: true
Template:
Metadata:
Creation Timestamp: <nil>
Labels:
kubevirt.io/vm: vm-alpine-datavolume
Spec:
Domain:
Devices:
Disks:
Disk:
Bus: virtio
Name: winatifdv
Machine:
Type: q35
Resources:
Requests:
Memory: 2Gi
Volumes:
Data Volume:
Name: winatifdv
Name: winatifdv
Status:
Conditions:
Last Probe Time: 2022-09-15T02:33:45Z
Last Transition Time: 2022-09-15T02:33:45Z
Message: virt-launcher pod has not yet been scheduled
Reason: PodNotExists
Status: False
Type: Ready
Created: true
Printable Status: Provisioning
Volume Snapshot Statuses:
Enabled: false
Name: winatifdv
Reason: No VolumeSnapshotClass: Volume snapshots are not configured for this StorageClass [longhorn] [winatifdv]
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal SuccessfulDelete 9m50s virtualmachine-controller Stopped the virtual machine by deleting the virtual machine instance e37bb1a5-75d3-4cc9-9daf-8d624379bbd9
Normal SuccessfulCreate 8m56s (x3 over 15h) virtualmachine-controller Started the virtual machine by creating the new virtual machine instance windows-test-vm6