On 05/11/2011 04:08 PM, Jan Kiszka wrote:
On 2011-05-11 13:25, Avi Kivity wrote:
On 05/09/2011 06:48 PM, Alex Williamson wrote:
That's an interesting trace! We'll check this here, but I bet it
contributes to the problems. Our FX 3800 has 1G memory...
Yes, qemu leaves far too little
On 2011-05-11 15:54, Avi Kivity wrote:
On 05/11/2011 04:50 PM, Jan Kiszka wrote:
On 2011-05-11 15:26, Avi Kivity wrote:
On 05/11/2011 04:08 PM, Jan Kiszka wrote:
On 2011-05-11 13:25, Avi Kivity wrote:
On 05/09/2011 06:48 PM, Alex Williamson wrote:
That's an interesting trace! We'll
On 2011-05-11 15:26, Avi Kivity wrote:
On 05/11/2011 04:08 PM, Jan Kiszka wrote:
On 2011-05-11 13:25, Avi Kivity wrote:
On 05/09/2011 06:48 PM, Alex Williamson wrote:
That's an interesting trace! We'll check this here, but I bet it
contributes to the problems. Our FX 3800 has 1G
On 2011-05-11 13:23, Avi Kivity wrote:
On 05/09/2011 06:27 PM, Jan Kiszka wrote:
To avoid having to deal with legacy I/O forwarding, we started with a
dual adapter setup in the hope to leave the primary guest adapter at
know-to-work cirrus-vga. But already in a native setup with on-board
On 2011-05-11 13:25, Avi Kivity wrote:
On 05/09/2011 06:48 PM, Alex Williamson wrote:
That's an interesting trace! We'll check this here, but I bet it
contributes to the problems. Our FX 3800 has 1G memory...
Yes, qemu leaves far too little MMIO space to think about assigning
graphics
On 05/09/2011 06:48 PM, Alex Williamson wrote:
That's an interesting trace! We'll check this here, but I bet it
contributes to the problems. Our FX 3800 has 1G memory...
Yes, qemu leaves far too little MMIO space to think about assigning
graphics cards. Both of my cards have 512MB and I
On 05/11/2011 05:06 PM, Jan Kiszka wrote:
I doubt it. A 64-bit BAR would be configured as 32-bit on an older
BIOS, no?
I'd guess 64-bit BARs are only needed for large BARs.
The BIOS can't configure the bars to 64 bit as it does not know which
type of OS (32 or 64 bits) is going to
On 05/11/2011 04:50 PM, Jan Kiszka wrote:
On 2011-05-11 15:26, Avi Kivity wrote:
On 05/11/2011 04:08 PM, Jan Kiszka wrote:
On 2011-05-11 13:25, Avi Kivity wrote:
On 05/09/2011 06:48 PM, Alex Williamson wrote:
That's an interesting trace! We'll check this here, but I bet it
On 05/09/2011 06:27 PM, Jan Kiszka wrote:
To avoid having to deal with legacy I/O forwarding, we started with a
dual adapter setup in the hope to leave the primary guest adapter at
know-to-work cirrus-vga. But already in a native setup with on-board
primary + NVIDIA secondary, the NVIDIA Windows
Hi,
Another problem with SeaBIOS which limits the amount of memory space
is: SeaBIOS allocates the BAR regions as they are encountered. As far
as I know, the BAR regions should be naturally aligned. Thus the
simple strategy of the SeaBIOS results in large fragmentation.
Therefore, even after
On 2011-05-05 17:17, Alex Williamson wrote:
And what about the host? When does Linux release the legacy range?
Always or only when a specific (!=vga/vesa) framebuffer driver is loaded?
Well, that's where it'd be nice if the vga arbiter was actually in more
widespread use. It currently seems
On Mon, 2011-05-09 at 13:14 +0200, Jan Kiszka wrote:
On 2011-05-05 17:17, Alex Williamson wrote:
And what about the host? When does Linux release the legacy range?
Always or only when a specific (!=vga/vesa) framebuffer driver is loaded?
Well, that's where it'd be nice if the vga arbiter
On Mon, May 9, 2011 at 12:14 PM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-05-05 17:17, Alex Williamson wrote:
And what about the host? When does Linux release the legacy range?
Always or only when a specific (!=vga/vesa) framebuffer driver is loaded?
Well, that's where it'd be nice if
On 2011-05-09 16:29, Alex Williamson wrote:
On Mon, 2011-05-09 at 13:14 +0200, Jan Kiszka wrote:
On 2011-05-05 17:17, Alex Williamson wrote:
And what about the host? When does Linux release the legacy range?
Always or only when a specific (!=vga/vesa) framebuffer driver is loaded?
Well,
On 2011-05-09 16:55, Prasad Joshi wrote:
On Mon, May 9, 2011 at 12:14 PM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-05-05 17:17, Alex Williamson wrote:
And what about the host? When does Linux release the legacy range?
Always or only when a specific (!=vga/vesa) framebuffer driver is
On Mon, May 9, 2011 at 4:27 PM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-05-09 16:55, Prasad Joshi wrote:
On Mon, May 9, 2011 at 12:14 PM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-05-05 17:17, Alex Williamson wrote:
And what about the host? When does Linux release the legacy
On Mon, 2011-05-09 at 17:27 +0200, Jan Kiszka wrote:
On 2011-05-09 16:55, Prasad Joshi wrote:
On Mon, May 9, 2011 at 12:14 PM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-05-05 17:17, Alex Williamson wrote:
And what about the host? When does Linux release the legacy range?
Always or
On 2011-05-09 17:48, Alex Williamson wrote:
On Mon, 2011-05-09 at 17:27 +0200, Jan Kiszka wrote:
On 2011-05-09 16:55, Prasad Joshi wrote:
On Mon, May 9, 2011 at 12:14 PM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-05-05 17:17, Alex Williamson wrote:
And what about the host? When does
Hi Alex,
On 2011-01-28 01:45, Alex Williamson wrote:
On Thu, 2011-01-27 at 12:56 +0100, André Weidemann wrote:
Hi Alex,
On 26.01.2011 06:12, Alex Williamson wrote:
So while your initial results are promising, my guess is that you're
using card specific drivers and still need to consider
Hi Alex,
On 28.01.2011 01:45, Alex Williamson wrote:
Do you mind sharing these patches?
Attached.
Thank you for attaching the patch. Unfortunately it does not apply to
current clone of the qemu-kvm git repository. The file hw/vfio.c does
not exist in the public repository, but your patch
On Fri, 2011-01-28 at 18:29 +0100, André Weidemann wrote:
Hi Alex,
On 28.01.2011 01:45, Alex Williamson wrote:
Do you mind sharing these patches?
Attached.
Thank you for attaching the patch. Unfortunately it does not apply to
current clone of the qemu-kvm git repository. The file
Hi Alex,
On 26.01.2011 06:12, Alex Williamson wrote:
So while your initial results are promising, my guess is that you're
using card specific drivers and still need to consider some of the
harder problems with generic support for vga assignment. I hacked on
this for a bit trying to see if I
On Thu, 2011-01-27 at 12:56 +0100, André Weidemann wrote:
Hi Alex,
On 26.01.2011 06:12, Alex Williamson wrote:
So while your initial results are promising, my guess is that you're
using card specific drivers and still need to consider some of the
harder problems with generic support
Hi,
The changes we made are very less, mostly disabling default QEMU VGA.
But there are few problems that we are still working on
1. The display on the monitor, probably only appears after the KMS is
enabled. It does not display the grub menu and booting log.
Sounds like you're not
Hello,
This is to announce that, we have been able to pass-through a ATI
Radeon RV370 FireGL V3100 to Ubuntu VM. This card was attached to a
separate monitor, after passing-through the Keyboard and Mouse
everything worked as normal.
The changes we made are very less, mostly disabling default
2011/1/25 Prasad Joshi prasadjoshi...@gmail.com:
Hello,
This is to announce that, we have been able to pass-through a ATI
Radeon RV370 FireGL V3100 to Ubuntu VM. This card was attached to a
separate monitor, after passing-through the Keyboard and Mouse
everything worked as normal.
The
26 matches
Mail list logo
