similar to: libvirt machine type rhel6.6.0 on CentOS 7

Hi all, What are the differences between pc and q35?? By default, virt-manager+libvirt setups kvm guest machine as a pc-i440fx-rhel7.1.0. [hicheck at ckvm015 ~]$ /usr/libexec/qemu-kvm -machine ? Supported machines are: pc RHEL 7.1.0 PC (i440FX + PIIX, 1996) (alias of pc-i440fx-rhel7.1.0) pc-i440fx-rhel7.1.0 RHEL 7.1.0 PC (i440FX + PIIX, 1996) (default) pc-i440fx-rhel7.0.0

Hello I have recently had to reinstall Centos 7.5 to on host computer. I have not be able to set-up qemu to support the q35 chip set. I have several virtual machines that require q35. This is not my first install, I have configured libvirt on many machines in the past, it just worked, it has not required any manual configuration. [root at sj aadmin]# /usr/libexec/qemu-kvm -machine help

On Tue, Jun 19, 2018 at 11:37:46AM +0100, Richard W.M. Jones wrote: > QEMU for x86 supports two machine types, "pc" (emulating the ancient > Intel i440FX chipset originally used by the Pentium Pro), and "q35" > (https://wiki.qemu.org/Features/Q35). > > Currently virt-v2v does not set any machine type, so libvirt or the > target hypervisor will choose some

I am using a debian 9 guest, hosted on a ESXi platform with nested virtualisation enabled. On this debian 9 guest when I run libguesfs-test-tool, it fails with an error: "qemu-system-x86_64: /build/qemu-DqynNa/qemu-2.8+dfsg/target-i386/kvm.c:1805: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed." Instead when I use a wrapper script and hook it with the env

QEMU for x86 supports two machine types, "pc" (emulating the ancient Intel i440FX chipset originally used by the Pentium Pro), and "q35" (https://wiki.qemu.org/Features/Q35). Currently virt-v2v does not set any machine type, so libvirt or the target hypervisor will choose some default, probably i440fx. Newer versions of libvirt and QEMU will probably switch over to defaulting

QEMU for x86 supports two machine types, "pc" (emulating the ancient Intel i440FX chipset originally used by the Pentium Pro), and "q35" (https://wiki.qemu.org/Features/Q35). Currently virt-v2v does not set any machine type, so libvirt or the target hypervisor will choose some default, probably i440fx. The latest advice from the QEMU and libvirt communities is not to rely on

Hi everyone, Using the QEMU hypervisor, when a live disk snapshot is requested through libvirt, the request can fail if the underyling qemu binary lacks the snapshotting support. In python, we have something like libvirtError: Operation not supported: live disk snapshot not supported with this QEMU binary I'd like to detect ahead of time if the underlying QEMU can or cannot do

On Tue, Jun 19, 2018 at 12:12:30PM +0100, Richard W.M. Jones wrote: > On Tue, Jun 19, 2018 at 11:43:38AM +0100, Daniel P. Berrangé wrote: > > I'd encourage apps to check the capabilities XML to see what > > machine types are available. > > One issue is we don't always have access to the target hypervisor. > > For example in the Glance case we have to write

On Thursday, 19 July 2018 15:51:04 CEST Tomáš Golembiovský wrote: > Add oVirt specific elemnt to OVF. It represents the combination of > machine type (i440fx/q35) and firmware (BIOS/UEFI). Other than adding a new element in the OVF, this also enables the conversion of UEFI guests to oVirt. It is tested? Does it require other changes? I'd split the addition of <BiosType> to the

Thanks for the breakdown Paul - I've had to learn all my sysadmin stuff through organic interactions like this. Still though - someone manages the default repositories - so my question is, who decides when a package gets an update from whatever CentOS ships with default to a newer version? How does that process take place, and, can I affect it by adding microcode_ctl-2.1-18 ? On Wed, Jan 4,

On Tue, 19 Apr 2016, david wrote: > > > > At 09:09 AM 4/18/2016, you wrote: >> On Mon, 18 Apr 2016, david wrote: >> >> > FOLLOWUP & REPORT >> > >> > I had lots of suggestions, and the most persuasive was to try OpenVPN. I >> > already had a CA working, so issuing certificates was easy. The HOW-TO >> > guides were less

On Tue, May 12, 2020 at 8:02 PM Paul Heinlein <heinlein at madboa.com> wrote: > On Tue, 12 May 2020, Thomas Stephen Lee wrote: > > > Hi, > > > > I am user of CentOS 8. > > When can we expect an image on AWS? > > I am just learning AWS and would like to use CentOS 8 for that. > > I can't speak to AWS per se, but Digital Ocean has a CentOS 8

On Mon, Nov 15, 2010 at 13:45, Paul Heinlein <heinlein at madboa.com> wrote: > On Mon, 15 Nov 2010, cliff here wrote: > > > You should check the perms on the dirs, ssh will not allow it use > > the keys if they are too permissive. So I would check starting at > > /home > > This is the most likely cause; I'd check there too. > > If not, > > 1.

Thanks Mark and Christian, I have two Samba servers running those two versions. That reassure me! Thanks, Bernard On Fri, May 26, 2017 at 12:08 PM, Paul Heinlein <heinlein at madboa.com> wrote: > On Fri, 26 May 2017, Christian, Mark wrote: > > On Fri, 2017-05-26 at 11:19 -0400, Bernard Fay wrote: >> >>> Hi, >>> >>> Does a fix has already been

On 03/08/2017 11:00 AM, Paul Heinlein wrote: > On Wed, 8 Mar 2017, Mark Weaver wrote: > > > Hello all, > > > > I've been googling my brains out since yesterday looking for up-to-date > > information on this matter, and have found information that is > anywhere from > > 15 to 5 years old. I'd really like some information that much more > up to

On Fri, 26 May 2017, Christian, Mark wrote: > On Fri, 2017-05-26 at 11:19 -0400, Bernard Fay wrote: >> Hi, >> >> Does a fix has already been made in the CenOS RPM repositories for this >> Samba remote execution code vulnerability, CVE-2017-7494? > yes. samba-3.6.23-43.el6_9.x86_64.rpm And samba-*-4.4.4-14.el7_3.x86_64 -- Paul Heinlein <> heinlein at

I updated my backup server to CentOS 6.6 this morning. As usual, I unmounted the current (nightly) tape from the changer before the reboot. Now Bacula complains it cannot access the changer: 3301 Issuing autochanger "loaded? drive 0" command. 3991 Bad autochanger "loaded? drive 0" command: ERR=Child exited with code 1. Results=cannot open SCSI device '/dev/changer' -

There is a slight performance related reason for exporting disk partitions individually, the performance boost is server-side as Paul says. The advantage is that the no_subtree_check can be used without any additional security risk. It is probably the case that the /export/base/a is a partition, is exported with no_subtree_check, and therefore there is a small performance boost. Preventing

On Tue, Jun 19, 2018 at 11:43:38AM +0100, Daniel P. Berrangé wrote: > I'd encourage apps to check the capabilities XML to see what > machine types are available. One issue is we don't always have access to the target hypervisor. For example in the Glance case we have to write something which will be picked up by Nova much later: > > + "hw_machine_type", >

On Wed, 8 Mar 2017, Mark Weaver wrote: > On 03/08/2017 11:00 AM, Paul Heinlein wrote: >> On Wed, 8 Mar 2017, Mark Weaver wrote: >> >> > Hello all, >> > >> > I've been googling my brains out since yesterday looking for >> > up-to-date information on this matter, and have found >> > information that is anywhere from 15 to 5