Ovirt 4.3.7 release notes

Bug fixes

  • BZ 1476265 The engine VM could not be registered to foreman/satellite from the engine
  • BZ 1486565 Unable to drag and drop vNuma to the Numa nodes when using Internet Explorer version 11
  • BZ 1478283 Cannot import VM from previously used SD / ImportVmFromConfigurationCommand’ failed: null
  • BZ 1478687 — Events in the engine appear in reverse order
  • BZ 1485804 Unable to Import a VM linked with its template to RHV 4.1 from export domain imported of RHEV 3.5
  • BZ 1481115 Downloading an image with backing files from the sdk is triggering disk deletion

VDSM

  • BZ 1487913 Migration leads to VM running on 2 Hosts
  • BZ 1485807 virt-v2v: trying to import a VM with unreachable cdrom device caused the import to fail with “disk storage error”

oVirt Hosted Engine Setup

BZ 1486579 hosted-engine –upgrade-appliance fails with KeyError: ‘stopped’ if the metadata area contains references to 3.5 decommissioned hosts

Unclassified

  • BZ 1478315 Empty quotaID for HE VM causes VM_CANNOT_UPDATE_HOSTED_ENGINE_FIELD
  • BZ 1348467 Text getting truncated on virtual machine->affinity group->new page
  • BZ 1418156 The text/UI alignment needs to adjusted on quota->add screen.
  • BZ 1445235 Storage subtab is unsorted and keeps sorting its items
  • BZ 1486293 Frequent traceback on MetadataDiskDescriptionHandler
  • BZ 1483889 Custom Id is not persisted to the database
  • BZ 1484762 Allow changing type details in fn_db_change_column_type without changing the actual type
  • BZ 1479693 AuditLogDirector does not log messages if transactional command fails
  • BZ 1482569 Force remove of a storage domain should release MAC addresses only for VMs which are removed from the setup

VDSM

  • BZ 1487150 vdsm should ignore dummy interfaces and not try to enable Lldp on the dummy ports
  • BZ 1432386 static ip remain on the interface when removing non-vm network from it in case it has another vlan network attached
  • BZ 1482014 vdsmd fails to start if system time moves backwards during boot
  • BZ 1486347 Live merge fails with KeyError: ‘name’ in __refreshDriveVolume

ovirt-engine-extension-aaa-ldap

  • BZ 1482940 Login sequence fails on setup
  • BZ 1476980 AAA LDAP setup does not add baseDN to *-authn.properties
  • BZ 1462815 Assume the user is going to use ‘Single Sing-On for Virtual Machines’

ovirt-engine-dwh

  • BZ 1490272 Failed to start dwh service on NumberFormatException: For input string: “6.1”
  • BZ 1478859 DWH sampling is too high — switch back to 60s
  • BZ 1482043 DWH error — value too long for type character varying(40)|1

oVirt Cockpit Plugin

  • BZ 1480902 image_handler:186:root:(make_imaged_request) Failed communicating with vdsm-imaged: A Connection error occurred. ovirt-imageio-proxy
  • BZ 1487596 Update the generated gdeploy config script to halt the installation if blacklisting all the disks fails
  • BZ 1483521 Trim whitespaces in all the user provided text in the cockpit UI

VDSM

  • BZ 1487078 EnableLldpError: (255, ‘’, ‘connect: Connection refused\nFailed to connect to lldpad — clif_open: Invalid argument\n’, ‘enp12s0f1’)
  • BZ 1488358 Slow Initialization of LLDP on failure

CVE-2018-3639 — Important — oVirt — Speculative Store Bypass

As you may have already heard, an industry-wide issue was found in the way
many modern microprocessor designs have implemented speculative execution
of Load & Store instructions.
This issue is well described by CVE-2018-3639 announce available at
https://access.redhat.com/security/cve/cve-2018-3639.

oVirt team has released on May 23th an update of ovirt-engine to version
4.2.3.7 which add support for SSBD CPUs in order to mitigate the security
issue.

If you are running oVirt on Red Hat Enterprise Linux, please apply updates
described in https://access.redhat.com/security/cve/cve-2018-3639.

If you are running oVirt on CentOS Linux please apply updates described by:

  • CESA-2018:1629 Important CentOS 7 kernel Security Update
  • CESA-2018:1632 Important CentOS 7 libvirt Security Update
  • CESA-2018:1649 Important CentOS 7 java-1.8.0-openjdk Security Update
  • CESA-2018:1648 Important CentOS 7 java-1.7.0-openjdk Security Update

An update for qemu-kvm-ev has been also tagged for release and announced
with CESA-2018:1655 Important: qemu-kvm-ev security update

If you’re running oVirt on a different Linux distribution, please check
with your vendor for available updates.

Please note that to fully mitigate this vulnerability, system
administrators must apply both hardware “microcode” updates and software
patches that enable new functionality.
At this time, microprocessor microcode will be delivered by the individual
manufacturers.

The oVirt team recommends end users and systems administrator to apply any
available updates as soon as practical.

No Fedora support

Regretfully, Fedora is not supported anymore, and RPMs for it are not provided.
At this point, we only try to fix problems specific to Fedora if they affect
developers. For some of the work to be done to restore support for Fedora, see
also tracker bug 1460625.

EPEL

Don’t enable all of EPEL on oVirt machines.

The ovirt-release package enables the EPEL repositories and includes several
specific packages that are required from there. It also enables and uses
the CentOS SIG repos, for other packages.

If you want to use other packages from EPEL, you should make sure to
use and add only those you need avoiding to override
packages from other repos.

Creating a Virtual Machine Based on a Template

Create virtual machines based on templates. This allows you to create virtual machines that are pre-configured with an operating system, network interfaces, applications and other resources.

Note: Virtual machines created based on a template depend on that template. This means that you cannot remove that template from the Engine if there is a virtual machine that was created based on that template. However, you can clone a virtual machine from a template to remove the dependency on that template.

Creating a Virtual Machine Based on a Template

  1. Click Compute → Virtual Machines.

  2. Click New.

  3. Select the Cluster on which the virtual machine will run.

  4. Select a template from the Template list.

  5. Enter a Name, Description, and any Comments, and accept the default values inherited from the template in the rest of the fields. You can change them if needed.

  6. Click the Resource Allocation tab.

  7. Select the Thin or Clone radio button in the Storage Allocation area. If you select Thin, the disk format is QCOW2. If you select Clone, select either QCOW2 or Raw for disk format.

  8. Use the Target drop-down list to select the storage domain on which the virtual machine’s virtual disk will be stored.

  9. Click OK.

The virtual machine is displayed in the Virtual Machines tab.

Bug fixes

oVirt Engine

  • BZ 1449084 Can’t connect to engine web ui with chrome 58 (due to missing subjectAltName)
  • BZ 1438188 Failed to create template from snapshot (At most one USB controller expected)
  • BZ 1440071 Can’t create gluster georeplication
  • BZ 1435088 Auto-Import of HostedEngine VM fails due to missing CPU Profile Permissions
  • BZ 1428863 Getting ticket for VM that is down fails with NPE
  • BZ 1402838 Block memory over-commitment when KSM and ballooning are not being used
  • BZ 1383156 Enable HE deploy option in 3.6 cluster compatibility and add note in hosted engine tab that it will only work in host that are 4.0 and above.
  • BZ 1329119 Engine fails to start if machine’s memory is reduced by 75%
  • BZ 1291064 Change vm memory and cpu number not update automatically VNUMA nodes memory and cpu number
  • BZ 1444848 Error while importing a VM from 4.0 data domain
  • BZ 1444982 Host can be moved to maintenance while it there are jobs running on it
  • BZ 1424986 Increase the default factor for the CPU weight modules to preserve balance behavior for the PowerSaving and EvenDistribution policy
  • BZ 1431412 Reduce number of transactions in commands that use NetworkClusterHelper.setStatus

VDSM

  • BZ 1336840 Prevent import of VMware machines with snapshot
  • BZ 1428514 RHEL guests cannot recognize attached CD after CD change

oVirt Log collector

BZ 1227019 Require sos >= 3.3 when available — ovirt sosreport plugin doesn’t obfuscate password used in aaa extensions

oVirt Hosted Engine HA

  • BZ 1441570 After hosted engine upgrade from 4.1.0 to 4.1.1 the ability to connect to the vm via console is lost
  • BZ 1419326 Migration of the HE VM via engine will drop source host to the status ‘EngineUnexpectedlyDown’

oVirt Cockpit Plugin

  • BZ 1433925 poolmetadatasize for the thinpool created on arbiter node should not be 16GB
  • BZ 1438596 Include gdeploy multipath disable script

Creating a Linux Virtual Machine

Create a new virtual machine and configure the required settings.

Creating Linux Virtual Machines

  1. Click Compute → Virtual Machines.

  2. Click New button to open the New Virtual Machine window.

  3. Select an Operating System from the drop-down list.

  4. Enter a Name for the virtual machine.

  5. Add storage to the virtual machine. Attach or Create a virtual disk under Instance Images.

    • Click Attach and select an existing virtual disk.

    • Click Create and enter a Size(GB) and Alias for a new virtual disk. You can accept the default settings for all other fields, or change them if required. See for more details on the fields for all disk types.

  6. Connect the virtual machine to the network. Add a network interface by selecting a vNIC profile from the nic1 drop-down list at the bottom of the General tab.

  7. Specify the virtual machine’s Memory Size on the System tab.

  8. Choose the First Device that the virtual machine will boot from on the Boot Options tab.

  9. You can accept the default settings for all other fields, or change them if required. For more details on all fields in the New Virtual Machine window, see .

  10. Click OK.

The new virtual machine is created and displays in the list of virtual machines with a status of .

Creating a Windows Virtual Machine

Create a new virtual machine and configure the required settings.

Procedure

  1. You can change the default virtual machine name length with the tool. Run the following command on the Engine machine:

  2. Click Compute → Virtual Machines.

  3. Click New to open the New Virtual Machine window.

  4. Select an Operating System from the drop-down list.

  5. Enter a Name for the virtual machine.

  6. Add storage to the virtual machine. Attach or Create a virtual disk under Instance Images.

    • Click Attach and select an existing virtual disk.

    • Click Create and enter a Size(GB) and Alias for a new virtual disk. You can accept the default settings for all other fields, or change them if required.

  7. Connect the virtual machine to the network. Add a network interface by selecting a vNIC profile from the nic1 drop-down list at the bottom of the General tab.

  8. Specify the virtual machine’s Memory Size on the System tab.

  9. Choose the First Device that the virtual machine will boot from on the Boot Options tab.

  10. You can accept the default settings for all other fields, or change them if required.

  11. Click OK.

The new virtual machine is created and displays in the list of virtual machines with a status of . Before you can use this virtual machine, you must install an operating system and VirtIO-optimized disk and network drivers.

Starting the Virtual Machine Using the Run Once Option

Installing Windows on VirtIO-Optimized Hardware

Install VirtIO-optimized disk and network device drivers during your Windows installation by attaching the diskette to your virtual machine. These drivers provide a performance improvement over emulated device drivers.

Use the Run Once option to attach the diskette in a one-off boot different from the Boot Options defined in the New Virtual Machine window. This procedure presumes that you added a network interface and a disk that uses the interface to your virtual machine.

Installing VirtIO Drivers during Windows Installation

  1. Click Compute → Virtual Machines.

  2. Click Run → Run Once.

  3. Expand the Boot Options menu.

  4. Select the Attach Floppy check box, and select virtio-win.vfd from the drop-down list.

  5. Select the Attach CD check box, and select the required Windows ISO from the drop-down list.

  6. Move CD-ROM to the top of the Boot Sequence field.

  7. Configure the rest of your Run Once options as required.

  8. Click OK.

The Status of the virtual machine changes to , and the operating system installation begins. Open a console to the virtual machine if one does not open automatically.

Windows installations include an option to load additional drivers early in the installation process. Use this option to load drivers from the diskette that was attached to your virtual machine as . For each supported virtual machine architecture and Windows version, there is a folder on the disk containing optimized hardware device drivers.

Opening a Console to a Virtual Machine

Use Remote Viewer to connect to a virtual machine.

Connecting to Virtual Machines

  1. Install Remote Viewer if it is not already installed.

  2. Click Compute → Virtual Machines and select a virtual machine.

  3. Click Console.

    • If the connection protocol is set to SPICE, a console window will automatically open for the virtual machine.

    • If the connection protocol is set to VNC, a console.vv file will be downloaded. Click on the file and a console window will automatically open for the virtual machine.

    Note: You can configure the system to automatically connect to a virtual machine. See the “Automatically Connecting to a Virtual Machine” section in Chapter 2.

Install oVirt Engine using RPM

oVirt Engine is installed using RPM packages on a supported Enterprise Linux 8 distribution,
such as CentOS Linux or Red Hat Enterprise Linux.

Users can also compile from source, using the guides found under the Developers section. This is not recommended
unless you are a developer or need to customize the source code.

Important: You cannot skip a version when updating oVirt Engine. For example, if you are updating from
3.6 to 4.4, you first need to update to 4.0, then to 4.1, 4.2, 4.3 and finally to 4.4. (Host upgrades can use the
oVirt Fast Forward Upgrade tool.)
If you are updating from 4.3, please note you’ll need to migrate your engine from el7 to el8.

Upgrading from previous releases

For a standalone engine this means basically:

  1. backup engine data on 4.3.10 with:

  2. copy the backup to a safe location
  3. reinstall engine host with EL 8
  4. enable repos with:

  5. (reboot if needed)
  6. enable modules with:

  7. install engine rpms with:

  8. restore the engine data with:

  9. run .

Red Hat Enterprise Linux, CentOS Linux

  1. Enable the Base, Optional, and Extra repositories (Red Hat Enterprise Linux only):

  2. Add the official oVirt repository.

  3. Install oVirt Engine.

  4. Set up oVirt Engine.

  5. Follow the prompts to configure and install the Engine.

  6. Once the installation completes, oVirt’s web UI management interface will start and the URL will be printed
    to the screen. Browse to this URL to begin using oVirt!

    See Browsers and Mobile Clients for supported browsers and
    mobile client information.

Installing Guest Agents and Drivers

Drivers and Guest Agents Included with the Guest Tools ISO

The oVirt guest agents and drivers provide additional information and functionality for Enterprise Linux and Windows virtual machines. Key features include the ability to monitor resource usage and gracefully shut down or reboot virtual machines from the User Portal and Administration Portal. Install the oVirt guest agents and drivers on each virtual machine on which this functionality is to be available.

oVirt Guest Drivers

Driver Description Works on
virtio-net Paravirtualized network driver provides enhanced performance over emulated devices like rtl. Server and Desktop.
virtio-block Paravirtualized HDD driver offers increased I/O performance over emulated devices like IDE by optimizing the coordination and communication between the guest and the hypervisor. The driver complements the software implementation of the virtio-device used by the host to play the role of a hardware device. Server and Desktop.
virtio-scsi Paravirtualized iSCSI HDD driver offers similar functionality to the virtio-block device, with some additional enhancements. In particular, this driver supports adding hundreds of devices, and names devices using the standard SCSI device naming scheme. Server and Desktop.
virtio-serial Virtio-serial provides support for multiple serial ports. The improved performance is used for fast communication between the guest and the host that avoids network complications. This fast communication is required for the guest agents and for other features such as clipboard copy-paste between the guest and the host and logging. Server and Desktop.
virtio-balloon Virtio-balloon is used to control the amount of memory a guest actually accesses. It offers improved memory over-commitment. The balloon drivers are installed for future compatibility but not used by default in oVirt. Server and Desktop.
qxl A paravirtualized display driver reduces CPU usage on the host and provides better performance through reduced network bandwidth on most workloads. Server and Desktop.

oVirt Guest Agents and Tools

Guest agent/tool Description Works on
ovirt-engine-guest-agent-common

Allows the oVirt Engine to receive guest internal events and information such as IP address and installed applications. Also allows the Engine to execute specific commands, such as shut down or reboot, on a guest.

On Enterprise Linux 6 and higher guests, the ovirt-engine-guest-agent-common installs tuned on your virtual machine and configures it to use an optimized, virtualized-guest profile.

Server and Desktop.
spice-agent The SPICE agent supports multiple monitors and is responsible for client-mouse-mode support to provide a better user experience and improved responsiveness than the QEMU emulation. Cursor capture is not needed in client-mouse-mode. The SPICE agent reduces bandwidth usage when used over a wide area network by reducing the display level, including color depth, disabling wallpaper, font smoothing, and animation. The SPICE agent enables clipboard support allowing cut and paste operations for both text and images between client and guest, and automatic guest display setting according to client-side settings. On Windows guests, the SPICE agent consists of vdservice and vdagent. Server and Desktop.
ovirt-sso An agent that enables users to automatically log in to their virtual machines based on the credentials used to access the oVirt Engine. Desktop.
Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *

Adblock
detector