virt August 2017

virt@lists.centos.org

13 participants
11 discussions

ovirt-engine package for oVirt 4.1.x
by C. L. Martinez 16 May '18

16 May '18

Hi all, I am trying to install oVirt 4.1.x from centos repos but it seems ovirt-engine doesn't exists. But instead, ovirt-hosted-engine-setup exists? Is ovirt-engine package removed? In official oVirt repos, exists. Thanks.

4 5

4.4.4-26 with XSA-226, 227, 230 in centos-virt-testing
by Kevin Stange 28 Nov '17

28 Nov '17

Xen 4.4.4 along with kernel 4.9.44 containing patches for XSAs (226 - 230) from August 15th are now available in centos-virt-testing. If possible, please test and provide feedback here so we can move these to release soon. XSA-228 did not affect Xen 4.4 XSA-229 only applies to the kernel XSA-235 disclosed today only affects ARM and isn't going to be added to these packages. Thanks. -- Kevin Stange Chief Technology Officer Steadfast | Managed Infrastructure, Datacenter and Cloud Services 800 S Wells, Suite 190 | Chicago, IL 60607 312.602.2689 X203 | Fax: 312.602.2688 kevin(a)steadfast.net | www.steadfast.net

3 4

Crash in CentOS 7 kernel-3.10.0-514.16.1.el7.x86_64 in Xen PV mode
by Sarah Newman 24 Oct '17

24 Oct '17

I experienced a bug that is likely the same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350373 . Commit b7dd0e350e0bd4c0fddcc9b8958342700b00b168 , which is supposed to fix it, doesn't appear in this kernel and doesn't apply cleanly either. Is there any point in trying to backport the patch? The backtrace is as follows: [ 32.304666] ------------[ cut here ]------------ [ 32.304679] kernel BUG at arch/x86/kernel/paravirt.c:252! [ 32.304683] invalid opcode: 0000 [#1] SMP [ 32.304687] Modules linked in: ip6t_rpfilter ipt_REJECT nf_reject_ipv4 ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter intel_powerclamp coretemp pcspkr ip_tables ext4 mbcache jbd2 xen_netfront xen_blkfront crc32c_intel [ 32.304734] CPU: 0 PID: 3901 Comm: dracut Not tainted 3.10.0-514.16.1.el7.x86_64 #1 [ 32.304739] task: ffff880002598000 ti: ffff88001b728000 task.ti: ffff88001b728000 [ 32.304743] RIP: e030:[<ffffffff8167eb81>] [<ffffffff8167eb81>] enter_lazy.part.0+0x4/0x6 [ 32.304755] RSP: e02b:ffff88001f803aa8 EFLAGS: 00010002 [ 32.304758] RAX: 0000000000000001 RBX: ffff88001eacd640 RCX: 00003ffffffff000 [ 32.304761] RDX: ffff880000000640 RSI: ffffc900000c8000 RDI: 0000000000000001 [ 32.304765] RBP: ffff88001f803aa8 R08: ffff88001f803b78 R09: ffffffff813d50f9 [ 32.304771] R10: ffff88001e801e00 R11: ffffea0000093dc0 R12: ffffc900000c9000 [ 32.304777] R13: ffffc900000c8000 R14: 0000000000000000 R15: ffff88001d150340 [ 32.304787] FS: 00007f64425b0740(0000) GS:ffff88001f800000(0000) knlGS:0000000000000000 [ 32.304796] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b [ 32.304801] CR2: 00000000006de2c8 CR3: 000000001b405000 CR4: 0000000000002660 [ 32.304807] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 32.304813] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 32.304818] Stack: [ 32.304823] ffff88001f803ab8 ffffffff81061857 ffff88001f803b60 ffffffff811b1fe2 [ 32.304833] ffffc900000c8fff ffffc900000c9000 ffffffff819bac90 ffffc900000c8fff [ 32.304843] ffffc900000c9000 ffff88001eacb000 ffffffff810206b0 0000000000000000 [ 32.304854] Call Trace: [ 32.304858] <IRQ> [ 32.304861] [<ffffffff81061857>] paravirt_enter_lazy_mmu+0x27/0x30 [ 32.304879] [<ffffffff811b1fe2>] apply_to_page_range+0x282/0x460 [ 32.304888] [<ffffffff810206b0>] ? map_pte_fn+0x60/0x60 [ 32.304894] [<ffffffff810207fb>] arch_gnttab_map_status+0x3b/0x70 [ 32.304904] [<ffffffff813d5176>] gnttab_map_frames_v2+0xd6/0x150 [ 32.304910] [<ffffffff813d5291>] gnttab_map+0xa1/0x140 [ 32.304917] [<ffffffff813d5430>] get_free_entries+0x100/0x2e0 [ 32.304923] [<ffffffff813d56d5>] gnttab_alloc_grant_references+0x15/0x30 [ 32.304933] [<ffffffffa000bd4f>] do_blkif_request+0x6bf/0x8a0 [xen_blkfront] [ 32.304945] [<ffffffff812eb0e2>] ? __freed_request+0x92/0xa0 [ 32.304951] [<ffffffff812eb6e3>] __blk_run_queue+0x33/0x40 [ 32.304957] [<ffffffff812eb719>] blk_start_queue+0x29/0x40 [ 32.304964] [<ffffffffa000bf51>] kick_pending_request_queues+0x21/0x30 [xen_blkfront] [ 32.304975] [<ffffffffa000c6ce>] blkif_interrupt+0x76e/0x820 [xen_blkfront] [ 32.304986] [<ffffffff811dcc8b>] ? kmem_cache_free+0x1bb/0x1f0 [ 32.304995] [<ffffffff8113079e>] handle_irq_event_percpu+0x3e/0x1e0 [ 32.305003] [<ffffffff8113097d>] handle_irq_event+0x3d/0x60 [ 32.305004] [<ffffffff81133647>] handle_edge_irq+0x77/0x130 [ 32.305004] [<ffffffff813d6217>] __xen_evtchn_do_upcall+0x227/0x350 [ 32.305004] [<ffffffff813d83c3>] xen_evtchn_do_upcall+0x33/0x50 [ 32.305004] [<ffffffff81698c7e>] xen_do_hypervisor_callback+0x1e/0x30 [ 32.305004] <EOI> [ 32.305004] [<ffffffff811af916>] ? copy_pte_range+0x2b6/0x5a0 [ 32.305004] [<ffffffff811af8e6>] ? copy_pte_range+0x286/0x5a0 [ 32.305004] [<ffffffff811b24d2>] ? copy_page_range+0x312/0x490 [ 32.305004] [<ffffffff81083012>] ? dup_mm+0x362/0x680 [ 32.305004] [<ffffffff810847ae>] ? copy_process+0x144e/0x1960 [ 32.305004] [<ffffffff81084e71>] ? do_fork+0x91/0x2c0 [ 32.305004] [<ffffffff81085126>] ? SyS_clone+0x16/0x20 [ 32.305004] [<ffffffff816974d9>] ? stub_clone+0x69/0x90 [ 32.305004] [<ffffffff81697189>] ? system_call_fastpath+0x16/0x1b [ 32.305004] Code: 20 e9 2f ff ff ff 44 89 fa 44 89 ee 48 c7 c7 10 45 8c 81 31 c0 e8 9d 14 00 00 58 5a 5b 41 5c 41 5d 41 5e 41 5f 5d c3 55 48 89 e5 <0f> 0b 66 66 66 66 90 55 48 89 e5 0f 0b 55 48 89 e5 0f 0b 55 48 [ 32.305004] RIP [<ffffffff8167eb81>] enter_lazy.part.0+0x4/0x6 [ 32.305004] RSP <ffff88001f803aa8> [ 32.305004] ---[ end trace 49f67f0d85e1ac69 ]--- [ 32.305004] Kernel panic - not syncing: Fatal exception in interrupt Thanks, Sarah

3 6

Status of reverted Linux patch "tty: Fix ldisc crash on reopened tty", Linux 4.9 kernel frequent crashes
by Pasi Kärkkäinen 20 Sep '17

20 Sep '17

Hello everyone, Recently Nathan March reported on centos-virt list he's getting frequent Linux kernel crashes with Linux 4.9 LTS kernel because of the missing patch "tty: Fix ldisc crash on reopened tty". The patch was already merged upstream here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… but then reverted here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… Nathan confirmed if he applies the patch from 71472fa9c52b1da27663c275d416d8654b905f05 to his Linux 4.9 LTS kernel the bug/problem goes away, so the patch (or similar fix) is still needed, at least for 4.9 LTS kernel. Mikulas reported he's able to trigger the same crash on Linux 4.10: https://www.spinics.net/lists/kernel/msg2440637.html https://lists.gt.net/linux/kernel/2664604?search_string=ldisc%20reopened;#2… Michael Neuling reported he's able to trigger the bug on PowerPC: https://lkml.org/lkml/2017/3/10/1582 So now the question is.. is anyone currently working on getting this patch fixed and applied upstream? I think one of the problems earlier was being able to reliable reproduce the crash.. Nathan says he's able to reproduce it many times per week on his environment on x86_64. Thanks a lot, -- Pasi

4 7

Xen CentOS 7.3 server + CentOS 7.3 VM fails to boot after CR updates (applied to VM)!
by PJ Welsh 14 Sep '17

14 Sep '17

A recently created and fully functional CentOS 7.3 VM fails to boot after applying CR updates: ... ;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f ... [ 194.011062] dracut-initqueue[227]: Warning: dracut-initqueue timeout - starting timeout scripts [ 194.546622] dracut-initqueue[227]: Warning: dracut-initqueue timeout - starting timeout scripts [ 194.547515] dracut-initqueue[227]: Warning: Could not boot. [ 194.557324] dracut-initqueue[227]: Warning: /dev/disk/by-uuid/bbafa3a5-0a24-40d2-a362-03cb33d5d76b does not exist Starting Dracut Emergency Shell... Warning: /dev/disk/by-uuid/bbafa3a5-0a24-40d2-a362-03cb33d5d76b does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. dracut:/# Server OS is CentOS 7.3 using Xen (no CR updates): rpm -qa xen\* xen-hypervisor-4.6.3-15.el7.x86_64 xen-4.6.3-15.el7.x86_64 xen-licenses-4.6.3-15.el7.x86_64 xen-libs-4.6.3-15.el7.x86_64 xen-runtime-4.6.3-15.el7.x86_64 uname -a Linux tsxen2.xx.com 4.9.39-29.el7.x86_64 #1 SMP Fri Jul 21 15:09:00 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Sadly, the other issue is that the grub menu will not display for me to select another kernel to see if it is just a kernel issue. The dracut prompt does not show any /dev/disk folder either. Any info? Thanks PJWelsh

6 16

New xen-4.6.6 rpms for CentOS-6 and CentOS-7
by Johnny Hughes 13 Sep '17

13 Sep '17

There are new xen-4.6.6 rpms for CentOS-6 and CentOS-7 in the testing repository on buildlogs.centos.org. Can we please get some testing of these RPMs and feedback to this list. Thanks, Johnny Hughes

4 5

Major stability problems with xen 4.6.6
by Nathan March 29 Aug '17

29 Aug '17

Hi, I'm seeing numerous crashes on the xen 4.6.6-1 / 4.6.6-2 releases, on both the 4.9.34-29 and 4.9.39-29 kernels. I've attached a txt with two different servers outputs. Xen-028: This crashed this morning while running 4.6.6-1 and 4.9.39-29 Xen-001: This crashed shortly after being upgraded to 4.6.6-2 and 4.9.34-29 Both are on different hardware platforms, and have had a long history of being stable until these upgrades. It sounds potentially related to https://kernel.googlesource.com/pub/scm/linux/kernel/git/tiwai/sound-unstabl e/+/9ce119f318ba1a07c29149301f1544b6c4bea52a%5E%21/ but I've confirmed this patch is in the above kernels. Any suggestions / thoughts? Cheers, Nathan

2 4

4.6.6-2, with XSAs 226, 227, 228, and 230, in centos-virt-testing
by George Dunlap 23 Aug '17

23 Aug '17

I've built Xen 4.6.6 with the XSAs released last week, and tagged it so that it shows up in centos-virt-testing. Please test it and let me know if you have any problems. Thanks, -George

1 0

Xen packages with XSA-226+?
by Nathan March 21 Aug '17

21 Aug '17

Hi, It's been almost a week now since XSA-226 through XSA-230 were released and just wondering when updated packages are expected to be posted? https://cbs.centos.org/koji/packageinfo?packageID=88 has nothing for the past month. Thanks! - Nathan

1 0

Copying CentOS AMIs for EBS encryption
by Andrew Hodgson 08 Aug '17

08 Aug '17

Hi, I am trying to copy the latest CentOS image to my own AWS account so that I can enable EBS volume encryption. It currently looks like the option when sharing the image is not enabled to allow direct copying of the snapshots, and I am wondering if this could be looked at? I can start an instance with this AMI, then create a new snapshot for the purpose of enabling EBS volume encryption, but I want to keep the image as clean as possible, and am worried if I run the image then some scripts will get ran that will customise the image with keys etc. If there is a better way to do this then happy to discuss. Thanks, Andrew.

2 2

Unsubscribe
by David Arnold 05 Aug '17

05 Aug '17

> On Aug 5, 2017, at 6:00 AM, centos-virt-request(a)centos.org wrote: > > Send CentOS-virt mailing list submissions to > centos-virt(a)centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.centos.org/mailman/listinfo/centos-virt > or, via email, send a message with subject or body 'help' to > centos-virt-request(a)centos.org > > You can reach the person managing the list at > centos-virt-owner(a)centos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CentOS-virt digest..." > > > Today's Topics: > > 1. Re: Copying CentOS AMIs for EBS encryption (Andrew Hodgson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 4 Aug 2017 21:11:24 +0000 > From: Andrew Hodgson <andrew(a)hodgsonfamily.org> > To: "centos-virt(a)lists.centos.org" <centos-virt(a)lists.centos.org> > Subject: Re: [CentOS-virt] Copying CentOS AMIs for EBS encryption > Message-ID: > <AM5PR0802MB25463D4E82490F0F84C6E8C9C5B60(a)AM5PR0802MB2546.eurprd08.prod.outlook.com> > > Content-Type: text/plain; charset="us-ascii" > > I, > > Just wondering if anyone was able to look at this option with the current images or could share some tips on copying the image to another AWS account so we can use EBS encryption on the volume without tainting the image too much? > > Thanks. > Andrew. > > -----Original Message----- > From: Andrew Hodgson > Sent: 27 July 2017 15:09 > To: centos-virt(a)lists.centos.org > Subject: Copying CentOS AMIs for EBS encryption > > Hi, > > I am trying to copy the latest CentOS image to my own AWS account so that I can enable EBS volume encryption. It currently looks like the option when sharing the image is not enabled to allow direct copying of the snapshots, and I am wondering if this could be looked at? I can start an instance with this AMI, then create a new snapshot for the purpose of enabling EBS volume encryption, but I want to keep the image as clean as possible, and am worried if I run the image then some scripts will get ran that will customise the image with keys etc. > > If there is a better way to do this then happy to discuss. > > Thanks, > Andrew. > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > CentOS-virt mailing list > CentOS-virt(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-virt > > > ------------------------------ > > End of CentOS-virt Digest, Vol 120, Issue 1 > *******************************************

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt August 2017