Bug 1387054

Please provide the virtio-win version.

Please provide full qemu command line.

(In reply to Karen Noel from comment #2)
> Please provide the virtio-win version.

> not install guest tool, only use virtio disk when install os.

> Please provide full qemu command line.

/usr/libexec/qemu-kvm -name i-00000019 -S -machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off -cpu SandyBridge,+erms,+smep,+fsgsbase,+pdpe1gb,+rdrand,+f16c,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 0fa5c0ee-15d4-4029-91a9-9e13db046ebb -smbios type=1,manufacturer=Fedora Project,product=OpenStack Nova,version=12.0.0-4,serial=f8474f12-f24f-45e9-b702-00f3c6fe7cc8,uuid=0fa5c0ee-15d4-4029-91a9-9e13db046ebb,family=Virtual Machine -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-i-00000019/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/opt/ssd/volume-3e8545b4-c4d3-4614-9295-113a15bc259b,if=none,id=drive-virtio-disk0,format=qcow2,serial=3e8545b4-c4d3-4614-9295-113a15bc259b,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-fdc0-0-0,readonly=on,format=raw -global isa-fdc.driveA=drive-fdc0-0-0 -drive file=/var/lib/nova/instances/0fa5c0ee-15d4-4029-91a9-9e13db046ebb/guest_meta/guest_meta.iso,if=none,id=drive-ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive if=none,id=drive-ide0-0-1,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:6f:1e:af,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/var/lib/nova/instances/0fa5c0ee-15d4-4029-91a9-9e13db046ebb/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -chardev socket,id=charchannel1,path=/tmp/extra_channles/0fa5c0ee-15d4-4029-91a9-9e13db046ebb/com.morningcloud.tcloud,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.morningcloud.tcloud -chardev socket,id=charchannel2,path=/tmp/extra_channles/0fa5c0ee-15d4-4029-91a9-9e13db046ebb/com.morningcloud.tcloud.multimedia,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.morningcloud.tcloud.multimedia -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -k en-us -spice port=5901,addr=0.0.0.0,agent-mouse=on,disable-ticketing,image-compression=auto_glz,streaming-video=filter,seamless-migration=on -k en-us -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -global qxl-vga.vgamem_mb=16 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,filter=0x03:-1:-1:-1:0|-1:-1:-1:-1:1 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,filter=0x03:-1:-1:-1:0|-1:-1:-1:-1:1 -chardev spicevmc,id=charredir2,name=usbredir -device usb-redir,chardev=charredir2,id=redir2,filter=0x03:-1:-1:-1:0|-1:-1:-1:-1:1 -chardev spicevmc,id=charredir3,name=usbredir -device usb-redir,chardev=charredir3,id=redir3,filter=0x03:-1:-1:-1:0|-1:-1:-1:-1:1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on

It's an old bug, should be fixed in

kernel-3.10.0-229.10.1.el7.x86_64
qemu-kvm-rhev-2.1.2-23.el7_1.9.x86_64

for more information please visit
https://bugzilla.redhat.com/show_bug.cgi?id=1225087
https://bugzilla.redhat.com/show_bug.cgi?id=1183947

Best regards,
Vadim.

(In reply to Vadim Rozenfeld from comment #4)
> It's an old bug, should be fixed in
> 
> kernel-3.10.0-229.10.1.el7.x86_64
> qemu-kvm-rhev-2.1.2-23.el7_1.9.x86_64
> 
> for more information please visit
> https://bugzilla.redhat.com/show_bug.cgi?id=1225087
> https://bugzilla.redhat.com/show_bug.cgi?id=1183947
> 
> Best regards,
> Vadim.

my env
kernel ver: 3.10.0-229.11.1.el7.x86_64 
qemu ver:  qemu-kvm-rhev-2.3.0-32.el7

this version has fixed this bug or not?

(In reply to uljtg from comment #5)
> (In reply to Vadim Rozenfeld from comment #4)
> > It's an old bug, should be fixed in
> > 
> > kernel-3.10.0-229.10.1.el7.x86_64
> > qemu-kvm-rhev-2.1.2-23.el7_1.9.x86_64
> > 
> > for more information please visit
> > https://bugzilla.redhat.com/show_bug.cgi?id=1225087
> > https://bugzilla.redhat.com/show_bug.cgi?id=1183947
> > 
> > Best regards,
> > Vadim.
> 
> my env
> kernel ver: 3.10.0-229.11.1.el7.x86_64 
> qemu ver:  qemu-kvm-rhev-2.3.0-32.el7
> 
> this version has fixed this bug or not?

You shouldn't see this problem on your system.

(In reply to Vadim Rozenfeld from comment #6)
> (In reply to uljtg from comment #5)
> > (In reply to Vadim Rozenfeld from comment #4)
> > > It's an old bug, should be fixed in
> > > 
> > > kernel-3.10.0-229.10.1.el7.x86_64
> > > qemu-kvm-rhev-2.1.2-23.el7_1.9.x86_64
> > > 
> > > for more information please visit
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1225087
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1183947
> > > 
> > > Best regards,
> > > Vadim.
> > 
> > my env
> > kernel ver: 3.10.0-229.11.1.el7.x86_64 
> > qemu ver:  qemu-kvm-rhev-2.3.0-32.el7
> > 
> > this version has fixed this bug or not?
> 
> You shouldn't see this problem on your system.

The problem can be reproduced with my steps in my env above.

I use windbg attach to debug, find  hal!halpwaitforphase0clocktick initialize failed cause the bsod. I guess the bug may be caused by qemu clock, but I don't know how to resolve.

(In reply to uljtg from comment #7)
> (In reply to Vadim Rozenfeld from comment #6)
> > (In reply to uljtg from comment #5)
> > > (In reply to Vadim Rozenfeld from comment #4)
> > > > It's an old bug, should be fixed in
> > > > 
> > > > kernel-3.10.0-229.10.1.el7.x86_64
> > > > qemu-kvm-rhev-2.1.2-23.el7_1.9.x86_64
> > > > 
> > > > for more information please visit
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=1225087
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=1183947
> > > > 
> > > > Best regards,
> > > > Vadim.
> > > 
> > > my env
> > > kernel ver: 3.10.0-229.11.1.el7.x86_64 
> > > qemu ver:  qemu-kvm-rhev-2.3.0-32.el7
> > > 
> > > this version has fixed this bug or not?
> > 
> > You shouldn't see this problem on your system.
> 
> The problem can be reproduced with my steps in my env above.
> 
> I use windbg attach to debug, find  hal!halpwaitforphase0clocktick
> initialize failed cause the bsod. I guess the bug may be caused by qemu
> clock, but I don't know how to resolve.

You are right.
BSOD  0x0000005C (0x0000010B,0x00000001,0x000000000,0x00000000) happens because no RTC interrupt (status register 0Ch, Bit 7 = IRQF flag) has been triggered during 3 second after rtc chip initialization.

Maybe I was wrong with the kernel version, checking it now.
Meanwhile, could you please disable APIC-v and check if it
helps to resolve the problem?

rmmod kvm_intel; rmmod kvm; modprobe kvm_intel enable_apicv=0

The problem was fixed kernel-3.10.0-258.el7

You can take a look at 
https://patchwork.kernel.org/patch/5231891/
for upstream version.

(In reply to Vadim Rozenfeld from comment #8)
> (In reply to uljtg from comment #7)
> > (In reply to Vadim Rozenfeld from comment #6)
> > > (In reply to uljtg from comment #5)
> > > > (In reply to Vadim Rozenfeld from comment #4)
> > > > > It's an old bug, should be fixed in
> > > > > 
> > > > > kernel-3.10.0-229.10.1.el7.x86_64
> > > > > qemu-kvm-rhev-2.1.2-23.el7_1.9.x86_64
> > > > > 
> > > > > for more information please visit
> > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1225087
> > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1183947
> > > > > 
> > > > > Best regards,
> > > > > Vadim.
> > > > 
> > > > my env
> > > > kernel ver: 3.10.0-229.11.1.el7.x86_64 
> > > > qemu ver:  qemu-kvm-rhev-2.3.0-32.el7
> > > > 
> > > > this version has fixed this bug or not?
> > > 
> > > You shouldn't see this problem on your system.
> > 
> > The problem can be reproduced with my steps in my env above.
> > 
> > I use windbg attach to debug, find  hal!halpwaitforphase0clocktick
> > initialize failed cause the bsod. I guess the bug may be caused by qemu
> > clock, but I don't know how to resolve.
> 
> You are right.
> BSOD  0x0000005C (0x0000010B,0x00000001,0x000000000,0x00000000) happens
> because no RTC interrupt (status register 0Ch, Bit 7 = IRQF flag) has been
> triggered during 3 second after rtc chip initialization.
> 
> Maybe I was wrong with the kernel version, checking it now.
> Meanwhile, could you please disable APIC-v and check if it
> helps to resolve the problem?
> 
> rmmod kvm_intel; rmmod kvm; modprobe kvm_intel enable_apicv=0

i will test it today.

(In reply to Vadim Rozenfeld from comment #9)
> The problem was fixed kernel-3.10.0-258.el7
> 
> You can take a look at 
> https://patchwork.kernel.org/patch/5231891/
> for upstream version.

Also: kernel-3.10.0-229.16.1.el7 for rhel-7.1.z

See https://bugzilla.redhat.com/show_bug.cgi?id=1225087 for the "Fixed in Version".

(In reply to Karen Noel from comment #11)
> (In reply to Vadim Rozenfeld from comment #9)
> > The problem was fixed kernel-3.10.0-258.el7
> > 
> > You can take a look at 
> > https://patchwork.kernel.org/patch/5231891/
> > for upstream version.
> 
> Also: kernel-3.10.0-229.16.1.el7 for rhel-7.1.z
> 
> See https://bugzilla.redhat.com/show_bug.cgi?id=1225087 for the "Fixed in
> Version".

Thanks very much, i will test this kernel version later.

Is 3.10.0-327.28.3.el7.x86_64 also fixed the problem?

(In reply to uljtg from comment #12)
> (In reply to Karen Noel from comment #11)
> > (In reply to Vadim Rozenfeld from comment #9)
> > > The problem was fixed kernel-3.10.0-258.el7
> > > 
> > > You can take a look at 
> > > https://patchwork.kernel.org/patch/5231891/
> > > for upstream version.
> > 
> > Also: kernel-3.10.0-229.16.1.el7 for rhel-7.1.z
> > 
> > See https://bugzilla.redhat.com/show_bug.cgi?id=1225087 for the "Fixed in
> > Version".
> 
> Thanks very much, i will test this kernel version later.
> 
> Is 3.10.0-327.28.3.el7.x86_64 also fixed the problem?

It should. 3.10.0-327.28.3.el7 was released almost 5 months after kernel-3.10.0-258.el7

(In reply to Vadim Rozenfeld from comment #13)
> (In reply to uljtg from comment #12)
> > (In reply to Karen Noel from comment #11)
> > > (In reply to Vadim Rozenfeld from comment #9)
> > > > The problem was fixed kernel-3.10.0-258.el7
> > > > 
> > > > You can take a look at 
> > > > https://patchwork.kernel.org/patch/5231891/
> > > > for upstream version.
> > > 
> > > Also: kernel-3.10.0-229.16.1.el7 for rhel-7.1.z
> > > 
> > > See https://bugzilla.redhat.com/show_bug.cgi?id=1225087 for the "Fixed in
> > > Version".
> > 
> > Thanks very much, i will test this kernel version later.
> > 
> > Is 3.10.0-327.28.3.el7.x86_64 also fixed the problem?
> 
> It should. 3.10.0-327.28.3.el7 was released almost 5 months after
> kernel-3.10.0-258.el7

Thanks.

I have tested  with modprobe kvm_intel enable_apicv=0,  don't  reproduce the problem in two days OS continue running. 

I will test this kernel version today.   3.10.0-327.28.3.el7.x86_64

I have testded 3.10.0-327.28.3.el7.x86_64, it also has fixed this problem.

Thanks very much.

(In reply to uljtg from comment #15)
> I have testded 3.10.0-327.28.3.el7.x86_64, it also has fixed this problem.
> 
> Thanks very much.

Great.

Can we close this bug then?

Best regards,
Vadim.

(In reply to Vadim Rozenfeld from comment #16)
> (In reply to uljtg from comment #15)
> > I have testded 3.10.0-327.28.3.el7.x86_64, it also has fixed this problem.
> > 
> > Thanks very much.
> 
> Great.
> 
> Can we close this bug then?
> 
> Best regards,
> Vadim.

Of course, thank you.