+1 (binding) from me based on the testing I've done.
---
Nux
www.nux.ro
On 2022-09-07 13:50, Abhishek Kumar wrote:
Hi All,
I've created a 4.17.1.0 release, with the following artifacts up for a
vote:
Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.17.1.0-RC20220907T170
Hi,
Check that the templates were registered with the appropriate profiles
(ie of type CentOS7 etc), particularly if their storage and network
devices are Virtio ones.
You can do this with lspci on Linux - inside the VM - ethernet and
storage should present themselves as "virtio" or similar.
Hi All,
I've created a 4.17.1.0 release, with the following artifacts up for a vote:
Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.17.1.0-RC20220907T1706
Commit: cf815b051d2cd0e88fda40ab1690d7b173f68fdf
Source release (checksums and signatures are available at the same
lo
Hi, the qcow2 volumes may be thin, sparse, full. Maybe the fs is slow, so
while the image does cow allocations, the performance degrades? Try to make
a full qcow2 image by:
qemu-img create -o preallocation=full -f qcow2
And check again.
ср, 7 сент. 2022 г., 16:26 Mevludin Blazevic :
> Hi all,
Hi all,
some of our users have reported that after they uploaded QCOW2 templates
to our ACS environment and started a VM from the template, the VMs ran
very slow. In contrast, VMs installed directly in ACS using ISOs for
example are very fast. I wonder if something in the upload view was
misc
