similar to: CentOS 8 VM 800x600

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,

Hi, I am trying to access my Galaxy Tab from Samsung KIES running on Windows 7 inside a KVM VM. This unfortunately does not seem to work as expected. My Distribution is debian unstable. I therefore have qemu-system-x86 version 1.4.0+dfsg-1exp, libvirt 1.0.3-1 and virt-manager 0.9.4-2. lsusb shows the Tab as follows: Bus 001 Device 016: ID 04e8:6877 Samsung Electronics Co., Ltd Galaxy S in

On 10/30/2016 07:33 AM, FrancisM wrote: > Any error in your host logs? Nothing obvious. I checked /var/log/messages, /var/log/libvirt/qemu, /var/log/libvirt/lxc & /var/log/qemu-ga. The /var/log/libvirt/lxc & /var/log/qemu-ga were empty. The /var/log/libvirt/qemu directory had a log file of interest Outgoing-CentOS-7-VM.log but nothing in it that tells me anything obvious.

On Tue, Jun 20, 2017 at 06:23:39AM +0000, Andy Gibbs wrote: >Hi, > > >I have created a VM with the option inside virt-manager to "start virtual machine on host boot up". It is the only VM on the host to be configured this way. However, I am getting this error in the log file when it attempts to start it on boot up: > > >2017-06-19 07:15:18.491+0000: starting up

On 06/29/2015 02:04 PM, Kanwar Ranbir Sandhu wrote: > On Mon, 2015-06-29 at 13:47 -0700, Greg Bailey wrote: >> I've installed it on a KVM guest on a CentOS 7 host. > > I was hoping it wasn't going to come to that. That is, I hope it's not a > CentOS 6 issue. > >> I've always had more success using the drivers obtained from running the >> spice guest

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

Hi all, I successfully virt-p2v'ed a Windows 10 laptop to my Centos 7.3 instance running KVM. However, on boot, the guest hangs. Is there a registry fix that is needed after the P2V is done? Here is what is in the guest's logfile: 017-01-08 03:20:37.508+0000: starting up libvirt version: 2.0.0, package: 10.el7_3.2 (CentOS BuildSystem <http://bugs.centos.org>, 2016-12-06-19:53:38,

Hi, I have created a VM with the option inside virt-manager to "start virtual machine on host boot up". It is the only VM on the host to be configured this way. However, I am getting this error in the log file when it attempts to start it on boot up: 2017-06-19 07:15:18.491+0000: starting up libvirt version: 2.0.0, package: 10.el7_3.9 (CentOS BuildSystem

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

I have set root in both for user and group in the qemu.conf and changed the file permissions to root like it was before. Now I'm getting this error: *# Error 1#* *Unable to complete install: 'internal error: process exited while connecting to monitor: us=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device

Hi, On a Fedora 18, I try to launch a VM with QEMU-GlusterFS native integration. I have enable fedora-virt-preview repo, and gluster-alpha3 repo. Below the list of installed package : glusterfs-3.4.0-0.3.alpha3.fc18.x86_64 glusterfs-devel-3.4.0-0.3.alpha3.fc18.x86_64 glusterfs-fuse-3.4.0-0.3.alpha3.fc18.x86_64 glusterfs-server-3.4.0-0.3.alpha3.fc18.x86_64

Am Donnerstag, 17. M?rz 2016, 08:57:40 CET schrieb Gordon Messmer: > On 03/17/2016 08:26 AM, G?nther J. Niederwimmer wrote: > > Have any a hint why ? The Problem is starting on three different Server, near to the same time ???? This is my Panic Situation. > You're going to have to provide logs, or error messages, or something. This is a a log from a client ? starting up

> install spice-vdagent Thanks - I installed the above. rebooted I only have 800x600 still. I have the video set for QXL Jerry

I use the video driver for optimal performance. You can download it here: http://www.spice-space.org/download.html Maybe installing this driver on the guest will resolve your issues. Van: libvirt-users-bounces@redhat.com [mailto:libvirt-users-bounces@redhat.com] Namens Ruzsinszky Attila Verzonden: woensdag 12 augustus 2015 11:31 Aan: libvirt-users@redhat.com Onderwerp: [libvirt-users] W2k3 with

Adam Jackson (1): Use pci_io_write8 instead of outb Christophe Fergeau (16): Remove unused variables Remove stray blank comment line Use <> for system-includes Fix compilation with newer Xorg versions Add missing licence header Add note about deprecated setting of mm_time Xspice: Fix 'erorr' typo in error message xspice:

Il 27/05/2014 17:05, Fabio Fantoni ha scritto: > Usage: > vga="qxl" > > Qxl vga support many resolutions that not supported by stdvga, > mainly the 16:9 ones and other high up to 2560x1600. > With QXL you can get improved performance and smooth video also > with high resolutions and high quality. > Require their drivers installed in the domU and spice used >

Hi, Is that possible? If I start in normal VGA mode I can see yellow ! next to the 2nd and 3rd QXL card and Win complains about can't start (Code 10). If I want to change the normal VGA resolution in a higher res (for example 800x600) I got black screen in virt-manager. I use SPICE protocol (for more screens). Any solution? W2k3 R2 Ent. Ed. SP2 TIA, Ruzsi

Usage: spicevdagent=1|0 (default=0) Enables spice vdagent. The Spice vdagent is an optional component for enhancing user experience and performing guest-oriented management tasks. Its features includes: client mouse mode (no need to grab mouse by client, no mouse lag), automatic adjustment of screen resolution, copy and paste (text and image) between client and domU. It also requires vdagent

- Enable vdagent on upstream qemu if spice is used. Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> --- tools/libxl/libxl_dm.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c index a8a36d7..110f1dc 100644 --- a/tools/libxl/libxl_dm.c +++ b/tools/libxl/libxl_dm.c @@ -427,6 +427,10 @@ static char **

Hi, I have a fedora21 system that's been running fine under normal network activity, but trying to perform a full backup of the 300GB filesystem is taking forever because the network speed appears to be very slow. Using rsync, the transfer speeds reach a max of like 180kB/s. Using rsync to copy files on the local filesystem is greater than 55MB/s, so I don't think it's a disk