Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1046275

Summary: win8 guest boots with virtio-scsi/blk or ahci as system image interference mutually
Product: Red Hat Enterprise Linux 7 Reporter: xhan
Component: virtio-winAssignee: Vadim Rozenfeld <vrozenfe>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: bcao, hhuang, juzhang, kraxel, lijin, mdeng, michen, pbonzini, rbalakri, rhod, scui, sluo, virt-maint, vrozenfe, xwei
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: 2014-11-01 11:30:47 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:
Attachments:
Description Flags
screen-shot.jpg none

Description xhan 2013-12-24 10:17:13 UTC
Description of problem:

After installing Win8.0 i386/x86_64 guest, install virtio-win driver for virtio-blk/virtio-scsi/ahci drives.

Then test if the guest can boot up with the drive which is virtio-blk/virtio-scsi/ahci as a sys image.

Booting up with ahci sys image failed. See the picture screen-shot.jpg. Follow the msdn resolution http://support.microsoft.com/kb/2795397. The Win8.0 i386 guest can recognize the sys drive and boot up successfully.

Then test booting with virtio-scsi sys image, it would fail with blue screen with error: INACCESSABLE_BOOT_DEVICE.
 

Version-Release number of selected component (if applicable):
kernel-3.10.0-57.el7.x86_64
qemu-kvm-rhev-1.5.3-20.el7.x86_64


How reproducible:
100%

Steps to Reproduce:
1. install win8.0 i386 guest with latest_prewhql.iso(virtio-win-prewhql-0.1-74.iso)

2. boot the win8.0 i386 guest with virtio-blk/virtio-scsi/ahci as data drives and ide as the sys image to install (virtio-blk/virtio-scsi/ahci) drivers

3. try to boot win8.0 guest with the virtio-blk/virtio-scsi/ahci drive as sys image to test if it can boot up.

 3.1 ahci:
  -device ahci,id=ahci0,bus=pci.0,addr=05 \
  -drive id=drive_image1,if=none,cache=writethrough,snapshot=off,aio=native,file=win8-32-virtio.qcow2 \
  -device ide-hd,id=image1,drive=drive_image1,bus=ahci0.0,unit=0 \

 3.2 virtio-blk:
   -drive id=drive_image1,if=none,cache=writethrough,snapshot=off,aio=native,file=win8-32-virtio.qcow2 \
  -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0,addr=05 \

 3.3 virtio-scsi:
  -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x05 \
  -drive id=drive_image1,if=none,cache=writethrough,snapshot=off,aio=native,file=win8-32-virtio.qcow2 \
  -device scsi-hd,id=image1,drive=drive_image1 \


Actual results:

Win8 guest failed to boot with ahci.
The image then could no boot with virtio-scsi as the sys image too.

Expected results:
Booting win8 guest should work normally.

Additional info:

Comment 1 xhan 2013-12-24 10:19:08 UTC
Created attachment 841171 [details]
screen-shot.jpg

Comment 3 xhan 2013-12-25 02:02:43 UTC
Win8.1/Win2012/Win2012r2 also have this problem.

Comment 4 Sibiao Luo 2013-12-25 02:17:48 UTC
(In reply to xhan from comment #0)
> Description of problem:
> 
> After installing Win8.0 i386/x86_64 guest, install virtio-win driver for
> virtio-blk/virtio-scsi/ahci drives.
> 
> Then test if the guest can boot up with the drive which is
> virtio-blk/virtio-scsi/ahci as a sys image.
> 
> Booting up with ahci sys image failed. See the picture screen-shot.jpg.
> Follow the msdn resolution http://support.microsoft.com/kb/2795397. The
> Win8.0 i386 guest can recognize the sys drive and boot up successfully.
> 
> Then test booting with virtio-scsi sys image, it would fail with blue screen
> with error: INACCESSABLE_BOOT_DEVICE.
>  
Please paste your qemu-kvm command line here. Could you switch to IDE interface to try it, as ahci driver is provided by the windows guest which not belong to virtio-win. And please help to narrow the range for this issue, maybe not related to the virtual block device issue. Thanks.

Best Regards,
sluo

Comment 5 Mike Cao 2013-12-25 02:35:56 UTC
Hi,xhan

Pls disable win8/win2012 fast boot option http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.html and retest 

Mike

Comment 6 xhan 2013-12-25 08:01:09 UTC
qemu \
  -name 'vm1'  \
  -sandbox off  \
  -M pc  \
  -nodefaults  \
  -vga cirrus \
  -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20131220-100951-hDnnIG42,server,nowait \
  -mon chardev=qmp_id_qmpmonitor1,mode=control  \
  -chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0-20131220-100951-hDnnIG42,server,nowait \
  -device isa-serial,chardev=serial_id_serial0 \
  -device virtio-serial-pci,id=virtio_serial_pci0,bus=pci.0,addr=03  \
  -chardev socket,id=devvs,path=/tmp/virtio_port-vs-20131220-100951-hDnnIG42,server,nowait \
  -device virtserialport,chardev=devvs,name=vs,id=vs,bus=virtio_serial_pci0.0  \
  -chardev socket,id=seabioslog_id_20131220-100951-hDnnIG42,path=/tmp/seabios-20131220-100951-hDnnIG42,server,nowait \
  -device isa-debugcon,chardev=seabioslog_id_20131220-100951-hDnnIG42,iobase=0x402 \
  -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=04 \
  -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x05 \
  -drive id=drive_image1,if=none,cache=writethrough,snapshot=off,aio=native,file=win8-32-virtio.qcow2 \
  -device scsi-hd,id=image1,drive=drive_image1 \
  -drive id=drive_stg,if=none,cache=writethrough,snapshot=off,aio=native,file=storage.qcow2 \
  -device virtio-blk-pci,id=stg,drive=drive_stg,bus=pci.0,addr=06 \
  -device virtio-scsi-pci,id=virtio_scsi_pci1,bus=pci.0,addr=09 \
  -drive id=drive_stg1,if=none,cache=writethrough,snapshot=off,aio=native,file=storage1.qcow2 \
  -device scsi-hd,id=stg1,drive=drive_stg1 \
  -device rtl8139,mac=9a:bc:bd:be:bf:c0,id=idRMlGT0,netdev=idBfdxm2,bus=pci.0,addr=07  \
  -netdev tap,id=idBfdxm2,vhost=on,script=qemu-ifup-switch \
  -device virtio-net-pci,mac=9a:c1:c2:c3:c4:c5,id=id2n2sPC,netdev=ide4xB37,bus=pci.0,addr=08 \
  -netdev tap,id=ide4xB37,vhost=on,script=qemu-ifup-switch  \
  -m 4096  \
  -smp 4,maxcpus=4,cores=2,threads=1,sockets=2  \
  -cpu 'SandyBridge' \
  -drive id=drive_cd1,if=none,snapshot=off,aio=native,media=cdrom,file=isos/windows/virtio-win.latest_prewhql.iso \
  -device ide-cd,id=cd1,drive=drive_cd1,bus=ide.0,unit=1 \
  -drive id=drive_virtio,if=none,snapshot=off,aio=native,media=cdrom,file=virtio-win.iso \
  -device ide-cd,id=virtio,drive=drive_virtio,bus=ide.1,unit=0 \
  -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1  \
  -vnc :0  \
  -rtc base=localtime,clock=host,driftfix=slew  \
  -boot order=cdn,once=c,menu=off  \
  -balloon virtio \
  -enable-kvm

Comment 7 xhan 2013-12-25 08:16:51 UTC
(In reply to Mike Cao from comment #5)
> Hi,xhan
> 
> Pls disable win8/win2012 fast boot option
> http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.
> html and retest 
> 
> Mike


Test guest with -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 options, the fast startup is enabled in default.

Comment 8 xhan 2013-12-25 08:46:03 UTC
(In reply to xhan from comment #7)
> (In reply to Mike Cao from comment #5)
> > Hi,xhan
> > 
> > Pls disable win8/win2012 fast boot option
> > http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.
> > html and retest 
> > 
> > Mike
> 
> 
> Test guest with -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0
> options, the fast startup is enabled in default.

Disable this fast startup in win8 guest. It doesn't work. 
Test result: 
                             sys image drive         result
  1) start win8 guest with  virtio-blk as sys drive -- ok (guest can start up).
  2) change to              virtio-scsi                ok
  3) change to              ahci                       failed 
  4) change to              virtio-scsi                failed 
  5) change to              virtio-blk                 ok

 Note: The failed error: INACCESSABLE_BOOT_DEVICE

Comment 9 Xiaoqing Wei 2013-12-30 10:04:41 UTC
(In reply to xhan from comment #8)
> (In reply to xhan from comment #7)
> > (In reply to Mike Cao from comment #5)
> > > Hi,xhan
> > > 
> > > Pls disable win8/win2012 fast boot option
> > > http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.
> > > html and retest 
> > > 
> > > Mike
> > 
> > 
> > Test guest with -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0
> > options, the fast startup is enabled in default.
> 
> Disable this fast startup in win8 guest. It doesn't work. 
> Test result: 
>                              sys image drive         result
>   1) start win8 guest with  virtio-blk as sys drive -- ok (guest can start
> up).
>   2) change to              virtio-scsi                ok

Hi xhan,

could you pls have a try update this registry during success of virtio-scsi boot(before ahci boot)
reg add HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IastorV /v Start /t REG_DWORD /d 0 /f

>   3) change to              ahci                       failed 
>   4) change to              virtio-scsi                failed 
>   5) change to              virtio-blk                 ok
> 
>  Note: The failed error: INACCESSABLE_BOOT_DEVICE


Regards,
Xiaoqing.

Comment 10 Vadim Rozenfeld 2014-01-05 12:25:37 UTC
What happens if you try to install Win8 on virtio-block or virtio-scsi drive.
It also will be interesting to know if you have the same problem with oter OSes,
like Win7 and WS2K8

Comment 11 xhan 2014-01-13 10:57:08 UTC
xwei,
Tried to update registry before ahci boot, and the result is 

win2012r2: 
                             sys image drive         result
  1) start win2012r2  with  virtio-blk as sys drive -- ok 
  2) change to              virtio-scsi                ok
    update registry
  3) change to              ahci                       ok 
  4) change to              virtio-scsi                failed 
  5) change to              virtio-blk                 failed

win8:
                             sys image drive         result
  1) start win8  with       virtio-blk as sys drive -- ok 
  2) change to              virtio-scsi                ok
    update registry
  3) change to              ahci                       ok 
  4) change to              virtio-scsi                failed 
  5) change to              virtio-blk                 failed

Vadim,

The guests are installed with virtio_blk. There is no this issue on Win7 and WS2K8 guests.

Comment 12 Vadim Rozenfeld 2014-01-13 11:45:03 UTC
(In reply to xhan from comment #11)
> xwei,
> Tried to update registry before ahci boot, and the result is 
> 
> win2012r2: 
>                              sys image drive         result
>   1) start win2012r2  with  virtio-blk as sys drive -- ok 
>   2) change to              virtio-scsi                ok
>     update registry
>   3) change to              ahci                       ok 
>   4) change to              virtio-scsi                failed 
>   5) change to              virtio-blk                 failed
> 
> win8:
>                              sys image drive         result
>   1) start win8  with       virtio-blk as sys drive -- ok 
>   2) change to              virtio-scsi                ok
>     update registry
>   3) change to              ahci                       ok 
>   4) change to              virtio-scsi                failed 
>   5) change to              virtio-blk                 failed
> 
> Vadim,
> 
> The guests are installed with virtio_blk. There is no this issue on Win7 and
> WS2K8 guests.

Thanks, 
Vadim.

Comment 13 lijin 2014-04-16 05:40:20 UTC
this issue still can be reproduced with virtio-win-1.7.0-1.el7.noarch

other packages info:
kernel-3.10.0-121.el7.x86_64
qemu-kvm-rhev-1.5.3-60.el7ev.x86_64
seabios-bin-1.7.2.2-12.el7.x86_64

Comment 16 Ronen Hod 2014-08-07 08:16:41 UTC
Vadim suspects that the driver has to be installed to the drivers store before the plugin. He will check.

Comment 17 Vadim Rozenfeld 2014-11-01 11:30:47 UTC

*** This bug has been marked as a duplicate of bug 1097078 ***