Bug 811110
Summary: | Qemu complains no space left during installation and migration while actually it should be enough | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Qunfang Zhang <qzhang> |
Component: | qemu-kvm | Assignee: | Kevin Wolf <kwolf> |
Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.3 | CC: | acathrow, areis, bsarathy, dyasny, juzhang, kwolf, michen, mkenneth, virt-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-04-11 05:28:39 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Qunfang Zhang
2012-04-10 07:31:24 UTC
After step 7: spice_server_add_interface: SPICE_INTERFACE_TABLET block I/O error in device 'drive-virtio-disk0': No space left on device (28) handle_dev_stop: stop block I/O error in device 'drive-virtio-disk0': No space left on device (28) block I/O error in device 'drive-virtio-disk0': No space left on device (28) block I/O error in device 'drive-virtio-disk0': No space left on device (28) block I/O error in device 'drive-virtio-disk0': No space left on device (28) block I/O error in device 'drive-virtio-disk0': No space left on device (28) (qemu) (qemu) info status VM status: paused (io-error) [root@t1 ~]# lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert lv-installation vgtest-qzhang -wi-ao-- 20.00g [root@t1 ~]# [root@t1 ~]# [root@t1 ~]# [root@t1 ~]# qemu-img info /dev/vgtest-qzhang/lv-installation image: /dev/vgtest-qzhang/lv-installation file format: qcow2 virtual size: 20G (21474836480 bytes) disk size: 0 cluster_size: 65536 When do you start qemu -incoming on host A? Is it before or after the lvextend? (In reply to comment #3) > When do you start qemu -incoming on host A? Is it before or after the lvextend? Hi, Kevin Re-test again, it will happen on both start qemu -incoming before and after the lvextend. And please check bug 683721 - qemu still claims ENOSPAC even if enlarge the image when doing migration. (closed as not a bug) When I tried the method in the bug 683721 comment 11, this bug will not exist any more. "(If you run fdisk -l <lv path> on dest the sizeis still 512M). If you run "lvmchange --refresh <LV path> " , and continue the dest vm everything run smoothly." So, I would like to close this bug. Please correct me if I am wrong. Thanks for investigating. Closing the bug looks right to me. |