Bug 858525
Summary: | [virtio-win][scsi] windows guest fail to automatically detect the new partition after online resize | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Sibiao Luo <sluo> |
Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.4 | CC: | acathrow, bcao, bsarathy, chayang, flang, juzhang, lijin, michen, qzhang, rhod, shuang, virt-bugs, xfu |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Do not document. This is not a bug, but expected behaviour. For more information please see comment in Devel Whiteboard
field.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-21 23:59: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
Sibiao Luo
2012-09-19 02:40:26 UTC
SCSI does not support resize yet. Moving to 6.5. Hi vrozenfe, This issue moving to 6.5, I donot know when the virtio-scsi support block_resize for virtio-win component? there are existing 'RFE - Virtio-scsi should support block_resize' bug for QEMU-KVM and kernel components, and just in ON_QA and POST status. Just as i disuse with Paolo in IRC that want to ask you whether need to open a RFE bug for virtio-win component for tracing the progress ? Best wishes. sluo (In reply to comment #3) > Hi vrozenfe, > > This issue moving to 6.5, I donot know when the virtio-scsi support > block_resize for virtio-win component? there are existing 'RFE - Virtio-scsi > should support block_resize' bug for QEMU-KVM and kernel components, and > just in ON_QA and POST status. Just as i disuse with Paolo in IRC that want > to ask you whether need to open a RFE bug for virtio-win component for > tracing the progress ? > > Best wishes. > sluo I don't think we need to create another one bug. 824814 was a viostor (virtio blk) problem only, but now it is fixed and verified. The current bug was created to track Windows virtio-scsi driver problem, which is a separate issue, and not related to 824814. Kind regards, Vadim. should be fixed in build 58 http://download.devel.redhat.com/brewroot/work/tasks/6819/5586819/virtio-win-prewhql-0.1.zip (In reply to comment #6) > should be fixed in build 58 > http://download.devel.redhat.com/brewroot/work/tasks/6819/5586819/virtio-win- > prewhql-0.1.zip Failed to install virtio scsi driver in win2k8-32 guest ,Re-assigned this issue (In reply to comment #7) > (In reply to comment #6) > > should be fixed in build 58 > > http://download.devel.redhat.com/brewroot/work/tasks/6819/5586819/virtio-win- > > prewhql-0.1.zip > > Failed to install virtio scsi driver in win2k8-32 guest ,Re-assigned this > issue Test this issue on virtio-win-prewhql-58 with qcow2 image (guest NTFS format) Actual Results: After block_resize ,We still need manually rescan to detect new partition Based on above ,this issue does not be fixed already (In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #6) > > > should be fixed in build 58 > > > http://download.devel.redhat.com/brewroot/work/tasks/6819/5586819/virtio-win- > > > prewhql-0.1.zip > > > > Failed to install virtio scsi driver in win2k8-32 guest ,Re-assigned this > > issue > > Test this issue on virtio-win-prewhql-58 with qcow2 image (guest NTFS format) > > Actual Results: > After block_resize ,We still need manually rescan to detect new partition > > Based on above ,this issue does not be fixed already Hi Mike Do you mean that you cannot see changes in Disk Management dialog without rescan? But if you rescan, or close and then open the Disk Management dialog, you can see the changes without reboot. If so, it is not a bug, Disk Management cannot detect a volume size change event automatically. (In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > (In reply to comment #6) > > > > should be fixed in build 58 > > > > http://download.devel.redhat.com/brewroot/work/tasks/6819/5586819/virtio-win- > > > > prewhql-0.1.zip > > > > > > Failed to install virtio scsi driver in win2k8-32 guest ,Re-assigned this > > > issue > > > > Test this issue on virtio-win-prewhql-58 with qcow2 image (guest NTFS format) > > > > Actual Results: > > After block_resize ,We still need manually rescan to detect new partition > > > > Based on above ,this issue does not be fixed already > > Hi Mike > Do you mean that you cannot see changes in Disk Management dialog without > rescan? Yes . > But if you rescan, or close and then open the Disk Management dialog, you > can see the changes without reboot. If so, it is not a bug, Disk Management > cannot detect a volume size change event automatically. OK BTW Do we support to shrink a FAT format disk ? (In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #8) > > > (In reply to comment #7) > > > > (In reply to comment #6) > > > > > should be fixed in build 58 > > > > > http://download.devel.redhat.com/brewroot/work/tasks/6819/5586819/virtio-win- > > > > > prewhql-0.1.zip > > > > > > > > Failed to install virtio scsi driver in win2k8-32 guest ,Re-assigned this > > > > issue > > > > > > Test this issue on virtio-win-prewhql-58 with qcow2 image (guest NTFS format) > > > > > > Actual Results: > > > After block_resize ,We still need manually rescan to detect new partition > > > > > > Based on above ,this issue does not be fixed already > > > > Hi Mike > > Do you mean that you cannot see changes in Disk Management dialog without > > rescan? > Yes . > > But if you rescan, or close and then open the Disk Management dialog, you > > can see the changes without reboot. If so, it is not a bug, Disk Management > > cannot detect a volume size change event automatically. > OK > > BTW Do we support to shrink a FAT format disk ? Hi Mike, As I said I'm not sure about shrinking. I remember I checked it once ans it worked. But now it seems to be blocked in QEMU (I'm trying to shrink 64G volume) (qemu) info version 0.12.1(qemu-kvm-devel) (qemu) block_resize drive-scsi0-0-0 62G this feature or command is not currently supported (qemu) But enlarging a FAT formatted volume should work. Best regards, Vadim. (In reply to comment #11) > (In reply to comment #10) > > (In reply to comment #9) > > > (In reply to comment #8) > > > > (In reply to comment #7) > > > > > (In reply to comment #6) > > > > > > should be fixed in build 58 > > > > > > http://download.devel.redhat.com/brewroot/work/tasks/6819/5586819/virtio-win- > > > > > > prewhql-0.1.zip > > > > > > > > > > Failed to install virtio scsi driver in win2k8-32 guest ,Re-assigned this > > > > > issue > > > > > > > > Test this issue on virtio-win-prewhql-58 with qcow2 image (guest NTFS format) > > > > > > > > Actual Results: > > > > After block_resize ,We still need manually rescan to detect new partition > > > > > > > > Based on above ,this issue does not be fixed already > > > > > > Hi Mike > > > Do you mean that you cannot see changes in Disk Management dialog without > > > rescan? > > Yes . > > > But if you rescan, or close and then open the Disk Management dialog, you > > > can see the changes without reboot. If so, it is not a bug, Disk Management > > > cannot detect a volume size change event automatically. > > OK > > > > BTW Do we support to shrink a FAT format disk ? > > Hi Mike, > As I said I'm not sure about shrinking. I remember I checked it once ans it > worked. But now it seems to be blocked in QEMU (I'm trying to shrink 64G > volume) > > > (qemu) info version > 0.12.1(qemu-kvm-devel) > (qemu) block_resize drive-scsi0-0-0 62G > this feature or command is not currently supported > (qemu) > > But enlarging a FAT formatted volume should work. > > Best regards, > Vadim. Hi, Vadim you must use qcow2 format image which only support extending Raw format image support both extending and shrinking . I tried Raw disk w/o format it in the guest ,it shrinking successfully Raw disk format w/ NFTS ,it shriking successfully ,but It can not use until format it Raw disk format as FAT ,it shrink failed Mike (In reply to comment #12) > (In reply to comment #11) > > (In reply to comment #10) > > > (In reply to comment #9) > > > > (In reply to comment #8) > > > > > (In reply to comment #7) > > > > > > (In reply to comment #6) > > > > > > > should be fixed in build 58 > > > > > > > http://download.devel.redhat.com/brewroot/work/tasks/6819/5586819/virtio-win- > > > > > > > prewhql-0.1.zip > > > > > > > > > > > > Failed to install virtio scsi driver in win2k8-32 guest ,Re-assigned this > > > > > > issue > > > > > > > > > > Test this issue on virtio-win-prewhql-58 with qcow2 image (guest NTFS format) > > > > > > > > > > Actual Results: > > > > > After block_resize ,We still need manually rescan to detect new partition > > > > > > > > > > Based on above ,this issue does not be fixed already > > > > > > > > Hi Mike > > > > Do you mean that you cannot see changes in Disk Management dialog without > > > > rescan? > > > Yes . > > > > But if you rescan, or close and then open the Disk Management dialog, you > > > > can see the changes without reboot. If so, it is not a bug, Disk Management > > > > cannot detect a volume size change event automatically. > > > OK > > > > > > BTW Do we support to shrink a FAT format disk ? > > > > Hi Mike, > > As I said I'm not sure about shrinking. I remember I checked it once ans it > > worked. But now it seems to be blocked in QEMU (I'm trying to shrink 64G > > volume) > > > > > > (qemu) info version > > 0.12.1(qemu-kvm-devel) > > (qemu) block_resize drive-scsi0-0-0 62G > > this feature or command is not currently supported > > (qemu) > > > > But enlarging a FAT formatted volume should work. > > > > Best regards, > > Vadim. > > Hi, Vadim > you must use qcow2 format image which only support extending > Raw format image support both extending and shrinking . You must be right. It was raw. > I tried Raw disk w/o format it in the guest ,it shrinking successfully > Raw disk format w/ NFTS ,it shriking successfully ,but It can not use until > format it Try defrag and shrink the volume first and only resize the disk itself. Also, make that the volume size is not bigger than the new disk size. > Raw disk format as FAT ,it shrink failed > Is it a BSOD? What is the bugcheck code? > Mike (In reply to comment #13) > (In reply to comment #12) > > (In reply to comment #11) > > > (In reply to comment #10) > > > > (In reply to comment #9) > > > > > (In reply to comment #8) > > > > > > (In reply to comment #7) > > > > > > > (In reply to comment #6) > > > > > > > > should be fixed in build 58 > > > > > > > > http://download.devel.redhat.com/brewroot/work/tasks/6819/5586819/virtio-win- > > > > > > > > prewhql-0.1.zip > > > > > > > > > > > > > > Failed to install virtio scsi driver in win2k8-32 guest ,Re-assigned this > > > > > > > issue > > > > > > > > > > > > Test this issue on virtio-win-prewhql-58 with qcow2 image (guest NTFS format) > > > > > > > > > > > > Actual Results: > > > > > > After block_resize ,We still need manually rescan to detect new partition > > > > > > > > > > > > Based on above ,this issue does not be fixed already > > > > > > > > > > Hi Mike > > > > > Do you mean that you cannot see changes in Disk Management dialog without > > > > > rescan? > > > > Yes . > > > > > But if you rescan, or close and then open the Disk Management dialog, you > > > > > can see the changes without reboot. If so, it is not a bug, Disk Management > > > > > cannot detect a volume size change event automatically. > > > > OK > > > > > > > > BTW Do we support to shrink a FAT format disk ? > > > > > > Hi Mike, > > > As I said I'm not sure about shrinking. I remember I checked it once ans it > > > worked. But now it seems to be blocked in QEMU (I'm trying to shrink 64G > > > volume) > > > > > > > > > (qemu) info version > > > 0.12.1(qemu-kvm-devel) > > > (qemu) block_resize drive-scsi0-0-0 62G > > > this feature or command is not currently supported > > > (qemu) > > > > > > But enlarging a FAT formatted volume should work. > > > > > > Best regards, > > > Vadim. > > > > Hi, Vadim > > you must use qcow2 format image which only support extending > > Raw format image support both extending and shrinking . > > You must be right. It was raw. > > > I tried Raw disk w/o format it in the guest ,it shrinking successfully > > Raw disk format w/ NFTS ,it shriking successfully ,but It can not use until > > format it > Try defrag and shrink the volume first and only resize the disk itself. > Also, make that the volume size is not bigger than the new disk size. > > Raw disk format as FAT ,it shrink failed > > > > Is it a BSOD? What is the bugcheck code? No. it is a 4GB data image with FAT format ,I shrink it to 3GB size . Tried qemu-img info test.img ,it shows the disk size is 3GB, but in the guest E:\(which is the partition of data image_ still shows 4GB), I copy 3.6GB file to E:\ when it reached 3GB ,in qemu-kvm monitor ,it should drive-ide-1-0 i/o error ,but guest still in running status (due to I did not add werror&rerror option),and at last I can finished the copying ,it shows the used size is 3.6GB and free size is 400MB > > > Mike QE, We suspect that FAT does not support resise. Can you check, Postponing to 6.6 (In reply to Ronen Hod from comment #15) > QE, > We suspect that FAT does not support resise. Can you check, > Postponing to 6.6 Hi,Ronen it is supported . Retest it on virtio-win-prewhql-66 with Raw format ,format it to FAT format then enlarge to 6GB in qemu monitor .We can see 2GB Unallocated Disk size in disk manager. Tried to shrink disks to 2GB ,We can see the disk shrinked to 2GB in disk manager but the disk can *not* format Based on above there is some bugs in disk shrinking.I prefer to close this bug as fixed and report new bugs for the disk shrinking Based on above ,Move status to VERIFIED. moving to 6.6 since we still have unresolved build problem. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1729.html |