Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 570162

Summary: Large virtual disk (3TB) corrupt via VirtIO but works via IDE
Product: Red Hat Enterprise Linux 5 Reporter: David Herselman <bbs2web>
Component: virtio-winAssignee: Yvugenfi <yvugenfi>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 5.4CC: gasmith, james.brown, knoel, llim, lmiksik, plyons, qzhang, riel, syeghiay, tao, ykaul
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-17 13:22:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 663588    

Description David Herselman 2010-03-03 14:10:29 UTC
Description of problem:
RedHat Enterprise Linux 5.4 guest previously using Xen hypervisor.
Second virtual disk is relatively large (3TB) but worked without
problems using Xen GPL PV drivers.

Since changing to KVM the 3TB disc appears unformatted and/or partitioned
to Windows 2008 32bit guest although it works without problems when
attaching the discs in IDE emulation mode.


Version-Release number of selected component (if applicable):
  kernel-2.6.18-164.11.1.el5
  kvm-83-105.el5_4.27
  virtio-win-1.0.0-7.39539.el5
  Guest: Windows 2008 32bit
         VirtIO Block Device Driver v1.0.0.31351 (Microsoft signed)

How reproducible:
  Also reported in KVM forum at Source Forge:
  https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2914397&group_id=180599

Steps to Reproduce:
  1. Setup Windows guest with VirtIO on small primary drive (vda)
  2. Switch guest to IDE mode (we install using VirtIO to get the drivers
     in to Windows)
  3. Attach secondary large disk of 3TB
  4. Format the disk
  5. Switch emulation back to VirtIO, small boot drive should be fine but
     large drive prompts you to initialise it when going in to disk manager
  
Actual results:
  1. Perhaps a LBA48 calculation problem when using VirtIO

Expected results:
  1. Should see the drive the same way IDE emulation does with the speed
     benefits of using VirtIO

Additional info:
  Only other reported case also mentioned running Windows 2008 guest.

Comment 4 David Herselman 2010-03-13 14:38:26 UTC
Flags? Do you perhaps want the command line command?

Managed via libvirt, herewith 'ps auxw | grep data':
/usr/libexec/qemu-kvm -S -M pc -m 4096 -smp 4 -name data -uuid 1f3616c6-f681-565b-1b25-7c5ff50a452c -no-kvm-pit-reinjection -monitor pty -pidfile /var/run/libvirt/qemu//data.pid -localtime -boot dc -drive file=/dev/vg_xen/data-kvm,if=virtio,index=0,boot=on -drive file=/dev/sdc,if=virtio,index=1 -net nic,macaddr=00:16:3e:06:00:02,vlan=0,model=virtio -net tap,fd=15,script=,vlan=0,ifname=vnet0 -serial none -parallel none -usb -usbdevice tablet -vnc 0.0.0.0:2,password

/etc/libvirt/qemu/data.xml:
<domain type='kvm'>
  <name>data</name>
  <uuid>1f3616c6-f681-565b-1b25-7c5ff50a452c</uuid>
  <memory>4194304</memory>
  <currentMemory>4194304</currentMemory>
  <vcpu>4</vcpu>
  <os>
    <type arch='x86_64' machine='pc'>hvm</type>
    <boot dev='cdrom'/>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <clock offset='localtime'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <disk type='block' device='disk'>
      <source dev='/dev/vg_kvm/data'/>
      <target dev='vda' bus='virtio'/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/sdc'/>
      <target dev='vdb' bus='virtio'/>
    </disk>
    <interface type='bridge'>
      <mac address='00:16:3e:06:00:02'/>
      <source bridge='eth0'/>
      <model type='virtio'/>
    </interface>
    <input type='tablet' bus='usb'/>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='5902' autoport='no' listen='0.0.0.0' passwd='*******'/>
  </devices>
</domain>

Comment 8 David Herselman 2010-03-20 07:13:39 UTC
We have an 'official' RedHat support case logged (626713), via Dell, which has not received an update with regards to there being newer VirtIO drivers which fix the problem.

Any chance of getting access to 32bit and 64bit signed Microsoft drivers for Windows 2008 to fix this problem?

Comment 9 Gary Smith 2010-03-22 10:07:29 UTC
Hi David


Just to let you know that this problem is being worked via the Issue Tracker case opened via Dell and in this Bugzilla simultaneously.

I have provided an update to Conor @ Dell confirm the current status and I will update him when I can confirm exactly the release vehicle and schedule for this fix.


Regards, Gary

Comment 13 David Herselman 2010-03-24 19:21:29 UTC
Dell inform me that RedHat only provide VirtIO drivers as part of major releases? I'm supposed to wait for RHEL5.5?!?!

We specifically purchased RedHat Enterprise Linux from RedHat, via Dell, to ensure we wouldn't have problems like this.

ie: Being told that RedHat have newer Microsoft signed drivers, which are
    confirmed to fix the problem we are experiencing, and then not letting
    us have them is quite simply ridiculous!

Comment 18 Qunfang Zhang 2010-11-26 09:08:47 UTC
Reproduced in virtio-win-1.0.0-7.39539.el5, and verified pass in virtio-win-1.0.0-13.45801.el5.

Steps: (as bug description)
  1. Install a Windows guest with VirtIO on small primary drive (vda)
  2. Switch guest to IDE mode (we install using VirtIO to get the drivers
     in to Windows)
  3. Attach secondary large disk of 3TB
  4. Format the disk
  5. Switch emulation back to VirtIO.

Result:
In old version:
The small boot drive (system disk) works fine but large drive prompts you to initialise it when going in to disk manager. If I click OK to initialise the disk, there's a new window pop up and prompts "function error".

In the latest version 1.0.0-13.45801.el5:
After step 5, guest can boot up and the large disk works fine, I can do read and write operation on it.

According to above, I will change the status to VERIFIED.

Comment 26 Yvugenfi@redhat.com 2012-07-17 08:21:53 UTC
Why it is reopen?