similar to: virt-manager windows guest on CentOS 7

Am 03.02.2016 um 22:29 schrieb Alexander Dalloz: > Am 03.02.2016 um 17:40 schrieb C. L. Martinez: >> Hi all, >> >> Where can I found QXL driver for Windows 2012 R2/Windows 8.1? I >> don't see inside latest/stable iso images from fedoraproject ... >> >> Thanks. >> > > Don't know what you are checking, but it is definitely included in >

Hi, On Sun, Jul 23, 2017 at 3:45 PM, Pavel Hrdina <phrdina@redhat.com> wrote: > On Sat, Jul 22, 2017 at 03:03:06PM -0400, Alex wrote: >> Hi, >> I have a fedora25 system with a Windows10 host and would like to use >> it for photoshop. However, it complains the video memory is too low. >> I'm using the QXL driver and it appears to be limited to 256MB? I've

Hi all, Where can I found QXL driver for Windows 2012 R2/Windows 8.1? I don't see inside latest/stable iso images from fedoraproject ... Thanks. -- Greetings, C. L. Martinez

Hi, I have a fedora25 system with a Windows10 host and would like to use it for photoshop. However, it complains the video memory is too low. I'm using the QXL driver and it appears to be limited to 256MB? I've installed the Red Hat QXL driver in Windows. I have 4GB of memory allocated overall, and could allocate more if necessary. How do I increase the available video memory? Photoshop

Some virtio-win drivers contain more files than just *.{cat,inf,sys}. They are filtered out currently, which prevents the drivers from being installed by PnP. Stop filtering driver files by extension, and copy all of them instead. Signed-off-by: Roman Kagan <rkagan@virtuozzo.com> --- v1 -> v2: - update unit test to match the changed behavior v2v/v2v_unit_tests.ml | 202

Patch 1 moves the v2v/fake-virtio-win and v2v/fake-virt-tools directories to the recently created test-data/ hierarchy. This is just refactoring with no functional change at all. Patches 2-4 then extend the available (fake) virtio-win drivers: - Patch 2 adds all of the drivers from the virtio-win RPM. - Patch 3 adds all of the drivers from the virtio-win ISO (which are different from the

On Tue, Nov 17, 2015 at 08:49:54PM +0000, Richard W.M. Jones wrote: > There was a copy and paste error. It should have read: > > $ md5sum viostor/2k8/amd64/* viostor/w7/amd64/* > d1132fbd27c98f25ea71a6eb4037b2f8 viostor/2k8/amd64/viostor.cat > defccbe48aca1cd97fee4d7b16053b72 viostor/2k8/amd64/viostor.inf > 6da6120368c097806e4ac7fc6b940810 viostor/2k8/amd64/viostor.pdb >

Since v1: - Fix a bug in the calculation of lc_basename. By luck this doesn't affect anything given the contents of the current ISO. - Don't copy the WdfCoInstaller*.dll files. Rich.

v2 -> v3 - Don't make a special case for WdfCoInstaller* files. There is a difference of opinion about whether copying these is necessary, but it seems like it is not harmful. Rich.

Instead of trying to split and parse elements from virtio-win paths, use the '*.inf' files supplied with the drivers to control how Windows drivers are installed. The following emails best explain how this works: https://www.redhat.com/archives/libguestfs/2015-October/msg00352.html https://www.redhat.com/archives/libguestfs/2015-November/msg00065.html Currently the product variant (eg.

https://github.com/rwmjones/libguestfs/tree/rewrite-virtio-copy-drivers Instead of trying to split and parse elements from virtio-win paths, use the '*.inf' files supplied with the drivers to control how Windows drivers are installed. The following emails best explain how this works: https://www.redhat.com/archives/libguestfs/2015-October/msg00352.html

I am trying to use the Video Virtio device and set it to Virtio (to get resolutions higher that 800x600). My host is CentOS 7 and my guest is CentOS 8. When I set the virtio for video - I get an add about QEMU does not support 'virtio' video device. Do I not have something loaded ? Real question is how to get video higher than 800x600. I tried every selection there Cirrus , QXL, VGA,

I''ve been trying to have all spice features working on xen domUs since the end of 2011. Basic functions were already working. Adding qemu parameters manually for vdagent and usbredirection was and is also working (I made the patches to support them directly on xl). Qxl was never working: one bug on xen and one on qemu about qxl are fixed, the other xen bug found months ago on the

I think one - maybe final? - problem. How can I tell the difference between drivers for "client" versions of Windows (eg. Windows 7) and server versions of Windows (eg. Windows 2008 Server)? It seems in many or most cases the drivers are identical, eg: $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat

Hi Pino, On 2/26/19 5:52 PM, Mike Latimer wrote: > On 2/21/19 3:07 AM, Pino Toscano wrote: >> My question is: is using cirrus still the best choice for SUSE guests? >> If not, what about using qxl as well, as done for any non-SUSE guest? >> (We can also do that depending on the version of the guest, in case >> only newer SUSE versions work fine with qxl). > At the

Hi Mike, in 2013 you added the support for SUSE guests in the old virt-v2v (the one written in Perl); the commit doing it is attached, since the old virt-v2v was hosted on fedorahosted.org, which is no more. As part of that change, the default graphics driver was changed to be cirrus for SUSE guests, and qxl (as before) for any other. When Rich Jones rewrote virt-v2v in 2014 in OCaml, he kept

The guest was setup through virt-manager. The machine is not configured much after a F20 install (I believe I didn't change any network things) Here is the network part: <interface type='direct'> <mac address='52:54:00:fe:b0:66'/> <source dev='em1' mode='bridge'/> <target dev='macvtap0'/> <model

I am not sure this issue is tight to Red Hat qxl GPU driver, but I can't initialize directxX on a guest windows 7. Trying to start a game, I get the error message : Failed to initialize directX Of course, directX is installed on the w7 guest, and properly. The dxdiag command, a directx diagnostic tool, does not show any error. Some summary under the video : Driver name : Red Hat QXL GPU

Libguestfs supports passing an ISO image as a source of virtio windows drivers to v2v. That support, however, looks too heavy-weight: in order to access those drivers, a separate guestfs handle is created (and thus a new emulator process is started), which runs until v2v completes. This series attempts to make it simpler and lighter-weight, by making the relevant code more local, and by