similar to: New error: Failed to create chardev

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

On 11/17/2013 09:18 PM, Matthew Harrold wrote: > On Sun, Nov 17, 2013 at 7:44 PM, Cole Robinson <crobinso@redhat.com > <mailto:crobinso@redhat.com>> wrote: > On 11/17/2013 01:26 PM, Matthew Harrold wrote: > > Hi All. > > > > I'm trying to setup a guest within my hypervisor that acts as a Console > > Server, using 10 USB

Hi All. I'm trying to setup a guest within my hypervisor that acts as a Console Server, using 10 USB to Serial adapters. The Host is all setup and can access each Serial Port without problems. I have attempted to add the Serial Connections to a Guest, using both Virtual Machine Manager and by editing the .XML file, and I can add up to 4 Serial devices (Including one for console access to the

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

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 2015-02-26 17:05, Kashyap Chamarthy wrote: > On Tue, Feb 24, 2015 at 11:56:50PM +0100, Olivier Mauras wrote: > >> On Tue, 2015-02-24 at 16:05 -0500, Laine Stump wrote: >> >>> On 02/24/2015 03:37 PM, Olivier Mauras wrote: >>> >>>>> Hello, I've been trying to boot a VM with the rootfs being a 9P share from the host. The VM OS is centos

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

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

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

Hi, When I'm trying to run qemu-kvm command on RHEL6(linux kernel 2.6.32) then I get following errors which I think related to tap devices in my setup. Any idea why is that? bash$ LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name instance-00000027 -uuid

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

On 10/03/2017 04:40 PM, Nick Gilmour wrote: > 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 >

Dear all, I install centos 6.3-64bit in a new server and also installed KVM using yum. Then I create a new virtual machine(i686) to install windows xp, but it's very slow, do you know why? Server: CPU: i7 3370, Memory: 16GB. Virtual machine: 1 cpu and 1GB ram. type: i686 KVM information: qemu 4223 1 9 15:10 ? 00:00:41 /usr/libexec/qemu-kvm -S -M rhel6.3.0 -cpu

On Thu, Nov 14, 2013 at 12:48:51PM +1300, Christian Gagneraud wrote: > On 14/11/13 10:53, Christian Gagneraud wrote: > >Hi there, > > > >I have used qemu to install FreeBSD 9.2 release, and i can boot it fine > >with: > >$ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img > > > >I then made virsh aware of my brand new VM (see attached XML),

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,

On 14/11/13 10:53, Christian Gagneraud wrote: > Hi there, > > I have used qemu to install FreeBSD 9.2 release, and i can boot it fine > with: > $ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img > > I then made virsh aware of my brand new VM (see attached XML), but when > i run it via virsh, It hangs after the bootloader whith this message: > Booting... >

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,

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