Bug 751709 - Virtio disk could not be used after disable/enable driver
Summary: Virtio disk could not be used after disable/enable driver
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win
Version: 6.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-07 09:14 UTC by Mike Cao
Modified: 2013-01-10 00:30 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-09 09:10:03 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Mike Cao 2011-11-07 09:14:53 UTC
Description of problem:


Version-Release number of selected component (if applicable):
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.209.el6.x86_64
[root@test Desktop]# rpm -q virtio-win
virtio-win-1.4.0-1.el6.noarch

How reproducible:
2/2

Steps to Reproduce:
1.start VM with 2 virtio disks (one is system disk ,another is data disk with NTFS format)
2.in the device manager ,right click Redhat VirtIO SCSI controller--->disabled
3.in the device manager ,right click Redhat VirtIO SCSI controller--->enabled
4.in the Computer managment ,format this disk,or change drive letter
  
Actual results:
after step2 ,the disk was missed in "My computer" 
after step3, the disk still can not show in "My computer"
after step4, the operation could not be completed.

Expected results:
after step3, the disk should show in "My computer"
after step4, the operation should be completed.

Additional info:
CLI:
CLI:/usr/libexec/qemu-kvm -M rhel6.2.0 -usb -device usb-tablet -cpu  cpu64-rhel6,+x2apic -enable-kvm -m 4G -smp 2 -name win2k3_64 -uuid  411e21b1-1740-4117-8328-c8ae7c94068b -monitor stdio -rtc base=localtime,driftfix=slew -boot c -device  virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4 -drive  file=/home/backup/test/win2003_32,if=none,id=drive-virtio-disk0,format=raw,serial=83-befe-af9a2dbb0177,cache=none,werror=stop,rerror=stop,aio=threads  -device virtio-blk-pci,bus=pci.0,addr=0x9,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,id=hostnet0 -device  e1000,netdev=hostnet0,id=net0,mac=00:1a:4a:42:0b:01,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/win7_64.com.redhat.rhevm.vdsm,server,nowait  -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm  -chardev spicevmc,id=charchannel1,name=vdagent -device  virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0  -usb -spice port=5910,disable-ticketing -k en-us -vga qxl  -device virtio-balloon-pci,id=balloon0 -qmp tcp:0:4445,server,nowait  -drive  file=~/Desktop/test.img,if=none,id=drive-virtio-disk1,format=qcow2,serial=83-befe-af9a2dbb0179,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-virtio-disk1,id=virtio-disk1

Comment 2 Mike Cao 2011-11-10 08:25:27 UTC
This issue happened with win2k3_32 bit guest ,
Tried win2k8_64 bit guest ,does not hit this issue .

Mike

Comment 3 Vadim Rozenfeld 2011-11-27 14:11:52 UTC
Hi Mike,

Can you please post output from "systeminfo"?
Does it happen on a freshly installed VM?

TIA,
Vadim.

Comment 4 Mike Cao 2011-12-09 09:10:03 UTC
(In reply to comment #3)
> Hi Mike,
> 
> Can you please post output from "systeminfo"?
> Does it happen on a freshly installed VM?
> 
> TIA,
> Vadim.

Hi, Vadim

I reinstall a win2k3_32 bit guest and can not reproduce this issue .close as not a bug ,Sorry for any in-continence .

Best Regards,
Mike


Note You need to log in before you can comment on or make changes to this bug.