On 07/21/2013 03:32 AM, Yan Vugenfirer wrote:
Can you provide results with iperf or netperf?
Actually, iperf seems to operate at expected speeds, while some other
applications don't. I'm working on getting a list of some of the
affected programs. I believe my users first reported the proble
Would anyone be so kind as to test the performance of TCP streams on
Windows 2k8R2 guests of KVM virt servers?
Red Hat's virtio-win-1.6.3 package was published to address a problem
described as "low performance" on Win2k8 guests. Actual performance was
not recorded in the bug report.
On my
On 10/07/2012 06:43 AM, Alex Williamson wrote:
On Sat, 2012-10-06 at 18:23 -0700, Gordon Messmer wrote:
If I don't pass an emulated VGA device (and modify seabios to not run
the VGA ROM), the guess won't read anything from the rom at all.
Can anyone point me at which parts of the co
I started trying to pass through a PCI-E card to a KVM guest early this
year. Other hardware can be passed through successfully, but the guest
sees the wrong option ROM for this card.
My system is an AMD CPU and GA-970A-D3 motherboard. There are currently
two Radeon HD 3470 cards installed,
On 05/01/2012 04:33 PM, Sean Kennedy wrote:
I am getting crashes (BSoD) when using Virtio for the disk driver in Windows XP.
I was getting the same thing on Windows Server 2008 guests. The systems
would crash and some of them corrupted their filesystems pretty badly.
I ended up reverting to
I still poke at this when I get time.
I notice that pci_update_mappings calls pci_bar_address, and the latter
will always return PCI_BAR_UNMAPPED for this device. For the emulated
devices, pci_bar_address will get an address with PCI_ROM_ADDRESS_ENABLE
at some point, and pci_map_option_rom wi
On 01/07/2012 02:21 PM, Gordon Messmer wrote:
I'm certain that qemu-kvm loads both
/usr/share/qemu-kvm/vgabios-cirrus.bin and
/var/lib/libvirt/images/Radeon3470.rom, which seems correct. However,
in the guest, both the virtual VGA card and the real PCI one have the
same ROM, from vg
On 01/06/2012 06:07 PM, Gordon Messmer wrote:
/usr/libexec/qemu-kvm\
-vnc 127.0.0.1:0 -vga cirrus \
-device
pci-assign,host=05:00.0,id=hostdev1,configfd=27,bus=pci.0,addr=0x7,romfile=/var/lib/libvirt/images/Radeon3470.rom
Snipped a bunch of other args... I'm certain that qemu-kvm loads
On 01/06/2012 01:31 AM, André Weidemann wrote:
On 06.01.2012 08:25, Gordon Messmer wrote:
Well, I finally figured out that I have to enable the reading of roms
from the device by writing "1" to the "rom" node in /sys/. Now the
problem is that the rom is 64k, and only 32k ar
On 01/05/2012 11:07 AM, Gordon Messmer wrote:
I started with an update to seabios, from the bundled version
0.6.1.2-8.el6 to a rebuilt package from F16, 0.6.2-3.el6. That's enough
to get the guest to boot with the pass-through video card. It doesn't
work, currently, and I'm pre
On 01/03/2012 07:44 PM, Alex Williamson wrote:
Yep, that's what I would have guessed, there's a 256MB resource. I'm
not sure if the seabios you're using is mapping the MMIO hole
efficiently enough to handle that. Can you test on new upstream
qemu-kvm? Thanks,
I'm not done poking the system,
Thanks, Alex. I really appreciate the reply.
On 01/03/2012 01:34 PM, Alex Williamson wrote:
This is actually the GART aperture, which Linux will try to use as an
IOMMU. You can pretty much ignore this, but it may be wasting memory
for no good reason if it's really hiding usable memory and allo
I'm going to summarize my questions first and write the long explanation
afterward...
1: What happens when Linux rejects the aperture allocated by the BIOS
for an AMD IOMMU?
2: What is unsafe about the allow_unsafe_assigned_interrupts option?
What are the potential consequences of its use?
3:
13 matches
Mail list logo
