Re: [CentOS-virt] OS-level virtualization using LXC and systemd-nspawn containers

2021-01-26 Thread Gena Makhomed
On 26.01.2021 20:24, Scott Dowdle wrote: Ok, so you are turning off SELinux and using ZFS too? And you still want to stay with EL? Why? RHEL is more stable than Ubuntu, it has 10 year support and rpm installs silently without additional questions and dialogues, as it in deb world. dnf / yum

Re: [CentOS-virt] OS-level virtualization using LXC and systemd-nspawn containers

2021-01-26 Thread Gena Makhomed
On 26.01.2021 18:41, Scott Dowdle wrote: Have you tried LXD? Not yet. My first post on this mailing list asked if anyone was using LXC in production: Does anyone use LXC and/or systemd-nspawn containers on RHEL 8 / CentOS 8 for production? What are advantages and disadvantages of each of the

Re: [CentOS-virt] OS-level virtualization using LXC and systemd-nspawn containers

2021-01-26 Thread Gena Makhomed
On 26.01.2021 0:05, Scott Dowdle wrote: OpenVZ 7 has no updates, and therefore is not suitable for production. The free updates lag behind the paid Virtuozzo 7 version and plenty of people are using it in production. I'm not one of those. See all released OpenVZ 7 updates: http://ftp.neti

Re: [CentOS-virt] OS-level virtualization using LXC and systemd-nspawn containers

2021-01-25 Thread Gena Makhomed
On 25.01.2021 22:24, Scott Dowdle wrote: I found only two possible free/open source alternatives for OpenVZ 6: - LXC - systemd-nspawn Some you seem to have overlooked?!? 1) OpenVZ 7 2) LXD from Canonical that is part of Ubuntu 3) podman containers with systemd installed (set /sbin/init as t

[CentOS-virt] OS-level virtualization using LXC and systemd-nspawn containers

2021-01-25 Thread Gena Makhomed
Hello All, OpenVZ 6 in the past was a very popular technology for creating OS-level virtualization containers. But OpenVZ 6 is EOL now (because RHEL 6 / CentOS 6 is EOL) and all OpenVZ 6 users should migrate to some alternatives. I found only two possible free/open source alternatives for OpenV

Re: [CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

2018-05-15 Thread Gena Makhomed
On 15.05.2018 13:52, Sandro Bonazzola wrote: failure: repodata/repomd.xml from centos-qemu-ev: [Errno 256] No more mirrors to try. http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/ repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Something wrong with $contentdir variable,

Re: [CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

2018-05-15 Thread Gena Makhomed
Hello, Sandro! On 15.05.2018 13:24, Gena Makhomed wrote: failure: repodata/repomd.xml from centos-qemu-ev: [Errno 256] No more mirrors to try. http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found I found workaround: # diff -u

[CentOS-virt] centos-qemu-ev repository not work for x86_64 arch on CentOS 7.5

2018-05-15 Thread Gena Makhomed
Hello, Sandro! On 11.05.2018 12:19, Sandro Bonazzola wrote: Sadly, the new qemu-kvm-ev we prepared for CentOS 7.5 didn't get released ( https://bugs.centos.org/view.php?id=14764) but the new build is ready. After installing CentOS 7.5 and installing package qemu-kvm-ev I can't install KVM on

Re: [CentOS-virt] Red Hat VirtIO SCSI pass-through controller

2017-03-15 Thread Gena Makhomed
On 14.03.2017 20:05, Gena Makhomed wrote: When I use "VirtIO SCSI controller" in virt-manager, and when I install Windows Server 2012 R2 - I can use only viostor driver and can't use vioscsi driver, Windows Server 2012 R2 can't load vioscsi driver (?) from virtio-win.iso and

Re: [CentOS-virt] Red Hat VirtIO SCSI pass-through controller

2017-03-15 Thread Gena Makhomed
On 15.03.2017 17:42, Jean-Marc LIGER wrote: When I use "VirtIO SCSI controller" in virt-manager, and when I install Windows Server 2012 R2 - I can use only viostor driver and can't use vioscsi driver, Windows Server 2012 R2 can't load vioscsi driver (?) from virtio-win.iso and did not see virtua

[CentOS-virt] Red Hat VirtIO SCSI pass-through controller

2017-03-14 Thread Gena Makhomed
Hello, All! virtio-win.iso contains two different Windows drivers. these Windows Server 2012 R2 drivers have different hardware IDs: \vioscsi\2k12R2\amd64\vioscsi.inf "Red Hat VirtIO SCSI pass-through controller" PCI\VEN_1AF4&DEV_1004&SUBSYS_00081AF4&REV_00 PCI\VEN_1AF4&DEV_1048&SUBSYS_11001AF4&

Re: [CentOS-virt] kvm-qemu-ev in testing

2015-12-19 Thread Gena Makhomed
On 30.11.2015 19:02, Jean-Marc LIGER wrote: Is it possible to add patch https://bugzilla.redhat.com/show_bug.cgi?id=1248758 into qemu-kvm-ev from Red Hat, oVirt and cbs/centos ? Could you rediff this patch for qemu-kvm-ev 2.3.0 series ? I am already wasting too many time for this patch...

Re: [CentOS-virt] kvm-qemu-ev in testing

2015-10-30 Thread Gena Makhomed
On 29.10.2015 0:00, Sandro Bonazzola wrote: it will be in http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/ enabled by http://mirror.centos.org/centos/7/extras/x86_64/Packages/centos-release-qemu-ev-1.0-1.el7.noarch.rpm Is it possible to add patch https://bugzilla.redhat.com/show_bug.c

Re: [CentOS-virt] Adding customized options to qemu command line

2015-08-18 Thread Gena Makhomed
On 18.08.2015 14:44, C. L. Martinez wrote: How can I add some options to qemu command line when a kvm guest starts up from libvirtd?? # virsh edit vm-name 1. change first line from to 2. add before tag 3. if you need qemu options for adding SLIC table - also you need pa

Re: [CentOS-virt] qemu-kvm SLIC acpitable workaround of Windows bug

2015-07-31 Thread Gena Makhomed
On 31.07.2015 10:19, Sandro Bonazzola wrote: https://bugzilla.redhat.com/show_bug.cgi?id=1248758 Have you checked 3.5.4 RC or CentOS Virt SIG[2] to see if the bug has been fixed in latest qemu-kvm-ev ? [1] http://resources.ovirt.org/pub/ovirt-3.5-pre/ [2] http://cbs.centos.org/repos/virt7-kv

Re: [CentOS-virt] qemu-kvm-ev with CentOS 7.1

2015-07-31 Thread Gena Makhomed
On 30.07.2015 15:25, Sandro Bonazzola wrote: Note that qemu-kvm-ev is built within Virt SIG too in kvm-common-testing CBS repo Packages from kvm-common-testing probably is not a good choice for using in production environment. I found in internet package http://cbs.centos.org/repos/virt7-kvm-

[CentOS-virt] qemu-kvm SLIC acpitable workaround of Windows bug

2015-07-30 Thread Gena Makhomed
On 30.07.2015 10:49, Nux! wrote: Then you should definitely submit a bug with redhat about this, seems like a serious one. Ok, done: https://bugzilla.redhat.com/show_bug.cgi?id=1248758 P.S. As I can see - bugzilla.redhat.com for oVirt Product does not contain qemu-kvm-ev Component at all -

[CentOS-virt] CentOS 7.1 + qemu-kvm-ev + SLIC acpitable windows bug workaround

2015-07-29 Thread Gena Makhomed
On 29.07.2015 21:34, Nux! wrote: Yes, you can. In fact you can use the binaries from the ovirt repo itself, no need to rebuild. Thank you! In fact - I can't use raw binaries from the ovirt repo itself, because these qemu-kvm binaries contains one bug, which is already fixed in Debian: If you

[CentOS-virt] qemu-kvm-ev with CentOS 7.1

2015-07-29 Thread Gena Makhomed
Hello, All! Is it possible to use binary packages build from http://resources.ovirt.org/pub/ovirt-3.5/rpm/el7/SRPMS/qemu-kvm-ev-2.1.2-23.el7_1.3.1.src.rpm with plain CentOS 7.1 and use all other packages from CentOS (libvirt, virt-manager, etc) Is it have reasons, if I not use live migrations an