From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Carlos Rodrigues <cmar@eurotux.com>
Cc: Alon Levy <alevy@redhat.com>, kvm@vger.kernel.org
Subject: Re: Problem after update windows VirtIO drivers
Date: Wed, 11 Dec 2013 19:26:07 +1100 [thread overview]
Message-ID: <1386750367.32091.66.camel@localhost> (raw)
In-Reply-To: <1386678487.2326.2.camel@cmar-laptop.lan>
On Tue, 2013-12-10 at 12:28 +0000, Carlos Rodrigues wrote:
> 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"
Can you please try switching virtio-blk device to ide and
see if it helps?
Thanks,
Vadim.
> Bus 0, device 6, function 0:
> Class 0255: PCI device 1af4:1002
> IRQ 5.
> BAR0: I/O at 0xc0a0 [0xc0bf].
> id "balloon0"
>
> Regards,
>
next prev parent reply other threads:[~2013-12-11 8:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 14:45 Problem after update windows VirtIO drivers Carlos Rodrigues
2013-12-09 16:45 ` Alon Levy
2013-12-09 20:13 ` Cole Robinson
2013-12-10 2:24 ` Vadim Rozenfeld
2013-12-10 12:28 ` Carlos Rodrigues
2013-12-11 8:26 ` Vadim Rozenfeld [this message]
2013-12-11 9:46 ` Carlos Rodrigues
2013-12-11 10:07 ` Vadim Rozenfeld
2013-12-11 12:16 ` Carlos Rodrigues
2013-12-13 10:25 ` Vadim Rozenfeld
2013-12-13 14:35 ` Carlos Rodrigues
2013-12-13 21:30 ` Vadim Rozenfeld
2013-12-17 9:43 ` Carlos Rodrigues
2013-12-29 10:09 ` Vadim Rozenfeld
2013-12-10 13:29 ` Alon Levy
2013-12-11 9:27 ` Vadim Rozenfeld
2013-12-11 12:40 ` Alon Levy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1386750367.32091.66.camel@localhost \
--to=vrozenfe@redhat.com \
--cc=alevy@redhat.com \
--cc=cmar@eurotux.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.