Hi Slavka,
This ISO is just the iPXE template because we deploy our VM automatically.
Since we deploy Windows and Linux i have to upload it twice? Once categorized
with Linux, the other time with Windows?
But since i want to have the same behaviour as with our old cloudstack, which
is
Hi Udo,
I saw where is the problem, the OS type of your ISO is "Other (32 bit)" on
which CloudStack sets "ide" for bus.
'sata' is set on Windows OS types;
'virtio' on these - Ubuntu, Fedora ,CentOS,Red Hat Enterprise Linux,Debian
GNU/Linux,FreeBSD,Oracle,Other PV;
'scsi' on "Other PV
Hi Slavka,
Deployment is done via WebUI. In this case i choose the target host
(since only this one has debug enabled), then choose service, disk and
network offering, activate advanced boot options and check UEFI Legacy.
After setting the name the vm is started.
The XML of the VM is
Hi Udo,
Could you please share more information about the deployment of a VM?
Are you creating a new instance from ISO or a template? Also, can you set
the DEBUG level at the agent, and is it possible to share the XML that
CloudStack sends to libvirt (it's in the
Hi guys,
I played around with cloudstack 4.15 and UEFI boot until someone here
pointed me to a PR which fixes the problem with the missing q35 chipset.
Thats the reason why I just installed the 4.15.1 SNAPSHOT.
Now I get the following problem:
Unable to start VM on Host... due to
