virt May 2019

virt@lists.centos.org

5 participants
3 discussions

CentOS 7 Xen 4.12 libvirt/virt-manager wrong path for qemu-system-i386
by Pasi Kärkkäinen 27 May '19

27 May '19

Hello, While testing Virt-SIG Xen 4.12 rpms on CentOS7 I noticed the following problem with libvirt/virt-manager when manually installing a new HVM guest from virt-manager GUI.. basicly the VM installation won't start, because libvirt/virt-manager is not able to start the VM, due to "missing" qemu-system-i386 binary: Unable to complete install: 'unsupported configuration: emulator '/usr/lib/xen/bin/qemu-system-i386' not found' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 2553, in _do_async_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 498, in start_install doboot, transient) File "/usr/share/virt-manager/virtinst/guest.py", line 434, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3725, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirtError: unsupported configuration: emulator '/usr/lib/xen/bin/qemu-system-i386' not found Quick'n'dirty fix is to create a symlink: ln -s /usr/lib64/xen/bin/qemu-system-i386 /usr/lib/xen/bin/qemu-system-i386 .. after creating that symlink the VM can be started just fine and works OK. We need to fix that default directory path for qemu-system-i386 to be correct out-of-the-box.. Thanks, -- Pasi

2 3

centos-virt CPU microcode updates?
by Karel Hendrych 17 May '19

17 May '19

Hi, is there any guide for CPU microcode updates on CentOS6, Xen 4.10, kernel 4.9 ? Thanks Karel

3 3

Centos7 Xen hypervisor console= options broken in default grub2 config
by Pasi Kärkkäinen 05 May '19

05 May '19

Hello, While testing Virt-SIG Xen 4.12 rpms on CentOS 7, I noticed the default Xen hypervisor console= option parameters are broken, and result in an error from Xen, and no output on the physical vga console: >From xen dmesg: (XEN) Bad console= option 'tty' Xen 4.12.0-1.el7 (XEN) Xen version 4.12.0-1.el7 (mockbuild(a)centos.org) (gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)) debug=n Tue Apr 2 13:09:41 UTC 2019 (XEN) Latest ChangeSet: (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 .. and indeed, 'tty' is not a valid option for Xen hypervisor console= parameter. That can be easily fixed in "/etc/sysconfig/grub", and executing "grub2-mkconfig -o /boot/grub2/grub.cfg" afterwards, but we should fix the default.. Here is the working setting (console=com1,vga, instead of console=com1,tty): # grep GRUB_CMDLINE_XEN_DEFAULT /etc/sysconfig/grub GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,vga loglvl=all guest_loglvl=all" Thanks, -- Pasi

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt May 2019