search

kubevirt / kubevirt.github.io

KubeVirt website repo, documentation at https://kubevirt.io/user-guide/
https://kubevirt.io
MIT License
30 stars 112 forks source link

VM not starting up on kubevirt using minikube #902

Closed astranero closed 11 months ago

astranero commented 1 year ago

While deploying kubevirt on minikube I get only 6 pods running.

NAME                                   READY   STATUS    RESTARTS      AGE
pod/virt-api-5888cc84c7-vwp8p          1/1     Running   1 (19m ago)   54m
pod/virt-controller-546465698c-jr86c   1/1     Running   1 (19m ago)   54m
pod/virt-controller-546465698c-qllxk   1/1     Running   1 (19m ago)   54m
pod/virt-handler-r42ql                 1/1     Running   0             54m
pod/virt-operator-6d56bb6986-28cvb     1/1     Running   0             55m
pod/virt-operator-6d56bb6986-8h445     1/1     Running   0             55m

NAME                                  TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE
service/kubevirt-operator-webhook     ClusterIP   10.110.94.19     <none>        443/TCP   54m
service/kubevirt-prometheus-metrics   ClusterIP   None             <none>        443/TCP   54m
service/virt-api                      ClusterIP   10.107.139.104   <none>        443/TCP   54m
service/virt-exportproxy              ClusterIP   10.108.239.237   <none>        443/TCP   54m

NAME                          DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
daemonset.apps/virt-handler   1         1         1       1            1           kubernetes.io/os=linux   54m

NAME                              READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/virt-api          1/1     1            1           54m
deployment.apps/virt-controller   2/2     2            2           54m
deployment.apps/virt-operator     2/2     2            2           55m

NAME                                         DESIRED   CURRENT   READY   AGE
replicaset.apps/virt-api-5888cc84c7          1         1         1       54m
replicaset.apps/virt-controller-546465698c   2         2         2       54m
replicaset.apps/virt-operator-6d56bb6986     2         2         2       55m

NAME                            AGE   PHASE
kubevirt.kubevirt.io/kubevirt   55m   Deployed

Also when deploying a testvm, I get following log error.

error: no kind "VirtualMachine" is registered for version "kubevirt.io/v1" in scheme "pkg/scheme/scheme.go:28"

Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT

Uncomment only one, leave it on its own line:

/kind bug /kind enhancement

What happened: Installation and setup of vms via kubevirt per instructions What you expected to happen: I expected vm to run correctly Anything else we need to know?: I have setup kvm and virtualization setting up correctly. I'm using latest ubuntu version.

URL where the problem can be found ... If the issue is with a lab, please provide information about your environment, platform, versions, ...

kubevirt-bot commented 1 year ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kubevirt-bot commented 1 year ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

kubevirt-bot commented 1 year ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

kubevirt-bot commented 1 year ago

@kubevirt-bot: Closing this issue.

In response to [this](https://github.com/kubevirt/kubevirt.github.io/issues/902#issuecomment-1732271125): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
aburdenthehand commented 1 year ago

Related to #901

cwilkers commented 1 year ago

What version of KubeVirt did you deploy? Recent versions have v1, but an older one might still consider the VirtualMachine object to be v1beta.

kubevirt-bot commented 11 months ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

kubevirt-bot commented 11 months ago

@kubevirt-bot: Closing this issue.

In response to [this](https://github.com/kubevirt/kubevirt.github.io/issues/902#issuecomment-1792425887): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.