similar to: Adjusting vram for windows/photoshop

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

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 > installed the Red Hat QXL driver in Windows. What driver did you installed? There are two drivers,

Using: edk2.git-0-20150803.b1141.ga0973dc.x86_64 edk2.git-ovmf-x64-0-20150802.b1139.gb234418.noarch On Fedora 22. Provisioning a i440FX system in virt-manager and attempting to boot results in successful EFI initialization, but the VM exits ungracefully after the bootloader (with F22 and CentOS 7 installer images). There's no really useful information in any of the logs. Using qemu-kvm

On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >On 08/03/2015 01:43 PM, Ryan Barry wrote: >> Using: >> >> edk2.git-0-20150803.b1141.ga0973dc.x86_64 >> edk2.git-ovmf-x64-0-20150802.b1139.gb234418.noarch >> >> On Fedora 22. >> >> Provisioning a i440FX system in virt-manager and attempting to boot >> results in successful EFI

On Tue, Aug 04, 2015 at 07:11:29AM -0700, Ryan Barry wrote: >On 08/03/2015 10:47 PM, Martin Kletzander wrote: >> On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >>> On 08/03/2015 01:43 PM, Ryan Barry wrote: >>>> Using: >>>> >>>> edk2.git-0-20150803.b1141.ga0973dc.x86_64 >>>>

On 08/03/2015 01:43 PM, Ryan Barry wrote: > Using: > > edk2.git-0-20150803.b1141.ga0973dc.x86_64 > edk2.git-ovmf-x64-0-20150802.b1139.gb234418.noarch > > On Fedora 22. > > Provisioning a i440FX system in virt-manager and attempting to boot > results in successful EFI initialization, but the VM exits ungracefully > after the bootloader (with F22 and CentOS 7

On 08/03/2015 10:47 PM, Martin Kletzander wrote: > On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >> On 08/03/2015 01:43 PM, Ryan Barry wrote: >>> Using: >>> >>> edk2.git-0-20150803.b1141.ga0973dc.x86_64 >>> edk2.git-ovmf-x64-0-20150802.b1139.gb234418.noarch >>> >>> On Fedora 22. >>> >>> Provisioning

On 08/06/2015 08:08 AM, Martin Kletzander wrote: > On Tue, Aug 04, 2015 at 07:11:29AM -0700, Ryan Barry wrote: >> On 08/03/2015 10:47 PM, Martin Kletzander wrote: >>> On Mon, Aug 03, 2015 at 03:39:30PM -0700, Ryan Barry wrote: >>>> On 08/03/2015 01:43 PM, Ryan Barry wrote: >>>>> Using: >>>>> >>>>>

Laine, Thank you for your response. I did use the numa element instead of using qemu commandline and that worked: 16 <cpu mode='custom' match='exact'> ... 34 <numa> 35 <cell id='0' cpus='0-1' memory='1048576' unit='KiB'/> 36 <cell id='1' cpus='2-3' memory='1048576'

After saving a particular VM running WinXP, any attempt to resume it (even when no other VM's are running) generates the following error: olympus ~ # virsh restore /var/lib/libvirt/qemu/save/WinXP.save error: Failed to restore domain from /var/lib/libvirt/qemu/save/WinXP.save error: internal error: Failed to reserve port 5908 This started sometimes towards the end of last year with only the

VirtIO DRM driver crashes when setting specific 16.16 fixed-point property values When running a virtual machine with a VirtIO GPU, it's possible to crash the entire VM by setting the value of a 16.16 fixed-point property to any value below 65536 (1.0 in 16.16 format or 0x00010000). As a specific example, setting the SRC_W property on a plane DRM object to a value of 30000 will cause the VM

VirtIO DRM driver crashes when setting specific 16.16 fixed-point property values When running a virtual machine with a VirtIO GPU, it's possible to crash the entire VM by setting the value of a 16.16 fixed-point property to any value below 65536 (1.0 in 16.16 format or 0x00010000). As a specific example, setting the SRC_W property on a plane DRM object to a value of 30000 will cause the VM

Thank you, Rich, This was the issue indeed. export LIBGUESTFS_BACKEND=direct fixed it. The next step I tried was to integrate libguestfs in collectd virt plugin to collect this data automatically. In this case I'm having an unknown error in add_libvirt_dom() (same with add_domain) when it's invoking qemu-img to create overlay image. There is no difference between manual and service

I would really appreciate some pointers on what I am doing wrong here. I have a need to run multiple virtual guests which have each their own GPU and some USB controllers passed-through. I am able to run one of the guests like this (assuming vfio stuff has happened elsewhere), but I would prefer to use virsh: kvm -M q35 -m 8192 -cpu host,kvm=off \ -smp 4,sockets=1,cores=4,threads=1 \ -bios

2016-02-18 11:25 GMT+01:00 Martin Kletzander <mkletzan@redhat.com>: > On Thu, Feb 18, 2016 at 10:41:42AM +0100, John Obaterspok wrote: > >> 2016-02-18 10:13 GMT+01:00 Martin Kletzander <mkletzan@redhat.com>: >> >> On Thu, Feb 18, 2016 at 08:49:38AM +0100, John Obaterspok wrote: >>> >>> Hello, >>>> >>>> I'm using

Hi, I'm investigating a performance issue on a virtualized windows server host that is run on a ubuntu machine via libvirt/qemu. While the host can easily read/write on the raid drive with 100Mmb/s as observable with dd, the virtualized windows server running on that host is barely able to read/write with at most 8Mb/s and averages around 1.4Mb/s. This has grown to the extent that the

Sorry for posting bad debug info. Here are the right one with the chardev error only: # virt-install --name f20vm --disk /home/kvmimages/f20vm --cdrom /home/kvmimages/Fedora-20-x86_64-DVD.iso --memory 2048 -d [dim., 15 juin 2014 10:56:25 virt-install 9795] DEBUG (cli:187) Launched with command line: /usr/share/virt-manager/virt-install --name f20vm --disk /home/kvmimages/f20vm --cdrom

Hello, Hope all is well. I've been looking at how I can create a virtual machine which is NUMA capable. I was able to do that by: 140 <qemu:commandline> 143 <qemu:arg value='-numa'/> 144 <qemu:arg value='node'/> 145 <qemu:arg value='-numa'/> 146 <qemu:arg value='node'/> 147 </qemu:commandline> This

Try setting autoport to yes in the graphics section of your xml... then libvirt will autosearch for a free port. You can get the port number by running 'ps aux | grep [vmname]' and look in the line for the port number. I gess you have another service running that is using port 5908... -----Oorspronkelijk bericht----- Van: libvirt-users-bounces@redhat.com

I am trying to connect a KVM-QEMU VM to OVS-DPDK vhostuser port. But, I am encountering a few errors. Since I am very new to libvrt and Linux I am not able to sort them out. Any guidance in this regard would be a great help. These are my System Logs: Mar 28 18:03:04 dpdk-OptiPlex-5040 libvirtd.service: 1529: debug : virCommandRunAsync:2429 : About to run LIBVIRT_LOG_OUTPUTS=3:stderr