virt December 2015

virt@lists.centos.org

19 participants
17 discussions

Differences between pc and q35
by C.L. Martinez 11 Dec '15

11 Dec '15

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@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 RHEL 7.0.0 PC (i440FX + PIIX, 1996) rhel6.6.0 RHEL 6.6.0 PC rhel6.5.0 RHEL 6.5.0 PC rhel6.4.0 RHEL 6.4.0 PC rhel6.3.0 RHEL 6.3.0 PC rhel6.2.0 RHEL 6.2.0 PC rhel6.1.0 RHEL 6.1.0 PC rhel6.0.0 RHEL 6.0.0 PC q35 RHEL-7.1.0 PC (Q35 + ICH9, 2009) (alias of pc-q35-rhel7.1.0) pc-q35-rhel7.1.0 RHEL-7.1.0 PC (Q35 + ICH9, 2009) pc-q35-rhel7.0.0 RHEL-7.0.0 PC (Q35 + ICH9, 2009) none empty machine But according to this, q35 is more new virtual hardware. Why??

1 1

Xen4CentOS and XSA-142
by Sarah Newman 10 Dec '15

10 Dec '15

It looks like no XSA-142 patch, which is "libxl fails to honour readonly flag on disks with qemu-xen" has been applied to Xen4CentOS. I assume this was on purpose? If not, I can have someone try adding the original patch from http://xenbits.xen.org/xsa/advisory-142.html and some variant of the commit from ef6cb76026628e26e3d1ae53c50ccde1c3c78b1b http://xen.1045712.n5.nabble.com/xen-master-libxl-relax-readonly-check-intr… . Thanks, Sarah

2 1

win2008r2 update on centos 6 host made system unbootable
by Dennis Jacobfeuerborn 10 Dec '15

10 Dec '15

Hi, today we ran into a strange problem: When performing a regular Windows 2008r2 update apparently among other things the following was installed: "SUSE - Storage Controller - SUSE Block Driver for Windows" Previously the disk drive was using the Red Hat virtio drivers which worked just fine but after the reboot after the update I just get a blue screen indicating that Windows cannot find a boot device. Does anyone understand what is going on here? Why is the windows update installing a Suse driver that overrides the Red Hat driver even though it is apparently incompatible with the system? Regards, Dennis

5 8

How to manually add a new interface to a bridge device?
by Howard Leadmon 09 Dec '15

09 Dec '15

Maybe my google-fu is failing me, but I have spent the past couple hours looking at how to add a vnet? Device to my KVM host running CentOS 6, and for the life of me I can't get this going. >From all my research if I want to add a device I should just do 'brctl addif br1 vnet14' if I want to add a vnet14 to bridge br1. When I do this, I get: # brctl addif br0 vnet14 interface vnet14 does not exist! If I run a 'brctl show' I get the following: # brctl show bridge name bridge id STP enabled interfaces br0 8000.00237dd22a4c no eth0 vnet0 vnet10 vnet11 vnet13 vnet2 vnet3 vnet4 vnet6 vnet8 br1 8000.00237dd22a50 no eth1 vnet1 vnet12 vnet5 vnet7 vnet9 Needless to say the existing vnet?? Devices are in use on guest VM's currently. When I create a new VM using virt-install, I usually add the following to my command line: --network=bridge:br0 --network=bridge:br1 I messed up building a new VM, and only added the br0 interface to the VM, but need the br1 interface as well. So my question is, or a pointer to how I can add that br1 interface to my existing VM, and create the needed vnet14 interface for it to attach to? If anyone can explain how to do this, or give me a good pointer on where the info is on how to do this, it would sure be a huge help.. Thanks. --- Howard Leadmon

2 7

new install of Xen 4.6 hangs on Loading initial ramdisk
by President 09 Dec '15

09 Dec '15

Not sure if this actually made it to the list the first time. Here is the SERIAL output (bottom of message after your questions). Googling the error indicates it's something people ran into a few years back but was supposedly fixed. Any ideas? I can verify that if I REMOVE the second CPU, it boots into Xen kernel no problem. The CPU itself doesn't matter, as I can swap either CPU into the first slot, and it boots. Only if there is a second CPU does it fail. -----Original message----- From: George Dunlap <dunlapg(a)umich.edu> Sent: Monday 30th November 2015 6:00 To: Discussion about the virtualization on CentOS <centos-virt(a)centos.org> Subject: Re: [CentOS-virt] new install of Xen 4.6 hangs on Loading initial ramdisk On Fri, Nov 27, 2015 at 11:18 PM, Craig Thompson <president(a)caldwellglobal.com <mailto:president@caldwellglobal.com> > wrote: First post to this list. I would appreciate some help on this issue. As background, I installed CentOS 7 on a Dell server, and then ran the following commands: yum update http://buildlogs.centos.org/centos/7/virt/x86_64/xen/centos-release-xen-7-1… <http://buildlogs.centos.org/centos/7/virt/x86_64/xen/centos-release-xen-7-1…> yum --enablerepo=centos-virt-xen-testing update yum --enablerepo=centos-virt-xen-testing install xen Doing that, I was able to successfully install Xen, create a virtual machine with its own HVM setup, logical volume, etc. and boot it just fine. I then tried to do the same on an IBM x3550 server I’m trying to install with CentOS 7. The CentOS 7 install went just fine. I can boot into the standard kernel and have a working machine. But after running the commands above to install the Xen hypervisor, the machine hangs on boot for a few moments after displaying the lines below and then reboots in a loop over and over and over: Loading Xen 4.6.0-2.el7 … Loading Linux 3.18.21-16.el7.x86_64 … Loading initial ramdisk … It never gets beyond that. If I choose the stock kernel (no Xen) from the Grub menu, it will continue to boot into that just fine. My grub.cfg file has these entries of note: multiboot /xen-4.6.0-2.el7.gz placeholder dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all ${xen_rm_opts} echo 'Loading Linux 3.18.21-16.el7.x86_64 ...' module /vmlinuz-3.18.21-16.el7.x86_64 placeholder root=UUID=9dc18146-f9b3-41cc-ba9c-7314689abcde ro crashkernel=auto debug irqpoll ipv6.disable=1 console=hvc0 earlyprintk=xen nomodeset echo 'Loading initial ramdisk ...' module --nounzip /initramfs-3.18.21-16.el7.x86_64.img What I have tried: 1) adding debug into the vmlinuz line 2) disabling ipv6 in that line 3) adding root=UUID=9dc18146-f9b3-41cc-ba9c-7314689abcde to the last line AFTER /initramfs …. Nothing so far has made any difference. Obviously the process works, as it works for me just fine on the Dell server. Underlying this machine is a SATA RAID 1 PCI card with two SSD drives attached in a RAID 1 mirror. Not that that should matter, but I’m including it for reference. As noted previously, it boots into the stock kernel just fine. Any help would be appreciated. Thanks for the testing and the report. Have you tried booting the Xen4CentOS kernel (Linux-3.18.21-16) by itself (i.e., not under Xen)? Also, is there any chance you could get the output of a serial console? That's pretty critical for debugging this sort of thing. CentOS-virt mailing list ### No such file or directory opening port (XEN) Bad console= option 'tty' Xen 4.6.0-2.el7 (XEN) Xen version 4.6.0-2.el7 (mockbuild(a)centos.org) (gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-9)) debug=n Tue Nov 3 17:23:39 UTC 2015 (XEN) Latest ChangeSet: Mon Oct 19 12:05:21 2015 +0100 git:36b6fe9-dirty (XEN) Bootloader: GRUB 2.02~beta2 (XEN) Command line: placeholder dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 2 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009c800 (usable) (XEN) 000000000009c800 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000bffcba40 (usable) (XEN) 00000000bffcba40 - 00000000bffcee00 (ACPI data) (XEN) 00000000bffcee00 - 00000000c0000000 (reserved) (XEN) 00000000fec00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 00000001fee00000 (usable) (XEN) 00000001fee00000 - 00000001fef00000 (reserved) (XEN) 00000001fef00000 - 00000002fee00000 (usable) (XEN) 00000002fee00000 - 00000002fef00000 (reserved) (XEN) 00000002fef00000 - 00000003fee00000 (usable) (XEN) 00000003fee00000 - 00000003fef00000 (reserved) (XEN) 00000003fef00000 - 0000000840000000 (usable) (XEN) ACPI: RSDP 000FDFD0, 0024 (r2 IBM ) (XEN) ACPI: XSDT BFFCED00, 004C (r1 IBM SERDEFNT 1000 IBM 45444F43) (XEN) ACPI: FACP BFFCEC40, 0084 (r2 IBM SERDEFNT 1000 IBM 45444F43) (XEN) ACPI: DSDT BFFCBA40, 246C (r2 IBM SERDEFNT 1000 INTL 20041203) (XEN) ACPI: FACS BFFCE980, 0040 (XEN) ACPI: APIC BFFCEB80, 0084 (r1 IBM SERDEFNT 1000 IBM 45444F43) (XEN) ACPI: SRAT BFFCEA40, 00E8 (r1 IBM SERDEFNT 1000 IBM 45444F43) (XEN) ACPI: HPET BFFCEA00, 0038 (r1 IBM SERDEFNT 1000 IBM 45444F43) (XEN) ACPI: MCFG BFFCE9C0, 003C (r1 IBM SERDEFNT 1000 IBM 45444F43) (XEN) System RAM: 32764MB (33550748kB) (XEN) SRAT: PXM 0 -> APIC 0 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 1 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 6 -> Node 0 (XEN) SRAT: PXM 0 -> APIC 7 -> Node 0 (XEN) SRAT: Node 0 PXM 0 0-c0000000 (XEN) SRAT: Node 0 PXM 0 100000000-840000000 (XEN) SRAT: Node 0 PXM 0 840000000-1000000000 (hotplug) (XEN) NUMA: Allocated memnodemap from 83d5cd000 - 83d5ce000 (XEN) NUMA: Using 18 for the hash shift. (XEN) Domain heap initialised (XEN) found SMP MP-table at 0009c940 (XEN) DMI 2.4 present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x588 (XEN) ACPI: SLEEP INFO: pm1x_cnt[1:584,1:0], pm1x_evt[1:580,1:0] (XEN) ACPI: wakeup_vec[bffce98c], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) Processor #0 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) (XEN) Processor #1 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled) (XEN) Processor #6 6:15 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled) (XEN) Processor #7 6:15 APIC version 20 (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1]) (XEN) ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 14, version 32, address 0xfec00000, GSI 0-23 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000 (XEN) ERST table was not found (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 4 CPUs (0 hotplug CPUs) (XEN) IRQ limits: 24 GSI, 760 MSI/MSI-X (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 4096K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 0 (XEN) CMCI: CPU0 has no CMCI support (XEN) CPU0: Thermal monitoring enabled (TM2) (XEN) Intel machine check reporting enabled (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Initializing CPU#0 (XEN) Detected 2000.117 MHz processor. (XEN) Initing memory sharing. (XEN) alt table ffff82d0802b8b50 -> ffff82d0802b9f24 (XEN) PCI: MCFG configuration 0: base e0000000 segment 0000 buses 00 - 14 (XEN) PCI: Not using MCFG for segment 0000 bus 00-14 (XEN) I/O virtualisation disabled (XEN) CPU0: Intel(R) Xeon(R) CPU 5130 @ 2.00GHz stepping 06 (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 32 KiB. (XEN) mwait-idle: does not run on family 6 model 15 (XEN) VMX: Supported advanced features: (XEN) - APIC TPR shadow (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs disabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) not detected (XEN) HVM: PVH mode not supported on this platform (XEN) CPU 0 APIC 0 -> Node 0 (XEN) CPU 1 APIC 1 -> Node 0 (XEN) Booting processor 1/1 eip 8c000 (XEN) Initializing CPU#1 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 4096K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 1 (XEN) CMCI: CPU1 has no CMCI support (XEN) CPU1: Thermal monitoring enabled (TM2) (XEN) CPU1: Intel(R) Xeon(R) CPU 5130 @ 2.00GHz stepping 06 (XEN) CPU 2 APIC 6 -> Node 0 (XEN) Booting processor 2/6 eip 8c000 (XEN) Initializing CPU#2 (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K (XEN) CPU: L2 cache: 4096K (XEN) CPU: Physical Processor ID: 3 (XEN) CPU: Processor Core ID: 0 (XEN) CMCI: CPU2 has no CMCI support (XEN) CPU2: Thermal monitoring enabled (TM2) (XEN) CPU2: Intel(R) Xeon(R) CPU 5130 @ 2.00GHz stepping 06 (XEN) ----[ Xen-4.6.0-2.el7 x86_64 debug=n Not tainted ]---- (XEN) CPU: 2 (XEN) RIP: e008:[<ffff82d080181ba9>] set_cpu_sibling_map+0x39/0x340 (XEN) RFLAGS: 0000000000010006 CONTEXT: hypervisor (XEN) rax: 0000000000000020 rbx: 0000000000000200 rcx: 00000037bd295580 (XEN) rdx: 0000000000000003 rsi: 0000000000000000 rdi: 0000000000000002 (XEN) rbp: 00000000000000c8 rsp: ffff83083d597e90 r8: 00000037bd295580 (XEN) r9: 00000037bd295580 r10: 0000000000000007 r11: 0000000000000001 (XEN) r12: 0000000000000002 r13: 0000000000000002 r14: 0000000000000000 (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000026e0 (XEN) cr3: 00000000bfc70000 cr2: 0000000000000020 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008 (XEN) Xen stack trace from rsp=ffff83083d597e90: (XEN) ffff82d0802f4380 0000000000000012 0000000000000000 00000100801ad1e1 (XEN) ffff82d0802f4380 0000000000000000 00000000000000c8 0000000000000002 (XEN) 0000000000000002 0000000000000000 0000000000000000 ffff82d08018206c (XEN) 0000000000000000 0000000000000001 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000002 ffff8300bfd0b000 (XEN) 00000037bd295580 0000000000000000 (XEN) Xen call trace: (XEN) [<ffff82d080181ba9>] set_cpu_sibling_map+0x39/0x340 (XEN) [<ffff82d08018206c>] start_secondary+0x1bc/0x260 (XEN) (XEN) Pagetable walk from 0000000000000020: (XEN) L4[0x000] = 000000083d5c1063 ffffffffffffffff (XEN) L3[0x000] = 000000083d5c0063 ffffffffffffffff (XEN) L2[0x000] = 000000083d5bf063 ffffffffffffffff (XEN) L1[0x000] = 0000000000000000 ffffffffffffffff (XEN) (XEN) **************************************** (XEN) Panic on CPU 2: (XEN) FATAL PAGE FAULT (XEN) [error_code=0002] (XEN) Faulting linear address: 0000000000000020 (XEN) **************************************** (XEN) (XEN) Reboot in five seconds... (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.

2 1

Xen build with XSAs through 163 in progress
by George Dunlap 08 Dec '15

08 Dec '15

Just a heads-up: A Xen package with XSAs through 163 is on its way through the build system. I'll send an announcement when I've tagged it as ready to be propagated to the mirrors. As with the last XSA update, it will depend on having manually updated to the new Virt SIG repository layout. If you haven't already please run the following in preparation: yum install http://buildlogs.centos.org/centos/6/virt/x86_64/xen/centos-release-xen-7-1… (And note that this package depends on a package from centos-extras, so if you have that repo disabled by default you'll need to enable it to perform the above command.) -George

1 1

CentOS 7.1 + KVM + OVMF for UEFI - can't reboot VM, only shutdown and start
by Dmitry E. Mikhailov 04 Dec '15

04 Dec '15

Hi, I'm trying to use OVMF to run EFI-partitioned Windows 8.0 virtualized on my laptop. The reason is to reuse the original HDD image intact without re-installation of any kind. I'm running fully updated CentOS 7.1 (1503). Virtualized storage subsystem is VirtIO if it matters. I'm almost OK with the notable exception of inability to reboot the VM. OVMF bootloader doesn't start upon reboot (or even 'Force reset') of VM and all I get a black screen and infrequent vCPU usage spikes, therefore I'm forced to shut the VM and start it over. Does anyone here have some similar experience? Best regards, Dmitry Mikhaylov

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt December 2015