similar to: Running libvirtd inside chroot (mock to be precise)

Displaying 20 results from an estimated 1000 matches similar to: "Running libvirtd inside chroot (mock to be precise)"

2017 Oct 19
0
Fwd: terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
Hello, I use libvirt 3.3.0 and qemu 2.9.0 My domain XML spec is the following: <domain type='qemu'> <name>s390_generic</name> <uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu
2017 Oct 20
0
Re: terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
On Thu, Oct 19, 2017 at 09:11:00PM +0300, Matwey V. Kornilov wrote: >Hello, > >I use libvirt 3.3.0 and qemu 2.9.0 > >My domain XML spec is the following: > ><domain type='qemu'> > <name>s390_generic</name> > <uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid> > <memory unit='KiB'>1048576</memory> >
2017 Oct 20
0
Re: terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
2017-10-20 17:14 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: > 2017-10-20 15:16 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: >> On Fri, Oct 20, 2017 at 03:07:19PM +0300, Matwey V. Kornilov wrote: >>> >>> 2017-10-20 14:59 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: >>>> >>>> On Thu, Oct 19, 2017 at
2017 Oct 25
0
Re: terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
2017-10-24 12:58 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: > On Fri, Oct 20, 2017 at 10:12:19PM +0300, Matwey V. Kornilov wrote: >> >> 2017-10-20 17:14 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: >>> >>> 2017-10-20 15:16 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: >>>> >>>> On Fri, Oct 20, 2017
2017 Oct 25
2
Re: terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
2017-10-25 17:28 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: > 2017-10-24 12:58 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: >> On Fri, Oct 20, 2017 at 10:12:19PM +0300, Matwey V. Kornilov wrote: >>> >>> 2017-10-20 17:14 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: >>>> >>>> 2017-10-20 15:16
2017 Oct 19
2
terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
Hello, I use libvirt 3.3.0 and qemu 2.9.0 My domain XML spec is the following: <domain type='qemu'> <name>s390_generic</name> <uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu
2017 Oct 20
3
Re: terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
2017-10-20 14:59 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: > On Thu, Oct 19, 2017 at 09:11:00PM +0300, Matwey V. Kornilov wrote: >> >> Hello, >> >> I use libvirt 3.3.0 and qemu 2.9.0 >> >> My domain XML spec is the following: >> >> <domain type='qemu'> >> <name>s390_generic</name> >>
2020 May 16
1
Stuck Centos 7 to 8 upgrade
Four problems below: # dnf -y groupupdate "Core" "Minimal Install" bintray-tvheadend-stable 0.0? B/s |?? 0? B???? 00:00 Failed to synchronize cache for repo 'bintray-tvheadend-stable', ignoring this repo. Last metadata expiration check: 0:03:11 ago on Sat 16 May 2020 12:30:47 PM CDT. Error: ?Problem 1: package python3-hawkey-0.35.1-9.el8_1.x86_64 requires
2017 Oct 24
2
Re: terminating on signal 15 from pid 2146 (/usr/sbin/libvirtd)
On Fri, Oct 20, 2017 at 10:12:19PM +0300, Matwey V. Kornilov wrote: >2017-10-20 17:14 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: >> 2017-10-20 15:16 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: >>> On Fri, Oct 20, 2017 at 03:07:19PM +0300, Matwey V. Kornilov wrote: >>>> >>>> 2017-10-20 14:59 GMT+03:00 Martin Kletzander
2020 Mar 16
2
CentOS rpm versioning
Hello Clair vulnerability scanner considers the latest version of CentOS mariadb vulnerable, because of RHSA-2019:3708 It states, that mariadb must be updated at least to the version "10.3.17-1.module+el8.1.0+3974+90eded84". CentOS' last version is "10.3.17-1.module_el8.1.0+257+48736ea6". Rpm/yum considers CentOS' version older, than RHEL's. % rpmdev-vercmp
2013 Apr 19
0
Unexplained shutdown of VM on upgrade of libvirt package
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
2020 Mar 16
0
CentOS rpm versioning
On Mon, 16 Mar 2020 at 12:17, koka miptpatriot <miptpatriot at gmail.com> wrote: > Hello > > Clair vulnerability scanner considers the latest version of CentOS mariadb > vulnerable, because of RHSA-2019:3708 > It states, that mariadb must be updated at least to the version > "10.3.17-1.module+el8.1.0+3974+90eded84". CentOS' last version is >
2020 Oct 15
2
Re: scsi passthrough differs between guests
Greetings Peter, > Sent: Thursday, October 15, 2020 at 9:52 AM > From: "Peter Krempa" <pkrempa@redhat.com> > To: "daggs" <daggs@gmx.com> > Cc: "libvirt-usersredhat.com" <libvirt-users@redhat.com> > Subject: Re: scsi passthrough differs between guests > > I don't see anything wrong with you configs. There were some changes
2017 Nov 23
1
Re: failure to virt-sysprep (FC27?)
On Thu, Nov 23, 2017 at 4:05 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Thu, Nov 23, 2017 at 03:00:45PM +0200, Yaniv Kaul wrote: > > On Thu, Nov 23, 2017 at 10:57 AM, Richard W.M. Jones <rjones@redhat.com> > > wrote: > > > > > On Tue, Nov 21, 2017 at 11:43:54PM +0200, Yaniv Kaul wrote: > > > > Since I upgrading to FC27, I
2020 Oct 13
2
Re: virt-sparsify failed (was: [oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 479 - Failure!)
On Mon, Oct 12, 2020 at 9:05 AM Yedidyah Bar David <didi@redhat.com> wrote: > > Hi all, > > On Mon, Oct 12, 2020 at 5:17 AM <jenkins@jenkins.phx.ovirt.org> wrote: > > > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ > > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/479/ > >
2015 Mar 02
2
QEMU interface type=ethernet
With Libvirt under modern kernels, you can't use <interface type='ethernet'> unless QEMU is running as root. Running qemu as root is not ideal, but I was able to track down the issue to this linux change: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ca6bb5d7ab22ac79f608fe6cbc6b12de6a5a19f0 Which means that if you're seeing errors like this:
2018 Nov 12
1
virsh reboot "in shutdown" state?
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
2017 Nov 23
0
Re: failure to virt-sysprep (FC27?)
On Tue, Nov 21, 2017 at 11:43:54PM +0200, Yaniv Kaul wrote: > Since I upgrading to FC27, I *sometimes* fail to virt-sysprep. > The debug messages: > libguestfs: trace: set_verbose true > libguestfs: trace: set_verbose = 0 > libguestfs: create: flags = 0, handle = 0x7f4600005dd0, program = python2 > libguestfs: trace: set_program "lago" > libguestfs: trace:
2017 Nov 21
2
failure to virt-sysprep (FC27?)
Since I upgrading to FC27, I *sometimes* fail to virt-sysprep. The debug messages: libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: create: flags = 0, handle = 0x7f4600005dd0, program = python2 libguestfs: trace: set_program "lago" libguestfs: trace: set_program = 0 libguestfs: trace: add_drive_ro
2017 Nov 23
3
Re: failure to virt-sysprep (FC27?)
On Thu, Nov 23, 2017 at 10:57 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Tue, Nov 21, 2017 at 11:43:54PM +0200, Yaniv Kaul wrote: > > Since I upgrading to FC27, I *sometimes* fail to virt-sysprep. > > The debug messages: > > libguestfs: trace: set_verbose true > > libguestfs: trace: set_verbose = 0 > > libguestfs: create: flags = 0, handle =