similar to: Where is QXL driver for Windows?

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, 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

My windows client is using "generic display adapter" and not QXL. So I mount the VirtIO iso, open windows Manager, right click on Generic display display driver and select Update Driver, Browse to my iso, click qxl and there are only three listed. 2k8R2 w7 xp There is Windows 10. I am using that latest stable 1.1.85 iso. how do I get a VIrtio display driver for windows 10 ? Thanks,

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 https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win.iso Have

Hello, All! virtio-win.iso contains two different Windows drivers. these Windows Server 2012 R2 drivers have different hardware IDs: \vioscsi\2k12R2\amd64\vioscsi.inf "Red Hat VirtIO SCSI pass-through controller" PCI\VEN_1AF4&DEV_1004&SUBSYS_00081AF4&REV_00 PCI\VEN_1AF4&DEV_1048&SUBSYS_11001AF4&REV_01 \viostor\2k12R2\amd64\viostor.inf "Red Hat VirtIO SCSI

On 11/27/2015 01:32 PM, Patrick Laimbock wrote: > On 11/26/15 09:47, C. L. Martinez wrote: >> Hi all, >> >> I am trying to install nested Esxi 6.x under a Centos7 kvm host to >> use it as test lab for new ESXi versions, but I am doing something >> wrong because I can't install it. >> >> I have configured kvm and kvm_intel modules with the

On Tue, Apr 14, 2015 at 9:39 AM, Sven Kieske <s.kieske at mittwald.de> wrote: > > > On 14/04/15 11:16, C. L. Martinez wrote: >> Hi all, >> >> Anyone knows where virt-manager stores user config files in CentOS >> 7.1?? I am not seeing anything in user's home directory .... > > Hi, > > well on my standard machine virt-manager just starts with

On 11/27/2015 01:46 PM, Patrick Laimbock wrote: > On 11/27/15 14:40, C.L. Martinez wrote: > [snip] >>> >>> or with the e1000 nic: >>> >>> # virt-install --connect=qemu:///system -n esxi6 --cpu=host --vcpus=2 >>> --ram 4096 --os-type=linux >>> --cdrom=/var/lib/libvirt/images/VMware-VMvisor-Installer-6.0.0-2494585.x86_64.iso >>>

On Tue, Oct 13, 2015 at 1:45 PM, Richard <lists-centos at listmail.innovate.net> wrote: > >> Date: Tuesday, October 13, 2015 13:41:56 +0000 >> From: "C. L. Martinez" <carlopmart at gmail.com> >> >> >> On Tue, Oct 13, 2015 at 1:39 PM, Jonathan Billings >> <billings at negate.org> wrote: >>> On Tue, Oct 13, 2015 at

Not sure if this is a factor yet, but your forwardzone is looking for 3 ports but only 2 ports are configured in the systemd startup.. so are 1/3 of all lookups going to fail? Or is the 6355 a 'given' (aka it will be set up whether 6353 and 6354 are setup?) On 9 December 2017 at 16:45, C. L. Martinez <carlopmart at gmail.com> wrote: > On Sat, Dec 09, 2017 at 10:25:41PM +0100, C.

On Fri, Aug 25, 2017 at 04:54:54PM +0200, Sandro Bonazzola wrote: > 2017-08-13 13:50 GMT+02:00 C. L. Martinez <carlopmart at gmail.com>: > > > Hi all, > > > > I am trying to install oVirt 4.1.x from centos repos but it seems > > ovirt-engine doesn't exists. But instead, ovirt-hosted-engine-setup > > exists? > > > > Is ovirt-engine

On Fri, Sep 18, 2015 at 7:38 AM, Sandro Bonazzola <sbonazzo at redhat.com> wrote: > > > On Thu, Sep 17, 2015 at 6:15 PM, C. L. Martinez <carlopmart at gmail.com> > wrote: >> >> On Thu, Sep 17, 2015 at 6:06 PM, George Dunlap <dunlapg at umich.edu> wrote: >> > On Thu, Sep 17, 2015 at 3:19 PM, C. L. Martinez <carlopmart at gmail.com> >>

Otherwise ttm throws a WARN because we try to pin without a reservation. Fixes: 9d36d4320462 ("drm/qxl: switch over to the new pin interface") Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/qxl/qxl_object.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/qxl/qxl_object.c b/drivers/gpu/drm/qxl/qxl_object.c index

Otherwise ttm throws a WARN because we try to pin without a reservation. Fixes: 9d36d4320462 ("drm/qxl: switch over to the new pin interface") Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/qxl/qxl_object.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/qxl/qxl_object.c b/drivers/gpu/drm/qxl/qxl_object.c index

On Sat, Dec 09, 2017 at 03:03:52PM -0500, Stephen John Smoogen wrote: > On 9 December 2017 at 14:04, C. L. Martinez <carlopmart at gmail.com> wrote: > > Hi all, > > > > I have installed dnscrypt's rpm package from EPEL repo under a CentOS 7.4 and using unbound as a resolver. But, I see constant timeouts and responses are very slow ... Using same config in a Debian 9

This can be if one of these interfaces isn't a wireless nic. But I need to use a wireless nic and another phys nic. At least, I have solved the problem using network namespaces. All works ok and expected now. Many thanks to all for your help On Tue, Apr 04, 2017 at 10:39:05AM +0100, Nux! wrote: > Just create a bridge, hook the host physical interface that you want in it, hook the VMs

Problem: qxl switches from native mode back into vga compatibility mode when it notices someone is accessing vga registers. And vgacon does exactly that before fbcon takes over. So make sure we kick out vgacon early enough that it wouldn't disturb us. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/qxl/qxl_drv.c | 1 + 1 file changed, 1 insertion(+) diff

Problem: qxl switches from native mode back into vga compatibility mode when it notices someone is accessing vga registers. And vgacon does exactly that before fbcon takes over. So make sure we kick out vgacon early enough that it wouldn't disturb us. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/qxl/qxl_drv.c | 1 + 1 file changed, 1 insertion(+) diff

qxl has two modes: "native" (used by the drm driver) and "vga" (vga compatibility mode, typically used for boot display and firmware framebuffers). Accessing any vga ioport will switch the qxl device into vga mode. The qxl driver never does that, but other drivers accessing vga ports can trigger that too and therefore disturb qxl operation. So aquire the legacy vga ioports