Failed to start VMI with error message "failed to find a sourceFile in containerDisk rootfs:"

[belegent]

I want to start a VM using the example vm.yaml https://github.com/kubevirt/demo/blob/master/manifests/vm.yaml. When I start the VM, the VMI reports Waring message that "failed to find a sourceFile in containerDisk rootfs: Failed to check /proc/1/root/var/lib/containers/storage/devicemapper/mnt/8f42be56572b3f6f79751c36b4b4f99d8335f36984d54504bac650b23a2b247a/disk for disks: open /proc/1/root/var/lib/containers/storage/devicemapper/mnt/8f42be56572b3f6f79751c36b4b4f99d8335f36984d54504bac650b23a2b247a/disk: no such file or directory".

[fabiand]

Hm, that's unusual.

Did you follow the demo README step by step? Or are you using something else than minikube?

[belegent]

I am using Kubernetes v1.16.0.

[kubevirt-bot]

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]

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]

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

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.