virt

virt@lists.centos.org

2 participants
1613 discussions

ANNOUNCEMENT: centos-release-xen switching to 4.6 later this week
by George Dunlap 22 Mar '16

22 Mar '16

In preparation for XSA-172, due to be made public next week (29 March), as discussed previously, I'm going to be updating the centos-release-xen package to point to Xen 4.6 rather than 4.4. As a reminder, you can "pin" your installation to Xen 4.4 by installing centos-release-xen-44 and then removing centos-release-xen. Also, I will not be applying any more patches to the Xen 4.4 packages. I will, however, review and push through the build system pull requests sent to https://github.com/CentOS-virt7/xen. -George

1 0

Re: [CentOS-virt] Networking in KVM
by paul.greene.va＠verizon.net 21 Mar '16

21 Mar '16

1 0

Re: [CentOS-virt] Networking in KVM
by paul.greene.va＠verizon.net 18 Mar '16

18 Mar '16

4 4

kernel-3.18.25-19 xen kernel with XSA-171 in virt6 and virt7 testing
by Johnny Hughes 16 Mar '16

16 Mar '16

George has built and I have pushed to virt6-xen-common-testing and virt7-xen-common-testing the kernel-3.18.25-19 kernel. Please test this kernel and we can release it. It also has the fix for XSA-171: http://xenbits.xen.org/xsa/advisory-171.html Thanks, Johnny Hughes

1 0

Networking in KVM
by paul.greene.va＠verizon.net 16 Mar '16

16 Mar '16

2 1

Soft lockups with Xen4CentOS 3.18.25-18.el6.x86_64
by Sarah Newman 15 Mar '16

15 Mar '16

I've been running 3.18.25-18.el6.x86_64 + our build of xen 4.4.3-9 on one host for the last couple of weeks and have gotten several soft lockups within the last 24 hours. I am posting here first in case anyone else has experienced the same issue. Here is the first instance: sched: RT throttling activated NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] Modules linked in: ebt_arp xen_pciback xen_gntalloc ebt_ip ebtable_filter ebtables ipt_REJECT nf_reject_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables xt_physdev br_netfilter bridge stp llc ip6t_REJECT nf_reject_ipv6 nf_c onntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 xen_acpi_processor blktap xen_netback xen_blkback xen_gntdev xen_evtchn xenfs xen_privcmd joydev sg 8250_fintek serio_raw gpio_ich iTCO_wdt iTCO_vendor_su pport coretemp intel_powerclamp crct10dif_pclmul crc32_pclmul crc32c_intel pcspkr i2c_i801 lpc_ich igb ptp pps_core hwmon ioatdma dca i7core_edac edac_core shpchp ext3 jbd mbcache raid10 raid1 sd_mod mptsas mptscsih mptbase scsi_transpor t_sas aesni_intel ablk_helper cryptd lrw gf128mul glue_helper aes_x86_64 ahci libahci mgag200 ttm drm_kms_helper dm_mirror dm_region_hash dm_log dm_mod CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.18.25-18.el6.x86_64 #1 Hardware name: Supermicro X8DTN+-F/X8DTN+-F, BIOS 080016 08/03/2011 task: ffffffff81c1b4c0 ti: ffffffff81c00000 task.ti: ffffffff81c00000 RIP: e030:[<ffffffffa02811d5>] [<ffffffffa02811d5>] xenvif_tx_build_gops+0xa5/0x890 [xen_netback] RSP: e02b:ffff88013f403ca8 EFLAGS: 00000206 RAX: 000000000000003c RBX: ffffc90012c28000 RCX: ffffc90012c280d0 RDX: 0000000000071ea1 RSI: 0000000000000040 RDI: ffffc90012c28000 RBP: ffff88013f403e38 R08: 0000000000000000 R09: 0000000000000001 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000071e65 R13: ffff88013f403e50 R14: 000000000000003c R15: 0000000000000032 FS: 00007fe942ac7980(0000) GS:ffff88013f400000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: ffff8000007f6800 CR3: 00000000bcd4c000 CR4: 0000000000002660 Stack: ffff88013f403d30 ffff880006de6800 ffff8800adfee1c0 ffff88013f403e54 000000015786e75a 00000040a0351878 ffffc90012c2def0 000000015786e73c ffffc90012c280d0 ffffc90012c2def0 ffffffffa03516c0 ffff8800bf29e000 Call Trace: <IRQ> [<ffffffffa03516c0>] ? br_handle_frame_finish+0x3f0/0x3f0 [bridge] [<ffffffff815a2b9e>] ? __netif_receive_skb_core+0x1ee/0x640 [<ffffffff815a3017>] ? __netif_receive_skb+0x27/0x70 [<ffffffff815a326d>] ? netif_receive_skb_internal+0x2d/0x90 [<ffffffffa01d5053>] ? igb_alloc_rx_buffers+0x63/0xe0 [igb] [<ffffffffa0281a0d>] xenvif_tx_action+0x4d/0xa0 [xen_netback] [<ffffffffa02843b5>] xenvif_poll+0x35/0x68 [xen_netback] [<ffffffff815a39c2>] net_rx_action+0x112/0x2a0 [<ffffffff81076b7c>] __do_softirq+0xfc/0x2b0 [<ffffffff81076e3d>] irq_exit+0xbd/0xd0 [<ffffffff813b2cbc>] xen_evtchn_do_upcall+0x3c/0x50 [<ffffffff8167659e>] xen_do_hypervisor_callback+0x1e/0x40 <EOI> [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 [<ffffffff8100a830>] ? xen_safe_halt+0x10/0x20 [<ffffffff8101ec84>] ? default_idle+0x24/0xc0 [<ffffffff8101e28f>] ? arch_cpu_idle+0xf/0x20 [<ffffffff810b2276>] ? cpuidle_idle_call+0xd6/0x1d0 [<ffffffff81091312>] ? __atomic_notifier_call_chain+0x12/0x20 [<ffffffff810b24a5>] ? cpu_idle_loop+0x135/0x1e0 [<ffffffff810b256b>] ? cpu_startup_entry+0x1b/0x70 [<ffffffff810b25b0>] ? cpu_startup_entry+0x60/0x70 [<ffffffff81667c57>] ? rest_init+0x77/0x80 [<ffffffff81d774c9>] ? start_kernel+0x441/0x448 [<ffffffff81d76ea6>] ? set_init_arg+0x5d/0x5d [<ffffffff81d76603>] ? x86_64_start_reservations+0x2a/0x2c [<ffffffff81d7aae1>] ? xen_start_kernel+0x5ef/0x5f1 Code: 00 0f 87 06 07 00 00 44 8b b3 b8 00 00 00 44 03 b3 c0 00 00 00 45 29 e6 41 39 c6 44 0f 47 f0 45 85 f6 0f 84 8f 00 00 00 0f ae e8 <8b> 83 c0 00 00 00 83 e8 01 44 21 e0 48 8d 04 40 48 c1 e0 02 48 Of the remaining lockups, here is the common backtrace with the exception that there have been two instances of RIP being in net_rx_action: [<ffffffff815a39c2>] net_rx_action+0x112/0x2a0 [<ffffffff81076b7c>] __do_softirq+0xfc/0x2b0 [<ffffffff81076e3d>] irq_exit+0xbd/0xd0 [<ffffffff813b2cbc>] xen_evtchn_do_upcall+0x3c/0x50 [<ffffffff8167659e>] xen_do_hypervisor_callback+0x1e/0x40 <EOI> [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20 [<ffffffff8100a830>] ? xen_safe_halt+0x10/0x20 [<ffffffff8101ec84>] ? default_idle+0x24/0xc0 [<ffffffff8101e28f>] ? arch_cpu_idle+0xf/0x20 [<ffffffff810b2276>] ? cpuidle_idle_call+0xd6/0x1d0 [<ffffffff81091312>] ? __atomic_notifier_call_chain+0x12/0x20 [<ffffffff810b24a5>] ? cpu_idle_loop+0x135/0x1e0 [<ffffffff810b256b>] ? cpu_startup_entry+0x1b/0x70 [<ffffffff810b25b0>] ? cpu_startup_entry+0x60/0x70 [<ffffffff81667c57>] ? rest_init+0x77/0x80 [<ffffffff81d774c9>] ? start_kernel+0x441/0x448 [<ffffffff81d76ea6>] ? set_init_arg+0x5d/0x5d [<ffffffff81d76603>] ? x86_64_start_reservations+0x2a/0x2c [<ffffffff81d7aae1>] ? xen_start_kernel+0x5ef/0x5f1 I can post more complete backtraces if that information would be useful to someone.

2 3

I would like to verify what are the available options for RAM storage.
by Eliezer Croitoru 13 Mar '16

13 Mar '16

Hey All, I am not sure what the status of the current technology in the market and was wondering if it would be fine to ask specifically here. I am using KVM for a time now and it's great but I have couple doubts. When I am running a test on a specific VM it's mostly on 10k SPINNING disks and they seem to survive like forever now(years...). But I need to run tests on RAM only. Until now what I did was to create a tmpfs, shutdown the VM, move the disk image to the tmpfs, change the disk location on the VM settings and then turn the machine on again when it's on RAM(I cannot 100% control swap since it's the kernel doings..). I am considering what to do next and the options are: - automate the process of migration from one storage to another - buy more ram - buy a very fast SSD? - a combination of RAM + SSD(SWAP) But I do not know exactly what to do. Every choice have it's price and it's unclear to me if OVIRT is the same as RHEV an if not then is this function available there? Eliezer

1 0

USB3 driver?
by ToddAndMargo 05 Mar '16

05 Mar '16

Hi All, Scientific Linux 7.2 # rpm -qa \*kvm\* qemu-kvm-1.5.3-105.el7_2.3.x86_64 pcp-pmda-kvm-3.10.6-2.el7.x86_64 qemu-kvm-common-1.5.3-105.el7_2.3.x86_64 libvirt-daemon-kvm-1.2.17-13.el7_2.3.x86_64 Question: when I set "Controller USB" to "USB3", what USB3 driver do I use to install Window 7? Many thanks, -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2 2

can't mount a bootable flash drive
by ToddAndMargo 04 Mar '16

04 Mar '16

Hi All, Scientific Linux 7.2 # rpm -qa \*kvm\* qemu-kvm-1.5.3-105.el7_2.3.x86_64 pcp-pmda-kvm-3.10.6-2.el7.x86_64 qemu-kvm-common-1.5.3-105.el7_2.3.x86_64 libvirt-daemon-kvm-1.2.17-13.el7_2.3.x86_64 I can mount NTFS flash drives on my Windows virtual machines by Add Hardware -> USB Host Device. They work fine. Except for one bootable Windows 7 Pro OEM x 64 USB flash drive I use for installing Windows 7. In Windows, under devices I get a bang mark saying the device failed to start. This same flash drive, when set as the bootable drive does boot into the Windows 7 install dialog. What am I doing wrong? Many thanks, -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Virtualized Server 2008R2 can't boot with multi-core
by Emmanuel Noobadmin 03 Mar '16

03 Mar '16

I previously tested a fresh install of Windows 2008R2 using the free evaluation download from Microsoft and worked without much hassle. However, when converting an actual physical W2008R2 machine to virtual using Windows' bare metal recovery, it would not boot with more than 1 core assigned. I''ve tried various suggestions such as - adding/removing <hyperv><relaxed state='on'></hyperv> - setting cpu type to core2duo and requiring nx But neither helps, basically a brief blinking cursor in the upper left corner after BIOS/EFI then blank. Any suggestion on how to fix this? Using CentOS 7, yum updated to latest ( 3.10.0-327.10.1.el7.x86_64) Physical server is UEFI so loader set use ovmf-x64/OVMF_CODE-pure-efi.fd

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt