You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

4157 lines
134 KiB

  1. ================
  2. libvirt releases
  3. ================
  4. This is the list of official releases for libvirt, along with an overview of
  5. the changes introduced by each of them.
  6. For a more fine-grained view, use the `git log`_.
  7. v6.5.0 (2020-07-03)
  8. ===================
  9. * **New features**
  10. * Allow firmware blobs configuration
  11. QEMU offers a way to tweak how firmware configures itself
  12. and/or provide new configuration blobs. New ``<sysinfo/>``
  13. type is introduced that will hold these new blobs.
  14. It's possible to either specify new value as a string or
  15. provide a filename which contents then serve as the value.
  16. * nodedev: Add ability to create mediated devices
  17. Mediated devices can now be created with ``virNodeDeviceCreateXML()``. This
  18. functionality requires the ``mdevctl`` utility to be installed. The XML
  19. schema for node devices was expanded to support attributes for mediated
  20. devices.
  21. * QEMU: add TPM Proxy device support
  22. libvirt can now create guests using a new device type called
  23. "TPM Proxy". The TPM Proxy connects to a TPM Resource Manager
  24. present in the host, enabling the guest to run in secure virtual
  25. machine mode with the help of an Ultravisor. Adding a TPM Proxy to
  26. a pSeries guest brings no security benefits unless the guest is
  27. running on a PPC64 host that has Ultravisor and TPM Resource Manager
  28. support. Only one TPM Proxy is allowed per guest. A guest using
  29. a TPM Proxy device can instantiate another TPM device at the same
  30. time. This device is supported only for pSeries guests via the new
  31. 'spapr-tpm-proxy' model of the TPM 'passthrough' backend.
  32. * virhook: Support hooks placed in several files
  33. Running all scripts from directory /etc/libvirt/hooks/<driver>.d in
  34. alphabetical order. Hook script in old place will be executed
  35. as first for backward compatibility.
  36. * qemu: Add support for migratable host-passthrough CPU
  37. QEMU 2.12 made it possible for guests to use a migration-friendly
  38. version of the host-passthrough CPU. This feature is now exposed by
  39. libvirt.
  40. * **Improvements**
  41. * network: Support NAT with IPv6
  42. It's now possible to use ``<nat ipv6="yes"/>`` in a libvirt network.
  43. * qemu: Auto-fill NUMA information for incomplete topologies
  44. If the NUMA topology is not fully described in the guest XML, libvirt
  45. will complete it by putting all unspecified CPUs in the first NUMA node.
  46. This is only done in the QEMU binary itself supports disjointed CPU
  47. ranges for NUMA nodes.
  48. * qemu: Assign hostdev-backed interfaces to PCIe slots
  49. All SR-IOV capable devices are PCIe, so when their VFs are assigned to
  50. guests they should end up in PCIe slots rather than conventional PCI ones.
  51. * **Bug fixes**
  52. * qemu: fixed crash in ``qemuDomainBlockCommit``
  53. This release fixes a regression which was introduced in libvirt v6.4.0
  54. where libvirtd always crashes when a block commit of a disk is requested.
  55. * qemu: fixed zPCI address auto generation on s390
  56. Removes the correlation between the zPCI address attributes uid and fid.
  57. Fixes the validation and autogeneration of zPCI address attributes.
  58. * qemu: Skip pre-creation of NVMe disks during migration
  59. libvirt has no way to create NVMe devices on the target host, so it now
  60. just makes sure they exist and let the migration proceed in that case.
  61. v6.4.0 (2020-06-02)
  62. ===================
  63. * **New features**
  64. * qemu: Add support for pvscsi controllers
  65. pvscsi is the VMware paravirtualized SCSI controller, which has been
  66. supported in QEMU for a number of years.
  67. * cpu: Report model information for ARM CPUs
  68. ``virsh capabilities`` will now include information about the host CPU when
  69. run on ARM machines.
  70. * **Improvements**
  71. * qemu: stricter validation for disk type='lun'
  72. The 'lun' type is meant for SCSI command passthrough, which can't be
  73. achieved if qemu's block layer features are used. Disk type='lun' is now
  74. allowed only when the format is 'raw' and no other block layer features are
  75. requested.
  76. * qemu: auto-fill of incomplete NUMA topologies
  77. Domains with incomplete NUMA topologies, where the sum of vCPUs in all NUMA
  78. cells is less than the total of vCPUs, will get their first NUMA cell to
  79. be auto-filled with the remaining vCPUs. This behavior reproduces what QEMU
  80. already does in these cases. Users are encouraged to provide complete NUMA
  81. topologies to avoid unexpected changes in the domain XML.
  82. * **Bug fixes**
  83. * qemu: fixed regression in network device hotplug with new qemu versions
  84. Starting from QEMU-5.0 it's required to conform to strict schema when
  85. hotplugging network devices. Libvirt didn't conform to the schema so in
  86. versions prior to 6.4.0 network device hotplug fails in certain cases. This
  87. version fixes it and adds stricter testing to prevent further issues.
  88. * remote: Look up libxl driver correctly
  89. This makes ``xen://`` connection URIs usable in split daemon mode.
  90. * systemd: Start libvirtd after firewalld/iptables services
  91. This solves an issue where iptables rules and chains created by libvirtd
  92. would get removed by a service started after it.
  93. * network: Re-create iptables chains on firewalld restart
  94. firewalld resets all iptables rules and chains on restart, and this
  95. includes deleting those created by libvirt.
  96. v6.3.0 (2020-05-05)
  97. ===================
  98. * **New features**
  99. * qemu: support network interface downscript
  100. QEMU has the ability to run a script when a NIC is brought up and down.
  101. Libvirt only enables use of the up script. Now add support for postscript
  102. when NIC is down/detached.
  103. * qemu: support disabling hotplug/unplug of PCIe devices
  104. libvirt can now set the "hotplug" option for pcie-root-ports and
  105. pcie-switch-downstream-ports, which can be used to disable hotplug/unplug
  106. of devices from these ports (default behavior is for these controllers to
  107. accept all hotplug/unplug attempts, but this is often undesireable).
  108. * vbox: added support for version 6.0 and 6.1 APIs
  109. libvirt can now support use of the VirtualBox 6.0 and 6.1 APIs. This is
  110. compile tested only, so we are looking for feedback from users on how well
  111. it works in practice.
  112. * xen: Add support for 'e820_host' hypervisor feature
  113. ``e820_host`` is a Xen-specific option only available for PV guests. When
  114. enabled it provides the guest with a virtual e820 memory map based on the
  115. host one. It must be enabled to allow hotplugging PCI devices to PV guests,
  116. particularly when memory ballooning is enabled.
  117. * xen: Add support for 'passthrough' hypervisor feature
  118. ``passthrough`` is a Xen-specific option new to Xen 4.13 that enables PCI
  119. passthrough for guests. It must be enabled to allow hotplugging PCI
  120. devices.
  121. * qemu: support async IO mode 'io_uring'
  122. Linux 5.1 introduces a fast and efficient async IO interface io_uring, then
  123. qemu implements that in version 5.0. It could be used in file, host device
  124. and host cdrom backend by ``io='io_uring'`` of disk XML.
  125. * Lease time option included for network DHCP settings
  126. Users can now configure expiry time for leases for networks where libvirt
  127. manages DHCP. The time can be specified for whole range and/or fine tuned
  128. per individual host.
  129. * qemu: Implement pSeries Spectre mitigation features
  130. Users can now setup the following capabilities of pSeries guests: CFPC
  131. (Cache Flush on Privilege Change), SBBC (Speculation Barrier Bounds
  132. Checking) and IBS (Indirect Branch Speculation).
  133. * **Improvements**
  134. * qemu: Allow checkpoint redefine for offline VMs
  135. Skip the liveness and capability checks when redefining checkpoints as we
  136. don't need QEMU interactions to update the metadata.
  137. * daemons: Improve timeout handling
  138. Daemons now support ``--timeout 0`` which suppresses daemon killing after
  139. given time of inactivity.
  140. * qemu: Add support for 'multidevs' option
  141. This option prevents misbehaviours on guest if a QEMU 9pfs export contains
  142. multiple devices, due to the potential file ID collisions this otherwise
  143. may cause.
  144. * **Bug fixes**
  145. * qemu: Various embed driver fixes
  146. When using shared resources from embed driver (e.g. hugepages, machined,
  147. etc.) libvirt now generates an unique handler that is not conflicting with
  148. other embed drivers or system or session daemons.
  149. * cpu: Distinguish Cascadelake-Server from Skylake-Server
  150. Libvirt now properly detects Cascadelake-Server and Skylake-Server
  151. processors which differ only in stepping.
  152. * qemu: Fix domain restore from a block device
  153. When using namespaces, libvirt was unable to restore a domain from a block
  154. device because libvirt tried to relabel the device inside the namespace
  155. while QEMU was given FD to the block device in the host.
  156. * node_device_udev: Handle move events
  157. Libvirt now handles ``move`` event which is emitted on a NIC rename.
  158. * qemu: Fix capabilities probing with TCG
  159. Libvirt no long assumes TCG is always available. It now detects whether
  160. QEMU supports TCG and reports it accordingly.
  161. * **Removed features**
  162. * vbox: removed support for version 5.0 and 5.1 APIs
  163. libvirt no longer supports use of VirtualBox 5.0 and 5.1 since these
  164. versions reached their end of life on 2017/05 and 2018/04 respectively.
  165. v6.2.0 (2020-04-02)
  166. ===================
  167. * **New features**
  168. * qemu: NVDIMM support for pSeries guests
  169. QEMU 5.0 implements NVDIMM memory support for pSeries guests. This is done
  170. by adding an 'uuid' element in the memory XML, which can either be provided
  171. in the XML or, if omitted, generated automatically.
  172. * qemu: Add virtiofs support
  173. This feature, introduced in QEMU 4.2, is a more modern alternative to
  174. virtio-9p, which is exposed through the same ``<filesystem/>`` element.
  175. * admin: Support reloading TLS certificates
  176. After renewing TLS certificates, it was usually necessary to restart
  177. libvirtd for the new ones to be loaded: now the same result can be obtained
  178. without restarting the daemon by using ``virt-admin server-update-tls`` .
  179. * **Removed features**
  180. * Removed support for INI style of comments
  181. With switching of our internal code to GLib, parsing of client
  182. authentication config files is handed over to GLib which does not support
  183. ``INI`` style of comments starting with a semicolon ( ``;`` ). Use number
  184. sign ( ``#`` ) instead.
  185. * **Improvements**
  186. * qemu: Don't compare local and remote hostnames on migration
  187. This check was introduced to prevent same-host migration, but did not work
  188. as expected when multiple libvirtd instances were running on the same host
  189. but in different containers. With this release, the host UUID (which should
  190. be unique to the container) is checked instead.
  191. * qemu: Use per-VM event loops
  192. Instead of using a single even loop to process communication with the QEMU
  193. monitor and guest agent, create a separate one for each VM. This helps with
  194. scalability and prevents scenarios where a single malfunctioning VM could
  195. affect all those running on the same host.
  196. * qemu: Support migration with SLIRP helper interface
  197. With QEMU 5.0, a new D-Bus backend allows migration of external processes.
  198. When needed, libvirt will start a per-vm D-Bus bus, and migrate the
  199. slirp-helper along with QEMU.
  200. * **Bug fixes**
  201. * qemu: Open backing chain late for shallow block copy reusing external
  202. images
  203. With introduction of -blockdev for QEMU storage configuration in
  204. libvirt-5.10 we've started opening the backing chain of the
  205. destination/mirror of a virDomainBlockcopy started with
  206. VIR_DOMAIN_BLOCK_COPY_REUSE_EXT | VIR_DOMAIN_BLOCK_COPY_SHALLOW flags when
  207. starting the job rather than when virDomainBlockJobAbort with
  208. VIR_DOMAIN_BLOCK_JOB_ABORT_PIVOT is issued. For users depending on this
  209. undocumented quirky pre-blockdev behaviour this caused a regression as the
  210. backing chain could not be modified while the copy of the top image was
  211. progressing due to QEMU image locking. Note that this fix also requires
  212. qemu-5.0 while -blockdev is used starting from QEMU-4.2.
  213. * Don't generate machine names containing dots
  214. Even though the guest name containing dots is not a problem for libvirt
  215. itself, we need to strip them out when registering with machined because of
  216. the latter's requirements.
  217. v6.1.0 (2020-03-03)
  218. ===================
  219. * **New features**
  220. * qemu: new rng backend type: builtin
  221. It implements qemu builtin rng backend. That uses getrandom syscall to
  222. generate random, no external rng source needed. Available since QEMU 4.2.
  223. * support for virtio+hostdev NIC <teaming>
  224. QEMU 4.2.0 and later, combined with a sufficiently recent guest virtio-net
  225. driver (e.g. the driver included in Linux kernel 4.18 and later), supports
  226. setting up a simple network bond device comprised of one virtio emulated
  227. NIC and one hostdev NIC (which must be an SRIOV VF). (in QEMU, this is
  228. known as the "virtio failover" feature). The allure of this setup is that
  229. the bond will always favor the hostdev device, providing better
  230. performance, until the guest is migrated - at that time QEMU will
  231. automatically unplug the hostdev NIC and the bond will send all traffic via
  232. the virtio NIC until migration is completed, then QEMU on the destination
  233. side will hotplug a new hostdev NIC and the bond will switch back to using
  234. the hostdev for network traffic. The result is that guests desiring the
  235. extra performance of a hostdev NIC are now migratable without network
  236. downtime (performance is just degraded during migration) and without
  237. requiring a complicated bonding configuration in the guest OS network
  238. config and complicated unplug/replug logic in the management application on
  239. the host - it can instead all be accomplished in libvirt with the interface
  240. <teaming> subelement "type" and "persistent" attributes.
  241. * support BR_ISOLATED flag for guest interfaces attached to a Linux host
  242. bridge
  243. Since Linux kernel 4.18, the Linux host bridge has had a flag BR_ISOLATED
  244. that can be applied to individual ports. When this flag is set for a port,
  245. traffic is blocked between that port and any other port that also has the
  246. BR_ISOLATED flag set. libvirt domain interface config now supports setting
  247. this flag via the <port isolated='yes'/> setting. It can also be set for
  248. all connections to a particular libvirt network by setting the same option
  249. in the network config - since the port for the host itself does not have
  250. BR_ISOLATED set, the guests can communicate with the host and the outside
  251. world, but guests on that network can't communicate with each other. This
  252. feature works for QEMU and LXC guests with interfaces attached to a Linux
  253. host bridge.
  254. * qemu: Introduce the 'armvtimer' timer type
  255. QEMU 5.0 introduces the ability to control the behavior of the virtual
  256. timer for KVM ARM/virt guests, and this new timer type exposes the same
  257. capability to libvirt users.
  258. * qemu: Storage configuration improvements
  259. Libvirt now accepts ``<backingStore type='volume'>`` and allows specifying
  260. the offset and size of the image format container inside the storage source
  261. via the ``<slices>`` subelement.
  262. * qemu: Introduce the 'tpm-spapr' TPM model
  263. This device, available starting from QEMU 5.0, is limited to pSeries
  264. guests.
  265. * **Improvements**
  266. * qemu: Image format probing is allowed in certain cases
  267. To resolve regressions when users didn't specify the backing image format
  268. in the overlay, libvirt now probes the format in certain secure scenarios
  269. which fixes a few common existing cases. Additionally the knowledge base
  270. was extended to provide more information on how to rectify the problem.
  271. * qemu: Support "dies" in CPU topology
  272. This CPU topology concept, new in QEMU 4.1.0, sits between the existing
  273. "socket" and "core".
  274. * libxl: Add support for Credit2 scheduler parameters
  275. * lxc: Add support LXC 3 network configuration format
  276. * **Bug fixes**
  277. * conf: Do not generate machine names ending with a dash
  278. Recent systemd versions do not allow them.
  279. * **Packaging changes**
  280. * use of gnulib has been completely eliminated
  281. Historically libvirt has embedded gnulib to provide fixes for various
  282. platform portability problems. This usage has now been eliminated and
  283. alternative approaches for platform portability problems adopted where
  284. required. This has been validated on the set of platforms covered by
  285. automated CI build testing. Other modern Linux distros using glibc are
  286. expected to work. Linux distros using non-glibc packages, and other
  287. non-Linux platforms may encounter regressions when building this release.
  288. Please report any build problems encountered back to the project
  289. maintainers for evaluation.
  290. v6.0.0 (2020-01-15)
  291. ===================
  292. * **Packaging changes**
  293. * support for python2 is removed
  294. Libvirt is no longer able to be built using the Python 2 binary. Python 3
  295. must be used instead.
  296. * docs: the python docutils toolset is now required
  297. The use of rst2html has been introduced for the website build process since
  298. docs are now being written in the RST as an alternative to HTML.
  299. * **New features**
  300. * new PCI hostdev address type: unassigned
  301. A new PCI hostdev address type 'unassigned' is introduced. An unassigned
  302. PCI hostdev behaves like any regular PCI hostdev inside Libvirt, but it is
  303. not usable by the guest. This gives the user a new option to manage the
  304. binding of PCI devices via Libvirt, declaring PCI hostdevs in the domain
  305. XML but allowing just a subset of them to be assigned to the guest.
  306. * Provide init scripts for sub-deaemons
  307. So far libvirt shipped systemd unit files for sub-daemons. With this
  308. release, init scripts are available too. Package maintainers can choose
  309. which one to install via ``--with-init-script`` configure option.
  310. * qemu: Support cold-unplug of sound devices
  311. * qemu: Implement VIR_MIGRATE_PARAM_TLS_DESTINATION
  312. This flag, which can be enabled using ``virsh`` 's ``--tls-destination``
  313. option, allows migration to succeed in situations where there is a mismatch
  314. between the destination's hostname and the information stored in its TLS
  315. certificate.
  316. * qemu: Support reporting memory bandwidth usage stats
  317. Implement Intel RDT-MBM in libvirt. The stats can be obtained via ``virsh
  318. domstats --memory`` .
  319. * qemu: Allow accessing NVMe disks directly
  320. Before this release there were two ways to configure a NVMe disk for a
  321. domain. The first was using <disk/> with the <source/> pointing to the
  322. ``/dev/nvmeXXXX`` . The other was using PCI assignment via <hostdev/>
  323. element. Both have their disadvantages: the former adds latency of file
  324. system and block layers of the host kernel, the latter prohibits domain
  325. migration. In this release the third way of configuring NVMe disk is added
  326. which combines the advantages and drops disadvantages of the previous two
  327. ways. It's accessible via <disk type='nvme'/>.
  328. * **Removed features**
  329. * 'phyp' Power Hypervisor driver removed
  330. The 'phyp' Power Hypervisor driver has not seen active development since
  331. 2011 and does not seem to have any real world usage. It has now been
  332. removed.
  333. * **Improvements**
  334. * qemu: xz save image compression is faster
  335. When using the xz format to compressed virtual machine saved state images,
  336. the "-3" compression level preset is now used. This results in slightly
  337. larger files, but with a massively reduced time to compress. The xz format
  338. offers the best compression level for saved state images, albeit still with
  339. the slowest running time. For the fastest possible running time, at cost of
  340. the larest compressed size, lzop should be used.
  341. * domain: Improve job stat handling
  342. It is now possible to retrieve stats for completed and failed jobs.
  343. * qemu: Don't hold monitor and agent job at the same time
  344. Before this change, a malicious (or buggy) ``qemu-guest-agent`` running in
  345. the guest could make other libvirt APIs unavailable for an unbounded amount
  346. of time.
  347. * **Bug fixes**
  348. * qemu: Report error if backing image format is not specified explicitly
  349. For a long time libvirt was assuming that a backing file is RAW when the
  350. format was not specified. This didn't pose a problem until blockdev support
  351. was enabled in last release. Libvirt now requires that the format is
  352. specified in the image metadata or domain XML and the VM will refuse to
  353. start otherwise. Additionally the error message now links to the knowledge
  354. base which summarizes how to fix the images.
  355. * qemu: Fix non-shared storage migration over NBD
  356. * qemu: Generate a single MAC address for hotplugged network devices
  357. Since libvirt 4.6.0, when hotplugging a network device that didn't have a
  358. MAC address already assigned by the user, two separate addresses would be
  359. generated: one for the live configuration, which would show up immediately,
  360. and one for the inactive configuration, which would show up after the first
  361. reboot. This situation was clearly undesirable, so a single MAC address is
  362. now generated and used both for the live configuration and the inactive
  363. one.
  364. v5.10.0 (2019-12-02)
  365. ====================
  366. * **New features**
  367. * qemu: Introduce support for ARM CPU features
  368. The only features supported at the moment are SVE vector lengths, which
  369. were introduced in QEMU 4.2.0.
  370. * qemu: Support boot display for GPU mediated devices
  371. Until now, GPU mediated devices generally did not show any output until the
  372. guest OS had initialized the vGPU. By specifying the ``ramfb`` attribute,
  373. QEMU can be configured to use ramfb as a boot display for the device: this
  374. allows for display of firmware messages, boot loader menu, and other output
  375. before the guest OS has initialized the vGPU.
  376. * Add API to change the response timeout for guest agent commands
  377. By default, when a command is sent to the guest agent, libvirt waits
  378. forever for a response from the guest agent. If the guest is unresponsive
  379. for any reason, this can block the calling thread indefinitely. By setting
  380. a custom timeout using ``virDomainAgentSetResponseTimeout()`` , API users
  381. can change this behavior.
  382. * **Improvements**
  383. * Devices CGroup v2 support
  384. Libvirt supported all controllers of CGroup v2 but the devices controller
  385. which is implemented in this release.
  386. * Cold plug of sound device
  387. The QEMU driver now can handle cold plug of ``<sound/>`` devices.
  388. * Probe for default CPU types
  389. With QEMU 4.2.0 we can probe for the default CPU model used by QEMU for a
  390. particular machine type and store it in the domain XML. This way the chosen
  391. CPU model is more visible to users and libvirt will make sure the guest
  392. will see the exact same CPU after migration.
  393. * Adaptation to qemu's blockdev
  394. QEMU introduced a new way of specifying disks on the command line which
  395. enables fine-grained control over the block stack. Libvirt has adapted to
  396. this.
  397. * **Refactors**
  398. * More GLib integration
  399. More patches were merged that replace our internal functions with GLib
  400. ones. Also some effort was invested in replacing gnulib modules with GLib
  401. functions.
  402. * Rewrite of Perl scripts into Python
  403. Libvirt used Perl scripts to check for coding style, generate some code and
  404. things like that. To bring the number of languages used down, these scripts
  405. were rewritten into Python.
  406. * **Bug fixes**
  407. * Warn verbosely if using old loader:nvram pairs
  408. Some distributions still use ``--with-loader-nvram`` or ``nvram`` variable
  409. in qemu.conf. This is now discouraged in favour of FW descriptors. However,
  410. instead of silently ignoring user's config, libvirt warns if outdated
  411. config is detected.
  412. * Drop pconfig from Icelake-Server CPU model
  413. The pconfig feature was enabled in QEMU by accident in 3.1.0. All other
  414. newer versions do not support it and it was removed from the Icelake-Server
  415. CPU model in QEMU.
  416. * Wait longer for device removal confirmation on PPC64
  417. After sending device hot unplug request to QEMU, libvirt waits up to 5
  418. seconds for qemu to confirm the device removal. On some architectures (like
  419. PPC64) this can take longer time and libvirt now reflects that.
  420. * Forcibly create nodes in domain's namespace
  421. The QEMU driver starts a domain in a namepsace with private ``/dev`` and
  422. creates only those nodes there which the domain is configured to have.
  423. However, it may have happened that if a node changed its minor number this
  424. change wasn't propagated to the namespace.
  425. * Various AppArmor bugfixes
  426. The AppArmor driver now knows how to handle ``<shmem/>`` devices and also
  427. snapshotting more disks at once.
  428. * Improved video model autoselection
  429. If a graphics device was added to XML that had no video device, libvirt
  430. automatically added a video device which was always of type 'cirrus' on
  431. x86_64, even if the underlying qemu didn't support cirrus. Libvirt now
  432. bases the decision on qemu's capabilities.
  433. v5.9.0 (2019-11-05)
  434. ===================
  435. * **Packaging changes**
  436. * Start linking against GLib and using its features
  437. Up until now, libvirt has been dealing with platform portability and the
  438. lack of certain features in libc by using gnulib and implementing its own
  439. functions and data structures respectively; going forward, it will prefer
  440. the facilities offered by GLib instead.
  441. * Stop distributing generated documentation
  442. Most downstreams already patch the libvirt source to some extent, so this
  443. change will probably not affect them.
  444. * Rewrite several Perl scripts in Python
  445. Phasing out Perl usage is part of the project strategy.
  446. * **New features**
  447. * qemu: Introduce a new video model of type 'ramfb'
  448. Introduce a new video model type to the domain XML that supports the
  449. ``ramfb`` standalone device in qemu.
  450. * qemu: Implement the ccf-assist pSeries feature
  451. Users can now decide whether ccf-assist (Count Cache Flush Assist) support
  452. should be available to pSeries guests.
  453. * Xen: Support specifying ACPI firmware path
  454. The libxl driver now supports specifying an ACPI firmware path using the
  455. ``acpi`` element.
  456. * qemu: Support specifying resolution for video devices
  457. * **Removed features**
  458. * logging: Drop support for including stack traces
  459. This feature was intended to aid debugging, but in practice it resulted in
  460. logs that were too verbose to be useful and also resulted in a significant
  461. performance penalty.
  462. * **Improvements**
  463. * qemu: Implement CPU comparison/baseline on s390x
  464. This functionality has been historically limited to x86_64, but it's now
  465. available on s390x too.
  466. * **Bug fixes**
  467. * lib: autostart objects exactly once
  468. If libvirtd or any of the sub-daemons is started with socket activation
  469. then objects might be autostarted more than once. For instance, if a domain
  470. under ``qemu:///session`` URI is mark as autostarted and the session daemon
  471. is started then the domain is started with it. If user shuts the domain
  472. down and the session daemon is started again, the user's wish to keep the
  473. domain shut off is ignored and the domain is autostarted again. This is now
  474. fixed.
  475. * qemu: Properly advertise bochs-display availability
  476. Support for ``bochs-display`` was introduced in libvirt 5.6.0, but until
  477. now the model was not listed in the domain capabilities.
  478. * security: Don't remember labels for TPM devices
  479. Due to the way they're implemented in the kernel, trying to remember labels
  480. for TPM devices makes it impossible to use them.
  481. * security: Properly rollback after failure in a stacked driver
  482. When multiple security drivers are involved, failure in one of them would
  483. result in only the corresponding changes being rolled back, leaving the
  484. ones performed by drivers that had been activated earlier in place. All
  485. changes are rolled back now.
  486. * Fix build with musl libc
  487. * Improve compatibility with non-bash shells
  488. v5.8.0 (2019-10-05)
  489. ===================
  490. * **New features**
  491. * qemu: Support use of precreated tap/macvtap devices by unprivileged
  492. libvirtd
  493. It is now possible for an unprivileged libvirtd to make use of tap and
  494. macvtap devices that were previously created by some other entity. This is
  495. done by setting ``managed='no'`` along with the device name in the
  496. ``target`` subelement of ``<interface type='ethernet'>`` .
  497. * qemu: Support vhost-user-gpu
  498. Support for running virtio GPUs in separate processes with vhost-user
  499. backend. It requires QEMU newer than 4.1.
  500. * Introduce virConnectSetIdentity API
  501. When split daemons are in use, this API is used to forward uid, gid and
  502. SELinux info from ``virproxyd`` to other driver daemons such as
  503. ``virtqemud`` .
  504. * **Improvements**
  505. * qemu: Support running SLIRP networking in a separate process
  506. User can configure the slirp-helper path in ``qemu.conf`` . It will start a
  507. slirp-helper process to provide SLIRP networking when the VM is started
  508. with network interface "user". That will allow stricter security policies
  509. for QEMU SLIRP network.
  510. * **Removed features**
  511. * Remove xenapi driver
  512. The xenapi driver is removed since it has not received any significant
  513. development since its initial contribution nine years ago and has no known
  514. user base.
  515. v5.7.0 (2019-09-03)
  516. ===================
  517. * **New features**
  518. * qemu: Support Direct Mode for Hyper-V Synthetic timers
  519. The QEMU driver now supports Direct Mode for Hyper-V Synthetic timers for
  520. Hyper-V guests.
  521. * lib: Add virDomainGetGuestInfo()
  522. This API is intended to aggregate several guest agent information queries
  523. and is inspired by stats API ``virDomainListGetStats()`` . It is
  524. anticipated that this information will be provided by a guest agent running
  525. within the domain. It's exposed as ``virsh guestinfo`` .
  526. * Experimental split of libvirtd into separate daemons
  527. The big monolithic libvirtd daemon can now be replaced by smaller
  528. per-driver daemons. The new split daemons are considered experimental at
  529. this time and distributions are encouraged to continue using the
  530. traditional libvirtd by default.
  531. * qemu: Support kvm-hint-dedicated performance hint
  532. With ``<hint-dedicated state='on'/>`` and ``<cpu
  533. mode='host-passthrough'/>`` , it allows a guest to enable optimizations
  534. when running on dedicated vCPUs. QEMU newer than 2.12.0 and kernel newer
  535. than 4.17 are required.
  536. * **Removed features**
  537. * Remove KVM assignment support
  538. The KVM style of PCI device assignment was removed from the kernel in
  539. version 4.12.0 after being deprecated since 4.2.0. Libvirt defaults to VFIO
  540. for a long time. Remove support for KVM device assignment from libvirt too.
  541. * libxml: min required libxml is now 2.9.1
  542. Support for building with libxml versions older than 2.9.1 has been
  543. dropped.
  544. * **Improvements**
  545. * virsh: Support setting bandwidth in migrate subcommand
  546. In addition to postcopy bandwidth, the ``virsh migrate`` subcommand now
  547. supports specifying precopy bandwidth with the ``--bandwidth`` parameter.
  548. * libxl: Implement domain metadata getter/setter
  549. The libxl driver now supports ``virDomainGetMetadata()`` and
  550. ``virDomainSetMetadata()`` APIs.
  551. * test driver: Expand API coverage
  552. Additional APIs have been implemented in the test driver.
  553. * Report RNG device in domain capabilities XML
  554. Libvirt now reports if RNG devices are supported by the underlying
  555. hypervisor in the domain capabilities XML.
  556. * Stop linking NSS plugins with libvirt.so
  557. This reduces the amount of code and 3rd party libraries are that loaded
  558. into all processes.
  559. * Split the setuid virt-login-shell binary into two pieces
  560. The setuid virt-login-shell binary is now a tiny shim that sanitizes the
  561. process execution environment variables and arguments, before launching the
  562. trusted virt-login-shell-helper binary.
  563. * qemu: Allow migration with disk cache on
  564. When QEMU supports flushing caches at the end of migration, we can safely
  565. allow migration even if ``disk/driver/@cache`` is neither ``none`` nor
  566. ``directsync`` .
  567. * **Bug fixes**
  568. * Various security label remembering fixes
  569. In the previous release libvirt introduced remembering of original owners
  570. and SELinux labels on files. However, the feature did not work properly
  571. with snapshots, on migrations or on network filesystems. This is now fixed.
  572. * Allow greater PCI domain numbers
  573. Libvirt used to require PCI domain number to be not greater than 0xFFFF.
  574. The code was changed to allow 32 bits long numbers.
  575. * Various D-Bus fixes
  576. When D-Bus is not available, libvirt was reporting random errors. These are
  577. now gone.
  578. * Prefer read-only opening of PCI config files
  579. When enumerating PCI bus, libvirt opens config files under ``sysfs`` mount
  580. and parses them to learn various aspects of the device (e.g. its
  581. capabilities). Only in a very limited number of cases it is actually
  582. writing into the file. However, it used to open the file also for writing
  583. even if it was only reading from it.
  584. * Fix AppArmor profile
  585. Since the ``5.6.0`` release, libvirt uses ``procfs`` to learn the list of
  586. opened file descriptors when spawning a command. However, our AppArmor
  587. profile was not allowing such access.
  588. * Don't block storage driver when starting or building a pool
  589. Starting or building a storage pool can take a long time to finish. During
  590. this time the storage driver was blocked and thus no other API involving
  591. the storage driver could run. This is now fixed.
  592. v5.6.0 (2019-08-05)
  593. ===================
  594. * **New features**
  595. * qemu: Introduce a new video model of type 'bochs'
  596. Introduce a new video model type that supports the ``bochs-display`` device
  597. that was added in qemu version 3.0.
  598. * api: new virDomainCheckpoint APIs
  599. Introduce several new APIs for creating and managing checkpoints in the
  600. test and qemu drivers (the latter requires qcow2 images). Checkpoints serve
  601. as a way to tell which portions of a disk have changed since a point in
  602. time.
  603. * qemu: Add support for overriding max threads per process limit
  604. systemd-based systems impose a limit on the number of threads a process can
  605. spawn, which in some cases can be exceeded by QEMU processes running VMs.
  606. Add a ``max_threads_per_process`` option to qemu.conf to override the
  607. system default.
  608. * Remember original owners and SELinux labels of files
  609. When a domain is starting up libvirt changes DAC and SELinux labels so that
  610. domain can access it. However, it never remembered the original labels and
  611. therefore the file was returned back to ``root:root`` . With this release,
  612. the original labels are remembered and restored properly.
  613. * network: Allow passing arbitrary options to dnsmasq
  614. This works similarly to the existing support for passing arbitary options
  615. to QEMU, and just like that feature it comes with no support guarantees.
  616. * **Removed features**
  617. * xen: Remove sxpr config support
  618. Remove the sxpr style config parser and formatter a year after the xend
  619. driver was removed.
  620. * **Improvements**
  621. * qemu: Allow XML validation for snapshot creation
  622. Add flag ``VIR_DOMAIN_SNAPSHOT_CREATE_VALIDATE`` to validate snapshot input
  623. XML. For virsh, users can use it as ``virsh snapshot-create --validate`` .
  624. * Support encrypted soft TPM
  625. A soft TPM backend could be encrypted with passphrase. Now libvirt supports
  626. using a ``secret`` object to hold the passphrase, and referring to it via
  627. the ``encryption`` element of the TPM device.
  628. * test driver: Expand API coverage
  629. Additional APIs have been implemented in the test driver.
  630. * Implement per-driver locking
  631. Drivers now acquire a lock when they're loaded, ensuring that there can
  632. never be two instances of the same driver active at a time.
  633. * nss: Report newer addresses first
  634. In some cases, a guest might be assigned a new IP address by DHCP before
  635. the previous lease has expired, in which case the NSS plugin will correctly
  636. report both addresses; many applications, however, ignore all addresses but
  637. the first, and may thus end up trying to connect using a stale address. To
  638. prevent that from happening, the NSS plugin will now always report the
  639. newest address first.
  640. * util: Optimize mass closing of FDs when spawning child processes
  641. When the limit on the number of FDs is very high, closing all unwanted FDs
  642. after calling ``fork()`` can take a lot of time and delay the start of the
  643. child process. libvirt will now use an optimized algorithm that minimizes
  644. such delays.
  645. * **Bug fixes**
  646. * logging: Ensure virtlogd rollover takes priority over logrotate
  647. virtlogd implements its own rollover mechanism, but until now logrotate
  648. could end up acting on the logs before virtlogd had a chance to do so
  649. itself.
  650. v5.5.0 (2019-07-02)
  651. ===================
  652. * **Security**
  653. * api: Prevent access to several APIs over read-only connections
  654. Certain APIs give root-equivalent access to the host, and as such should be
  655. limited to privileged users. CVE-2019-10161, CVE-2019-10166,
  656. CVE-2019-10167, CVE-2019-10168.
  657. * **New features**
  658. * qemu: Support SMMUv3 IOMMU
  659. SMMUv3 is an IOMMU implementation for ARM virt guests.
  660. * network: Introduce the network port API
  661. This new public API can be used by virtualization drivers to manage network
  662. resources associated with guests, and is a further step towards splitting
  663. libvirtd into multiple daemons.
  664. * **Removed features**
  665. * qemu: Remove support for virDomainQemuAttach and
  666. virConnectDomainXMLFromNative APIs
  667. The qemu implementations for the APIs mentioned above were removed and the
  668. APIs now return an error. The implementation was stale for a long time and
  669. did not work with modern QEMU command lines, generated from libvirt or
  670. otherwise.
  671. * Stop supporting migration of config files from pre-XDG layout
  672. The new layout was introduced with libvirt 0.9.13 (Jul 2012).
  673. * Remove Avahi mDNS support
  674. This feature was never used outside of virt-manager, which has itself
  675. stopped using it a while ago.
  676. * **Improvements**
  677. * sysinfo: Report SMBIOS information on aarch64
  678. While SMBIOS support has historically been limited to x86_64, modern
  679. aarch64 machines often offer access to the same information as well, and
  680. libvirt now exposes it to the user when that's the case.
  681. * test driver: Expand API coverage
  682. Even more APIs that were missing from the test driver have now been
  683. implemented.
  684. * virt-xml-validate: Allow input to be read from stdin
  685. * qemu: Validate spapr-vio addresses as 32-bit
  686. libvirt has always considered these addresses (used for pSeries guests) as
  687. 64-bit, but the sPAPR specification says that they're 32-bit instead.
  688. * **Bug fixes**
  689. * qemu: Set process affinity correctly when using <numatune>
  690. libvirt would mistakenly interpret the ``nodeset`` attribute as a list of
  691. CPUs instead of as a list of NUMA node, and the process affinity would be
  692. set incorrectly as a result; this has now been fixed.
  693. v5.4.0 (2019-06-03)
  694. ===================
  695. * **Security**
  696. * cpu: Introduce support for the md-clear CPUID bit
  697. This bit is set when microcode provides the mechanism to invoke a flush of
  698. various exploitable CPU buffers by invoking the x86 ``VERW`` instruction.
  699. CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091.
  700. * Restrict user access to virt-admin, virtlogd and virtlockd
  701. The intended users for these facilities are the ``root`` user and the
  702. ``libvirtd`` service respectively, but these restrictions were not enforced
  703. correctly. CVE-2019-10132.
  704. * **Improvements**
  705. * test driver: Expand API coverage
  706. Several APIs that were missing from the test driver have now been
  707. implemented.
  708. * Avoid unnecessary static linking
  709. Most binaries shipped as part of libvirt, for example ``virtlogd`` and
  710. ``libvirt_iohelper`` , were embedding parts of the library even though they
  711. also linked against the ``libvirt.so`` dynamic library. This is no longer
  712. the case, which results in both the disk and memory footprint being
  713. reduced.
  714. * qemu: Report stat-htlb-pgalloc and stat-htlb-pgfail balloon stats
  715. These stats have been introduced in QEMU 3.0.
  716. * **Bug fixes**
  717. * qemu: Fix emulator scheduler support
  718. Setting the scheduler for QEMU's main thread before QEMU had a chance to
  719. start up other threads was misleading as it would affect other threads
  720. (vCPU and I/O) as well. In some particular situations this could also lead
  721. to an error when the thread for vCPU #0 was being moved to its cpu,cpuacct
  722. cgroup. This was fixed so that the scheduler for the main thread is set
  723. after QEMU starts.
  724. * apparmor: Allow hotplug of vhost-scsi devices
  725. v5.3.0 (2019-05-04)
  726. ===================
  727. * **New features**
  728. * qemu: Add support for setting the emulator scheduler parameters
  729. I/O threads and vCPU threads already support setting schedulers, but until
  730. now it was impossible to do so for the main QEMU thread (emulator thread in
  731. the libvirt naming). This is, however, requested for some very specific
  732. scenarios, for example when vCPU threads are running at such priority that
  733. could starve the main thread.
  734. * **Removed features**
  735. * vbox: Drop support for VirtualBox 4.x releases
  736. Support for all the 4.x releases was ended by VirtualBox maintainers in
  737. December 2015. Therefore, libvirt support for these releases is dropped.
  738. * **Improvements**
  739. * qemu: Use PCI by default for RISC-V guests
  740. PCI support for RISC-V guests was already available in libvirt 5.1.0, but
  741. it required the user to opt-in by manually assigning PCI addresses: with
  742. this release, RISC-V guests will use PCI automatically when running against
  743. a recent enough (4.0.0+) QEMU release.
  744. * qemu: Advertise firmware autoselection in domain capabilities
  745. The firmware autoselection feature is now exposed in domain capabilities
  746. and management applications can query for accepted values, i.e. values that
  747. are accepted and for which libvirt found firmware descriptor files.
  748. Firmware Secure Boot support is also advertised.
  749. * Drop YAJL 1 support
  750. YAJL 2 is widely adopted and maintaining side by side support for two
  751. versions is unnecessary.
  752. * **Bug fixes**
  753. * rpc: cleanup in virNetTLSContextNew
  754. Failed new gnutls context allocations in virNetTLSContextNew function
  755. results in double free and segfault. Occasional memory leaks may also
  756. occur.
  757. * virsh: various completers fixes
  758. There were some possible crashers, memory leaks, etc. which are now fixed.
  759. * qemu: Make hugepages work with memfd backend
  760. Due to a bug in command line generation libvirt did not honor hugepages
  761. setting with memfd backend.
  762. * Enforce ACL write permission for getting guest time & hostname
  763. Getting the guest time and hostname both require use of guest agent
  764. commands. These must not be allowed for read-only users, so the permissions
  765. check must validate "write" permission not "read".
  766. v5.2.0 (2019-04-03)
  767. ===================
  768. * **New features**
  769. * Add Storage Pool Capabilities output
  770. Add support to list an enumerated list of supported Storage Pools via the
  771. virConnectGetCapabilities API when connected via a Storage Driver. Add
  772. support to get a more detailed list XML output Storage Pool Capabilities
  773. vis the virConnectGetStoragePoolCapabilites API.
  774. * qemu: Support virtio-{non-}transitional device models
  775. ``virtio-transitional`` and ``virtio-non-transitional`` ``model`` values
  776. were added to the QEMU driver for the following devices: ``disk`` ,
  777. ``interface`` , ``filesystem`` , ``rng`` , ``vsock`` , ``memballoon`` ,
  778. ``controller`` type ``scsi`` , ``controller`` type ``virtio-serial`` ,
  779. ``input`` bus ``virtio`` type ``passthrough`` , ``hostdev`` type
  780. ``scsi_host`` . These new models can be used to give fine grained control
  781. over what virtio device version is presented to the guest.
  782. * qemu: Enable firmware autoselection
  783. Libvirt allows users to provide loader path for some time now. However,
  784. this puts some burden on users because they need to know what firmware
  785. meets their requirements. Now that QEMU ships firmware description files
  786. this burden can be moved onto libvirt. It is as easy as setting the
  787. ``firmware`` attribute in the ``os`` element (accepted values are ``bios``
  788. and ``efi`` ). Moreover, libvirt automatically enables domain features
  789. needed for firmware it chooses.
  790. * snapshots: Add support for topological listings
  791. A new flag VIR_DOMAIN_SNAPSHOT_LIST_TOPOLOGICAL is available for the
  792. various snapshot listing APIs such as virDomainListAllSnapshots(). For
  793. drivers that support the flag, the listed snapshots are guaranteed to be
  794. sorted such that parents occur before children.
  795. * Xen: Add support for max grant frames setting
  796. Add support for Xen's max_grant_frames setting by adding a new xenbus
  797. controller type with a maxGrantFrames attribute. E.g. ``<controller
  798. type='xenbus' maxGrantFrames='64'/>``
  799. * qemu: Add support for parallel migration
  800. With QEMU 4.0.0 libvirt can enable parallel migration which causes the
  801. memory pages to be processed in parallel by several threads and sent to the
  802. destination host using several connections at the same time. This may
  803. increase migration speed in case a single thread is unable to saturate the
  804. network link.
  805. * **Removed features**
  806. * Drop support for Upstart and "Red Hat" init scripts
  807. Not a single one of the platforms we target still uses Upstart, and the
  808. Upstart project itself has been abandoned for several years now; the same
  809. is true for the "Red Hat" (really System V) init scripts, since RHEL 7 and
  810. later releases use systemd.
  811. * **Improvements**
  812. * Report class information for PCI node device capability.
  813. * Split setup of IPv4 and IPv6 top level chain
  814. The requirement resulting from private chains improvement done in
  815. ``v5.1.0`` was refined so that only tables from corresponding IP version
  816. are required. This means that if a network doesn't have ``IPv6`` enabled
  817. then those tables are not required.
  818. * Don't default to building the QEMU driver
  819. Historically, the QEMU driver has been special in that it was enabled by
  820. default, with the option to explicitly opt-out of it; starting now, we're
  821. enabling it opportunistically if we detect that all requirements are
  822. available, just like we do with other drivers.
  823. * **Bug fixes**
  824. * virt-host-validate: Fix IOMMU check on s390x
  825. * qemu: Allow creating pSeries guests with graphics and no USB mouse
  826. It's now possible to prevent libvirt from automatically adding a USB mouse
  827. to pSeries guests by including a USB tablet in the input XML: doing so is
  828. desiderable as using a tablet results in a much better user experience when
  829. working with GUIs.
  830. * qemu: Set $HOME and XGD variables for qemu:///system guests
  831. This avoids files being accidentally created under ``/`` or the guests not
  832. being able to start because they lack the necessary permissions to write to
  833. that location.
  834. v5.1.0 (2019-03-04)
  835. ===================
  836. * **New features**
  837. * bhyve: Add support for additional command-line arguments
  838. The bhyve driver now supports passing additional command-line arguments to
  839. the bhyve process using the new ``<bhyve:commandline>`` element in domain
  840. configuration.
  841. * network: Support setting a firewalld "zone" for virtual network bridges
  842. All libvirt virtual networks with bridges managed by libvirt (i.e. those
  843. with forward mode of "nat", "route", "open", or no forward mode) will now
  844. be placed in a special firewalld zone called "libvirt" by default. The zone
  845. of any network bridge can be changed using the ``zone`` attribute of the
  846. network's ``bridge`` element.
  847. * bhyve: Support for ignoring unknown MSRs reads and writes
  848. A new <features> element <msrs unknown='ignore'/> was introduced and the
  849. bhyve driver supports it to control unknown Model Specific Registers (MSRs)
  850. reads and writes.
  851. * qemu: Add support for encrypted VNC TLS keys
  852. Use the password stored in the secret driver under the uuid specified by
  853. the ``vnc_tls_x509_secret_uuid`` option in qemu.conf.
  854. * Add storage pool namespace options
  855. Allow for adjustment of RBD configuration options via Storage Pool XML
  856. Namespace adjustments.
  857. * qemu: Add support for setting post-copy migration bandwidth
  858. Users can now limit the bandwidth of post-copy migration, e.g. via ``virsh
  859. migrate --postcopy-bandwidth`` .
  860. * **Improvements**
  861. * Create private chains for virtual network firewall rules
  862. Historically firewall rules for virtual networks were added straight into
  863. the base chains. This works but has a number of bugs and design
  864. limitations. To address them, libvirt now puts firewall rules into its own
  865. chains. Note that with this change the ``filter`` , ``nat`` and ``mangle``
  866. tables are required for both ``IPv4`` and ``IPv6`` .
  867. * Detect CEPH and GPFS as shared FS
  868. When starting a migration libvirt performs some sanity checks to make sure
  869. domain will be able to run on the destination. One of the requirements is
  870. that the disk has to either be migrated too or be accessible from a network
  871. filesystem. CEPH and GPFS weren't detected as a network filesystem.
  872. * Advertise network MTU via DHCP when specified
  873. If network MTU is set and the network has DHCP enabled, advertise the MTU
  874. in DHCP transaction too so that clients can adjust their link accordingly.
  875. * qemu: Allocate memory at the configured NUMA nodes from start
  876. Libvirt used to just start QEMU, let it allocate memory for the guest, and
  877. then use CGroups to move the memory to configured NUMA nodes. This is
  878. suboptimal as huge chunks of memory have to be moved. Moreover, this relies
  879. on ability to move memory later which is not always true. A change was made
  880. to set process affinity correctly from the start so that memory is
  881. allocated on the configured nodes from the beginning.
  882. * Support for newer Wireshark
  883. Adapt libvirt to use the more recent release requiring a source build
  884. configuration of libvirt ``--with-wireshark`` to upgrade to the more recent
  885. version.
  886. * Batch mode virsh and virt-admin parsing improvements
  887. When parsing a single-argument command_string in batch mode, virsh and
  888. virt-admin now permit newlines in addition to semicolons for splitting
  889. commands, and backslash-newline for splitting long lines, to be more like
  890. shell parsing.
  891. * **Bug fixes**
  892. * qemu: Use CAP_DAC_OVERRIDE during QEMU capabilities probing
  893. By default, libvirt runs the QEMU process as ``qemu:qemu`` which could
  894. cause issues during probing as some features like AMD SEV might be
  895. inaccessible to QEMU because of file system permissions. Therefore,
  896. ``CAP_DAC_OVERRIDE`` is granted to overcome these for the purposes of
  897. probing.
  898. * storage: Add default mount options for fs/netfs storage pools
  899. Altered the command line generation for fs/netfs storage pools to add some
  900. default options. For Linux based systems, the options added are "nodev,
  901. nosuid, noexec". For FreeBSD based systems, the options added are "nosuid,
  902. noexec".
  903. * qemu: Allow use of PCI for RISC-V guests
  904. This works with QEMU 4.0.0+ only and is opt-in at the moment, since it
  905. requires users to manually assign PCI addresses, but is otherwise fully
  906. functional.
  907. * network: Fix virtual networks on systems using firewalld+nftables
  908. Because of the transitional state of firewalld's new support for nftables,
  909. not all iptables features required by libvirt are yet available, so libvirt
  910. must continue to use iptables for its own packet filtering rules even when
  911. the firewalld backend is set to use nftables. However, due to the way
  912. iptables support is implemented in kernels using nftables (iptables rules
  913. are converted to nftables rules and processed in a separate hook from the
  914. native nftables rules), guest networking was broken on hosts with firewalld
  915. configured to use nftables as the backend. This has been fixed by putting
  916. libvirt-managed bridges in their own firewalld zone, so that guest traffic
  917. can be forwarded beyond the host and host services can be exposed to guests
  918. on the virtual network without opening up those same services to the rest
  919. of the physical network. This means that host access from virtual machines
  920. is no longer controlled by the firewalld default zone (usually "public"),
  921. but rather by the new firewalld zone called "libvirt" (unless configured
  922. otherwise using the new zone attribute of the network bridge element).
  923. * qemu: Fix i6300esb watchdog hotplug on Q35
  924. Ensure that libvirt allocates a PCI address for the device so that QEMU did
  925. not default to an address that would not allow for device hotplug.
  926. * lxc: Don't reboot host on virDomainReboot
  927. If the container is really a simple one (init is just bash and the whole
  928. root is passed through) then virDomainReboot and virDomainShutdown would
  929. reboot or shutdown the host. The solution is to use different method to
  930. reboot or shutdown the container in that case (e.g. signal).
  931. * rpc: Various stream fixes
  932. One particular race was fixed, one locking problem and error reporting from
  933. streams was made better.
  934. * qemu: Fix guestfwd hotplug/hotunplug
  935. Fixed the generation of the guestfwd hotplug/unplug command sent to QEMU to
  936. match the syntax used when creating the initial command line.
  937. * qemu: Forbid CDROMs on virtio bus
  938. Attempting to create an empty virtio-blk drive or attempting to eject it
  939. results into an error. Forbid configurations where users would attempt to
  940. use CDROMs in virtio bus.
  941. * qemu: Use 'raw' for 'volume' disks without format
  942. Storage pools might want to specify format of the image when translating
  943. the volume thus libvirt can't add any default format when parsing the XML.
  944. Add an explicit format when starting the VM and format is not present
  945. neither by user specifying it nor by the storage pool translation function.
  946. * qemu: Assume 'raw' default storage format also for network storage
  947. Post parse callback adds the 'raw' type only for local files. Remote files
  948. can also have backing store (even local) so we should do this also for
  949. network backed storage.
  950. * qemu: Fix block job progress reporting and advocate for READY event
  951. In some cases QEMU can get to 100% and still not reach the synchronised
  952. phase. Initiating a pivot in that case will fail. Therefore it is strongly
  953. advised to wait for ``VIR_DOMAIN_BLOCK_JOB_READY`` event which does not
  954. suffer from this problem.
  955. * qemu: Don't format image properties for empty drive
  956. If a ``-drive`` has no image, then formatting attributes such as cache,
  957. readonly, etc. would cause errors to be reported from QEMU. This was fixed
  958. by not supplying the attributes for devices without an image.
  959. * External snapshot metadata redefinition is fixed
  960. Attempting to use VIR_DOMAIN_SNAPSHOT_CREATE_REDEFINE to reinstate the
  961. metadata describing an external snapshot created earlier for an offline
  962. domain no longer fails.
  963. v5.0.0 (2019-01-15)
  964. ===================
  965. * **New features**
  966. * Xen: Add support for openvswitch
  967. The libxl driver now supports virtual interfaces that connect to an
  968. openvswitch bridge, including interfaces with VLAN tagging and trunking
  969. configuration.
  970. * qemu: Report whether KVM nesting is available
  971. Running nested KVM guests requires specific configuration steps to be
  972. performed on the host; libvirt will now report in the host capabilities
  973. whether KVM nesting support is available.
  974. * **Removed features**
  975. * Drop UML driver
  976. The UML driver was unmaintained and not tested for quite some time now.
  977. Worse, there is a bug that causes it to deadlock on some very basic
  978. operations (e.g. dumping domain XML). These facts make us believe no one
  979. uses it.
  980. * **Improvements**
  981. * qemu: Add support for ARMv6l guests
  982. * Support more NVDIMM configuration options
  983. Introduce more configuration options. For the source element, add the
  984. 'alignsize' and 'pmem' subelements. For the target element, add the
  985. 'readonly' subelement.
  986. * cpu: Add support for "stibp" x86_64 feature
  987. Add cpu flag stibp (Single Thread Indirect Branch Predictors) to prevent
  988. indirect branch predictions from being controlled by the sibling
  989. Hyperthread.
  990. * libxl: Handle external domain destroy
  991. Historically, if a domain was destroyed using ``xl`` rather than through
  992. libvirt APIs, libvirt would not be aware of the fact and keep considering
  993. it as running. This is no longer the case.
  994. * Start selecting the first available DRI device for OpenGL operations
  995. If OpenGL support is needed (either with SPICE gl enabled or with
  996. egl-headless), libvirt is now able to pick the first available DRI device
  997. for the job. At the same time, this improvement is also a bugfix as it
  998. prevents permission-related issues with regards to our mount namespaces and
  999. the default DRI render node's permissions which would normally prevent QEMU
  1000. from accessing such a device.
  1001. * qemu: Add support for postcopy-requests migration statistics
  1002. The ``virDomainJobInfo`` can get number page requests received from the
  1003. destination host during post-copy migration.
  1004. * **Bug fixes**
  1005. * lxc: Don't forbid interfaces with type=direct
  1006. Such interfaces are supported by lxc and should be allowed.
  1007. * qemu: Fully clean up RNG devices on detach
  1008. Some RNG device types, such as those using EGD, might need extra clean up
  1009. on the host in addition to removing the guest-side device.
  1010. v4.10.0 (2018-12-03)
  1011. ====================
  1012. * **New features**
  1013. * qemu: Add Hyper-V PV IPI and Enlightened VMCS support
  1014. The QEMU driver now has support for Hyper-V PV IPI and Enlightened VMCS for
  1015. Windows and Hyper-V guests.
  1016. * qemu: Added support for PCI devices on S390
  1017. PCI addresses can now include the new zpci element which contains uid
  1018. (user-defined identifier) and fid (PCI function identifier) attributes and
  1019. makes the corresponding devices usable by S390 guests.
  1020. * Support changing IOThread polling parameters for a live guest
  1021. Introduced virDomainSetIOThreadParams which allows dynamically setting the
  1022. IOThread polling parameters used by QEMU to manage the thread polling
  1023. interval and the algorithm for growth or shrink of the polling time. The
  1024. values only affect a running guest with IOThreads. The guest's IOThread
  1025. polling values can be viewed via the domain statistics.
  1026. * Xen: Add support for PVH
  1027. The libxl driver now supports Xen's PVH virtual machine type. PVH machines
  1028. are enabled with the new "xenpvh" OS type, e.g.
  1029. ``<os><type>xenpvh</type></os>``
  1030. * qemu: Added support for CMT (Cache Monitoring Technology)
  1031. Introduced cache monitoring using the ``monitor`` element in ``cachetune``
  1032. for vCPU threads. Added interfaces to get and display the cache utilization
  1033. statistics through the command 'virsh domstats' via the
  1034. virConnectGetAllDomainStats API.
  1035. * qemu: Add support for nested HV for pSeries guests
  1036. Nested HV support makes it possible to run nested (L2) guests with minimal
  1037. performance penalty when compared to regular (L1) guests on ppc64 hardware.
  1038. * **Bug fixes**
  1039. * Xen: Handle soft reset shutdown event
  1040. The pvops Linux kernel uses soft reset to handle the crash machine
  1041. operation. The libxl driver now supports the soft reset shutdown event,
  1042. allowing proper crash handling of pvops-based HVM domains.
  1043. v4.9.0 (2018-11-04)
  1044. ===================
  1045. * **New features**
  1046. * util: Add cgroup v2 support
  1047. cgroup v2 support has been implemented in libvirt, with both "unified" (v2
  1048. only) and "hybrid" (v2 + v1) setups being usable; existing "legacy" (v1
  1049. only) setups will keep working.
  1050. * qemu: Add vfio AP support
  1051. The QEMU driver now has support to passthrough adjunct processors into QEMU
  1052. guests on S390.
  1053. * **Improvements**
  1054. * rpc: Make 'genprotocol' output reproducible
  1055. This is another step towards making libvirt builds fully reproducible.
  1056. * **Bug fixes**
  1057. * security: Fix permissions for UNIX sockets
  1058. Since 4.5.0, libvirt is using FD passing to hand sockets over to QEMU,
  1059. which in theory removes the need for them to be accessible by the user
  1060. under which the QEMU process is running; however, other processes such as
  1061. vdsm need to access the sockets as well, which means adjusting permissions
  1062. is still necessary.
  1063. * cpu_map: Add Icelake model definitions
  1064. These CPU models will be available in the upcoming 3.1.0 QEMU release.
  1065. * util: Properly parse URIs with missing trailing slash
  1066. Some storage URIs were not parsed correctly, in which case libvirt ended up
  1067. emitting XML that it would then refuse to parse back.
  1068. v4.8.0 (2018-10-01)
  1069. ===================
  1070. * **New features**
  1071. * Xen: Support PM Suspend and Wakeup
  1072. The libxl driver now supports the virDomainPMSuspendForDuration and
  1073. virDomainPMWakeup APIs.
  1074. * **Removed features**
  1075. * Xen: Drop support for Xen 4.4 and 4.5
  1076. Xen 4.4 and 4.5 are no longer supported by the Xen community. Drop support
  1077. for these older versions and require Xen >= 4.6.
  1078. * nwfilter: Disallow binding creation in session mode
  1079. Ensure that a filter binding creation is not attempted in session mode and
  1080. generates a proper error message.
  1081. * **Improvements**
  1082. * qemu: Retrieve guest hostname through QEMU Guest Agent command
  1083. QEMU is now able to retrieve the guest hostname using a new QEMU-GA command
  1084. called 'guest-get-host-name'. Virsh users can execute 'domhostname' for
  1085. QEMU driver for domains configured to use the Guest Agent.
  1086. * virsh: Implement vsh-table in virsh and virsh-admin
  1087. The new API fixes problems with table-alignment, making the tables more
  1088. readable and deals with unicode.
  1089. * **Bug fixes**
  1090. * storage: Allow inputvol to be encrypted
  1091. When creating a storage volume based on another volume, the base input
  1092. volume is allowed to be encrypted.
  1093. * virsh: Require explicit --domain for domxml-to-native
  1094. The --domain option for domxml-to-native virsh command has always been
  1095. documented as required, but commit v4.3.0-127-gd86531daf2 accidentally made
  1096. it optional.
  1097. * lxc_monitor: Avoid AB / BA lock race
  1098. A deadlock situation could occur when autostarting a LXC domain 'guest' due
  1099. to two threads attempting to take opposing locks while holding opposing
  1100. locks (AB BA problem).
  1101. v4.7.0 (2018-09-03)
  1102. ===================
  1103. * **New features**
  1104. * storage: add storage pool iscsi-direct
  1105. Introduce a new storage pool backend that uses libiscsi instead of
  1106. iscsiadm. It support basic pool operations: checkPool and refreshPool.
  1107. * Add support for MBA (Memory Bandwidth Allocation technology)
  1108. Domain vCPU threads can now have allocated some parts of host memory
  1109. bandwidth by using the ``memorytune`` element in ``cputune`` .
  1110. * qemu: Add support for RISC-V guests
  1111. riscv32 and riscv64 guest architectures are now supported.
  1112. * **Improvements**
  1113. * qemu: Add ccw support for vhost-vsock
  1114. Support the vhost-vsock-ccw device on S390.
  1115. * qemu: Make default machine type independent of QEMU
  1116. We can't control whether or not QEMU will change its default machine type
  1117. in the future, or whether downstream distributions will decide to compile
  1118. out some machine types, so our only option to provide a predictable
  1119. behavior is taking care of the default ourselves; management applications
  1120. and users are encouraged to explicitly pick a machine type when creating
  1121. new guests.
  1122. * apparmor: Various improvements
  1123. Rules have been added to deal with a number of scenarios that didn't work
  1124. correctly.
  1125. * **Bug fixes**
  1126. * esx: Truncate CPU model name
  1127. Some CPU model names are too long to be stored into the corresponding
  1128. property, and should be explicitly truncated to avoid unexpected behavior
  1129. in users of the ``virNodeGetInfo()`` API such as ``virsh nodeinfo`` .
  1130. * utils: Remove arbitrary limit on socket_id/core_id
  1131. Both values were assumed to be smaller than 4096, but in fact they are
  1132. entirely hardware-dependent and there have been reports of machines
  1133. presenting much bigger values, preventing libvirt from working correctly;
  1134. all such limits have now been removed.
  1135. v4.6.0 (2018-08-06)
  1136. ===================
  1137. * **New features**
  1138. * qemu: Implement the HTM pSeries feature
  1139. Users can now decide whether HTM (Hardware Transactional Memory) support
  1140. should be available to the guest.
  1141. * qemu: Enable VNC console for mediated devices
  1142. Host devices now support a new atribute 'display' which can be used to turn
  1143. on frame buffer rendering on a vgpu mediated device instead of on an
  1144. emulated GPU, like QXL.
  1145. * **Improvements**
  1146. * qemu: Introduce a new video model of type 'none'
  1147. Introduce a new video model type that disables the automatic addition of a
  1148. video device to domains with 'graphics' specified in their XML. This can be
  1149. useful with GPU mediated devices which can serve as the only rendering
  1150. devices within the guest.
  1151. * virsh: Add --alias to attach-disk and attach-interface commands
  1152. Add option --alias to set customized device alias name when using
  1153. attach-disk or attach-interface commands.
  1154. * virsh: Support usb and sata address to attach-disk
  1155. Usb or sata address could be used when attach-disk with --address. For
  1156. example, use usb address as usb:<bus>.<port>, use sata address as
  1157. <controller>.<bus>.<unit>.
  1158. v4.5.0 (2018-07-02)
  1159. ===================
  1160. * **New features**
  1161. * qemu: Provide TPM emulator support
  1162. Support QEMU's TPM emulator based on swtpm. Each QEMU guest gets its own
  1163. virtual TPM.
  1164. * bhyve: Support specifying guest CPU topology
  1165. Bhyve's guest CPU topology could be specified using the ``<cpu><topology
  1166. ../></cpu>`` element.
  1167. * qemu: Add support for extended TSEG size
  1168. Support specifying extended TSEG size for SMM in QEMU.
  1169. * qemu: Add support for SEV guests
  1170. SEV (Secure Encrypted Virtualization) is a feature available on AMD CPUs
  1171. that encrypts the guest memory and makes it inaccessible even to the host
  1172. OS.
  1173. * **Removed features**
  1174. * Remove support for qcow/default encrypted volumes
  1175. Disallow using a qcow encrypted volume for the guest and disallow creation
  1176. of the qcow or default encrypted volume from the storage driver. Support
  1177. for qcow encrypted volumes has been phasing out since QEMU 2.3 and by QEMU
  1178. 2.9 creation of a qcow encrypted volume via qemu-img required usage of
  1179. secret objects, but that support was never added to libvirt.
  1180. * Make GnuTLS mandatory
  1181. Building without GnuTLS is no longer possible.
  1182. * qemu: Remove allow_disk_format_probing configuration option
  1183. The option represented a security risk when used with malicious disk
  1184. images, so users were recommended against enabling it; with this release,
  1185. it's been removed altogether.
  1186. * **Improvements**
  1187. * capabilities: Provide info about host IOMMU support
  1188. Capabilities XML now provide information about host IOMMU support.
  1189. * virsh: Add --all to domblkinfo command
  1190. Alter the ``domblkinfo`` command to add the option --all in order to
  1191. display the size details of each domain block device from one command in a
  1192. output table.
  1193. * qemu: Allow concurrent access to monitor and guest agent
  1194. Historically libvirt prevented concurrent accesses to the qemu monitor and
  1195. the guest agent. Therefore two independent calls (one querying the monitor
  1196. and the other querying guest agent) would serialize which hurts
  1197. performance. The code was reworked to allow two independent calls run at
  1198. the same time.
  1199. * qemu: Allow configuring the page size for HPT pSeries guests
  1200. For HPT pSeries guests, the size of the host pages used to back guest
  1201. memory and the usable guest page sizes are connected; the new setting can
  1202. be used to request that a certain page size is available in the guest.
  1203. * Add support to use an raw input volume for encryption
  1204. It is now possible to provide a raw input volume as input for to generate a
  1205. luks encrypted volume via either virsh vol-create-from or
  1206. virStorageVolCreateXMLFrom.
  1207. * qemu: Add support for vsock hot (un)plug and cold (un)plug
  1208. * qemu: Add support for NBD over TLS
  1209. NBD volumes can now be accessed securely.
  1210. * qemu: Implement FD passing for Unix sockets
  1211. Instead of having QEMU open the socket and then connecting to it, which is
  1212. inherently racy, starting with QEMU 2.12 we can open the socket ourselves
  1213. and pass it to QEMU, avoiding race conditions.
  1214. * virsh: Introduce --nowait option for domstat command
  1215. When this option is specified, virsh will try to fetch the guest stats but
  1216. abort instead of stalling if they can't be retrieved right away.
  1217. * **Bug fixes**
  1218. * qemu: Fix a potential libvirtd crash on VM reconnect
  1219. Initialization of the driver worker pool needs to come before libvirtd
  1220. trying to reconnect to all machines, since one of the QEMU processes migh
  1221. have already emitted events which need to be handled prior to us getting to
  1222. the worker pool initialization.
  1223. * qemu: Fix domain resume after failed migration
  1224. Recent versions of QEMU activate block devices before the guest CPU has
  1225. been started, which makes it impossible to roll back a failed migration.
  1226. Use the ``late-block-activate`` migration capability if supported to avoid
  1227. the issue.
  1228. * vmx: Permit guests to have an odd number of vCPUs
  1229. An odd number of vCPUs greater than 1 was forbidden in the past, but
  1230. current versions of ESXi have lifted that restriction.
  1231. v4.4.0 (2018-06-04)
  1232. ===================
  1233. * **New features**
  1234. * bhyve: Support locking guest memory
  1235. Bhyve's guest memory may be wired using the
  1236. ``<memoryBacking><locked/></memoryBacking>`` element.
  1237. * qemu: Provide VFIO channel I/O passthrough support
  1238. Support passthrough devices that use channel I/O based mechanism in a QEMU
  1239. virtual machine.
  1240. * qemu: Add support for migration of VMs with non-shared storage over TLS
  1241. It's now possible to use the VIR_MIGRATE_TLS flag together with
  1242. VIR_MIGRATE_NON_SHARED_DISK. The connection is then secured using the TLS
  1243. environment which is setup for the migration connection.
  1244. * Add support for VM Generation ID
  1245. The VM Generatation ID exposes a 128-bit, cryptographically random, integer
  1246. value identifier, referred to as a Globally Unique Identifier (GUID) to the
  1247. guest in order to notify the guest operating system when the virtual
  1248. machine is executed with a different configuration. Add a new domain XML
  1249. processing and a domain capabilities feature.
  1250. * Introduce virDomainDetachDeviceAlias
  1251. This new API enables users to detach device using only its alias.
  1252. * Introduce new virConnectCompareHypervisorCPU and
  1253. virConnectBaselineHypervisorCPU APIs
  1254. Unlike the old virConnectCompareCPU and virConnectBaselineCPU APIs, both
  1255. new APIs consider capabilities of a specific hypervisor.
  1256. * Introduce SCSI persistent reservations support
  1257. The QEMU driver gained support for qemu-pr-helper which enables guests to
  1258. issue SCSI commands for persistent reservation.
  1259. * qemu: Implement multiple screen support for virDomainScreenshot
  1260. While the virDomainScreenshot API supported multihead video cards, the
  1261. implementation was missing. But now that QEMU implemented it libvirt has
  1262. done as well.
  1263. * qemu: add support for vhost-vsock-device
  1264. A new vsock device was introduced, allowing communication between the guest
  1265. and the host via the AF_VSOCK family.
  1266. * **Improvements**
  1267. * qemu: Add suport for OpenGL rendering with SDL
  1268. Domains using SDL as a graphics backend will now be able to use OpenGL
  1269. accelerated rendering.
  1270. * qemu: Add support for 'output' audio codec
  1271. Support QEMU's 'hda-output' codec advertising only a line-out for ich6 and
  1272. ich9 sound devices.
  1273. * virsh: Enhance event name completion
  1274. Implement event name completion for some commands (e.g. event,
  1275. secret-event, pool-event and nodedev-event)
  1276. v4.3.0 (2018-05-02)
  1277. ===================
  1278. * **New features**
  1279. * qemu: Add support for the pcie-to-pci-bridge controller
  1280. Pure PCIe guests such as x86_64/q35 and aarch64/virt will now add this
  1281. controller when traditional PCI devices are in use.
  1282. * Xen: Support setting CPU features for host-passthrough model
  1283. The CPU model presented to Xen HVM domains is equivalent to libvirt's
  1284. host-passthrough model, although individual features can be enabled and
  1285. disabled via the cpuid setting. The libvirt libxl driver now supports
  1286. enabling and disabling individual features of the host-passthrough CPU
  1287. model.
  1288. * **Removed features**
  1289. * Xen: Drop the legacy xend-based driver
  1290. The xm/xend toolstack was deprecated in Xen 4.2 and removed from the Xen
  1291. sources in the 4.5 development cycle. The libvirt driver based on xend is
  1292. now removed from the libvirt sources.
  1293. * **Improvements**
  1294. * qemu: Support hot plug and hot unplug of mediated devices
  1295. Libvirt now allows mediated devices to be hot plugged and hot unplugged
  1296. from a guest rather than reporting an error that this isn't supported. In
  1297. fact, kernel has been supporting this since 4.10.
  1298. * **Bug fixes**
  1299. * Improve handling of device mapper targets
  1300. When starting a domain with a disk backed by a device mapper volume libvirt
  1301. also needs to allow the storage backing the device mapper in CGroups. In
  1302. the past kernel did not care, but starting from 4.16 CGroups are consulted
  1303. on each access to the device mapper target.
  1304. v4.2.0 (2018-04-01)
  1305. ===================
  1306. * **New features**
  1307. * Support building with Python 3
  1308. Python is required to build libvirt, and up until now only Python 2 could
  1309. be used as an interpreter. All scripts used during build have now been made
  1310. compatible with Python 3, which means both major releases of the language
  1311. are fully supported.
  1312. * qemu: Provide ccw address support for graphics and input devices
  1313. Support the virtio-gpu-ccw device as a video device and virtio-{keyboard,
  1314. mouse, tablet}-ccw devices as input devices on S390.
  1315. * **Improvements**
  1316. * qemu: Add logging of guest crash information on S390
  1317. On S390, when the guest crashes and QEMU exposes the guest crash
  1318. information, log the relevant data to the domain log file.
  1319. * qemu: use arp table of host to get the IP address of guests
  1320. Find IP address of a VM by arp table on hosts. If someone customizing IP
  1321. address inside VM, it will be helpful.
  1322. * Xen: Remove hard-coded scheduler weight
  1323. The libxl driver was accidentally hard-coding the per-domain scheduler
  1324. weight to 1000, silently ignoring any user-provided ``<shares>`` in
  1325. ``<cputune>`` . The driver now honors ``<shares>`` , and defers setting a
  1326. default value to Xen. Note that the Xen default is 256, so any domains
  1327. started after this improvement will have one fourth the shares of
  1328. previously started domains. If all domains must have equal CPU shares,
  1329. administrators must manually set the weight of previously started domains
  1330. to 256, or restart them.
  1331. * **Bug fixes**
  1332. * qemu: TLS migration now enforces use of TLS for the NBD connection
  1333. When the VIR_MIGRATE_TLS flag was used with the migration API libvirt did
  1334. not ensure that the NBD connection was using TLS as well. The code now
  1335. rejects such migration as the TLS transport for NBD is not ready yet, but
  1336. prevents a false sense of security that TLS would be used. The support TLS
  1337. for NBD will be added soon.
  1338. v4.1.0 (2018-03-05)
  1339. ===================
  1340. * **New features**
  1341. * Added support for CAT (Cache allocation Technology)
  1342. Domain vCPU threads can now have allocated some parts of host cache using
  1343. the ``cachetune`` element in ``cputune`` .
  1344. * Allow opening secondary drivers
  1345. Up until now it was possible to connect to only hypervisor drivers (e.g.
  1346. qemu:///system, lxc:///, vbox:///system, and so on). The internal drivers
  1347. (like network driver, node device driver, etc.) were hidden from users and
  1348. users could use them only indirectly. Starting with this release new
  1349. connection URIs are accepted. For instance network:///system,
  1350. storage:///system and so on.
  1351. * virtlogd, virtlockd: Add support for admin protocol
  1352. These two daemons now support admin protocol through which some admin info
  1353. can be gathered or some configuration tweaked on the fly.
  1354. * **Improvements**
  1355. * virsh: Enhance bash completion
  1356. Implement more bash completions so that basic libvirt objects can be
  1357. auto-completed (e.g. networks, interfaces, NWFilters, and so on).
  1358. * qemu: Use VIR_ERR_DEVICE_MISSING for various hotplug/detach messages
  1359. * qemu: Allow showing the dump progress for memory only dump
  1360. Alter the QEMU dump-guest-memory command processing to check for and allow
  1361. asynchronous completion which then allows for the virsh dump --memory-only
  1362. --verbose command to display percent completion data.
  1363. * conf: add support for setting Chassis SMBIOS data fields
  1364. * libxl: add support for setting clock offset and adjustment
  1365. * Make port allocator global
  1366. Up until now each driver had their own port allocator module. This meant
  1367. that info on port usage was not shared. Starting with this release, the
  1368. port allocator module is made global and therefore drivers allocate ports
  1369. from global pool.
  1370. * Fixed some compiler warnings that appear with GCC 8
  1371. * **Bug fixes**
  1372. * qemu: Check for unsafe migration more thoroughly
  1373. If a domain disk is stored on local filesystem (e.g. ext4) but is not being
  1374. migrated it is very likely that domain is not able to run on destination.
  1375. Regardless of share/cache mode.
  1376. * qemu: Fix updating device with boot order
  1377. Starting with 3.7.0 release updating any device with boot order would fail
  1378. with 'boot order X is already used by another device' while in fact it was
  1379. the very same device.
  1380. * virlog: determine the hostname on startup CVE-2018-6764
  1381. At later point it might not be possible or even safe to use getaddrinfo().
  1382. It can in turn result in a load of NSS module which can even be loaded from
  1383. unsage guest filesystem and thus escape the confinment of its container.
  1384. * qemu: Rework vCPU statistics fetching
  1385. Fetching vCPU statistics was very expensive because it lead to waking up
  1386. vCPU threads in QEMU and thus it degraded performance. The code was
  1387. reworked so that fetching statistics does not wake up halted vCPUs.
  1388. * qemu: unlink memory backing file on domain shutdown
  1389. Depending on the filesystem where domain memory is stored, some files might
  1390. have been left behind. This is not a problem on hugetlbfs, but it is a
  1391. problem on regular filesystems like ext4.
  1392. * qemu: Fix shutting down domains in parallel
  1393. If multiple domains were being shut down in parallel, libvirtd might have
  1394. deadlocked.
  1395. * nodedev: Update PCI mdev capabilities dynamically
  1396. PCI devices may have other nested capabilities, like SRIOV and mdev which
  1397. depend on the device being plugged into the native vendor driver. However,
  1398. in case such a device is directly assigned to a guest using VFIO driver,
  1399. the device will naturally lose these capabilities and libvirt needs to
  1400. reflect that.
  1401. v4.0.0 (2018-01-19)
  1402. ===================
  1403. * **New features**
  1404. * tools: Provide bash completion support
  1405. Both ``virsh`` and ``virt-admin`` now implement basic bash completion
  1406. support.
  1407. * qemu: Refresh capabilities on host microcode update
  1408. A microcode update can cause the CPUID bits to change; therefore, the
  1409. capabilities cache should be rebuilt when such an update is detected on the
  1410. host.
  1411. * lxc: Set hostname based on container name
  1412. * **Improvements**
  1413. * CPU frequency reporting improvements
  1414. The CPU frequency will now be reported by ``virsh nodeinfo`` and other
  1415. tools for s390 hosts; at the same time; CPU frequency has been disabled on
  1416. aarch64 hosts because there's no way to detect it reliably.
  1417. * libxl: Mark domain0 as persistent
  1418. * Xen: Add support for multiple IP addresses on interface devices
  1419. * qemu: Add support for hot unplugging redirdev device
  1420. * **Bug fixes**
  1421. * qemu: Enforce vCPU hotplug granularity constraints
  1422. QEMU 2.7 and newer don't allow guests to start unless the initial vCPUs
  1423. count is a multiple of the vCPU hotplug granularity, so validate it and
  1424. report an error if needed.
  1425. v3.10.0 (2017-12-04)
  1426. ====================
  1427. * **New features**
  1428. * conf: Support defining distances between virtual NUMA cells
  1429. A NUMA hardware architecture supports the notion of distances between NUMA
  1430. cells. This can now be specified using the ``<distances>`` element within
  1431. the NUMA cell configuration. Drivers which support this include Xen and
  1432. QEMU.
  1433. * Xen: Support defining vNUMA topology
  1434. Xen now supports defining a virtual NUMA topology for VMs, including
  1435. specifying distances between NUMA cells.
  1436. * qemu: Add the ability to configure HPT resizing for pSeries guests
  1437. The user can now decide whether HPT (Hash Page Table) resizing should be
  1438. enabled, disabled or required instead of leaving it up to hypervisor
  1439. defaults and negotiation between the guest and the host.
  1440. * qemu: Add vmcoreinfo feature
  1441. Starting with QEMU 2.11, the guest can save kernel debug details when this
  1442. feature is enabled and the kernel supports it. It is useful to process
  1443. kernel dump with KASLR enabled, and also provides various kernel details to
  1444. crash tools.
  1445. * conf: Move the auth and encryption definitions to disk source
  1446. Allow parsing and formatting of the ``auth`` and ``encryption``
  1447. sub-elements to be a child of the ``source`` element. This will allow
  1448. adding an ``auth`` sub-element to a ``backingStore`` or ``mirror`` elements
  1449. as a means to track specific authentication and/or encryption needs.
  1450. * **Improvements**
  1451. * vbox: Add VirtualBox 5.2 support
  1452. * vbox: Add support for configuring storage controllers
  1453. The VirtualBox driver now supports the ``<controller>`` element in the
  1454. domain XML for configuring storage controllers in VBOX VMs. Additionally,
  1455. libvirt's domain XML schema was updated to allow optional ``model``
  1456. attribute for ``<controller type='ide'>`` which is used by the VBOX driver
  1457. to set the IDE controller model to be one of 'piix4', 'piix4' (default), or
  1458. 'ich6'. Finally, with this change ``dumpxml`` generates ``<controller>``
  1459. elements that correspond to current VBOX VM storage controller
  1460. configuration.
  1461. * vbox: Add support for attaching empty removable disks
  1462. The VirutalBox driver now supports adding CD-ROM and floppy disk devices
  1463. that do not have the disk source specified. Previously such devices were
  1464. silently ignored.
  1465. * vbox: Add support for attaching SAS storage controllers
  1466. In VirtualBox, SCSI and SAS are distinct controller types whereas libvirt
  1467. does not make such distinction. Therefore, the VBOX driver was updated to
  1468. allow attaching SAS controllers via ``<controller type='scsi'
  1469. model='lsisas1068'>`` element. If there are both SCSI and SAS controllers
  1470. present in the VBOX VM, the domain XML can associate the disk device using
  1471. the ``<address>`` element with the ``controller`` attribute, and
  1472. optionally, set the port via ``unit`` attribute.
  1473. * qemu: Generate predictable paths for qemu memory backends
  1474. In some cases management applications need to know paths passed to
  1475. memory-backend-file objects upfront. Libvirt now generates predictable
  1476. paths so applications can prepare the files if they need to do so.
  1477. * Shareable disks work properly with recent qemu
  1478. Recent qemu versions added image locking to avoid potential corruption of
  1479. disk images. This broke shareable disks with libvirt since the feature was
  1480. turned on by default in qemu. Libvirt now enables sharing of those disks in
  1481. qemu so that the image locking is not applied in that case. Additionally
  1482. libvirt now checks that shareable disks have supported format (raw) to
  1483. avoid metadata corruption.
  1484. * Improve serial console behavior on non-x86 architectures
  1485. ppc64, aarch64 and s390x guests were treating the <serial> and <console>
  1486. elements differently from x86, in some cases presenting misleading
  1487. information to the user. The behavior is now consistent across all
  1488. architectures and the information reported is always accurate.
  1489. * **Bug fixes**
  1490. * vbox: Do not ignore failures to attach disk devices when defining
  1491. The ``define`` now fails and reports an error if any of the ``controller``
  1492. or ``disk`` devices specified in the domain XML fail to attach to the
  1493. VirtualBox VM.
  1494. * vbox: Fix dumpxml to always output disk devices
  1495. The VirtualBox driver was ignoring any disk devices in ``dumpxml`` output
  1496. if there was a SAS storage controller attached to the VM.
  1497. * vbox: Fix dumpxml to always generate valid domain XML
  1498. When a VirtualBox VM has multiple disks attached, each to a different
  1499. storage controller that uses 'sd' prefix for block device names e.g. one
  1500. disk attached to SATA and one to SCSI controller, it no longer generates
  1501. XML where both would have 'sda' device name assigned. Instead it properly
  1502. assigns 'sda' and 'sdb' to those disks in the order of appearance.
  1503. * Securely pass iSCSI authentication data
  1504. Rather than supplying the authentication data as part of the iSCSI URL for
  1505. a disk or host device, utilize the encrypted secret object to securely pass
  1506. the authentication data.
  1507. v3.9.0 (2017-11-02)
  1508. ===================
  1509. * **New features**
  1510. * Add capability to allow hot (un)plug of a domain watchdog device
  1511. * Allow users to set device aliases
  1512. Users can set aliases to domain devices and thus identify them easily.
  1513. * qemu: Support multiqueue for virtio-blk
  1514. Multiqueue support for ``virtio-blk`` has been available in QEMU ever since
  1515. 2.7.0, and now libvirt guests can enable it.
  1516. * Add virDomainSetLifecycleAction API
  1517. Provided a new API to allow dynamic guest lifecycle control for guest
  1518. reactions to poweroff, restart, or crash type events related to the domain
  1519. XML ``on_poweroff`` , ``on_reboot`` , and ``on_crash`` elements. The
  1520. ``virsh set-lifecycle-action`` command was created to control the actions.
  1521. * qemu: Allow cold(un)plugging and hot(un)plugging input devices
  1522. * net: Implement QoS for vhostuser
  1523. * **Improvements**
  1524. * Allow a logical volume to be create using LUKS
  1525. A logical volume may be created using an ``encryption`` element using
  1526. "luks" format. This does require a previously created ``secret`` to store
  1527. the passphrase used to encrypt the volume Adding the volume to a domain can
  1528. then either provide the secret or allow the consumer in the guest to
  1529. provide the passphrase in order to decrypt the volume.
  1530. * net: Ignore auto-generated MAC address when detaching an interface
  1531. If the MAC address has not been specified by the user, libvirt will try and
  1532. fill in the gaps by generating one; however, for some error paths that led
  1533. to some confusing error messages, so when an auto-generated MAC address is
  1534. specified the error message will not include the auto-generated MAC.
  1535. * net: Enable MAC address lookup for virDomainInterfaceStats
  1536. * apparmor: Several improvements
  1537. Changes include permitting access to data about USB devices and ``dnsmasq``
  1538. instances, allowing spaces in guest names and many more.
  1539. * cpu: Use CPU information obtained from QEMU when possible
  1540. Recent QEMU versions can expose information about which CPU models are
  1541. available and usable on the host; libvirt will now make use of such
  1542. information whenever possible.
  1543. * hyperv: Various improvements
  1544. The error reported when clients can't connect to Hyper-V has been made more
  1545. descriptive, and memory limits for guests are now mapped to more
  1546. appropriate libvirt equivalents.
  1547. * qemu: Report QEMU error on failed migration
  1548. Instead of reporting a generic error, ask QEMU for a more detailed and thus
  1549. hopefully more helpful one.
  1550. * vbox: Implement autoport for RDP
  1551. libvirt will now obtain the (dynamically allocated) RDP port number from
  1552. VirtualBox itself, avoiding conflicts between multiple guests wanting to
  1553. use RDP at the same time.
  1554. * qemu: Allow rotation of small logs
  1555. On a host where numerous unique instances are executed per day, it's quite
  1556. possible that, even though each of the single log files are fairly small,
  1557. collectively the quantity and volume may add tens of thousands of log files
  1558. to the ``/var/log/libvirt/qemu/`` directory. Removing the constraints that
  1559. log have to be bigger than 100 KiB before they can be rotated solves the
  1560. issue.
  1561. * **Bug fixes**
  1562. * Fix swapped interface statistics and QoS
  1563. Due to internal implementation, reported statistics for some types of
  1564. interfaces were swapped (RX appeared in TX and vice versa). Similarly, QoS
  1565. was set in reversed way.
  1566. * Properly resize local LUKS encrypted volume
  1567. Resizing of a local LUKS encrypted volume will now use qemu-img to resize
  1568. the volume. This will require configuring a secret for the LUKS encrypted
  1569. volume.
  1570. * qemu: Reserve PCI addresses for implicit i440fx devices
  1571. Failing to do so causes the addresses to be considered usable by libvirt,
  1572. which means they could be assigned to more than one device resulting in the
  1573. guest failing to start.
  1574. * spec: Restart libvirtd only at the end of the upgrade process
  1575. Use ``%posttrans`` to make sure ``libvirtd`` is not restarted before all
  1576. other components, such as the library itself and storage / hypervisor
  1577. drivers, have already been upgraded.
  1578. * **Security**
  1579. * qemu: Ensure TLS clients always verify the server certificate
  1580. While it's reasonable to turn off client certificate validation, as setting
  1581. it up can be non-trivial, clients should always verify the server
  1582. certificate to avoid MITM attacks. However, libvirt was using the same knob
  1583. to control both checks, leading to CVE-2017-1000256 / LSN-2017-0002.
  1584. v3.8.0 (2017-10-04)
  1585. ===================
  1586. * **New features**
  1587. * qemu: Added support for cold-(un)plug of watchdog devices
  1588. * qemu: Added support for setting IP address os usernet interfaces
  1589. * qemu: Added support for Veritas Hyperscale (VxHS) block devices
  1590. * storage: Added new events for pool-build and pool-delete
  1591. * **Improvements**
  1592. * qemu: Set DAC permissions properly for spice rendernode
  1593. When a ``rendernode`` path is set for SPICE GL on ``qemu:///system`` , we
  1594. now correctly set DAC permissions on the device at VM startup. This is the
  1595. last remaining hurdle to let SPICE GL work for ``qemu:///system`` without
  1596. any external host changes.
  1597. * nodedev: Add switchdev offload query to NIC capabilities
  1598. Allow querying the NIC interface capabilities for the availability of
  1599. switchdev offloading (also known as kernel-forward-plane-offload).
  1600. * New CPU models for AMD and Intel
  1601. AMD EPYC and Intel Skylake-Server CPU models were added together with their
  1602. features
  1603. * Improve long waiting when saving a domain
  1604. While waiting for a write to disk to be finished, e.g. during save, even
  1605. simple operations like ``virsh list`` would be blocking due to domain lock.
  1606. This is now resolved by unlocking the domain in places where it is not
  1607. needed.
  1608. * **Bug fixes**
  1609. * Proper units are now used in virsh manpage for dom(mem)stats
  1610. Previously the documentation used multiples of 1000, but now it is fixed to
  1611. use multiples of 1024.
  1612. * qemu: Fix error reporting when disk attachment fails
  1613. There was a possibility for the actual error to be overridden or cleared
  1614. during the rollback.
  1615. * qemu: Fix assignment of graphics ports after daemon restart
  1616. This could be seen with newer kernels that have bug regarding SO_REUSEADDR.
  1617. After libvirtd was restarted it could assign already used address to new
  1618. guests which would make them fail to start. This is fixed by marking used
  1619. ports unavailable when reconnecting to running QEMU domains.
  1620. * Fix message decoding which was causing a very strange bug
  1621. When parsing an RPC message with file descriptors was interrupted and had
  1622. to restart, the offset of the payload was calculated badly causing strange
  1623. issues like not being able to find a domain that was not requested.
  1624. v3.7.0 (2017-09-04)
  1625. ===================
  1626. * **New features**
  1627. * qemu: Add managedsave-edit commands
  1628. Using managedsave-dumpxml, managedsave-define and managedsave-edit
  1629. commands, now we can dump and edit the XML configuration of domain which
  1630. has managedsave image.
  1631. * qemu: Add migrate-getmaxdowntime command
  1632. Currently, the maximum tolerable downtime for a domain being migrated is
  1633. write-only from libvirt, via migrate-setmaxdowntime. This implements a
  1634. complementary migrate-getmaxdowntime command
  1635. * bhyve: Support autoport for VNC ports
  1636. It's no longer necessary to explicitly specify VNC port for the bhyve
  1637. guests. With the autoport feature it will be allocated automatically.
  1638. Please refer to the bhyve driver documentation for examples.
  1639. * qemu: Added support for setting heads of virtio GPU
  1640. * qemu: Added support to configure reconnect timeout for chardev devices
  1641. When you have a TCP or UNIX chardev device and it's connected somewhere you
  1642. can configure reconnect timeout if the connection is closed.
  1643. * **Improvements**
  1644. * qemu: Report a clear error when dropping a VM during startup
  1645. "Failed to load config for domain 'DOMNAME'" is now reported if a VM config
  1646. can't be parsed for some reason, and thus provides a clear indication for
  1647. users (and devs).
  1648. * apparmor: Update for QEMU 2.10 compatibility
  1649. Starting with QEMU 2.10, disk images and NVRAM files get automatically
  1650. locked to prevent them from being corrupted; however, file locking needs to
  1651. be explicitly allowed through ``virt-aa-helper`` or AppArmor will reject
  1652. the requests and the guest will not be able to run.
  1653. * virsh: List Unix sockets in 'domdisplay' output
  1654. VNC and SPICE graphics can use Unix sockets instead of TCP/IP sockets as
  1655. connection endpoints, but such a configuration was not handled correctly by
  1656. ``virsh domdisplay`` , causing the respective endpoints to be missing from
  1657. the output.
  1658. * qemu: Don't check whether offline migration is safe
  1659. Since offline migration only copies the guest definition to the destination
  1660. host, data corruption is not a concern and the operation can always be
  1661. performed safely.
  1662. * virt-host-validate: Fix IOMMU detection on ppc64
  1663. * **Bug fixes**
  1664. * qemu: Better support for international domain names (with wide characters)
  1665. There were some issues with multi-byte domains getting lost on daemon
  1666. restart due to truncation, so the code now handles multi-byte names a bit
  1667. better.
  1668. * qemu: Support long domain names with namespaces
  1669. Domains with extremely long names would fail to start due to temporary
  1670. namespace paths being created with the whole name. The path is now
  1671. generated with shortened name instead.
  1672. * qemu: Tolerate missing emulator binary during libvirtd restart
  1673. For some time libvirt required qemu capabilities being present when parsing
  1674. VM configs during startup. As a side effect VM configs would fail to parse
  1675. and thus vanish, if the emulator binary would be uninstalled or broken.
  1676. Libvirt now tolerates when capabilities are missing during startup.
  1677. * qemu: Prevent pSeries guests from disappearing in some situations
  1678. pSeries guest would disappear if any of the host devices they were
  1679. configured to use was not available during libvirtd startup, which could
  1680. easily happen for SR-IOV Virtual Functions. This scenario is now handled
  1681. correctly.
  1682. * qemu: Honor <on_reboot/> setting
  1683. The setting was accepted by the parser, but not actually implemented.
  1684. * Fix --verbose option for all daemons
  1685. Since v3.0.0, the option had been ignored by all libvirt daemons (
  1686. ``libvirtd`` , ``virtlogd`` and ``virtlockd`` ); it's now working as
  1687. intended once again.
  1688. v3.6.0 (2017-08-02)
  1689. ===================
  1690. * **New features**
  1691. * hyperv: Implement virDomainSetMemory and virDomainSendKey APIs
  1692. * qemu: Support multiple PHBs for pSeries guests
  1693. pSeries guests can now have multiple PHBs (PCI Host Bridges), which show up
  1694. as separate PCI domains in the guest. To create additional PHBs, simply add
  1695. PCI controllers with model ``pci-root`` to the guest configuration.
  1696. * qemu: Isolate hostdevs on pSeries guests
  1697. To enable better error reporting and recovery, unrelated hostdevs will now
  1698. be automatically isolated on pSeries guests by placing them on separate
  1699. PHBs (PCI Host Bridges).
  1700. * **Improvements**
  1701. * qemu: platform serial devices can now use chardev features
  1702. QEMU VMs that depend on platform serial devices can now use QEMU's
  1703. ``-chardev`` option, which enables access to advanced features like log
  1704. file configuration. This applies to the default serial devices for arm,
  1705. aarch64, and some ppc configurations.
  1706. * Require use of GCC 4.4 or Clang compilers
  1707. We only ever test libvirt with GCC or Clang (which provides a GCC
  1708. compatible compilation environment). Between them, these compilers cover
  1709. every supported operating system platform, including Windows.
  1710. * qemu: shared disks with directsync cache should be safe for migration
  1711. At present shared disks can be migrated with either readonly or
  1712. ``cache=none`` . But ``cache=directsync`` should be safe for migration,
  1713. because both ``cache=directsync`` and ``cache=none`` don't use the host
  1714. page cache, and ``cache=direct`` write through qemu block layer cache.
  1715. * Handle hotplug change on VLAN configuration using OVS
  1716. Libvirt was taught to handle VLAN change for running OVS interface.
  1717. * **Bug fixes**
  1718. * qemu: Use vCPU 'node-id' property and pass it back to qemu
  1719. vCPU properties gathered from query-hotpluggable-cpus need to be passed
  1720. back to QEMU. As QEMU did not use the node-id property until now and
  1721. libvirt forgot to pass it back properly (it was parsed but not passed
  1722. around) we did not honor this.
  1723. * Miscellaneous stream fixes
  1724. After introducing sparse stream features there were still some known bugs
  1725. left. Those are fixed in this release.
  1726. * qemu: Miscellaneous domain NS fixes
  1727. Libvirt starts qemu domains in separate Linux namespaces for a while now.
  1728. However, there were still some bugs lingering. For instance libvirt did not
  1729. know how to handle file based bind mounts.
  1730. * Various CPU driver improvements
  1731. There were some minor bugs when using 'host-model' CPU.
  1732. v3.5.0 (2017-07-04)
  1733. ===================
  1734. * **New features**
  1735. * qemu: Add support for loadparm for a boot device
  1736. Add an optional boot parameter 'loadparm' for a boot device. Loadparm is an
  1737. 8 byte parameter that, when present, is queried by S390 guests via sclp or
  1738. diag 308. Linux guests on S390 use it to select a boot entry.
  1739. * Support controlling how video devices are exposed to the bhyve guests
  1740. The ``vgaconf`` attribute was added to ``video`` 's ``driver`` element.
  1741. Possible values are: ``on`` , ``off`` , and ``io`` . It controls the way
  1742. how bhyve exposes video devices to its guests; various guest OSes might
  1743. require different settings to boot properly.
  1744. * qemu: Add support for live updates of coalesce settings
  1745. Users can now use ``virsh update-device`` to change the coalesce settings
  1746. of an interfaces while the domain is running.
  1747. * qemu: Allow VirtIO devices to use vIOMMU
  1748. It is now possible to turn on IOTBL for the vIOMMU and have VirtIO devices
  1749. use it, provided they have been configured appropriately.
  1750. * **Improvements**
  1751. * qemu: block copy job can be used with persistent domains
  1752. Until now it was not possible to use block copy with persistent VMs. In use
  1753. cases where it's not required to recover the job after VM shutdown, it's
  1754. possible to specify VIR_DOMAIN_BLOCK_COPY_TRANSIENT_JOB flag to start the
  1755. copy job.
  1756. * JSON pseudo-protocol backing store parser supports new format of qemu 2.9
  1757. QEMU 2.9 modified a few structures corresponding to the JSON format of
  1758. specifying a backing store for a disk image. Libvirt now implements the new
  1759. format.
  1760. * Capabilities now include info about host's CAT settings
  1761. Various information about resource control from the host is gathered and
  1762. presented in capabilities if available.
  1763. * apparmor: Several improvements
  1764. Allow access to Ceph config, EFI firmware on both x86_64 and aarch64,
  1765. device tree on ppc64 and more.
  1766. * qemu: Support host-model on POWER9 machines
  1767. * **Bug fixes**
  1768. * qemu: snapshot: retrieve image metadata from user provided files
  1769. Disk images of an external snapshot created with
  1770. VIR_DOMAIN_SNAPSHOT_CREATE_REUSE_EXT flag specified would not be scanned
  1771. for metadata after recent changes. The metadata is necessary to allow
  1772. keeping relative paths between images when doing a block-commit.
  1773. * Parse decimal numbers in a locale-independent way
  1774. Some locales, such as ``de_DE`` and ``pt_BR`` , use comma rather than dot
  1775. to separate the integer part from the fractional part of a decimal number;
  1776. however, several data sources such as the kernel use a locale-independent
  1777. representation and need to be treated accordingly.
  1778. * Support compilation with newer compiler and libc versions
  1779. Several fixes have been included to make compilation with Clang 4.0.0, GCC
  1780. 7.1 and glibc >= 2.25.90 possible.
  1781. * qemu: Query name for vhost-user interfaces at runtime
  1782. This makes it possible to use ``virsh`` subcommands such as ``domiflist``
  1783. and ``domifstat`` on vhost-user interfaces.
  1784. * qemu: Set MTU for hotplugged interfaces correctly
  1785. When hotplugging a network interface, the MTU was only set on the guest
  1786. side. Set it on the host side as well.
  1787. * qemu: Forbid updating MTU for interfaces of running guests
  1788. The MTU setting can't be modified while the guest is running, so any
  1789. attempt to alter it at runtime will now result in an error rather than
  1790. being silently ignored.
  1791. * qemu: Fix specifying QXL heads with older QEMU releases
  1792. Specifying the number of QXL heads was not working correctly for QEMU
  1793. releases older than 1.6.
  1794. * qemu: Fix migration to older libvirt/QEMU versions
  1795. When the guest is started, libvirt updates the CPU definition to reflect
  1796. the actual CPU features to enforce ABI. We need to send original and
  1797. updated CPU definition in order to support migration to older libvirt/QEMU
  1798. versions. Only the updated CPU definition was sent to destination.
  1799. v3.4.0 (2017-06-02)
  1800. ===================
  1801. * **New features**
  1802. * Improved streams to efficiently transfer sparseness
  1803. New extension to virStream was implemented so that virStorageVolDownload
  1804. and virStorageVolUpload can preserve file sparseness.
  1805. * I/O APIC type can be specified for QEMU/KVM domains
  1806. The ``ioapic`` tag was added to domain ``features`` , so the type of the
  1807. I/O APIC can now be specified (e.g. putting it in userspace for KVM
  1808. domains).
  1809. * The reason for VM shutdown is reported, if known
  1810. QEMU 2.10 will be able to report the reason for shutting down (whether that
  1811. was caused by the guest or not), and libvirt is prepared for that and
  1812. reports that information in its shutdown event as well, if it is known.
  1813. * **Improvements**
  1814. * Repository now has new README.md file
  1815. The new file uses markdown syntax, so it looks better on github and
  1816. possibly other web pages, but it has also more useful information. The old
  1817. README is now symlink to the new file.
  1818. * qemu: Use GICv2 by default for aarch64/virt TCG guests
  1819. The emulated GICv3 has some limitations that make it unusable as a default;
  1820. use GICv2 until they're sorted out. This change makes it once again
  1821. possible to run aarch64/virt guests on a x86_64 host without having to
  1822. tweak their configuration.
  1823. * Additional capabilities for the node_device module
  1824. Introduce two new capabilities to the node_device module. The first is for
  1825. CCW devices, most common on the S390 architecture. The second is for fibre
  1826. channel-backed SCSI devices and exposes the fc_remote_port sub-capability
  1827. to SCSI target devices.
  1828. * Node devices now report Mediated device capabilities
  1829. Endpoint devices support new ``mdev`` capability and their parents now
  1830. report the supported types in new ``mdev_types`` capability.
  1831. * Capabilities now report information about host caches
  1832. If supported in the kernel, host capabilities will now list L3 caches. The
  1833. code for other levels was added as well, but only L3 caches are reported
  1834. currently.
  1835. * POWER9 CPU model was added
  1836. It is now properly reported in host capabilities.
  1837. * libxl: NUMA sibling distances are now reported in host capabilities
  1838. * VMDK version 3 files are now properly detected
  1839. * Interrupt remapping and Extended interrupt mode for IOMMU devices
  1840. These two new features can now be controlled with new ``<driver
  1841. intremap='on/off' eim='on/off'/>`` tag for ``iommu`` devices.
  1842. * Graphics in libxl domains now have default addresses
  1843. Even though there were default addresses before this change, they were not
  1844. saved in the XML. It is now possible to see and control the listen
  1845. addresses properly.
  1846. * Default USB controllers are now added for devices in libxl domains
  1847. Even though they were added automatically when USB device was attached,
  1848. they could've been missing in some other cases. The logic is now fixed so
  1849. there are always USB controllers, even if there was none of them in the
  1850. specified XML.
  1851. * Limits for RPC messages were increased
  1852. Hitting the RPC limits we have is easier every day, so they were increased
  1853. once again and some guessing logic was improved as well. It is now possible
  1854. to get more stats than ever using the ``virConnectGetAllDomainStats()``
  1855. call and push through even bigger requests and replies for all APIs.
  1856. * **Bug fixes**
  1857. * qemu: Create memory_backing_dir on startup
  1858. Libvirt's policy is that directories are created on startup if they don't
  1859. exist. We've missed this one.
  1860. * PCIe 4.0 cards now report proper link speeds
  1861. It could happen that the link speed for PCIe devices was not properly
  1862. reported or the nodedev-dumpxml just failed. That was due to mistake in the
  1863. field width, but should now work properly.
  1864. * qemu: Do not report errors on shutdown
  1865. For some users, in some rare cases, it could happen that there was an error
  1866. message "internal error: End of file from qemu monitor" in the logs even
  1867. though no problem happened. The detection of these false positives was
  1868. improved and such errors should not show any more.
  1869. * User-specified UNIX socket paths for virtio channels should not be reset
  1870. It could happen, in some cases, that libvirt would mistake a user-specified
  1871. path for its own generated one and thus remove it from the XML. The
  1872. detection of such addresses was improved now.
  1873. * Fix address reservation during RNG hot-plug
  1874. When error occurred in a specific point in time during the hot-plug of an
  1875. RNG device, it could happen that an address was released even though
  1876. another device was already using it, making it possible to hot-plug another
  1877. device with that address, effectively having duplicated addresses in the
  1878. XML.
  1879. v3.3.0 (2017-05-05)
  1880. ===================
  1881. * **New features**
  1882. * net: Add support for coalesce settings
  1883. Enabling data batching through these settings can improve network
  1884. performance for guests.
  1885. * qemu: Add support for guest CPU cache specification
  1886. This features allows fine-grained control of the cache behavior of the
  1887. guest CPU.
  1888. * qemu: Add support for the qemu-xhci USB controller
  1889. * **Improvements**
  1890. * hyperv: Support Hyper-V 2012 and newer
  1891. Starting with Hyper-V 2012 the API has changed causing the existing driver
  1892. to be unable to send and process requests properly. This has been resolved
  1893. by adding abstractions to handle the differences and ease handling such
  1894. breaks if they happen in the future.
  1895. * libxl: Add support for nested HVM domains
  1896. Xen has supported nested HVM domains since version 4.4. The libvirt libxl
  1897. driver now supports nested HVM domains by specifying the host-passthrough
  1898. CPU mode when defining a domain.
  1899. * qemu: Implement ACPI support for aarch64 guests
  1900. Up until this point, ACPI support was only advertised for x86_64 guests and
  1901. disabling it for aarch64 guests was not possible at all.
  1902. * vz: Add support for changing the number of vCPUs
  1903. * qemu: Automatically choose the best USB controller for guests
  1904. The recently introduced qemu-xhci USB controller is the best choice for
  1905. both ppc64 and aarch64 guests, so use it by default on those architectures
  1906. if available.
  1907. * daemon: Increase default task limit for libvirtd
  1908. The default number of tasks for the pids cgroup controller is 512, which
  1909. libvirtd can quickly bump into when starting lots of guests. Raise the
  1910. limit to a more reasonable 32768.
  1911. * docs: Include man pages describing key code names and values
  1912. * virsh: Report initialization errors
  1913. Sometimes virsh might be unable to start: when that happens, report useful
  1914. diagnostics instead of failing silently.
  1915. * **Bug fixes**
  1916. * nss: Don't require a network restart for libvirt_guest
  1917. Previously, the libvirt_guest NSS module would only work properly after the
  1918. corresponding network had been restarted; now newly started guests will be
  1919. reported correctly right away.
  1920. * storage: Remove unavailable transient pools after restart
  1921. Solve an issue where transient storage pools would be stuck in an
  1922. unmanageable state if the source disappeared and libvirtd was subsequently
  1923. restarted.
  1924. * storage: Fix capacity value for LUKS encrypted volumes
  1925. The 'capacity' value (e.g. guest logical size) for a LUKS volume is smaller
  1926. than the 'physical' value of the file in the file system, so we need to
  1927. account for that.
  1928. * qemu: Fix regression when hyperv/vendor_id feature is used
  1929. Guests using the feature would not be started at all; it is now possible to
  1930. start them as expected.
  1931. * qemu: Do not crash on USB address with no port and invalid bus
  1932. * crypto: Always pad data before encrypting it
  1933. If this step is not performed, when the data length matches the chunk size
  1934. the decryption routines will misinterpret the last byte of data as the
  1935. padding length and fail to decode it correctly.
  1936. v3.2.0 (2017-04-02)
  1937. ===================
  1938. * **New features**
  1939. * The virt-host-validate tool now supports bhyve hypervisor
  1940. * Introduce NVDIMM memory model
  1941. NVDIMM is new type of memory introduced into QEMU 2.6. The idea is that we
  1942. have a non-volatile memory module that keeps the data persistent across
  1943. domain reboots and offers much faster data accesses. However, due to a bug
  1944. in QEMU, this feature is not enabled for QEMUs older than 2.9.0.
  1945. * qemu: Introduce support for generic PCIe Root Ports
  1946. For new controllers, a generic device (pcie-root-port) will be used by
  1947. default instead of the Intel-specific device (ioh3420), provided the QEMU
  1948. binary supports it.
  1949. * qemu: Add support for checking guest CPU ABI compatibility
  1950. When migrating a domain to a different host, restoring a domain from a file
  1951. or reverting a snapshot libvirt will make sure the guest CPU QEMU presents
  1952. to the guest OS exactly matches the one provided on the source host (or
  1953. before the domain's state was saved). This enhanced check may also be
  1954. requested when starting a new domain to ensure the virtual CPU exactly
  1955. matches the one specified in the XML.
  1956. * qemu: Add support to migrate using TLS
  1957. Add the ability to migrate QEMU guests using TLS via a new flag
  1958. VIR_MIGRATE_TLS or virsh migrate '--tls' option. Requires using at least
  1959. QEMU 2.9.0 in order to work properly.
  1960. * qemu: add mediated devices framework support
  1961. Recent kernel version introduced new mediated device framework, so provide
  1962. an initial support of this framework for libvirt, mainly by introducing a
  1963. new host device type in the XML.
  1964. * qemu: Add support for setting TSC frequency
  1965. Setting TSC frequency is required to enable migration for domains with
  1966. 'invtsc' CPU feature turned on.
  1967. * Add support for block device threshold event
  1968. When using thin provisioning, management tools need to resize the disk in
  1969. certain cases. To avoid having them to poll disk usage this version
  1970. introduces an event which will be fired when a given offset of the storage
  1971. is written by the hypervisor. Together with the API it allows registering
  1972. thresholds for given storage backing volumes and this event will then
  1973. notify management if the threshold is exceeded. Currently only the qemu
  1974. driver supports this.
  1975. * bhyve: Add support for UEFI boot ROM, VNC, and USB tablet
  1976. The bhyve driver now supports booting using the UEFI boot ROM, so
  1977. non-FreeBSD guests that support UEFI could be booted without using an
  1978. external boot loader like grub-bhyve. Video is also supported now, allowing
  1979. to connect to guests via VNC and use an USB tablet as an input device.
  1980. Please refer to the driver page for domain XML examples.
  1981. * **Improvements**
  1982. * qemu: Detect host CPU model by asking QEMU on x86_64
  1983. Previously, libvirt detected the host CPU model using CPUID instruction,
  1984. which caused libvirt to detect a lot of CPU features that are not supported
  1985. by QEMU/KVM. Asking QEMU makes sure we don't start it with unsupported
  1986. features.
  1987. * perf: Add more perf statistics
  1988. Add support to get the count of cpu clock time, task clock time, page
  1989. faults, context switches, cpu migrations, minor page faults, major page
  1990. faults, alignment faults, emulation faults by applications running on the
  1991. platform.
  1992. * Write hyperv crash information into vm log
  1993. qemu's implementation of the hyperv panic notifier now reports information
  1994. about the crash from the guest os. Starting with this version, libvirt logs
  1995. the information to the vm log file for possible debugging.
  1996. * **Bug fixes**
  1997. * QEMU: Use adaptive timeout for connecting to monitor
  1998. When starting qemu, libvirt waits for qemu to create the monitor socket
  1999. which libvirt connects to. Historically, there was sharp 30 second timeout
  2000. after which the qemu process was killed. This approach is suboptimal as in
  2001. some scenarios with huge amounts of guest RAM it can take a minute or more
  2002. for kernel to allocate and zero out pages for qemu. The timeout is now
  2003. flexible and computed by libvirt at domain startup.
  2004. * Overwrite (clear) 2 KB instead of just 512 bytes when initializing logical
  2005. device
  2006. * Describe the logical backend requirements better for pool-create-as
  2007. v3.1.0 (2017-03-03)
  2008. ===================
  2009. * **New features**
  2010. * storage: Add Virtuozzo storage backend storage pool
  2011. Add new storage backend to support pool and volume management within the
  2012. Virtuozzo Storage environment. Virtuozzo Storage is a highly available
  2013. distributed software defined storage with built-in replication and disaster
  2014. recovery.
  2015. * qemu: Add support for memory backing with file source
  2016. Add support in numa topology for file source inside memory backing
  2017. (hugepages are not needed) Three new elements <source/>,<access/> and
  2018. <allocation/> were added to <memoryBacking/> element. Also new
  2019. configuration parameter ``memory_backing_dir`` was added to qemu.conf.
  2020. * network: make openvswitch call timeout configurable
  2021. Adding the ability to specify the timeout value in seconds for openvswitch
  2022. calls in the libvirtd configuration file.
  2023. * bhyve: add e1000 NIC support
  2024. Add support for e1000 NIC. Previously, the only available option was
  2025. ``virtio-net`` .
  2026. * libxl: add tunneled migration support
  2027. Add tunneled migration to libxl driver, which is always capable of strong
  2028. encryption and doesn't require any extra network connection other than
  2029. what's required for remote access of libvirtd.
  2030. * qemu: add rendernode argument
  2031. Add a new attribute 'rendernode' to <gl> spice element.
  2032. * nodedev: add drm capability
  2033. Add a new 'drm' capability for Direct Rendering Manager (DRM) devices,
  2034. providing device type information.
  2035. * Add API for individual/specific vCPU hotplug
  2036. The new API allows selecting specific vCPUs to be added/removed from the
  2037. VM. The existing APIs allowed only adding/removing from the end which did
  2038. not play well with NUMA.
  2039. * **Improvements**
  2040. * virsh: pool-list: allow both --uuid and --name in one command
  2041. Adjust the virsh-pool command to support the --uuid and/or --name options
  2042. in order to print just the --name and/or --uuid of pools.
  2043. * Introduce MTU to domain <interface/> and <network>
  2044. Allow setting MTU size for some types of domain interface and network.
  2045. * libxl: improve support for <timer> configurations
  2046. Add support for multiple timers. Extend the tsc timer to support the
  2047. emulate mode. Improve conversion of timer XML to/from xl.cfg.
  2048. * storage: modularize the storage driver
  2049. Split up the storage driver backends into loadable modules so that binary
  2050. distributions don't have to compromise on shipping the storage driver with
  2051. all backends which may pull in too many dependencies.
  2052. * **Bug fixes**
  2053. * nodedev: Fabric name must not be required for fc_host capability
  2054. fabric_name is one of many fc_host attributes in Linux that is optional and
  2055. left to the low-level driver to decide if it is implemented. For example
  2056. the zfcp device driver does not provide a fabric name for an fcp host. The
  2057. requirement for the existence of a fabric name has been removed by making
  2058. it optional.
  2059. * bhyve: change address allocation schema for SATA disks
  2060. Previously, the bhyve driver assigned PCI addresses to SATA disks directly
  2061. rather than assigning that to a controller and using SATA addresses for
  2062. disks. It was implemented this way because bhyve has no notion of an
  2063. explicit SATA controller. However, as this doesn't match libvirt's
  2064. understanding of disk addresses, the bhyve driver was changed to follow the
  2065. common schema and have PCI addresses for SATA controllers and SATA
  2066. addresses for disks. If you're having issues because of this, it's
  2067. recommended to edit the domain's XML and remove <address type='pci'> from
  2068. the <disk> elements with <target bus='sata'/> and let libvirt regenerate it
  2069. properly.
  2070. * libxl: maximum memory fixes
  2071. Fix reporting of domain maximum memory. Fix setting dom0 maximum memory.
  2072. * libxl: fix disk detach when <driver> not specified
  2073. * libxl: fix dom0 autoballooning with Xen 4.8
  2074. * qemu: Allow empty script path to <interface/>
  2075. Historically, this was always allowed. Unfortunately, due to some rework
  2076. done for 1.3.2 release a bug was dragged in which suddenly stop allowing
  2077. domain with such configuration to start.
  2078. v3.0.0 (2017-01-17)
  2079. ===================
  2080. * **New features**
  2081. * Domain events for metadata content changes
  2082. The domain events framework has a new event ID that can be used to get
  2083. notifications when domain metadata content changes.
  2084. * Event notifications for the secret object
  2085. The secret object now supports event notifications, covering lifcycle
  2086. changes and secret value changes.
  2087. * New localPtr attribute for "ip" element in network XML
  2088. * qemu: Support QEMU group I/O throttling
  2089. Add the capability to allow group I/O throttling via a new domain <disk>
  2090. <iotune> subelement "group_name" to allow sharing I/O throttling quota
  2091. between multiple drives.
  2092. * nss: Introduce libvirt_guest
  2093. New ``libvirt_guest`` nss module that translates libvirt guest names into
  2094. IP addresses.
  2095. * daemon: Add support for runtime logging settings adjustment
  2096. Logging-related settings like log outputs and filters can now be adjusted
  2097. during runtime using the admin interface without the necessity of the
  2098. daemon's restart.
  2099. * storage: Add virStorageVolInfoFlags API
  2100. Add the API to support using the VIR_STORAGE_VOL_GET_PHYSICAL flag in order
  2101. to return the host physical size in bytes of the image container in the
  2102. allocation field of the _virStorageVolInfo structure. The --physical flag
  2103. has been added to the virsh vol-info command to access the data.
  2104. * libxl: Implement virDomainGetMaxVcpus API
  2105. * storage: Add overwrite flag checking for logical pool
  2106. Add support for the OVERWRITE flags for the logical storage backend
  2107. including checking for existing data on the target volumes when building a
  2108. new logical pool on target volume(s).
  2109. * qemu: Add support for guest CPU configuration on s390(x)
  2110. * **Improvements**
  2111. * perf: Add more perf statistics
  2112. Add support to get the count of branch instructions executed, branch
  2113. misses, bus cycles, stalled frontend cpu cycles, stalled backend cpu
  2114. cycles, and ref cpu cycles by applications running on the platform.
  2115. * conf: Display <physical> for volume xml
  2116. Add a display of the <physical> size of a disk volume in the output of the
  2117. volume XML.
  2118. * qemu: Use virtio-pci by default for aarch64 mach-virt guests
  2119. virtio-pci provides several advantages over virtio-mmio, such as the
  2120. ability to hotplug devices and improved performance. While opting in to
  2121. virtio-pci has been possible for a while, newly-defined guests will now use
  2122. it automatically.
  2123. * vbox: remove support for VirtualBox 3.x and older
  2124. Those old VirtualBox versions have been unsupported by upstream for a long
  2125. time and the API of 4.0 and newer has diverged enough to require code
  2126. abstractions to handle differences. Removing support for those old versions
  2127. drops lots of code from the driver and simplifies the logic to ease
  2128. implementation of new features going forward.
  2129. * virsh: pool-info: introduce option --bytes
  2130. Add option --bytes to virsh pool-info in order ti allow display of units in
  2131. bytes rather than default of human readable output.
  2132. * scsi: Add parent wwnn/wwpn or fabric capability for createVport
  2133. Improve the algorithm searching for the parent scsi_host device for
  2134. vHBA/NPIV scsi_host creation. Rather than supplying the "parent" by name,
  2135. it's now possible to define the parent by it's wwnn/wwpn or fabric_wwn in
  2136. the node device create XML or the storage pool XML.
  2137. * qemu: aggregate pcie-root-ports onto multiple functions of a slot
  2138. When pcie-root-ports are added to pcie-root in order to provide a place to
  2139. connect PCI Express endpoint devices, libvirt now aggregates multiple root
  2140. ports together onto the same slot (up to 8 per slot) in order to conserve
  2141. slots. Using this method, it's possible to connect more than 200 endpoint
  2142. devices to a guest that uses PCIe without requiring setup of any PCIe
  2143. switches.
  2144. * **Bug fixes**
  2145. * lxc: fix accidental killing of containers during libvirtd restart
  2146. The libvirt_lxc process was previously not moved into the container scope.
  2147. As a result, if systemd reloads its config after a container is started,
  2148. when libvirtd is later restarted it will accidentally kill the containers.
  2149. * qemu: Correct GetBlockInfo values
  2150. For an active domain, correct the physical value provided for a raw sparse
  2151. file backed storage and the allocation value provided for a qcow2 file
  2152. backed storage that hasn't yet been opened on the domain.
  2153. * qemu: Make virtio console usable on ppc64 guests
  2154. The chardev detection code has been improved and can now handle this
  2155. configuration properly.
  2156. * qemu: Enable mount namespace
  2157. To avoid funny races with udev relabelling devices under our hands and to
  2158. enhance security, libvirt now spawns each qemu process with its own
  2159. ``/dev`` .
  2160. * storage: Fix implementation of no-overwrite for file system backend
  2161. Fix file system storage backend implementation of the OVERWRITE flags to be
  2162. consistent between code and documentation. Add checks to ensure that when
  2163. building a new file system on a target volume that there is not something
  2164. already on the disk in a format that libvirt can recognize.
  2165. * qemu: Create hugepage path on per domain basis
  2166. Historically, all hugepage enabled domains shared the same path under
  2167. hugetlbfs. This left libvirt unable to correctly set security labels on it.
  2168. With this release, however, each domain is put into a separate path which
  2169. is also correctly labeled.
  2170. * conf: Reject domains with duplicate drive addresses
  2171. Reject duplicate drive addresses for disks and hostdevs at domain
  2172. definition.
  2173. * libxl: reverse defaults on HVM net device attach
  2174. Fixes network interface attach for HVM domains when no model is specified.
  2175. Emulated hotplug isn't yet supported and hence we should default to the
  2176. general working scenario.
  2177. * libxl: always enable pae for x86_64 HVM
  2178. By default pae is disabled in libxl. Without an explicit <pae/> setting in
  2179. the domain <features> configuration, an x86_64 HVM domain would be get an
  2180. i686 environment. pae should always be enabled for x86_64 HVM domains.
  2181. * qemu: Fix XML dump of autogenerated websocket
  2182. As a result autogenerated websocket port is regenerated on domain restore,
  2183. migration and such as it should be.
  2184. v2.5.0 (2016-12-04)
  2185. ===================
  2186. * **New features**
  2187. * shmem: Add support for additional models
  2188. The shmem device can now utilize QEMU's ivshmem-plain and ivshmem-doorbell,
  2189. more modern versions of ivshmem.
  2190. * vbox: Add VirtualBox 5.1 support
  2191. * libssh: New transport
  2192. The new libssh transport allows one to connect to a running libvirtd via
  2193. SSH, using the libssh library; for example: ``qemu+libssh://server/system``
  2194. .
  2195. * vhost-scsi: Add support scsi_host hostdev passthrough
  2196. Add the capability to pass through a scsi_host HBA and the associated LUNs
  2197. to the guest.
  2198. * Allow debugging of gluster volumes in qemu
  2199. Users can now enable debug logging for native gluster volumes in qemu using
  2200. the "gluster_debug_level" option in qemu.conf
  2201. * Pre-allocate memory slots for memory hotplug
  2202. Slot numbers for memory devices are now automatically allocated and thus
  2203. persistent. In addition slot numbers can be specified without providing a
  2204. base address, which simplifies user configuration
  2205. * qemu: Express devices will be placed on PCIe bus by default
  2206. For machine types that use a PCI Express root bus (e.g. x86_64/Q35 and
  2207. aarch64/virt), any unaddressed PCI device that is an Express device (all
  2208. virtio-1.0 devices, e1000e, nec-xhci, vfio assigned devices) will be placed
  2209. on an Express controller (i.e. a pcie-root-port) instead of a legacy PCI
  2210. controller (i.e. pci-bridge) with the root ports added as needed.
  2211. * **Improvements**
  2212. * docs: Better documentation for migration APIs and flags
  2213. * vbox: Address thread safety issues
  2214. * virsh: Add support for passing an alternative persistent XML to migrate
  2215. command
  2216. * vhostuser: Allow hotplug of multiqueue devices
  2217. * NEWS: Switch to an improved format
  2218. List user-visible changes instead of single commits for a better high-level
  2219. overview of differences between libvirt releases.
  2220. * website: Modernize layout and branding
  2221. The libvirt website looked very cluttered and outdated; it has now been
  2222. completely overhauled, resulting in a design that's better organized and
  2223. more pleasant to look at.
  2224. * **Bug fixes**
  2225. * vz: Fix migration in P2P mode
  2226. * Forbid newline character in names of some libvirt objects
  2227. * Fix compilation on macOS
  2228. v2.4.0 (2016-11-01)
  2229. ===================
  2230. No release notes.
  2231. v2.3.0 (2016-10-04)
  2232. ===================
  2233. No release notes.
  2234. v2.2.0 (2016-09-02)
  2235. ===================
  2236. No release notes.
  2237. v2.1.0 (2016-08-02)
  2238. ===================
  2239. No release notes.
  2240. v2.0.0 (2016-07-01)
  2241. ===================
  2242. No release notes.
  2243. v1.3.5 (2016-06-04)
  2244. ===================
  2245. No release notes.
  2246. v1.3.4 (2016-05-01)
  2247. ===================
  2248. No release notes.
  2249. v1.3.3 (2016-04-06)
  2250. ===================
  2251. No release notes.
  2252. v1.3.2 (2016-03-01)
  2253. ===================
  2254. No release notes.
  2255. v1.3.1 (2016-01-17)
  2256. ===================
  2257. No release notes.
  2258. v1.3.0 (2015-12-09)
  2259. ===================
  2260. No release notes.
  2261. v1.2.21 (2015-11-04)
  2262. ====================
  2263. No release notes.
  2264. v1.2.20 (2015-10-02)
  2265. ====================
  2266. No release notes.
  2267. v1.2.19 (2015-09-02)
  2268. ====================
  2269. No release notes.
  2270. v1.2.18 (2015-08-03)
  2271. ====================
  2272. No release notes.
  2273. v1.2.17 (2015-07-02)
  2274. ====================
  2275. No release notes.
  2276. v1.2.16 (2015-06-01)
  2277. ====================
  2278. No release notes.
  2279. v1.2.15 (2015-05-04)
  2280. ====================
  2281. No release notes.
  2282. v1.2.14 (2015-04-02)
  2283. ====================
  2284. No release notes.
  2285. v1.2.13 (2015-03-02)
  2286. ====================
  2287. No release notes.
  2288. v1.2.12 (2015-01-27)
  2289. ====================
  2290. No release notes.
  2291. v1.2.11 (2014-12-13)
  2292. ====================
  2293. No release notes.
  2294. v1.2.10 (2014-11-03)
  2295. ====================
  2296. No release notes.
  2297. v1.2.9 (2014-10-01)
  2298. ===================
  2299. No release notes.
  2300. v1.2.8 (2014-09-02)
  2301. ===================
  2302. No release notes.
  2303. v1.2.7 (2014-08-02)
  2304. ===================
  2305. No release notes.
  2306. v1.2.6 (2014-07-02)
  2307. ===================
  2308. No release notes.
  2309. v1.2.5 (2014-06-02)
  2310. ===================
  2311. No release notes.
  2312. v1.2.4 (2014-05-04)
  2313. ===================
  2314. No release notes.
  2315. v1.2.3 (2014-04-01)
  2316. ===================
  2317. No release notes.
  2318. v1.2.2 (2014-03-02)
  2319. ===================
  2320. No release notes.
  2321. v1.2.1 (2014-01-16)
  2322. ===================
  2323. No release notes.
  2324. v1.2.0 (2013-12-02)
  2325. ===================
  2326. No release notes.
  2327. v1.1.4 (2013-11-04)
  2328. ===================
  2329. No release notes.
  2330. v1.1.3 (2013-10-01)
  2331. ===================
  2332. No release notes.
  2333. v1.1.2 (2013-09-02)
  2334. ===================
  2335. No release notes.
  2336. v1.1.1 (2013-07-30)
  2337. ===================
  2338. No release notes.
  2339. v1.1.0 (2013-07-01)
  2340. ===================
  2341. No release notes.
  2342. v1.0.6 (2013-06-03)
  2343. ===================
  2344. No release notes.
  2345. v1.0.5 (2013-05-02)
  2346. ===================
  2347. No release notes.
  2348. v1.0.4 (2013-04-01)
  2349. ===================
  2350. No release notes.
  2351. v1.0.3 (2013-03-05)
  2352. ===================
  2353. No release notes.
  2354. v1.0.2 (2013-01-30)
  2355. ===================
  2356. No release notes.
  2357. v1.0.1 (2012-12-17)
  2358. ===================
  2359. No release notes.
  2360. v1.0.0 (2012-11-02)
  2361. ===================
  2362. No release notes.
  2363. v0.10.2 (2012-09-24)
  2364. ====================
  2365. No release notes.
  2366. v0.10.1 (2012-08-31)
  2367. ====================
  2368. No release notes.
  2369. v0.10.0 (2012-08-29)
  2370. ====================
  2371. No release notes.
  2372. v0.9.13 (2012-08-02)
  2373. ====================
  2374. No release notes.
  2375. v0.9.12 (2012-05-14)
  2376. ====================
  2377. No release notes.
  2378. v0.9.11 (2012-04-03)
  2379. ====================
  2380. No release notes.
  2381. v0.9.10 (2012-02-13)
  2382. ====================
  2383. No release notes.
  2384. v0.9.9 (2012-01-07)
  2385. ===================
  2386. No release notes.
  2387. v0.9.8 (2011-12-08)
  2388. ===================
  2389. No release notes.
  2390. v0.9.7 (2011-11-08)
  2391. ===================
  2392. No release notes.
  2393. v0.9.6 (2011-09-22)
  2394. ===================
  2395. No release notes.
  2396. v0.9.5 (2011-09-20)
  2397. ===================
  2398. No release notes.
  2399. v0.9.4 (2011-08-03)
  2400. ===================
  2401. No release notes.
  2402. v0.9.3 (2011-07-04)
  2403. ===================
  2404. No release notes.
  2405. v0.9.2 (2011-06-06)
  2406. ===================
  2407. No release notes.
  2408. v0.9.1 (2011-05-05)
  2409. ===================
  2410. No release notes.
  2411. v0.9.0 (2011-04-04)
  2412. ===================
  2413. No release notes.
  2414. v0.8.8 (2011-02-17)
  2415. ===================
  2416. No release notes.
  2417. v0.8.7 (2011-01-04)
  2418. ===================
  2419. No release notes.
  2420. v0.8.6 (2010-11-30)
  2421. ===================
  2422. No release notes.
  2423. v0.8.5 (2010-10-29)
  2424. ===================
  2425. No release notes.
  2426. v0.8.4 (2010-09-10)
  2427. ===================
  2428. No release notes.
  2429. v0.8.3 (2010-08-04)
  2430. ===================
  2431. No release notes.
  2432. v0.8.2 (2010-07-05)
  2433. ===================
  2434. No release notes.
  2435. v0.8.1 (2010-04-30)
  2436. ===================
  2437. No release notes.
  2438. v0.8.0 (2010-04-12)
  2439. ===================
  2440. No release notes.
  2441. v0.7.7 (2010-03-05)
  2442. ===================
  2443. No release notes.
  2444. v0.7.6 (2010-02-03)
  2445. ===================
  2446. No release notes.
  2447. v0.7.5 (2009-12-23)
  2448. ===================
  2449. No release notes.
  2450. v0.7.4 (2009-11-20)
  2451. ===================
  2452. No release notes.
  2453. v0.7.3 (2009-11-20)
  2454. ===================
  2455. No release notes.
  2456. v0.7.2 (2009-10-14)
  2457. ===================
  2458. No release notes.
  2459. v0.7.1 (2009-09-15)
  2460. ===================
  2461. No release notes.
  2462. v0.7.0 (2009-08-05)
  2463. ===================
  2464. No release notes.
  2465. v0.6.5 (2009-07-03)
  2466. ===================
  2467. No release notes.
  2468. v0.6.4 (2009-05-29)
  2469. ===================
  2470. No release notes.
  2471. v0.6.3 (2009-04-24)
  2472. ===================
  2473. No release notes.
  2474. v0.6.2 (2009-04-03)
  2475. ===================
  2476. No release notes.
  2477. v0.6.1 (2009-03-03)
  2478. ===================
  2479. No release notes.
  2480. v0.6.0 (2009-01-31)
  2481. ===================
  2482. No release notes.
  2483. v0.5.1 (2008-12-04)
  2484. ===================
  2485. No release notes.
  2486. v0.5.0 (2008-11-25)
  2487. ===================
  2488. No release notes.
  2489. v0.4.6 (2008-09-23)
  2490. ===================
  2491. No release notes.
  2492. v0.4.5 (2008-09-08)
  2493. ===================
  2494. No release notes.
  2495. v0.4.4 (2008-06-25)
  2496. ===================
  2497. No release notes.
  2498. v0.4.3 (2008-06-12)
  2499. ===================
  2500. No release notes.
  2501. v0.4.2 (2008-04-08)
  2502. ===================
  2503. No release notes.
  2504. v0.4.1 (2008-03-03)
  2505. ===================
  2506. No release notes.
  2507. v0.4.0 (2007-12-18)
  2508. ===================
  2509. No release notes.
  2510. v0.3.3 (2007-09-30)
  2511. ===================
  2512. No release notes.
  2513. v0.3.2 (2007-08-21)
  2514. ===================
  2515. No release notes.
  2516. v0.3.1 (2007-07-24)
  2517. ===================
  2518. No release notes.
  2519. v0.3.0 (2007-07-09)
  2520. ===================
  2521. No release notes.
  2522. v0.2.3 (2007-06-08)
  2523. ===================
  2524. No release notes.
  2525. v0.2.2 (2007-04-17)
  2526. ===================
  2527. No release notes.
  2528. v0.2.1 (2007-03-16)
  2529. ===================
  2530. No release notes.
  2531. v0.2.0 (2007-02-14)
  2532. ===================
  2533. No release notes.
  2534. v0.1.11 (2007-01-22)
  2535. ====================
  2536. No release notes.
  2537. v0.1.10 (2006-12-20)
  2538. ====================
  2539. No release notes.
  2540. v0.1.9 (2006-11-29)
  2541. ===================
  2542. No release notes.
  2543. v0.1.8 (2006-10-16)
  2544. ===================
  2545. No release notes.
  2546. v0.1.7 (2006-09-29)
  2547. ===================
  2548. No release notes.
  2549. v0.1.6 (2006-09-22)
  2550. ===================
  2551. No release notes.
  2552. v0.1.5 (2006-09-05)
  2553. ===================
  2554. No release notes.
  2555. v0.1.4 (2006-08-16)
  2556. ===================
  2557. No release notes.
  2558. v0.1.3 (2006-07-11)
  2559. ===================
  2560. No release notes.
  2561. v0.1.2 (2006-07-03)
  2562. ===================
  2563. No release notes.
  2564. v0.1.1 (2006-06-21)
  2565. ===================
  2566. No release notes.
  2567. v0.1.0 (2006-04-10)
  2568. ===================
  2569. No release notes.
  2570. v0.0.6 (2006-02-28)
  2571. ===================
  2572. No release notes.
  2573. v0.0.5 (2006-02-23)
  2574. ===================
  2575. No release notes.
  2576. v0.0.4 (2006-02-10)
  2577. ===================
  2578. No release notes.
  2579. v0.0.3 (2006-02-09)
  2580. ===================
  2581. No release notes.
  2582. v0.0.2 (2006-01-29)
  2583. ===================
  2584. No release notes.
  2585. v0.0.1 (2005-12-19)
  2586. ===================
  2587. No release notes.
  2588. .. _git log: https://gitlab.com/libvirt/libvirt/-/commits/master