From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vadim Rozenfeld Subject: Re: Problem after update windows VirtIO drivers Date: Wed, 11 Dec 2013 21:07:22 +1100 Message-ID: <1386756442.7616.4.camel@localhost> References: <1386600306.2456.15.camel@cmar-laptop.lan> <52A5F3AC.3090705@redhat.com> <1488140279.34434310.1386642242307.JavaMail.root@redhat.com> <1386678487.2326.2.camel@cmar-laptop.lan> <1386750367.32091.66.camel@localhost> <1386755194.2178.1.camel@cmar-laptop.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Alon Levy , kvm@vger.kernel.org To: Carlos Rodrigues Return-path: Received: from mx1.redhat.com ([209.132.183.28]:32307 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750800Ab3LKKHd (ORCPT ); Wed, 11 Dec 2013 05:07:33 -0500 In-Reply-To: <1386755194.2178.1.camel@cmar-laptop.lan> Sender: kvm-owner@vger.kernel.org List-ID: --=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 Qua, 2013-12-11 at 19:26 +1100, Vadim Rozenfeld wrote: > On Tue, 2013-12-10 at 12:28 +0000, Carlos Rodrigues wrote: > > Hello Vadim, > >=20 > > I'm using libvirt to help to configure the virtual machines, so the > > output of qemu command through libvirt is: > >=20 > > # 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" >=20 > Can you please try switching virtio-blk device to ide and=20 > see if it helps? When i switch the virtio-blk device to ide i get a bluescreen. [VR] What is the bugcheck code you're getting? Can you capture and post BSOD screen image? Btw, if you install VM from scratch - do you see the same problems? Thanks, Vadim. >=20 > Thanks, > Vadim.=20 >=20 > > Bus 0, device 6, function 0: > > Class 0255: PCI device 1af4:1002 > > IRQ 5. > > BAR0: I/O at 0xc0a0 [0xc0bf]. > > id "balloon0" > >=20 > > Regards, > >=20 >=20 >=20 > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlOn Wed, 2013-12-11 at 09:46 +0000, Carlos Rodrigues wrote: >=20