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

Unable to setup vms,when starting it using virtctl the pod is running and than going in terminating phase #901

Closed AThakur812001 closed 11 months ago

AThakur812001 commented 1 year ago

kubectl logs virt-launcher-testvm-d8s75 is giving **{"component":"virt-launcher","level":"info","msg":"Collected all requested hook sidecar sockets","pos":"manager.go:86","timestamp":"2023-04-24T23:36:20.237487Z"} {"component":"virt-launcher","level":"info","msg":"Sorted all collected sidecar sockets per hook point based on their priority and name: map[]","pos":"manager.go:89","timestamp":"2023-04-24T23:36:20.237558Z"} {"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon: qemu+unix:///session?socket=/var/run/libvirt/virtqemud-sock","pos":"libvirt.go:519","timestamp":"2023-04-24T23:36:20.238618Z"} {"component":"virt-launcher","level":"info","msg":"Connecting to libvirt daemon failed: virError(Code=38, Domain=7, Message='Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory')","pos":"libvirt.go:527","timestamp":"2023-04-24T23:36:20.238934Z"} {"component":"virt-launcher","level":"error","msg":"failed to start virtqemud","pos":"libvirt_helper.go:250","reason":"fork/exec /usr/sbin/virtqemud: errno 0","timestamp":"2023-04-24T23:36:20.239471Z"} panic: fork/exec /usr/sbin/virtqemud: errno 0

goroutine 19 [running]: kubevirt.io/kubevirt/pkg/virt-launcher/virtwrap/util.LibvirtWrapper.StartVirtquemud.func1() pkg/virt-launcher/virtwrap/util/libvirt_helper.go:251 +0x4ce created by kubevirt.io/kubevirt/pkg/virt-launcher/virtwrap/util.LibvirtWrapper.StartVirtquemud pkg/virt-launcher/virtwrap/util/libvirt_helper.go:218 +0x65 {"component":"virt-launcher-monitor","level":"info","msg":"Reaped pid 12 with status 512","pos":"virt-launcher-monitor.go:120","timestamp":"2023-04-24T23:36:20.244316Z"} {"component":"virt-launcher-monitor","level":"error","msg":"dirty virt-launcher shutdown: exit-code 2","pos":"virt-launcher-monitor.go:138","timestamp":"2023-04-24T23:36:20.244506Z"}** I have checked the libvrt daemon,its running perfectly fine,also restarted it multiple times but still no luck.Also triend uninstalling and re-installing kubevirt but issue is still not solved

AThakur812001 commented 1 year ago

As per official doc for setup on minikube it is supposed to have 7 pods running in kubevirt namespace but its showing only 6,replica set,daemon set and deployments are all running fine

astranero commented 1 year ago

I have almost the same problem and would gladly accept any tips on how to get it to work. :+1:

astranero commented 1 year ago

Do you also get log error 'error: no kind "VirtualMachine" is registered for version "kubevirt.io/v1" in scheme "pkg/scheme/scheme.go:28" '?

AThakur812001 commented 1 year ago

Yeah I am facing the same error,as per my research the manifests required to setup kube-operator properly is there but the path mentioned in official doc command is incorrect As per setup command the yaml is supposed to be inside manifests directory but it is present in some other directory because of which we are only getting 6 pods as it is not getting the yaml for setting up the 7th pod

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/901#issuecomment-1732364214): >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

/reopen Sorry folks, this seemed to have slipped under the radar a while back. @cwilkers do you have any pointers about this?

cwilkers commented 1 year ago

Hi @ayuSH8033 is this related to minikube? You didn't really give much information about your environment.

Useful info would be what guide or quickstart are you following (if any) and what steps have you taken to arrive at this point.

Also, you mention that there's a pod missing. can you show the listing of the pods you do have running and point out what the missing pod should be?

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/901#issuecomment-1783913476): >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.