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 /dev/sdX naming for the root device, Windows is the way to go, correct? I will try it out. Thx for your help! But cloudstack has to be changed in order to get a vm created with UEFI boot and an other OS than the named ones. At least an error must be shown when using UEFI boot with a template categorized Other and deployed on KVM. Gruß Udo Müller > Am 01.06.2021 um 19:01 schrieb Slavka Peleva <[email protected]>: > > 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 Virtio-SCSI" OS types; > the rest gets 'ide' for bus > > Regards, > Slavka > >> On Tue, Jun 1, 2021 at 6:24 PM Udo Müller <[email protected]> wrote: >> >> 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 attached. >> >> There you see >> >> <target dev='hda' bus='ide'/> >> >> But the VM will work with sata instead of ide. I tested it by defining a >> VM via virt-manager and choosing sata for the bus type. >> >> See also: >> >> https://bugs.launchpad.net/nova/+bug/1831538 >> >> Regards Udo >> >> >>> Am 01.06.21 um 16:16 schrieb Slavka Peleva: >>> 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 >>> /var/log/cloudstack/agent/agent.log)? >>> >>> One more question did you update and the management with the 4.15.1.0 >>> version? >>> >>> Kind regards, >>> Slavka >>> >>>> On Tue, Jun 1, 2021 at 4:33 PM Udo Müller <[email protected]> wrote: >>> >>>> 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 Unsupported Configuration: IDE >>>> controllers >>>> are unsupported for this QEMU binary or machine type >>>> >>>> I am using cloudstack on CentOS 7.9 with >>>> >>>> # rpm -qa | egrep "(qemu|libvirtd|OVMF|cloudstack)" >>>> *cloudstack*-agent-4.15.1.0-SNAPSHOT.20210601.el7.x86_64 >>>> *qemu*-kvm-ev-2.12.0-44.1.el7_8.1.x86_64 >>>> ipxe-roms-*qemu*-20180825-3.git133f4c.el7.noarch >>>> libvirt-daemon-driver-*qemu*-4.5.0-36.el7.x86_64 >>>> *OVMF*-20180508-6.gitee3198e672e2.el7.noarch >>>> *qemu*-img-ev-2.12.0-44.1.el7_8.1.x86_64 >>>> *cloudstack*-common-4.15.1.0-SNAPSHOT.20210601.el7.x86_64 >>>> *qemu*-kvm-common-ev-2.12.0-44.1.el7_8.1.x86_64 >>>> >>>> 1) Is the PR regarding the q35 chipset already included in the SNAPSHOT? >>>> I guess yes, because with 4.15.0 and i440 chipset the VM could be >>>> created and was running. >>>> >>>> 2) What do I have to change inside my settings to switch from IDE to >>>> SCSI or SATA? >>>> >>>> Regards Udo >>>> >>
