virt October 2017

virt@lists.centos.org

9 participants
9 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

Install virtual guest from console
by C. L. Martinez 31 Oct '17

31 Oct '17

HI all, Is it possible to install a virtual guest (FreeBSD and OpenBSD mainly) from kvm host's console? I have tried to do some search about this but I haven't found anything about it. My idea is to launch "virsh start guest1" and inmediately "virsh console guest1", but it doesn't works until serial console is configured inside guest .... Any tip? Thanks.

2 1

Fwd: Network interface regression on F26 VM after 4.13/4.12 kernel update
by Philip Prindeville 27 Oct '17

27 Oct '17

I did not hear back on this posting so I figured I was addressing the wrong audience. Maybe someone on the host-side better understands how the 4.12 kernel is interacting with KVM. Thanks, -Philip > Begin forwarded message: > > From: Philip Prindeville <philipp_subx(a)redfish-solutions.com> > Subject: Network interface regression on F26 VM after 4.13/4.12 kernel update > Date: October 26, 2017 at 4:16:53 PM MDT > To: devel(a)lists.fedoraproject.org > Reply-To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org> > > I was running F25 (4.10) on a VM inside KVM/Qemu/libvirt on CentOS 7.3 (updated). > > Then I upgraded it (via dnf system-upgrade) to F26 and 4.11 and it was still working well, as I recall. > > Then I upgraded it again to 4.13 and now I’m seeing flakiness in the network: the NIC will randomly come up and go down. > > Right now I’m seeing: > > $ ip link show > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > 2: ens3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 > link/ether 52:54:00:29:01:5b brd ff:ff:ff:ff:ff:ff > $ > > my messages file shows: > > Oct 26 14:25:51 son-of-builder kernel: igbvf 0000:00:03.0: Link is Down > Oct 26 14:25:56 son-of-builder NetworkManager[824]: <info> [1509049556.0757] device (ens3): state change: activated -> unavailable (reason 'carrier-changed', internal state 'managed') > Oct 26 14:25:56 son-of-builder audit: NETFILTER_CFG table=filter family=2 entries=86 > Oct 26 14:25:56 son-of-builder NetworkManager[824]: <info> [1509049556.0932] dhcp4 (ens3): canceled DHCP transaction, DHCP client pid 8008 > Oct 26 14:25:56 son-of-builder audit: NETFILTER_CFG table=nat family=2 entries=52 > Oct 26 14:25:56 son-of-builder audit: NETFILTER_CFG table=mangle family=2 entries=40 > Oct 26 14:25:56 son-of-builder audit: NETFILTER_CFG table=raw family=2 entries=29 > Oct 26 14:25:56 son-of-builder NetworkManager[824]: <info> [1509049556.0933] dhcp4 (ens3): state changed bound -> done > Oct 26 14:25:56 son-of-builder avahi-daemon[756]: Withdrawing address record for 192.168.1.56 on ens3. > Oct 26 14:25:56 son-of-builder avahi-daemon[756]: Leaving mDNS multicast group on interface ens3.IPv4 with address 192.168.1.56. > Oct 26 14:25:56 son-of-builder avahi-daemon[756]: Interface ens3.IPv4 no longer relevant for mDNS. > Oct 26 14:25:56 son-of-builder nm-dispatcher[8018]: req:4 'connectivity-change': new request (5 scripts) > Oct 26 14:25:56 son-of-builder nm-dispatcher[8018]: req:4 'connectivity-change': start running ordered scripts... > Oct 26 14:25:56 son-of-builder audit: NETFILTER_CFG table=filter family=10 entries=87 > Oct 26 14:25:56 son-of-builder audit: NETFILTER_CFG table=nat family=10 entries=52 > Oct 26 14:25:56 son-of-builder audit: NETFILTER_CFG table=mangle family=10 entries=40 > Oct 26 14:25:56 son-of-builder audit: NETFILTER_CFG table=raw family=10 entries=30 > Oct 26 14:25:56 son-of-builder NetworkManager[824]: <info> [1509049556.1140] manager: NetworkManager state is now CONNECTED_LOCAL > Oct 26 14:25:56 son-of-builder NetworkManager[824]: <info> [1509049556.1145] manager: NetworkManager state is now DISCONNECTED > Oct 26 14:25:56 son-of-builder NetworkManager[824]: <info> [1509049556.1256] policy: set-hostname: set hostname to 'localhost.localdomain' (no default device) > Oct 26 14:25:56 son-of-builder systemd-hostnamed[8026]: Changed host name to 'localhost.localdomain' > Oct 26 14:25:56 son-of-builder nm-dispatcher[8018]: req:5 'down' [ens3]: new request (5 scripts) > Oct 26 14:25:56 son-of-builder nm-dispatcher[8018]: req:6 'hostname': new request (5 scripts) > Oct 26 14:25:56 son-of-builder nm-dispatcher[8018]: req:5 'down' [ens3]: start running ordered scripts... > Oct 26 14:25:56 son-of-builder nm-dispatcher[8018]: req:6 'hostname': start running ordered scripts... > Oct 26 14:26:06 son-of-builder audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > Oct 26 14:26:21 son-of-builder NetworkManager[824]: <info> [1509049581.0808] connectivity: (ens3) timed out > Oct 26 14:26:21 son-of-builder dbus-daemon[761]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=824 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0") > Oct 26 14:26:21 son-of-builder systemd[1]: Starting Network Manager Script Dispatcher Service... > Oct 26 14:26:21 son-of-builder dbus-daemon[761]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' > Oct 26 14:26:21 son-of-builder systemd[1]: Started Network Manager Script Dispatcher Service. > Oct 26 14:26:21 son-of-builder audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > Oct 26 14:26:21 son-of-builder nm-dispatcher[8169]: req:1 'connectivity-change': new request (5 scripts) > Oct 26 14:26:21 son-of-builder nm-dispatcher[8169]: req:1 'connectivity-change': start running ordered scripts... > Oct 26 14:26:26 son-of-builder audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > Oct 26 14:26:31 son-of-builder audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’ > > > Before the network configuration used to be rock-solid. I’m running on a Xeon D-1548 SoC with an on-chip X552/557 (ixgbe.ko) and an off-chip i350 (igb.ko) quad-NIC. In this case, I’m using the first port of the i350. > > The VM’s XML is unchanged, as it was previously (while things were working reliably): > > <interface type='network'> > <mac address='52:54:00:29:01:5b'/> > <source network='hostdev-net0'/> > <model type='virtio'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> > </interface> > > I’ve also tried “e1000”, “igb”, and “rtl8139” as the model type, with no appreciable difference since this problem started. > > Just did a quick check: reinstalling 4.11.10-300 seems to restore functionality. > > It was broken when I tried 4.12.11-300 as well. > > -Philip

1 0

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

qemu-kvm-ev-2.9.0-16.el7_4.8.1 now available for testing
by Sandro Bonazzola 18 Oct '17

18 Oct '17

Hi, qemu-kvm-ev-2.9.0-16.el7_4.8.1 <https://cbs.centos.org/koji/buildinfo?buildID=20353> is now available for testing. If no negative feedback will be reported, I'm going to push to release on Monday, October 23rd. Here's the changelog: * Wed Oct 18 2017 Sandro Bonazzola <sbonazzo(a)redhat.com> - ev-2.9.0-16.el7_4.8.1 - Removing RH branding from package name * Fri Sep 15 2017 Danilo Cesar Lemes de Paula <ddepaula(a)redhat.com> - rhev-2.9.0-16.el7_4.8 - kvm-ui-move-qemu_input_linux_to_qcode.patch [bz#1482388] - kvm-ui-update-keymaps.patch [bz#1482388] - kvm-ui-add-multimedia-keys.patch [bz#1482388] - kvm-ps2-enable-multimedia-keys.patch [bz#1482388] - kvm-ui-drop-altgr-and-altgr_r-QKeyCodes.patch [bz#1482388] - kvm-ui-drop-ac_search-and-ac_stop.patch [bz#1482388] - Resolves: bz#1482388 (Keys to control audio are not forwarded to the guest [rhel-7.4.z]) * Thu Sep 14 2017 Danilo Cesar Lemes de Paula <ddepaula(a)redhat.com> - rhev-2.9.0-16.el7_4.7 - kvm-vhost-Release-memory-references-on-cleanup.patch [bz#1490742] - Resolves: bz#1490742 (Hot-unplugging a vhost network device leaks references to VFIOPCIDevice's [rhel-7.4.z]) * Tue Sep 05 2017 Miroslav Rezanina <mrezanin(a)redhat.com> - rhev-2.9.0-16.el7_4.6 - kvm-ps2-fix-sending-of-PAUSE-BREAK-scancodes.patch [bz#1482389] - kvm-ui-correctly-detect-spice-PAUSE-scancode-sequence.patch [bz#1482389] - kvm-vhost-ensure-vhost_ops-are-set-before-calling-iotlb-.patch [bz#1480446] - kvm-vhost-user-unregister-slave-req-handler-at-cleanup-t.patch [bz#1480446] - Resolves: bz#1480446 (vhost-user/iommu: crash when backend disconnects [rhel-7.4.z]) - Resolves: bz#1482389 (Unable to send PAUSE/BREAK to guests in VNC or SPICE [rhel-7.4.z]) -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>

1 0

Updates for today VIrt SIG meeting
by Sandro Bonazzola 17 Oct '17

17 Oct '17

Hi, I won't be able to attend today Virt SIG meeting. On KVM side, there should be a RHEL update in the coming days, an update to qemu-kvm-ev will follow (https://bugzilla.redhat.com/show_bug.cgi?id=1501910 ). On oVirt side, upstream is finalizing 4.1.7 release and 4.2.0 beta; Virt SIG repos will be update after the releases. The oVirt 4.2 testing repos are now live on https://buildlogs.centos.org/centos/7/virt/x86_64/ovirt-4.2/ for x86_64, ppc64le, aarch64 Bug queue: - https://bugs.centos.org/view.php?id=12877 can be closed - https://bugs.centos.org/view.php?id=11457 was opened against oVirt 4.0, still valid for 4.1 and 4.2; still missing packages in altarch release mirrors. - https://bugs.centos.org/view.php?id=13747 can be closed - https://bugs.centos.org/view.php?id=13660 can be closed - https://bugs.centos.org/view.php?id=13633 still needed, opstools is still missing packages in altarch release mirrors. - https://bugs.centos.org/view.php?id=13463 I think this has been solved and can be closed - https://bugs.centos.org/view.php?id=13332 I think this has been solved and can be closed - https://bugs.centos.org/view.php?id=13283 still needed, not sure if there's any action needed on my side. - https://bugs.centos.org/view.php?id=12336 was reported on fc25, seems to work on fc26 I think it can be closed. - https://bugs.centos.org/view.php?id=11279 still needed, debuginfo missing for ppc64 and ppc64le packages. -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>

1 0

kernel-plus PXE virt-install with Xen?
by PJ Welsh 11 Oct '17

11 Oct '17

I'm trying to figure out how to replace the vmlinuz and initrd.img from CentOS 7.4 with "fixed" kernel-plus versions in order create CentOS 7.4 VM's. So far I'm stuck booting via 7.3 install, adding new kernel-plus and upgrading to 7.4. I've not found any complete Google answers and was looking for help making sure I choose the correct approach. I've tried to build an initrd.img from a kernel-plus booting system via "mkinitrd -f -v /boot/initrd.img $(uname -r)", but the file size is less than half the one from CentOS 7.4 (17MB -vs- 47MB). I'm not even sure I can just replace those files yet either. Any help going the correct path? Thanks PJ

2 3

"Error starting domain: Path '/usr/share/OVMF/OVMF_CODE.fd' is not accessible"
by Craig M 04 Oct '17

04 Oct '17

Recently upgraded my centOS 7 host, and was giving this error after trying to start the guest VM with virt-manager from my desktop: "Error starting domain: Path '/usr/share/OVMF/OVMF_CODE.fd' is not accessible, no such file or directory" I was told on irc that the OVMF package is now part the base centOS repos, so it replaced the installed OVMF package from the repo centos-release-qemnu-ev As a quick workaround to get the VM running again, i was able to do "yum downgrade OVMF" which did: Removed: OVMF.noarch 0:20170228-5.gitc325e41585e3.el7 Installed: OVMF.noarch 0:20150414-2.gitc9e5618.el7 i'm sending this email to ask is there another file i should be using instead of OVMF_Code.fd, for example was it replaced by something else that i should be using ? or is there an issue somewhere else.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt October 2017