similar to: KVM (Centos 6.3 64bit): Windowx XP is very slow

Hi. I've been running CentOS 5 for ages. (Thanks!) I went to install 6.3 - I downloaded the 64-bit DVD 1 image, and put it on a USB drive. Booted into a screen that said boot will start in 10.. 9... 8.. 7.. 6.. 5.. 4.. 3.. 2.. 1.. 10.. and so on, infinite loop, the boot never starts. I tried booting in text mode, but it doesn't boot, just goes back to the menu. Is there some way to

I am running KVM on Centos 6.3 and am seeing an unexplained shut down of two guests. The libvirt package was upgraded to libvirt-0.10.2-18.el6_4.4.x86_64 at the time of the shutdown. Only the two guests shown below was affected, while 9 others running on the same hypervisor were not. Can some one help me to find the cause please ? Regards Chandana GUEST #1 ======== 2013-04-10

Hi all, I've got a weird issue, and I'm trying to confirm if it's a bug, and if so, if there is a workaround until it is fixed. The situation is this: If I virsh reboot <domain> --mode acpi, it will actually reboot the domain cleanly (watching from the console allows me to see the full shutdown messages, followed by a bootup). However, after this point, virsh domstate

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

WinXP ignores a USB passthrough! Hello, I need a persistent passthrough of a USB-device: Bus 001 Device 020: ID 04e6:5311 SCM Microsystems, Inc. I added <hostdev mode='subsy.... </hostdev> like this to xml file: [...] <on_crash>restart</on_crash> <devices> <hostdev mode='subsystem' type='usb' managed='no'>

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

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 Thu, Feb 18, 2016 at 08:49:38AM +0100, John Obaterspok wrote: >Hello, > >I'm using virt-manager on my F23 box to run a Windows 10 image but the >performance is so bad it's killing me. > >I have "vmx" flag in /proc/cpuinfo > ># lsmod |grep kvm >kvm_intel 167936 6 >kvm 503808 1 kvm_intel >

Is the rsync a first copy or are you overwriting a previous copy. How fast is the transfer rate with scp? -----Oorspronkelijk bericht----- Van: Alex Regan [mailto:mysqlstudent@gmail.com] Verzonden: maandag 29 juni 2015 4:46 Aan: libvirt-users@redhat.com Onderwerp: [libvirt-users] Slow network performance issues Hi, I have a fedora21 system that's been running fine under normal network

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.

Libvirt doesn't care about security during hot add disk images. It even accepts addition of disk images of other guest running on the host. Steps followed to create this scenario : Started two VMs with following security configurations: vm1: <seclabel type='dynamic' model='selinux' relabel='yes'>

Hello list, In short: I am experiencing a problem where trying to start a VM which is allready running on a different libvirt host. Starting it fails, thanks to sanlock, but the disk dies on the original hypervisor and the vms filesystem is rendered read-only. Long version: i have the following setup: Two machines (H1 and H2) using CentOS 6.2 with the packages:

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

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

I'm looking for assistance with pci-passthrough on CentOS 6.2. I've installed libvirt version: 0.9.4, package: 23.el6_2.8 from yum. I have a windows XP client setup via virt-manager which boots and runs fine until I attempt to assign a PCI device to it. The error log reads: -----------------/var/log/libvirt/qemu/SageTv.log---------------- 2012-06-02 22:55:07.801: starting up LC_ALL=C

Hello, I'm using virt-manager on my F23 box to run a Windows 10 image but the performance is so bad it's killing me. I have "vmx" flag in /proc/cpuinfo # lsmod |grep kvm kvm_intel 167936 6 kvm 503808 1 kvm_intel virtio-win-0.1.112-1.noarch But no virtio modules loaded. Should they be loaded nowadays? The disk format used is vmdk with no

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,

I've "ported" an old VMware VM containing Windows NT 4 SP6 into libvirt/kvm/qemu and got it running (more or less). However, the CPU graph next to the VM in virt-manager shows it starts using 100% of the allocated CPU as soon as it reaches the "OS Loader" screen, and stays there even after Windows has booted and I've logged in. (There's a dip now and then,

Hello, I'm trying to test what found here: http://blog.wikichoon.com/2016/05/spice-openglvirgl-acceleration-on.html and here: https://www.kraxel.org/blog/tag/virgl/ My system is a fedora 25 laptop, born in version 23 and gradually updated to 24 and 25 now. I had a fedora 25 guest that worked ok with "normal"spice and I'm trying to configure with virgl Main components currently