From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carlos Rodrigues Subject: Re: Problem after update windows VirtIO drivers Date: Tue, 10 Dec 2013 12:28:07 +0000 Message-ID: <1386678487.2326.2.camel@cmar-laptop.lan> References: <1386600306.2456.15.camel@cmar-laptop.lan> <52A5F3AC.3090705@redhat.com> <1488140279.34434310.1386642242307.JavaMail.root@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Alon Levy , kvm@vger.kernel.org To: Vadim Rozenfeld Return-path: Received: from brg.eurotux.com ([194.107.127.5]:40479 "EHLO brg.eurotux.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751215Ab3LJM2J (ORCPT ); Tue, 10 Dec 2013 07:28:09 -0500 In-Reply-To: <1488140279.34434310.1386642242307.JavaMail.root@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Hello Vadim, I'm using libvirt to help to configure the virtual machines, so the output of qemu command through libvirt is: # virsh qemu-monitor-command win-test --hmp --cmd '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 0xc0c0 [0xc0cf]. id "" Bus 0, device 1, function 2: USB controller: PCI device 8086:7020 IRQ 5. BAR4: I/O at 0xc040 [0xc05f]. id "usb" Bus 0, device 1, function 3: Bridge: PCI device 8086:7113 IRQ 9. id "" Bus 0, device 2, function 0: VGA controller: PCI device 1013:00b8 BAR0: 32 bit prefetchable memory at 0xfc000000 [0xfdffffff]. BAR1: 32 bit memory at 0xfebf0000 [0xfebf0fff]. BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe]. id "" Bus 0, device 3, function 0: Ethernet controller: PCI device 1af4:1000 IRQ 0. BAR0: I/O at 0xc060 [0xc07f]. BAR1: 32 bit memory at 0xfebf1000 [0xfebf1fff]. BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe]. id "net0" Bus 0, device 4, function 0: Class 1920: PCI device 1af4:1003 IRQ 0. BAR0: I/O at 0xc080 [0xc09f]. BAR1: 32 bit memory at 0xfebf2000 [0xfebf2fff]. id "virtio-serial0" Bus 0, device 5, function 0: SCSI controller: PCI device 1af4:1001 IRQ 0. BAR0: I/O at 0xc000 [0xc03f]. BAR1: 32 bit memory at 0xfebf3000 [0xfebf3fff]. id "virtio-disk0" Bus 0, device 6, function 0: Class 0255: PCI device 1af4:1002 IRQ 5. BAR0: I/O at 0xc0a0 [0xc0bf]. id "balloon0" Regards, --=20 Carlos Rodrigues=20 Engenheiro de Software S=C3=A9nior Eurotux Inform=C3=A1tica, S.A. | www.eurotux.com (t) +351 253 680 300 (m) +351 911 926 110 On Seg, 2013-12-09 at 21:24 -0500, Vadim Rozenfeld wrote: >=20 > ----- Original Message ----- > From: "Alon Levy" > To: "Carlos Rodrigues" , kvm@vger.kernel.org, "Vadi= m Rozenfeld" > Sent: Tuesday, December 10, 2013 3:45:32 AM > Subject: Re: Problem after update windows VirtIO drivers >=20 > On 12/09/2013 04:45 PM, Carlos Rodrigues wrote: > > Hello, > >=20 > > After update the VirtIO drivers for Windows Server 2008 R2 64-bit, = when > > i reboot virtual machine, the windows OS get stuck on loading bar. > >=20 > > The VirtIO drivers is the latest stable that i made the download fr= om > > http://alt.fedoraproject.org/pub/alt/virtio-win/stable/virtio-win-0= =2E1-74.iso > >=20 > > And i use version 1.2.1 of kvm and the OS of host is Centos 5.8. > >=20 > > I try to install a fresh and clean version same Windows and same dr= ivers > > and get the same problem. With virtio-win-0.1-52 version of drivers= , the > > windows server works properly. > >=20 > > I will use the oldest stable version of drivers, but anyone knows s= ome > > issue with latest drivers? > >=20 > [VR] > Hi Carlos, > Could you please post the QEMU command line as well as output > from 'info pci' >=20 > I have an issue that also existed with 0.65, on windows 7 64 bit: whe= n I > have qxl enabled as well I get a crash shortly after initialization o= f > qxl (at the login screen) in a memory management function of the qxl > driver, indicating something overwrote parts of the allocators > accounting structures. When I disable the virtio driver (leaving the > virtio device) the problem goes away. >=20 > Vadim, is this a known problem? (sorry for hijacking the thread) >=20 > Does it crash into BSOD? Can you share the crash dump file? >=20 > Best regards, > Vadim. >=20 >=20 > > Regards, > >=20 >=20