[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Libvirt-announce] Release of libvirt-4.7.0



  I didn't do this this week-end, that gave time to Andrea to update the release
notes :-) it's now tagged in git and signed tarball and rpms are pushed to the
usual place:

   ftp://libvirt.org/libvirt/

I also pushed a release 4.7.0 for the python bindings but they are virtually equivalent
to 4.6.0 ones, you can find them at

   ftp://libvirt.org/libvirt/python/

 This seems a reasonably large release, many commits, not that many people were in
vacations last month ! The resulting is a balanced release with new features,
improvements, and obviously the usual amount of bug fixes !


New features:

- storage: add storage pool iscsi-direct
  Introduce a new storage pool backend that uses libiscsi instead of
  iscsiadm. It support basic pool operations: checkPool and refreshPool.

- Add support for MBA (Memory Bandwidth Allocation technology)
  Domain vCPU threads can now have allocated some parts of host memory
  bandwidth by using the memorytune element in cputune.

- qemu: Add support for RISC-V guests
  riscv32 and riscv64 guest architectures are now supported.

Improvements:

- qemu: Add ccw support for vhost-vsock
  Support the vhost-vsock-ccw device on S390.

- qemu: Make default machine type independent of QEMU
  We can't control whether or not QEMU will change its default machine
  type in the future, or whether downstream distributions will decide to
  compile out some machine types, so our only option to provide a
  predictable behavior is taking care of the default ourselves;
  management applications and users are encouraged to explicitly pick a
  machine type when creating new guests.

- apparmor: Various improvements
  Rules have been added to deal with a number of scenarios that didn't
  work correctly.

Bug fixes:

- esx: Truncate CPU model name
  Some CPU model names are too long to be stored into the corresponding
  property, and should be explicitly truncated to avoid unexpected
  behavior in users of the virNodeGetInfo() API such as virsh nodeinfo.

- utils: Remove arbitrary limit on socket_id/core_id
  Both values were assumed to be smaller than 4096, but in fact they are
  entirely hardware-dependent and there have been reports of machines
  presenting much bigger values, preventing libvirt from working
  correctly; all such limits have now been removed.


  Thanks everybody for your help with this release be it with code, bug reports,
patch reviews, documentation, ...

   Enjoy !

Daniel

-- 
Daniel Veillard      | Red Hat Developers Tools http://developer.redhat.com/
veillard redhat com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]