Bug 769136
Summary: | [virtio-win][viostor]System disk cannot boot up with "virtio" on windows 2k3-64 guest | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Min Deng <mdeng> | ||||||||||
Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||||
Severity: | high | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 6.3 | CC: | ailan, juzhang, knoel, lijin, mdeng, michen, qzhang, rbalakri, rpacheco, vrozenfe, yvugenfi | ||||||||||
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: | 2016-10-27 08:13:56 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: | |||||||||||||
Attachments: |
|
Description
Min Deng
2011-12-20 02:19:00 UTC
By the way,the issue cannot be found on windows 2k3 32 bits.thank you,any issues please let me know. 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? (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 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. Too late for 6.3, we are busy with blockers. Postponed. Hi Min, Could you please re-check this issue with our latest, MS-signed drivers? Thank you, Vadim. Min / QE, Can you please recheck with build30. Thanks, Ronen. (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 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. Hi Min, Could you please confirm that it still reproducible with the latest drivers on RHEL 6.7? Thanks, Vadim. 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 (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. (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 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" Created attachment 985451 [details]
guest stuck at boot stage
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. 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 Can you please post the guest stuck image once again (just like in #26), and output from "info qtree" command? Thanks. Vadim. Created attachment 992072 [details]
upstream bios screenshot
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)
(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. 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) (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? (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 :-) 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. |