This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 769136 - [virtio-win][viostor]System disk cannot boot up with "virtio" on windows 2k3-64 guest
[virtio-win][viostor]System disk cannot boot up with "virtio" on windows 2k3...
Status: ASSIGNED
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win (Show other bugs)
6.3
Unspecified Unspecified
unspecified Severity high
: rc
: ---
Assigned To: Vadim Rozenfeld
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-12-19 21:19 EST by dengmin
Modified: 2016-02-18 02:08 EST (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
guest stuck at boot stage (15.47 KB, image/png)
2015-01-29 02:51 EST, lijin
no flags Details
upstream bios screenshot (15.97 KB, image/png)
2015-02-16 03:39 EST, lijin
no flags Details
rhel bios screenshot (15.00 KB, image/png)
2015-02-16 03:40 EST, lijin
no flags Details
F12 boot list (17.78 KB, image/png)
2015-02-16 21:39 EST, lijin
no flags Details

  None (edit)
Description dengmin 2011-12-19 21:19:00 EST
Description of problem:
Install viostor driver to four data disks of windows 2k3-64 guest which has one ide-drive system disk as well.Then shutdown the guest and changing the ide-drive to "virtio".The guest cannot boot up successfully.the screen always show "booting from Hard Disk ..."


Version-Release number of selected component (if applicable):
kernel-2.6.32-220.1.1.el6.x86_64
seabios-0.6.1.2-4.el6.x86_64 (QE need to run whql testing via this version)
qemu-kvm-0.12.1.2-2.211.el6.x86_64
virtio-win-prewhql-0.1-20
How reproducible:


Steps to Reproduce:
1.install a guest with ide-drive
  you can refer to the screenshot for the ide driver version
2.Boot up with following CLI
  /usr/libexec/qemu-kvm -m 2G -smp 4 -cpu cpu64-rhel6,+x2apic,family=0xf -usb -device usb-tablet -drive file=win2k3-64-blk.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device rtl8139,netdev=hostnet0,mac=00:13:45:14:F5:01 -uuid 1b3ac854-3eec-4d92-96cd-a5d64db12102 -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2k3-64-blk,server,nowait -mon chardev=111a,mode=readline -spice port=5930,disable-ticketing -vga qxl -rtc base=localtime,clock=host,driftfix=slew -drive file=disk1.raw,if=none,format=raw,id=drive-virtio-data1,werror=stop,rerror=stop -device virtio-blk-pci,id=virtio-data1,drive=drive-virtio-data1 -drive file=disk2.raw,if=none,format=raw,id=drive-virtio-data2,werror=stop,rerror=stop -device virtio-blk-pci,id=virtio-data2,drive=drive-virtio-data2 -drive file=disk3.raw,if=none,format=raw,id=drive-virtio-data3,werror=stop,rerror=stop -device virtio-blk-pci,id=virtio-data3,drive=drive-virtio-data3 -drive file=disk4.raw,if=none,format=raw,id=drive-virtio-data4,werror=stop,rerror=stop -device virtio-blk-pci,id=virtio-data4,drive=drive-virtio-data4

3.install virtio-win-prewhql-0.1-20 to four data disk from Device Manager update driver ...

4.change step2 system data driver type from "ide" to "virtio"

5.boot up guest again
  
Actual results:
The guest cannot boot up with virtio system disk, if change back to "ide" guest works well,the image should be fine.

Expected results:
Both "virtio" and "ide" system disk should be fine for win2k3 64 guest.

Additional info:
Reproduced the issue on more than one host and provide the ide driver version screenshot,please see the attachment in the bug
Comment 2 dengmin 2011-12-19 21:23:29 EST
By the way,the issue cannot be found on windows 2k3 32 bits.thank you,any issues please let me know.
Comment 4 Yan Vugenfirer 2011-12-20 05:43:51 EST
As far as I know you cannot change boot device on the fly (after installation) on Windows 2003. 

Is this a real requirement that the boot disk type will be changed after installation?
Comment 5 dengmin 2011-12-20 21:55:30 EST
(In reply to comment #4)
> As far as I know you cannot change boot device on the fly (after installation)
> on Windows 2003. 
> 
> Is this a real requirement that the boot disk type will be changed after
> installation?

Hi Vadim,

   We had better fix the issue if possible.If not,We have to re-install&Update OS via a floppy(windows 2003 and xp).As we all know,there is no any floppy or iso in prewhql package.We have to make one by ourselves and we cannot ensure the installation to be success every time with the floppy either.
   Even if developer would like to provide us floppy every time,it will take us much time to install&update our OS before whql tesing.Actually,we prepare clean 8 OS for us to install drivers before the whql testing,Only by this way can we save time for whql,we just hit the issue on one OS at this time.If we hit the issue on all the OS,it implies we have to re-install&Update all the OS.The process will be effected severely.
  Jump to a conclusion,could you please double check the issues ? thank you very much.Any issues feel free to let me know.

Thanks,
Min Deng
Comment 6 Vadim Rozenfeld 2012-02-13 16:32:36 EST
I was able to boot my W2K3-64 VM after switching from ide to virtio, and
adding "boot=on" parameter. However my BIOS was pretty old 
(version 0.5.0-2009128_212336...). 
Could you please try it with a more recent BIOS?

best regards,
Vadim.
Comment 7 Ronen Hod 2012-03-13 11:52:04 EDT
Too late for 6.3, we are busy with blockers. Postponed.
Comment 8 Vadim Rozenfeld 2012-06-19 14:07:30 EDT
Hi Min,

Could you please re-check this issue with our latest, MS-signed drivers?

Thank you,
Vadim.
Comment 11 Ronen Hod 2012-07-10 05:12:25 EDT
Min / QE,

Can you please recheck with build30.

Thanks, Ronen.
Comment 12 dengmin 2012-07-11 04:31:48 EDT
(In reply to comment #11)
> Min / QE,
> 
> Can you please recheck with build30.
> 
> Thanks, Ronen.

Hi Ronen,

   It didn't work for me via build 30 and it showed me a black screen with "Booting from Hard disk" while changing system disk from ide to virtio. 
   I used the same CLI to step 2 of Description.

Thanks,
Min
Comment 18 Ronen Hod 2014-08-21 10:17:47 EDT
Removing the Testblocker and blocker flag, as apparently, we survive without it already 3 years.
Postponed to 6.7, since Vadim did not give up yet.
Comment 20 Vadim Rozenfeld 2015-01-15 23:23:09 EST
Hi Min,
Could you please confirm that it still reproducible with the latest drivers
on RHEL 6.7?

Thanks,
Vadim.
Comment 21 lijin 2015-01-20 01:22:41 EST
still CAN reproduce this issue with virtio-win-prewhql-100,guest stuck at "booting from Hard Disk ..." after change system disk from ide to virtio.
steps same with comment#0

package info:
with virtio-win-prewhql-100
kernel-2.6.32-524.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.451.el6.x86_64
spice-server-0.12.4-11.el6.x86_64
seabios-0.6.1.2-28.el6.x86_64
Comment 22 Vadim Rozenfeld 2015-01-28 05:00:48 EST
(In reply to lijin from comment #21)
> still CAN reproduce this issue with virtio-win-prewhql-100,guest stuck at
> "booting from Hard Disk ..." after change system disk from ide to virtio.
> steps same with comment#0
> 
> package info:
> with virtio-win-prewhql-100
> kernel-2.6.32-524.el6.x86_64
> qemu-kvm-rhev-0.12.1.2-2.451.el6.x86_64
> spice-server-0.12.4-11.el6.x86_64
> seabios-0.6.1.2-28.el6.x86_64

Unfortunately, I don't have rhel6 system at the moment, and cannot reproduce the problem on rhel 7 (qemu 1.5.3). It's the reason why I will ask you to do the following things:
- can you post the exact CLI when the problem is happening (step #5)?
- can you post "info pci" output (steps #2 and #5)?
- can you post screenshot with "booting from Hard Disk ..." image?
- Does the number of virtio-blk devices matter? Or the problem is reproducible with any number of disks? 
- Can you try reproducing the problem on rhel 7 host?
- Do you use a freshly installed VM or template? 
- What kind of WS2K3 it is - Standard/Enterprise, SP1/SP2? Did you install 
recommended Windows Updates before step #5?

Thanks,
Vadim.
Comment 24 lijin 2015-01-29 02:48:07 EST
(In reply to Vadim Rozenfeld from comment #22)
> - can you post the exact CLI when the problem is happening (step #5)?
will post the command in next comment
> - can you post "info pci" output (steps #2 and #5)?
will post the info in next comment

> - can you post screenshot with "booting from Hard Disk ..." image?
please check the attachment

> - Does the number of virtio-blk devices matter? Or the problem is
> reproducible with any number of disks? 
the number of virtio-blk devices does NOT matter,just make sure you have at lease one virtio-blk disk

> - Can you try reproducing the problem on rhel 7 host?
try on rhel7.1 host,still can NOT reproduce this issue,guest can boot up correctly after change the system disk from ide to virtio-blk
package info:
virtio-win-prewhql-100
qemu-kvm-rhev-2.1.2-20.el7.x86_64
kernel-3.10.0-223.el7.x86_64
seabios-1.7.5-5.el7.x86_64
spice-server-0.12.4-9.el7.x86_64

> - Do you use a freshly installed VM or template? 
I use freshly installed VM

> - What kind of WS2K3 it is - Standard/Enterprise, SP1/SP2? Did you install 
> recommended Windows Updates before step #5?
I use the enterprise sp2 version and install the update,following are the iso link:
http://tree.englab.nay.redhat.com/pub/windows/win2003/x64/en_win_srv_2003_r2_enterprise_x64_with_sp2_cd1_X13-06188.iso
http://tree.englab.nay.redhat.com/pub/windows/win2003/x64/en_win_srv_2003_r2_enterprise_x64_with_sp2_cd2_X13-68588.iso
Comment 25 lijin 2015-01-29 02:49:27 EST
here is the detailed steps:
1.qemu-img create win2k3-64-blk.raw 40G
2.install win2k3-64 guest with following command:
/usr/libexec/qemu-kvm -m 2G -smp 4 -cpu cpu64-rhel6,+x2apic,family=0xf -usb -device usb-tablet -drive file=win2k3-64-blk.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device rtl8139,netdev=hostnet0,mac=00:13:45:14:F5:01 -uuid 1b3ac854-3eec-4d92-96cd-a5d64db12102 -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2k3-64-blk,server,nowait -mon chardev=111a,mode=readline -spice port=5930,disable-ticketing -vga qxl -rtc base=localtime,clock=host,driftfix=slew -drive file=disk1.raw,if=none,format=raw,id=drive-virtio-data1,werror=stop,rerror=stop -device virtio-blk-pci,id=virtio-data1,drive=drive-virtio-data1 -drive file=disk2.raw,if=none,format=raw,id=drive-virtio-data2,werror=stop,rerror=stop -device virtio-blk-pci,id=virtio-data2,drive=drive-virtio-data2 -drive file=disk3.raw,if=none,format=raw,id=drive-virtio-data3,werror=stop,rerror=stop -device virtio-blk-pci,id=virtio-data3,drive=drive-virtio-data3 -drive file=disk4.raw,if=none,format=raw,id=drive-virtio-data4,werror=stop,rerror=stop -device virtio-blk-pci,id=virtio-data4,drive=drive-virtio-data4 -boot menu=on -cdrom en_win_srv_2003_r2_enterprise_x64_with_sp2_cd1_X13-06188.iso -drive file=en_win_srv_2003_r2_enterprise_x64_with_sp2_cd2_X13-68588.iso,format=raw,if=none,id=drive-ide0-0-1,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-1,id=ide0-0-1,bus=ide.0,unit=1 -monitor stdio
3.(qemu) info pci
  Bus  0, device   0, function 0:
    Host bridge: PCI device 8086:1237
      id ""
  Bus  0, device   1, function 0:
    ISA bridge: PCI device 8086:7000
      id ""
  Bus  0, device   1, function 1:
    IDE controller: PCI device 8086:7010
      BAR4: I/O at 0xc000 [0xc00f].
      id ""
  Bus  0, device   1, function 2:
    USB controller: PCI device 8086:7020
      IRQ 10.
      BAR4: I/O at 0xc020 [0xc03f].
      id ""
  Bus  0, device   1, function 3:
    Bridge: PCI device 8086:7113
      IRQ 9.
      id ""
  Bus  0, device   2, function 0:
    VGA controller: PCI device 1b36:0100
      IRQ 10.
      BAR0: 32 bit memory at 0xf0000000 [0xf3ffffff].
      BAR1: 32 bit memory at 0xffffffffffffffff [0x03fffffe].
      BAR2: 32 bit memory at 0xf4000000 [0xf4001fff].
      BAR3: I/O at 0xc040 [0xc05f].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe].
      id ""
  Bus  0, device   3, function 0:
    Ethernet controller: PCI device 10ec:8139
      IRQ 11.
      BAR0: I/O at 0xc100 [0xc1ff].
      BAR1: 32 bit memory at 0xf4020000 [0xf40200ff].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe].
      id ""
  Bus  0, device   4, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 11.
      BAR0: I/O at 0xc200 [0xc23f].
      BAR1: 32 bit memory at 0xf4040000 [0xf4040fff].
      id "virtio-data1"
  Bus  0, device   5, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 10.
      BAR0: I/O at 0xc240 [0xc27f].
      BAR1: 32 bit memory at 0xf4041000 [0xf4041fff].
      id "virtio-data2"
  Bus  0, device   6, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 10.
      BAR0: I/O at 0xc280 [0xc2bf].
      BAR1: 32 bit memory at 0xf4042000 [0xf4042fff].
      id "virtio-data3"
  Bus  0, device   7, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 11.
      BAR0: I/O at 0xc2c0 [0xc2ff].
      BAR1: 32 bit memory at 0xf4043000 [0xf4043fff].
      id "virtio-data4"
4.install windows update
5.install virtio-win-prewhql-100 viostor driver to four data disk from Device Manager
6.shutdown guest and change the system data driver type from "ide" to "virtio-blk-pci",then boot up the gues again with:
/usr/libexec/qemu-kvm -m 2G -smp 4 -cpu cpu64-rhel6,+x2apic,family=0xf -usb -device usb-tablet -drive file=win2k3-64-blk.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device virtio-blk-pci,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device rtl8139,netdev=hostnet0,mac=00:13:45:14:F5:01 -uuid 1b3ac854-3eec-4d92-96cd-a5d64db12102 -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2k3-64-blk,server,nowait -mon chardev=111a,mode=readline -spice port=5930,disable-ticketing -vga qxl -rtc base=localtime,clock=host,driftfix=slew -drive file=disk1.raw,if=none,format=raw,id=drive-virtio-data1,werror=stop,rerror=stop -device virtio-blk-pci,id=virtio-data1,drive=drive-virtio-data1 -drive file=disk2.raw,if=none,format=raw,id=drive-virtio-data2,werror=stop,rerror=stop -device virtio-blk-pci,id=virtio-data2,drive=drive-virtio-data2 -drive file=disk3.raw,if=none,format=raw,id=drive-virtio-data3,werror=stop,rerror=stop -device virtio-blk-pci,id=virtio-data3,drive=drive-virtio-data3 -drive file=disk4.raw,if=none,format=raw,id=drive-virtio-data4,werror=stop,rerror=stop -device virtio-blk-pci,id=virtio-data4,drive=drive-virtio-data4 -boot menu=on -cdrom en_win_srv_2003_r2_enterprise_x64_with_sp2_cd1_X13-06188.iso -drive file=en_win_srv_2003_r2_enterprise_x64_with_sp2_cd2_X13-68588.iso,format=raw,if=none,id=drive-ide0-0-1,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-1,id=ide0-0-1,bus=ide.0,unit=1 -monitor stdio
7.(qemu) info pci
  Bus  0, device   0, function 0:
    Host bridge: PCI device 8086:1237
      id ""
  Bus  0, device   1, function 0:
    ISA bridge: PCI device 8086:7000
      id ""
  Bus  0, device   1, function 1:
    IDE controller: PCI device 8086:7010
      BAR4: I/O at 0xc000 [0xc00f].
      id ""
  Bus  0, device   1, function 2:
    USB controller: PCI device 8086:7020
      IRQ 11.
      BAR4: I/O at 0xc020 [0xc03f].
      id ""
  Bus  0, device   1, function 3:
    Bridge: PCI device 8086:7113
      IRQ 9.
      id ""
  Bus  0, device   2, function 0:
    VGA controller: PCI device 1b36:0100
      IRQ 10.
      BAR0: 32 bit memory at 0xf0000000 [0xf3ffffff].
      BAR1: 32 bit memory at 0xffffffffffffffff [0x03fffffe].
      BAR2: 32 bit memory at 0xf4000000 [0xf4001fff].
      BAR3: I/O at 0xc040 [0xc05f].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe].
      id ""
  Bus  0, device   3, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 11.
      BAR0: I/O at 0xc080 [0xc0bf].
      BAR1: 32 bit memory at 0xf4020000 [0xf4020fff].
      id "ide0-0-0"
  Bus  0, device   4, function 0:
    Ethernet controller: PCI device 10ec:8139
      IRQ 11.
      BAR0: I/O at 0xc100 [0xc1ff].
      BAR1: 32 bit memory at 0xf4021000 [0xf40210ff].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe].
      id ""
  Bus  0, device   5, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 10.
      BAR0: I/O at 0xc200 [0xc23f].
      BAR1: 32 bit memory at 0xf4040000 [0xf4040fff].
      id "virtio-data1"
  Bus  0, device   6, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 10.
      BAR0: I/O at 0xc240 [0xc27f].
      BAR1: 32 bit memory at 0xf4041000 [0xf4041fff].
      id "virtio-data2"
  Bus  0, device   7, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 11.
      BAR0: I/O at 0xc280 [0xc2bf].
      BAR1: 32 bit memory at 0xf4042000 [0xf4042fff].
      id "virtio-data3"
  Bus  0, device   8, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 11.
      BAR0: I/O at 0xc2c0 [0xc2ff].
      BAR1: 32 bit memory at 0xf4043000 [0xf4043fff].
      id "virtio-data4"
Comment 26 lijin 2015-01-29 02:51:41 EST
Created attachment 985451 [details]
guest stuck at boot stage
Comment 27 Vadim Rozenfeld 2015-02-15 00:32:18 EST
Thanks,
Can reproduce the problem on qemu-kvm-rhev-0.12.1.2-2.451.el6.x86_64.
However, the problem disappears after switching to rhel7 or upstream bios.
Can you try adding "-bios xxx/bios.bin" option to the qemu command line,
where xxx points to rhel7 or upstream seabios location?

Cheers,
Vadim.
Comment 28 lijin 2015-02-16 02:00:29 EST
still hit this issue with upstream and rhel7 seabios.

package info: 
qemu-kvm-rhev-0.12.1.2-2.451.el6.x86_64
kernel-2.6.32-504.el6.x86_64
spice-server-0.12.4-11.el6.x86_64
virtio-win-prewhql-100
seabios:rel-1.7.5.2
Comment 29 Vadim Rozenfeld 2015-02-16 03:31:20 EST
Can you please post the guest stuck image once again (just like in #26), and
output from "info qtree" command?

Thanks.
Vadim.
Comment 30 lijin 2015-02-16 03:39:21 EST
Created attachment 992072 [details]
upstream bios screenshot
Comment 31 lijin 2015-02-16 03:40:05 EST
Created attachment 992074 [details]
rhel bios screenshot

(qemu) info qtree
bus: main-system-bus
  type System
  dev: i440FX-pcihost, id ""
    bus: pci.0
      type PCI
      dev: virtio-blk-pci, id "virtio-data1"
        dev-prop: class = 0x100
        dev-prop: drive = drive-virtio-data1
        dev-prop: logical_block_size = 512
        dev-prop: physical_block_size = 512
        dev-prop: min_io_size = 0
        dev-prop: opt_io_size = 0
        dev-prop: bootindex = -1
        dev-prop: discard_granularity = 0
        dev-prop: serial = <null>
        dev-prop: ioeventfd = on
        dev-prop: x-data-plane = off
        dev-prop: vectors = 2
        dev-prop: indirect_desc = on
        dev-prop: event_idx = on
        dev-prop: scsi = on
        bus-prop: addr = 05.0
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = off
        class SCSI controller, addr 00:05.0, pci id 1af4:1001 (sub 1af4:0002)
        bar 0: i/o at 0xc140 [0xc17f]
        bar 1: mem at 0xfc024000 [0xfc024fff]
      dev: rtl8139, id ""
        dev-prop: mac = 00:13:45:14:f5:01
        dev-prop: vlan = <null>
        dev-prop: netdev = hostnet0
        dev-prop: bootindex = -1
        bus-prop: addr = 04.0
        bus-prop: romfile = "pxe-rtl8139.bin"
        bus-prop: rombar = 1
        bus-prop: multifunction = off
        class Ethernet controller, addr 00:04.0, pci id 10ec:8139 (sub 1af4:1100)
        bar 0: i/o at 0xc000 [0xc0ff]
        bar 1: mem at 0xfc023000 [0xfc0230ff]
        bar 6: mem at 0xffffffffffffffff [0xfffe]
      dev: virtio-blk-pci, id "ide0-0-0"
        dev-prop: class = 0x100
        dev-prop: drive = drive-ide0-0-0
        dev-prop: logical_block_size = 512
        dev-prop: physical_block_size = 512
        dev-prop: min_io_size = 0
        dev-prop: opt_io_size = 0
        dev-prop: bootindex = 1
        dev-prop: discard_granularity = 0
        dev-prop: serial = <null>
        dev-prop: ioeventfd = on
        dev-prop: x-data-plane = off
        dev-prop: vectors = 2
        dev-prop: indirect_desc = on
        dev-prop: event_idx = on
        dev-prop: scsi = on
        bus-prop: addr = 03.0
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = off
        class SCSI controller, addr 00:03.0, pci id 1af4:1001 (sub 1af4:0002)
        bar 0: i/o at 0xc100 [0xc13f]
        bar 1: mem at 0xfc022000 [0xfc022fff]
      dev: PIIX4_PM, id ""
        dev-prop: smb_io_base = 45312
        dev-prop: disable_s3 = 1
        dev-prop: disable_s4 = 1
        dev-prop: s4_val = 2
        bus-prop: addr = 01.3
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = off
        class Bridge, addr 00:01.3, pci id 8086:7113 (sub 1af4:1100)
      dev: piix3-usb-uhci, id ""
        dev-prop: masterbus = <null>
        dev-prop: firstport = 0
        bus-prop: addr = 01.2
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = off
        class USB controller, addr 00:01.2, pci id 8086:7020 (sub 1af4:1100)
        bar 4: i/o at 0xc180 [0xc19f]
        bus: usb.0
          type USB
          dev: usb-tablet, id ""
            dev-prop: migrate = 1
            bus-prop: port = <null>
            bus-prop: create_unique_serial = 1
            bus-prop: msos-desc = on
            addr 0.1, port 1, speed 12, name QEMU USB Tablet, attached
      dev: piix3-ide, id ""
        bus-prop: addr = 01.1
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = off
        class IDE controller, addr 00:01.1, pci id 8086:7010 (sub 1af4:1100)
        bar 4: i/o at 0xc1c0 [0xc1cf]
        bus: ide.1
          type IDE
          dev: ide-drive, id ""
            dev-prop: unit = 0
            dev-prop: drive = ide1-cd0
            dev-prop: logical_block_size = 512
            dev-prop: physical_block_size = 512
            dev-prop: min_io_size = 0
            dev-prop: opt_io_size = 0
            dev-prop: bootindex = -1
            dev-prop: discard_granularity = 0
            dev-prop: ver = <null>
            dev-prop: wwn = 0x0
        bus: ide.0
          type IDE
      dev: qxl-vga, id ""
        dev-prop: ram_size = 67108864
        dev-prop: vram_size = 67108864
        dev-prop: revision = 4
        dev-prop: debug = 0
        dev-prop: guestdebug = 0
        dev-prop: cmdlog = 0
        bus-prop: addr = 02.0
        bus-prop: romfile = "vgabios-qxl.bin"
        bus-prop: rombar = 1
        bus-prop: multifunction = off
        class VGA controller, addr 00:02.0, pci id 1b36:0100 (sub 1af4:1100)
        bar 0: mem at 0xf4000000 [0xf7ffffff]
        bar 1: mem at 0xf8000000 [0xfbffffff]
        bar 2: mem at 0xfc020000 [0xfc021fff]
        bar 3: i/o at 0xc1a0 [0xc1bf]
        bar 6: mem at 0xffffffffffffffff [0xfffe]
      dev: PIIX3, id ""
        bus-prop: addr = 01.0
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = on
        class ISA bridge, addr 00:01.0, pci id 8086:7000 (sub 1af4:1100)
        bus: isa.0
          type ISA
          dev: isa-fdc, id ""
            dev-prop: driveA = floppy0
            dev-prop: driveB = <null>
            dev-prop: bootindexA = -1
            dev-prop: bootindexB = -1
            dev-prop: migrate_dir = 1
            isa irq 6
          dev: i8042, id ""
            isa irqs 1,12
          dev: isa-parallel, id ""
            dev-prop: index = 0
            dev-prop: iobase = 0x378
            dev-prop: irq = 7
            dev-prop: chardev = parallel0
            isa irq 7
          dev: isa-serial, id ""
            dev-prop: index = 0
            dev-prop: iobase = 0x3f8
            dev-prop: irq = 4
            dev-prop: chardev = serial0
            dev-prop: wakeup = 0
            isa irq 4
          dev: mc146818rtc, id ""
            dev-prop: base_year = 2000
            isa irq 8
      dev: i440FX, id ""
        bus-prop: addr = 00.0
        bus-prop: romfile = <null>
        bus-prop: rombar = 1
        bus-prop: multifunction = off
        class Host bridge, addr 00:00.0, pci id 8086:1237 (sub 1af4:1100)
Comment 32 Vadim Rozenfeld 2015-02-16 06:01:13 EST
(In reply to lijin from comment #31)
> Created attachment 992074 [details]
> rhel bios screenshot

What happens if you hit F12. Do you see the list of bootable devices with "Virtio Disk PCI:0:3" as one of the options? Can you try booting from this device?

Thanks,
Vadim.
Comment 33 lijin 2015-02-16 21:39:19 EST
Created attachment 992460 [details]
F12 boot list

(In reply to Vadim Rozenfeld from comment #32)
> (In reply to lijin from comment #31)
> > Created attachment 992074 [details]
> > rhel bios screenshot
> 
> What happens if you hit F12. Do you see the list of bootable devices with
> "Virtio Disk PCI:0:3" as one of the options? 
  Yes,it's the first option of the list
> Can you try booting from this device?
  boot from this option,guest stuck(please check the attachment)
Comment 34 Vadim Rozenfeld 2015-02-16 23:20:55 EST
(In reply to lijin from comment #33)
> Created attachment 992460 [details]
> F12 boot list
> 
> (In reply to Vadim Rozenfeld from comment #32)
> > (In reply to lijin from comment #31)
> > > Created attachment 992074 [details]
> > > rhel bios screenshot
> > 
> > What happens if you hit F12. Do you see the list of bootable devices with
> > "Virtio Disk PCI:0:3" as one of the options? 
>   Yes,it's the first option of the list
> > Can you try booting from this device?
>   boot from this option,guest stuck(please check the attachment)

Thanks,
Can you please post the command line, used in this run?
Comment 35 lijin 2015-02-16 23:57:20 EST
(In reply to Vadim Rozenfeld from comment #34)
> (In reply to lijin from comment #33)
> > Created attachment 992460 [details]
> > F12 boot list
> > 
> > (In reply to Vadim Rozenfeld from comment #32)
> > > (In reply to lijin from comment #31)
> > > > Created attachment 992074 [details]
> > > > rhel bios screenshot
> > > 
> > > What happens if you hit F12. Do you see the list of bootable devices with
> > > "Virtio Disk PCI:0:3" as one of the options? 
> >   Yes,it's the first option of the list
> > > Can you try booting from this device?
> >   boot from this option,guest stuck(please check the attachment)
> 
> Thanks,
> Can you please post the command line, used in this run?

 /usr/libexec/qemu-kvm -m 2G -smp 4 -cpu cpu64-rhel6,+x2apic,family=0xf -usb -device usb-tablet -drive file=win2k3-64-blk-new.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device virtio-blk-pci,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device rtl8139,netdev=hostnet0,mac=00:13:45:14:F5:01 -uuid 1b3ac854-3eec-4d92-96cd-a5d64db12102 -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2k3-64-blk,server,nowait -mon chardev=111a,mode=readline -spice port=5930,disable-ticketing -vga qxl -rtc base=localtime,clock=host,driftfix=slew -drive file=disk1.raw,if=none,format=raw,id=drive-virtio-data1,werror=stop,rerror=stop -device virtio-blk-pci,id=virtio-data1,drive=drive-virtio-data1 -boot menu=on -cdrom en_win_srv_2003_r2_enterprise_x64_with_sp2_cd1_X13-06188.iso -monitor stdio -bios /home/bios.bin

anything else,please let me know :-)
Comment 37 lijin 2016-01-05 00:40:17 EST
still CAN reproduce this issue with virtio-win-prewhql-112 on rhel6 host.
steps same with comment#0

BTW,copy an win2003-64 image installed on rhel7 to rhel6,can NOT hit this issue,guest can boot correctly after change ide to blk.

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