similar to: Libvirt: dynamic ownership did not work

Am Do, 4. Aug, 2016 um 1:38 schrieb Michal Privoznik <mprivozn@redhat.com>: > On 04.08.2016 12:12, Jonatan Schlag wrote: >> >> >> Am Do, 4. Aug, 2016 um 11:32 schrieb Michal Privoznik >> <mprivozn@redhat.com>: >>> On 03.08.2016 21:17, Jonatan Schlag wrote: >>>> Hi, >>>> I have a very strange problem with libvirt. I

Am Do, 4. Aug, 2016 um 11:32 schrieb Michal Privoznik <mprivozn@redhat.com>: > On 03.08.2016 21:17, Jonatan Schlag wrote: >> Hi, >> I have a very strange problem with libvirt. I work on some machines >> with >> libvirt (Debian/ Arch Linux) and libvirt set the ownership of images >> file automatically to the qemu user / group for example on Arch

@Michal: Thanks for your reply! Indeed I have found a package in the AUR (libvirt-zfs) and only had to change to the current version and add zfs-utils as dependency in the PKGBUILD. Now I don't get the previous error anymore but I still cannot setup a VM because I constantly get errors due to wrong permissions. I have tried to change the permissions in: - /etc/libvirt/qemu.conf -

Am Do, 4. Aug, 2016 um 5:07 schrieb Michal Privoznik <mprivozn@redhat.com>: > On 04.08.2016 13:59, Jonatan Schlag wrote: >> >> >> Am Do, 4. Aug, 2016 um 1:38 schrieb Michal Privoznik >> <mprivozn@redhat.com>: >>> On 04.08.2016 12:12, Jonatan Schlag wrote: >>>> >>>> >>>> Am Do, 4. Aug, 2016 um 11:32

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

On 04.08.2016 12:12, Jonatan Schlag wrote: > > > Am Do, 4. Aug, 2016 um 11:32 schrieb Michal Privoznik > <mprivozn@redhat.com>: >> On 03.08.2016 21:17, Jonatan Schlag wrote: >>> Hi, >>> I have a very strange problem with libvirt. I work on some machines >>> with >>> libvirt (Debian/ Arch Linux) and libvirt set the ownership of images

On 04.08.2016 13:59, Jonatan Schlag wrote: > > > Am Do, 4. Aug, 2016 um 1:38 schrieb Michal Privoznik <mprivozn@redhat.com>: >> On 04.08.2016 12:12, Jonatan Schlag wrote: >>> >>> >>> Am Do, 4. Aug, 2016 um 11:32 schrieb Michal Privoznik >>> <mprivozn@redhat.com>: >>>> On 03.08.2016 21:17, Jonatan Schlag wrote:

On 03.08.2016 21:17, Jonatan Schlag wrote: > Hi, > I have a very strange problem with libvirt. I work on some machines with > libvirt (Debian/ Arch Linux) and libvirt set the ownership of images > file automatically to the qemu user / group for example on Arch Linux to > nobody:kvm. > So when I copy an image file with root and use I then with qemu, libvirt > change the owner/

Any error in your host logs? On Sunday, 30 October 2016, Steven Tardy <sjt5atra at gmail.com> wrote: > > > On Oct 30, 2016, at 3:27 AM, Paul R. Ganci <ganci at nurdog.com > <javascript:;>> wrote: > > > > grub> set root=(hd0,msdos2) > > grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 > root=(hd0,msdos2)/ > > grub> initrd

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

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

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

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

Greetings, I have two machines running the same distro, both running qemu 5.1.0, one runs libvirt 6.7.0, the other 6.8.0. I've decided to test the viability of passing through my sata cdrom into a vm, so I went to the libvirt docs, read a bit and added the following to a debian10 uefi vm running on libvirt 6.8.0: <controller type='scsi' index='0'

Hello, CentOS 7.2 I have three Server on all is now broken the KVM System, it is not possible to start KVM Clients ? Have any a hint why ? Thanks for a answer -- mit freundlichen Gr??en / best regards, G?nther J. Niederwimmer

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