similar to: Differences between pc and q35

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

Hi, All The vm can't start when using numa based on centos 6.5(kernel: kernel-2.6.32-431.17.1.el6.x86_64, qemu-kvm: qemu-kvm-0.12.1.2-2.415.el6_5.8.x86_64). My numa setting in vm xml is the following: -------------------- <numatune> <memory mode='strict' nodeset='1'/> </numatune> -------------------- When 'nodeset' sets '0', the

On Mon, 23 Mar 2015 10:36:33 -0400 John Snow <jsnow@redhat.com> wrote: > > Are the needed patches in 2.3.0-rc0? > > Is it possible to backport AHCI migration to RHEL 7.1 qemu or will it be too much work? > > The patches that improve the stability of AHCI migration are in 2.3-rc0. > We still have not /enabled/ migration upstream, but editing to code to > allow it

One of our VM clusters has four CentOS 6.6 machines. I'm in the process of testing the addition of a CentOS 7 box (with the goal of upgrading the 6.6 machines soon). A newly created VM running on a 6.6 node has a machine type of rhel6.6.0: <os> <type arch='x86_64' machine='rhel6.6.0'>hvm</type> <boot dev='hd'/> </os>

On 03/23/2015 08:05 PM, Nerijus Baliunas wrote: > On Mon, 23 Mar 2015 10:36:33 -0400 John Snow <jsnow@redhat.com> wrote: > >>> Are the needed patches in 2.3.0-rc0? >>> Is it possible to backport AHCI migration to RHEL 7.1 qemu or will it be too much work? >> >> The patches that improve the stability of AHCI migration are in 2.3-rc0. >> We still have

On Thu, 12 Mar 2015 14:56:08 -0400 Laine Stump <laine@laine.org> wrote: > Here is the info straight from the author (I've also Cc'ed him to this > mail): > > =============== > The AHCI migration series is here: > > http://lists.gnu.org/archive/html/qemu-devel/2015-02/msg05200.html > These are all just tests, at any rate -- the actual patch that enables

Hi there, I met one problem that guest fail to boot up when Selinux is enabled with guest storage based on ceph. However, I can boot the guest with qemu directly. I also can boot it up with Selinux disabled. Not sure it is a libvirt bug or wrong use case. 1. Enable Selinux # getenforce && iptables -L Enforcing Chain INPUT (policy ACCEPT) target prot opt source destination

hello , thanks for comments . I tried now with force options for CPU flag which were not supported . Now the command with non fully supported CPU model gets executed , But i am surprised to see that still Guest cpu model is not changed and still same as host cpu model(SAndy Bridge) Why don't i see the model as HAswell now , could you please comment. Command used : virt-install

Hi, Could anybody give me some advice, how to define virtual machine type "pc-i440fx-2.1" on latest centos 7.1? I need to live migrate vms from debian based hypervisor and I get an error about unsupported machine types, because on centos there are different naming "pc-i440fx-rhel7.1.0". -- Marius Vaitiek?nas

Hi, Please let me know in case I am posting my question to the wrong forum. I apologize if that is the case! Here is my question: We run CentOS 6.3 on a server with dual Xeon CPU's. Our "dual blade" server uses this motherboard: http://www.supermicro.com/products/motherboard/Xeon/C600/X9DRT-HF.cfm We have two of these CPUs installed and working: Intel(R) Xeon(R) CPU E5-2620 0 @

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

Hi, I'm using QEMU/KVM on RHEL (CentOS) 7.8.2003: # cat /etc/redhat-release CentOS Linux release 7.8.2003 I'm passing an NVMe drive into a Linux KVM virtual machine (<type arch='x86_64' machine='pc-i440fx-rhel7.0.0'>hvm</type>) which has the following 'hostdev' entry: <hostdev mode='subsystem' type='pci' managed='yes'>

Reports posted look good for me. Config should provide the best available performance for cloud VM (L2) on Compute Node. 1. Please, remind me what goes wrong from your standpoint ? 2. Which CPU is installed on Compute Node && how much RAM ? Actually , my concern is :- Number_of_ Cloud_VMs versus Number_CPU_Cores ( not threads) Please, check `top` report in

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

I would attempt to decrease number of VCPUS allocated to cloud VMs. Say try 4 => 2 . My guess there is not enough VCPUs to run OS itself. I also guess CPU model << Haswell. Please , confirm ( or not) if possible. Since Haswell was launched via my experience Intel Xeons based on this kernel (or latter kernels ) behaves much better then SandyBridge or IvyBridge based. Boris.

________________________________ From: centos-virt-bounces at centos.org <centos-virt-bounces at centos.org> on behalf of Laurentiu Soica <laurentiu at soica.ro> Sent: Sunday, August 14, 2016 10:17 AM To: Discussion about the virtualization on CentOS Subject: Re: [CentOS-virt] Nested KVM issue More details on the subject: I suppose it is a nested KVM issue because it raised after I

I am digging a bit into RHEL 7 roadmap info. It seems there are statements that RHEL 7 will only support 64 bit. Is this corrent, and what for Centos 7? Also the ARM info I found was the target is ARMv8 which is 64 bit, not the ARMv7 which is 32bit. Any clearification is appreciated.

Purchased DQ35JO on Vt-d/PCI passthrough wiki''s recommendations. Built latest xen-unstable and am getting the following via ''xm dmesg'': (XEN) [VT-D]dmar.c:374: RMRR error: base_addr d0000000 end_address cfffffff (XEN) Failed to parse ACPI DMAR. Disabling VT-d. My grub.conf looks like this: kernel /xen.gz vga=mode-0x0317 vtd=1 iommu=1

On 03/11/2015 08:20 PM, Nerijus Baliunas wrote: > Laine Stump <laine@...> writes: > >> And it is also true that any machine with a SATA controller can't be >> migrated because of problems with the driver. I just talked to the >> person responsible for fixing these bugs in qemu, and he said that the >> patches will go upstream "soon", and that he

On 03/22/2015 08:23 PM, Nerijus Baliunas wrote: > On Thu, 12 Mar 2015 14:56:08 -0400 Laine Stump <laine@laine.org> wrote: > >> Here is the info straight from the author (I've also Cc'ed him to this >> mail): >> >> =============== >> The AHCI migration series is here: >> >>