kubev2v / forklift

Apache License 2.0
29 stars 21 forks source link

Failing to import VM from oVirt on no space left on device #86

Open sandrobonazzola opened 2 years ago

sandrobonazzola commented 2 years ago

While trying to import a very small VM with CirrOS as guest OS, the migration fails on no space left on the target disk. Looks like the target disk is smaller than the source disk. Logs:

I0111 08:05:41.700028       1 importer.go:52] Starting importer
I0111 08:05:41.700188       1 importer.go:135] begin import process
I0111 08:05:42.054312       1 http-datasource.go:251] Attempting to get certs from /certs/ca.pem
I0111 08:05:42.161221       1 data-processor.go:323] Calculating available size
I0111 08:05:42.161329       1 data-processor.go:335] Checking out file system volume size.
I0111 08:05:42.161348       1 data-processor.go:343] Request image size not empty.
I0111 08:05:42.161396       1 data-processor.go:348] Target size 41488384.
I0111 08:05:42.161684       1 data-processor.go:231] New phase: TransferDataFile
I0111 08:05:42.161970       1 util.go:172] Writing data...
I0111 08:05:43.162335       1 prometheus.go:69] 100.00
E0111 08:05:43.521009       1 util.go:174] Unable to write file from dataReader: write /data/disk.img: no space left on device
E0111 08:05:43.534161       1 data-processor.go:228] write /data/disk.img: no space left on device
unable to write to file
kubevirt.io/containerized-data-importer/pkg/util.StreamDataToFile
    pkg/util/util.go:176
kubevirt.io/containerized-data-importer/pkg/importer.(*ImageioDataSource).TransferFile
    pkg/importer/imageio-datasource.go:130
kubevirt.io/containerized-data-importer/pkg/importer.(*DataProcessor).ProcessDataWithPause
    pkg/importer/data-processor.go:203
kubevirt.io/containerized-data-importer/pkg/importer.(*DataProcessor).ProcessData
    pkg/importer/data-processor.go:165
main.main
    cmd/cdi-importer/importer.go:189
runtime.main
    GOROOT/src/runtime/proc.go:225
runtime.goexit
    GOROOT/src/runtime/asm_amd64.s:1371
Unable to transfer source data to target file
kubevirt.io/containerized-data-importer/pkg/importer.(*DataProcessor).ProcessDataWithPause
    pkg/importer/data-processor.go:205
kubevirt.io/containerized-data-importer/pkg/importer.(*DataProcessor).ProcessData
    pkg/importer/data-processor.go:165
main.main
    cmd/cdi-importer/importer.go:189
runtime.main
    GOROOT/src/runtime/proc.go:225
runtime.goexit
    GOROOT/src/runtime/asm_amd64.s:1371
E0111 08:05:43.534401       1 importer.go:191] write /data/disk.img: no space left on device
unable to write to file
kubevirt.io/containerized-data-importer/pkg/util.StreamDataToFile
    pkg/util/util.go:176
kubevirt.io/containerized-data-importer/pkg/importer.(*ImageioDataSource).TransferFile
    pkg/importer/imageio-datasource.go:130
kubevirt.io/containerized-data-importer/pkg/importer.(*DataProcessor).ProcessDataWithPause
    pkg/importer/data-processor.go:203
kubevirt.io/containerized-data-importer/pkg/importer.(*DataProcessor).ProcessData
    pkg/importer/data-processor.go:165
main.main
    cmd/cdi-importer/importer.go:189
runtime.main
    GOROOT/src/runtime/proc.go:225
runtime.goexit
    GOROOT/src/runtime/asm_amd64.s:1371
Unable to transfer source data to target file
kubevirt.io/containerized-data-importer/pkg/importer.(*DataProcessor).ProcessDataWithPause
    pkg/importer/data-processor.go:205
kubevirt.io/containerized-data-importer/pkg/importer.(*DataProcessor).ProcessData
    pkg/importer/data-processor.go:165
main.main
    cmd/cdi-importer/importer.go:189
runtime.main
    GOROOT/src/runtime/proc.go:225
runtime.goexit
    GOROOT/src/runtime/asm_amd64.s:1371
# oc version
Client Version: 4.9.0-0.okd-2021-11-28-035710
Server Version: 4.9.0-0.okd-2021-12-12-025847
Kubernetes Version: v1.22.1-1824+934e08bc2ce38f-dirty
kubevirt-hyperconverged-operator.v1.5.0
konveyor-forklift-operator.v2.2.0

oVirt 4.4.8.5-1.el8

VM created from CirrOS cloud image from oVirt Glance repository.

ahadas commented 1 year ago

@sandrobonazzola do you remember if the file system was ext4?

sandrobonazzola commented 1 year ago

do you remember if the file system was ext4?

@ahadas sorry no, I don't remember. But I think it was XFS as we used to share the storage from a CentOS Stream 8 clean installation.