Re: Maximum size of ROOTDISK

[小林 美佳子]

Hi. Thanks everyone for your answers.

The hypervisor uses VMware.
I understand that there is a limit to the hypervisor; are you saying that 
CloudStack does not have an upper limit? (Is it possible to create a ROOT disk 
with the hypervisor's maximum size?)

Also, if you find any code to support this, please let me know.

On 2022/01/06 15:48, Vivek Kumar wrote:

It depends on your hypvervisor limit, I.e XenServer supports 2TB Max, so it 
won’t any sense if you create 3 TB disk offering. So check you backend 
hypervisor limit and test.

Vivek Kumar
Sr. Manager - Cloud & DevOps
IndiQus Technologies
24*7  O +91 11 4055 1411  |   M +91 7503460090
www.indiqus.com



On 06-Jan-2022, at 7:25 AM, 小林 美佳子  wrote:


Hi.

I am currently using CloudStack 4.10, and I am trying to build a new CloudStack 
4.14.

The GrobalConfig "root.disk.size.max" that existed in CloudStack4.10 has been 
removed from CloudStack4.14.
In CloudStack 4.14, what determines the maximum size of the ROOTDISK? Is it 
built into the code? If so, what is the maximum size?

Re: [!!Mass Mail]Re: Maximum size of ROOTDISK

[小林 美佳子]

Hi. Thanks everyone for your answers.

The hypervisor uses VMware.
I understand that there is a limit to the hypervisor; are you saying that 
CloudStack does not have an upper limit? (Is it possible to create a ROOT disk 
with the hypervisor's maximum size?)

On 2022/01/06 16:08, Дикевич Евгений Александрович wrote:

Hi. This is not entirely true. If you use standart LVM over iSCSI/FC max disk 
size is 2 TB but if you use GFS2 SR you can create 16 TB disk:)

-Original Message-
From: Vivek Kumar [mailto:vivek.ku...@indiqus.com.INVALID]
Sent: Thursday, January 6, 2022 9:48 AM
To: users@cloudstack.apache.org
Subject: [!!Mass Mail]Re: Maximum size of ROOTDISK

It depends on your hypvervisor limit, I.e XenServer supports 2TB Max, so it 
won’t any sense if you create 3 TB disk offering. So check you backend 
hypervisor limit and test.

Vivek Kumar
Sr. Manager - Cloud & DevOps
IndiQus Technologies
24*7  O +91 11 4055 1411  |   M +91 7503460090
www.indiqus.com



On 06-Jan-2022, at 7:25 AM, 小林 美佳子  wrote:


Hi.

I am currently using CloudStack 4.10, and I am trying to build a new CloudStack 
4.14.

The GrobalConfig "root.disk.size.max" that existed in CloudStack4.10 has been 
removed from CloudStack4.14.
In CloudStack 4.14, what determines the maximum size of the ROOTDISK? Is it 
built into the code? If so, what is the maximum size?

RE: [!!Mass Mail]Re: Maximum size of ROOTDISK

[Дикевич Евгений Александрович]

Hi. This is not entirely true. If you use standart LVM over iSCSI/FC max disk 
size is 2 TB but if you use GFS2 SR you can create 16 TB disk:)

-Original Message-
From: Vivek Kumar [mailto:vivek.ku...@indiqus.com.INVALID] 
Sent: Thursday, January 6, 2022 9:48 AM
To: users@cloudstack.apache.org
Subject: [!!Mass Mail]Re: Maximum size of ROOTDISK

It depends on your hypvervisor limit, I.e XenServer supports 2TB Max, so it 
won’t any sense if you create 3 TB disk offering. So check you backend 
hypervisor limit and test. 

Vivek Kumar
Sr. Manager - Cloud & DevOps 
IndiQus Technologies
24*7  O +91 11 4055 1411  |   M +91 7503460090 
www.indiqus.com


> On 06-Jan-2022, at 7:25 AM, 小林 美佳子  wrote:
> 
> 
> Hi.
> 
> I am currently using CloudStack 4.10, and I am trying to build a new 
> CloudStack 4.14.
> 
> The GrobalConfig "root.disk.size.max" that existed in CloudStack4.10 has been 
> removed from CloudStack4.14.
> In CloudStack 4.14, what determines the maximum size of the ROOTDISK? Is it 
> built into the code? If so, what is the maximum size?


-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.

Re: Maximum size of ROOTDISK

[Vivek Kumar]

It depends on your hypvervisor limit, I.e XenServer supports 2TB Max, so it 
won’t any sense if you create 3 TB disk offering. So check you backend 
hypervisor limit and test. 

Vivek Kumar
Sr. Manager - Cloud & DevOps 
IndiQus Technologies
24*7  O +91 11 4055 1411  |   M +91 7503460090 
www.indiqus.com


> On 06-Jan-2022, at 7:25 AM, 小林 美佳子  wrote:
> 
> 
> Hi.
> 
> I am currently using CloudStack 4.10, and I am trying to build a new 
> CloudStack 4.14.
> 
> The GrobalConfig "root.disk.size.max" that existed in CloudStack4.10 has been 
> removed from CloudStack4.14.
> In CloudStack 4.14, what determines the maximum size of the ROOTDISK? Is it 
> built into the code? If so, what is the maximum size?


-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.

Maximum size of ROOTDISK

[小林 美佳子]

Hi.

I am currently using CloudStack 4.10, and I am trying to build a new CloudStack 
4.14.

The GrobalConfig "root.disk.size.max" that existed in CloudStack4.10 has been 
removed from CloudStack4.14.
In CloudStack 4.14, what determines the maximum size of the ROOTDISK? Is it 
built into the code? If so, what is the maximum size?

Re: Public IP is stucked in state "released" after usage for static nat

[vas...@gmx.de]

@ Wei

As suggested i wanted to trie to update the network / tier to an offering
with userdata.
Sadly i don't find a way to update the serviceoffering for an existing vpc
in the gui. Updateing the serviceoffering for the network wasn't
successfull as well. Got the error that the serviceprovider (the existing
VPC) doesn't support service user data. Therefore i couldn't update the
network as well.
So this seems to be a dead-lock.

Regards,
Chris

Am Di., 4. Jan. 2022 um 16:41 Uhr schrieb vas...@gmx.de :

> Hi Wei,
>
> Will have to think that through as I am not sure if I could revert back an
> service offering without Service User data. Also do you guess  It could be
> sufficent to only upgrade the effected network (as the error is pointing at
> the network id)?
> Why not using userdata... Well short: not needed in the current usecase of
> the VPC as it is quiet static in regards of deploying vm's.
> Also I have to argue such decisions with our compliance team which
> basically comes to: If not needed then disable it. Especially in Our
> CUrrent usecase.
> As the GUI as well as the docs didn't suggested the actual need for this
> service we are not deploying it.
>
>
> Wei ZHOU  schrieb am Di., 4. Jan. 2022, 14:41:
>
>> Hi Chris,
>>
>> You can try to update the network/vpc tier to an offering with Userdata
>> and then disable static nat.
>> May I ask why you decided not to use Userdata ?
>>
>> -Wei
>>
>>
>>
>>
>> On Tue, 4 Jan 2022 at 14:35, vas...@gmx.de  wrote:
>>
>>> As i will need to fix this - i guess somewhat during the reset of the
>>> week
>>> are there any ideas on how to "remove" this from CS? (BackUP Jobs will be
>>> started for DB and i wouldn't have the chance to perform a binarylog
>>> rollback / recovery)
>>>
>>> The "clean" way i guess would be a DB Rollback to a point prior to
>>> enableing static NAT.
>>> Taking a look into the DB itself, i only found one entry in the table
>>> "user_ip_address": Entry with rulestate / state "Releasing" for the ip is
>>> present. one_to_one_nat = 1 and the dnat_vmip is present.
>>> Does anyone has some experience on cleaning this up directly in db?
>>>
>>> Regards,
>>> Chris
>>>
>>> Am Di., 4. Jan. 2022 um 13:16 Uhr schrieb vas...@gmx.de :
>>>
>>> > Hi Wei,
>>> >
>>> > of course! :-)
>>> >
>>> > https://github.com/apache/cloudstack/issues/5824
>>> >
>>> > Regards,
>>> > Chris
>>> >
>>> > Am Di., 4. Jan. 2022 um 11:32 Uhr schrieb Wei ZHOU <
>>> ustcweiz...@gmail.com
>>> > >:
>>> >
>>> >> Hi Chris,
>>> >>
>>> >> This seems to be a bug. Can you file an issue on
>>> >> https://github.com/apache/cloudstack/issues ?
>>> >>
>>> >> -Wei
>>> >>
>>> >> On Tue, 4 Jan 2022 at 11:16, vas...@gmx.de  wrote:
>>> >>
>>> >>> Hi Dan,
>>> >>>
>>> >>> Sorry for the misunderstanding.
>>> >>> The VPC was created using a "custome" service offering which is not
>>> >>> using /
>>> >>> offering "service user data" . The same goes for the NW-Offering
>>> which is
>>> >>> used for creation of the tiers. There is no service user data in this
>>> >>> VPC.
>>> >>>
>>> >>> The default / out-of-the-box VPC offering has the service "user data"
>>> >>> included. Same goes for the default nework offering for VPC Tiers. So
>>> >>> this
>>> >>> service should be supported at all from my understanding.
>>> >>> That's why this error seems a bit "bogus" to me. I was understanding
>>> >>> somethin like "static nat can't be disabled due to missing service
>>> "user
>>> >>> data" for the network".
>>> >>>
>>> >>> Deleting and building the whole thing from scratch will be the last
>>> >>> resort,
>>> >>> yes. Even taking the risk that it won't be deletable as the allocated
>>> >>> ressourcces can't be released properly at the moment, e.g. using the
>>> >>> cloudstack.api.command.user.nat.DisableStaticNatCmd.
>>> >>> Seems like i found a configuration which doesn't work well but can be
>>> >>> created via the GUI. Even if i don't understand the connection
>>> between
>>> >>> the
>>> >>> service user data and the service stativ nat.
>>> >>>
>>> >>>
>>> >>>
>>> >>> Daan Hoogland  schrieb am Di., 4. Jan.
>>> 2022,
>>> >>> 09:21:
>>> >>>
>>> >>> > Chris, it looks to me like you should delete the VPC and then
>>> check if
>>> >>> all
>>> >>> > IPs are available before creating a new one.
>>> >>> >
>>> >>> > As for the user data service, the message already says that user
>>> data
>>> >>> is
>>> >>> > not supported, so why create another offering?
>>> >>> >
>>> >>> > On Tue, Jan 4, 2022 at 2:50 AM vas...@gmx.de 
>>> wrote:
>>> >>> >
>>> >>> >> hi everyone,
>>> >>> >>
>>> >>> >> sadly i am encountering some problems in my CS 4.16 set-up.
>>> >>> >>
>>> >>> >> today i wanted to take a look into static-nat for the routers of
>>> my
>>> >>> vpc.
>>> >>> >> Sadly i missed, that the VM i wanted to assaign to the static
>>> public
>>> >>> ip
>>> >>> >> had
>>> >>> >> was already targeted by an port forwarding.
>>> >>> >> As you can imagine i got an error that static can't be applied for
>>> >>> this VM
>>> >>> >> / 

Re: UEFI on KVM silently becomes BIOS mode

[vas...@gmx.de]

Hi Piotr,

sadly i don't have a solution for your problem at the moment.
My suggestion is at least to open a issue at github. The last issues
mentioning anything UEFI-related are nearly 18 months old.

Am Mi., 5. Jan. 2022 um 11:08 Uhr schrieb Piotr Pisz :

> Hello,
>
>
>
> Does anyone know a workaround for this problem?
>
> This error prevents any VM from booting from UEFI, this is a serious
> problem.
>
> I have a lot of VMs converted from vSphere, all from UEFI, I can't imagine
> that none of them will be bootable! :-(
>
>
>
> Regards,
>
> Piotr
>
>
>
>
>
> From: Pieter Harvey 
> Sent: Monday, December 20, 2021 10:06 AM
> To: users@cloudstack.apache.org
> Subject: Re: UEFI on KVM silently becomes BIOS mode
>
>
>
> Got it, okay will continue other testing while 4.16.1 is in the works.
>
>
>
> Thank you
>
>
>
> On 20 Dec 2021, at 8:13, Piotr Pisz  pi...@piszki.pl> > wrote:
>
>
>
>
>
> Hey,
>
>
>
> I just wanted to write this, Pieter you are right, in 4.16 it doesn't work
> properly, old UEFI VMs work as is but new ones don't start up properly.
>
>
>
> Regards,
>
> Piotr
>
>
>
>
>
> -Original Message-
>
> From: Slavka Peleva  slav...@storpool.com.INVALID> >
>
> Sent: Monday, December 20, 2021 9:03 AM
>
> To: users@cloudstack.apache.org 
>
> Subject: Re: UEFI on KVM silently becomes BIOS mode
>
>
>
> Hi Pieter,
>
>
>
> This is a known issue in 4.16 with the missing loader tag in the XML
> definition. There is a fix that will get in the 4.16.1.0 release -
>
> https://github.com/apache/cloudstack/pull/5692
>
>
>
> Best regards,
>
> Slavka
>
> 
>
>
>
> On Sat, Dec 18, 2021 at 3:15 PM Piotr Pisz  pi...@piszki.pl> > wrote:
>
>
>
> Hi Pieter,
>
>
>
>
>
>
>
> I run it in CentOS 8:
>
>
>
>
>
>
>
> Cloudstack:
>
>
>
>
>
>
>
> i-4-46-VM
>
>
>
> e9c33f2d-7237-4cc1-b466-5d85a04ed549
>
>
>
> Other PV Virtio-SCSI (64-bit)
>
>
>
> 
> policy='require' name='vmx'/>
> name='vme'/>
> type='smbios'>
>
>
>
> 
>
>
>
> Apache Software Foundation
>
>
>
> CloudStack KVM Hypervisor
>
>
>
> e9c33f2d-7237-4cc1-b466-5d85a04ed549
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
>
>
> hvm
>
>
>
> 
> template='/usr/share/edk2/ovmf/OVMF_VARS.fd'>/var/lib/libvirt/qemu/nvr
>
> am/e9c33f2d-7237-4cc1-b466-5d85a04ed549.fd
> dev='cdrom'/>
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
>
>
>
>
>
>
> Virsh dump:
>
>
>
>
>
>
>
> 
>
>
>
> 
>
>
>
> Apache Software Foundation
>
>
>
> CloudStack KVM Hypervisor
>
>
>
> e9c33f2d-7237-4cc1-b466-5d85a04ed549
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
>
>
> hvm
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
>
>
> 
>
>
>
>
>
>
>
> Regards,
>
>
>
> Piotr
>
>
>
>
>
>
>
>
>
>
>
> From: Pieter Harvey  pieter.har...@icloud.com.INVALID> >
>
> Sent: Friday, December 17, 2021 5:46 PM
>
> To: Pieter Harvey  pieter.har...@icloud.com> >
>
> Cc: "users@cloudstack.apache.org  " <
> users@cloudstack.apache.org  >
>
> Subject: Re: UEFI on KVM silently becomes BIOS mode
>
>
>
>
>
>
>
> Hi Piotr,
>
>
>
>
>
>
>
> Is there any way to get this debug info (or xml dump) from CloudStack,
>
> what it is creating versus what ends up in virsh?
>
>
>
>
>
>
>
> I think I have configured everything correctly
>
>
>
> 1. cloudstack uefi enabled in database for host (host.uefi.enable)
>
>
>
> 2. host agent has uefi.properties with all paths configured (snippet
>
> below based Ubuntu 20.04.3)
>
>
>
> 3. instance is configured for UEFI (tried both legacy and secure boot)
>
>
>
>
>
>
>
> uefi.properties
>
>
>
> ==
>
>
>
> guest.nvram.template.secure=/usr/share/OVMF/OVMF_VARS.fd
>
>
>
> guest.nvram.template.legacy=/usr/share/OVMF/OVMF_VARS.fd
>
>
>
> guest.loader.secure=/usr/share/OVMF/OVMF_CODE.secboot.fd
>
>
>
> guest.loader.legacy=/usr/share/OVMF/OVMF_CODE.fd
>
>
>
> guest.nvram.path=/var/lib/libvirt/qemu/nvram/
>
>
>
>
>
>
>
> sudo ls -lh /usr/share/OVMF/
>
>
>
> 
>
>
>
> -rw-r--r-- 1 root root 1.9M Sep 20 13:11 OVMF_CODE.fd
>
>
>
> lrwxrwxrwx 1 root root 20 Sep 20 13:11 OVMF_CODE.ms.fd ->
>
> OVMF_CODE.secboot.fd
>
>
>
> -rw-r--r-- 1 root root 1.9M Sep 20 13:11 OVMF_CODE.secboot.fd
>
>
>
> -rw-r--r-- 1 root root 128K Sep 20 13:11 OVMF_VARS.fd
>
>
>
> -rw-r--r-- 1 root root 128K Sep 20 13:11 OVMF_VARS.ms.fd
>
>
>
> -rw-r--r-- 1 root root 128K Sep 20 13:11 OVMF_VARS.snakeoil.fd
>
>
>
>
>
>
>
> syslog
>
>
>
> =
>
>
>
> java[47841]: INFO [kvm.resource.LibvirtComputingResource] (main:)
>
> (logid:) uefi.properties file found at
>
> /etc/cloudstack/agent/uefi.properties
>
>
>
> java[47841]: INFO [kvm.resource.LibvirtComputingResource] (main:)
>
> (logid:) guest.nvram.template.legacy = /usr/share/OVMF/OVMF_VARS.fd
>
>
>
> java[47841]: INFO [kvm.resource.LibvirtComputingResource] (main:)
>
> (logid:) guest.loader.legacy = /usr/share/OVMF/OVMF_CODE.fd
>
>
>
> java[47841]: INFO [kvm.resource.LibvirtComputingResource] (main:)
>
> (logid:) guest.nvram.template.secure = /usr/share/OVMF/OVMF_VARS.fd
>
>
>
> java[47841]: INFO [kv

Re: Cloudstack 4.16 - GUI unable to submit SSL

[Suresh Anaparti]

Hi,

You can check the certificate configuration process through API/cmk here: 
https://www.shapeblue.com/securing-cloudstack-4-11-with-https-tls/


Regards,
Suresh

On 05/01/22, 4:55 PM, "Hean Seng"  wrote:

Any body know how to use the API to upload this cert for console proxy,
Otherwise this  4.16 is not workable .  This function seems no
alternative to make it work


 

On Mon, Jan 3, 2022 at 4:08 PM Hean Seng  wrote:

> Is there anyway to manual update it before 4.16.1 release ,  otherwise the
> SSL cannot be install.
>
> On Mon, Jan 3, 2022 at 3:06 PM Suresh Anaparti <
> suresh.anapa...@shapeblue.com> wrote:
>
>> Good, thanks for the update Pearl!
>>
>>
>> Regards,
>> Suresh
>>
>> On 03/01/22, 12:31 PM, "Pearl d'Silva" 
>> wrote:
>>
>> Hi,
>>
>> This seems to be an issue in 4.16.0 but has been addressed with:
>> https://github.com/apache/cloudstack/pull/5682/ and should be available
>> in 4.16.1.
>>
>> Thanks,
>> Pearl
>>
>> [
>> 
https://opengraph.githubassets.com/a85d63087cbc026a03525dcc5d491e900913e0ad6e2b09a6dd8eb27f392c60a8/apache/cloudstack/pull/5682
>> ]
>> UI : Fix SSL certificate submit button not working by dhslove · Pull
>> Request #5682 · apache/cloudstack<
>> https://github.com/apache/cloudstack/pull/5682/>
>> Description This PR fixes an issue where clicking the Submit button
>> in the SSL Certificates dialog in the Infrastructure Summary UI did not
>> work. Types of changes Breaking change (fix o...
>> github.com
>>
>>
>> 
>> From: Deepak Kumar 
>> Sent: Monday, January 3, 2022 12:23 PM
>> To: users@cloudstack.apache.org 
>> Subject: Re: Cloudstack 4.16 - GUI unable to submit SSL
>>
>> Hi  Hean Seng,
>>
>> I am facing the same issue.
>>
>> Thanks & Regards,
>> Deepak Kumar
>> IndiQus Global Technical Support
>> www.indiqus.com
>>
>>
>>
>>
>>
>>
>>
>>
>> On Sun, Jan 2, 2022 at 11:55 PM Hean Seng  wrote:
>>
>> > Hi
>> >
>> > I am using Cloudstack 4.16 , Ubuntu 20 for Mgmt server.
>> >
>> > Infrastructure ->. Summary -> SSL Certification
>> >
>> > Entering all the SSL detail, and click submit ,  but the click has
>> no
>> > responding .
>> > Clecking the MGMT log, and nothing seems processed .
>> >
>> > Tried on both  Chrome, Safari and same issue .
>> > Tried the same SSL to  Cloudstack 4.15 , and it has no issue
>> submitting the
>> > SSL
>> >
>> > Anybody facing the same issue ?
>> >
>> >
>> > --
>> > Regards,
>> > Hean Seng
>> >
>>
>> --
>> This message is intended only for the use of the individual or entity
>> to
>> which it is addressed and may contain confidential and/or privileged
>> information. If you are not the intended recipient, please delete the
>> original message and any copy of it from your computer system. You 
are
>> hereby notified that any dissemination, distribution or copying of
>> this
>> communication is strictly prohibited unless proper authorization has
>> been
>> obtained for such action. If you have received this communication in
>> error,
>> please notify the sender immediately. Although IndiQus attempts to
>> sweep
>> e-mail and attachments for viruses, it does not guarantee that both
>> are
>> virus-free and accepts no liability for any damage sustained as a
>> result of
>> viruses.
>>
>>
>
> --
> Regards,
> Hean Seng
>


-- 
Regards,
Hean Seng

Re: Cloudstack 4.16 - GUI unable to submit SSL

[Hean Seng]

Any body know how to use the API to upload this cert for console proxy,
Otherwise this  4.16 is not workable .  This function seems no
alternative to make it work

On Mon, Jan 3, 2022 at 4:08 PM Hean Seng  wrote:

> Is there anyway to manual update it before 4.16.1 release ,  otherwise the
> SSL cannot be install.
>
> On Mon, Jan 3, 2022 at 3:06 PM Suresh Anaparti <
> suresh.anapa...@shapeblue.com> wrote:
>
>> Good, thanks for the update Pearl!
>>
>>
>> Regards,
>> Suresh
>>
>> On 03/01/22, 12:31 PM, "Pearl d'Silva" 
>> wrote:
>>
>> Hi,
>>
>> This seems to be an issue in 4.16.0 but has been addressed with:
>> https://github.com/apache/cloudstack/pull/5682/ and should be available
>> in 4.16.1.
>>
>> Thanks,
>> Pearl
>>
>> [
>> https://opengraph.githubassets.com/a85d63087cbc026a03525dcc5d491e900913e0ad6e2b09a6dd8eb27f392c60a8/apache/cloudstack/pull/5682
>> ]
>> UI : Fix SSL certificate submit button not working by dhslove · Pull
>> Request #5682 · apache/cloudstack<
>> https://github.com/apache/cloudstack/pull/5682/>
>> Description This PR fixes an issue where clicking the Submit button
>> in the SSL Certificates dialog in the Infrastructure Summary UI did not
>> work. Types of changes Breaking change (fix o...
>> github.com
>>
>>
>> 
>> From: Deepak Kumar 
>> Sent: Monday, January 3, 2022 12:23 PM
>> To: users@cloudstack.apache.org 
>> Subject: Re: Cloudstack 4.16 - GUI unable to submit SSL
>>
>> Hi  Hean Seng,
>>
>> I am facing the same issue.
>>
>> Thanks & Regards,
>> Deepak Kumar
>> IndiQus Global Technical Support
>> www.indiqus.com
>>
>>
>>
>>
>>
>>
>>
>>
>> On Sun, Jan 2, 2022 at 11:55 PM Hean Seng  wrote:
>>
>> > Hi
>> >
>> > I am using Cloudstack 4.16 , Ubuntu 20 for Mgmt server.
>> >
>> > Infrastructure ->. Summary -> SSL Certification
>> >
>> > Entering all the SSL detail, and click submit ,  but the click has
>> no
>> > responding .
>> > Clecking the MGMT log, and nothing seems processed .
>> >
>> > Tried on both  Chrome, Safari and same issue .
>> > Tried the same SSL to  Cloudstack 4.15 , and it has no issue
>> submitting the
>> > SSL
>> >
>> > Anybody facing the same issue ?
>> >
>> >
>> > --
>> > Regards,
>> > Hean Seng
>> >
>>
>> --
>> This message is intended only for the use of the individual or entity
>> to
>> which it is addressed and may contain confidential and/or privileged
>> information. If you are not the intended recipient, please delete the
>> original message and any copy of it from your computer system. You are
>> hereby notified that any dissemination, distribution or copying of
>> this
>> communication is strictly prohibited unless proper authorization has
>> been
>> obtained for such action. If you have received this communication in
>> error,
>> please notify the sender immediately. Although IndiQus attempts to
>> sweep
>> e-mail and attachments for viruses, it does not guarantee that both
>> are
>> virus-free and accepts no liability for any damage sustained as a
>> result of
>> viruses.
>>
>>
>
> --
> Regards,
> Hean Seng
>


-- 
Regards,
Hean Seng

RE: UEFI on KVM silently becomes BIOS mode

[Piotr Pisz]

Hello,

 

Does anyone know a workaround for this problem? 

This error prevents any VM from booting from UEFI, this is a serious problem. 

I have a lot of VMs converted from vSphere, all from UEFI, I can't imagine that 
none of them will be bootable! :-(

 

Regards,

Piotr

 

 

From: Pieter Harvey  
Sent: Monday, December 20, 2021 10:06 AM
To: users@cloudstack.apache.org
Subject: Re: UEFI on KVM silently becomes BIOS mode

 

Got it, okay will continue other testing while 4.16.1 is in the works.

 

Thank you

 

On 20 Dec 2021, at 8:13, Piotr Pisz mailto:pi...@piszki.pl> > 
wrote:

 

 

Hey,

 

I just wanted to write this, Pieter you are right, in 4.16 it doesn't work 
properly, old UEFI VMs work as is but new ones don't start up properly.

 

Regards,

Piotr

 

 

-Original Message-

From: Slavka Peleva mailto:slav...@storpool.com.INVALID> > 

Sent: Monday, December 20, 2021 9:03 AM

To: users@cloudstack.apache.org  

Subject: Re: UEFI on KVM silently becomes BIOS mode

 

Hi Pieter,

 

This is a known issue in 4.16 with the missing loader tag in the XML 
definition. There is a fix that will get in the 4.16.1.0 release -

https://github.com/apache/cloudstack/pull/5692

 

Best regards,

Slavka



 

On Sat, Dec 18, 2021 at 3:15 PM Piotr Pisz mailto:pi...@piszki.pl> > wrote:

 

Hi Pieter,

 

 

 

I run it in CentOS 8:

 

 

 

Cloudstack:

 

 

 

i-4-46-VM

 

e9c33f2d-7237-4cc1-b466-5d85a04ed549

 

Other PV Virtio-SCSI (64-bit)

 



 



 

Apache Software Foundation

 

CloudStack KVM Hypervisor

 

e9c33f2d-7237-4cc1-b466-5d85a04ed549

 



 



 



 

hvm

 

/var/lib/libvirt/qemu/nvr

am/e9c33f2d-7237-4cc1-b466-5d85a04ed549.fd

 



 



 



 

 

 

Virsh dump:

 

 

 



 



 

Apache Software Foundation

 

CloudStack KVM Hypervisor

 

e9c33f2d-7237-4cc1-b466-5d85a04ed549

 



 



 



 

hvm

 



 



 



 



 

 

 

Regards,

 

Piotr

 

 

 

 

 

From: Pieter Harvey mailto:pieter.har...@icloud.com.INVALID> >

Sent: Friday, December 17, 2021 5:46 PM

To: Pieter Harvey mailto:pieter.har...@icloud.com> >

Cc: "users@cloudstack.apache.org  " 
mailto:users@cloudstack.apache.org> >

Subject: Re: UEFI on KVM silently becomes BIOS mode

 

 

 

Hi Piotr,

 

 

 

Is there any way to get this debug info (or xml dump) from CloudStack, 

what it is creating versus what ends up in virsh?

 

 

 

I think I have configured everything correctly

 

1. cloudstack uefi enabled in database for host (host.uefi.enable)

 

2. host agent has uefi.properties with all paths configured (snippet 

below based Ubuntu 20.04.3)

 

3. instance is configured for UEFI (tried both legacy and secure boot)

 

 

 

uefi.properties

 

==

 

guest.nvram.template.secure=/usr/share/OVMF/OVMF_VARS.fd

 

guest.nvram.template.legacy=/usr/share/OVMF/OVMF_VARS.fd

 

guest.loader.secure=/usr/share/OVMF/OVMF_CODE.secboot.fd

 

guest.loader.legacy=/usr/share/OVMF/OVMF_CODE.fd

 

guest.nvram.path=/var/lib/libvirt/qemu/nvram/

 

 

 

sudo ls -lh /usr/share/OVMF/

 



 

-rw-r--r-- 1 root root 1.9M Sep 20 13:11 OVMF_CODE.fd

 

lrwxrwxrwx 1 root root 20 Sep 20 13:11 OVMF_CODE.ms.fd ->

OVMF_CODE.secboot.fd

 

-rw-r--r-- 1 root root 1.9M Sep 20 13:11 OVMF_CODE.secboot.fd

 

-rw-r--r-- 1 root root 128K Sep 20 13:11 OVMF_VARS.fd

 

-rw-r--r-- 1 root root 128K Sep 20 13:11 OVMF_VARS.ms.fd

 

-rw-r--r-- 1 root root 128K Sep 20 13:11 OVMF_VARS.snakeoil.fd

 

 

 

syslog

 

=

 

java[47841]: INFO [kvm.resource.LibvirtComputingResource] (main:)

(logid:) uefi.properties file found at 

/etc/cloudstack/agent/uefi.properties

 

java[47841]: INFO [kvm.resource.LibvirtComputingResource] (main:)

(logid:) guest.nvram.template.legacy = /usr/share/OVMF/OVMF_VARS.fd

 

java[47841]: INFO [kvm.resource.LibvirtComputingResource] (main:)

(logid:) guest.loader.legacy = /usr/share/OVMF/OVMF_CODE.fd

 

java[47841]: INFO [kvm.resource.LibvirtComputingResource] (main:)

(logid:) guest.nvram.template.secure = /usr/share/OVMF/OVMF_VARS.fd

 

java[47841]: INFO [kvm.resource.LibvirtComputingResource] (main:)

(logid:) guest.loader.secure =/usr/share/OVMF/OVMF_CODE.secboot.fd

 

java[47841]: INFO [kvm.resource.LibvirtComputingResource] (main:)

(logid:) guest.nvram.path = /var/lib/libvirt/qemu/nvram/

 

 

 

 

 

-

 

Pieter

 

 

 

On 17 Dec 2021, at 16:15, Piotr Pisz mailto:pi...@piszki.pl> > > wrote:

 

 

 

 

 

Hi Pieter,

 

 

 

 

 

 

 

I have just checked, everything works as expected, maybe you have 

something wrongly configured, check according to this:

 

 

 

 

 

 

 

https://lab.piszki.pl/cloudstack-vm-with-vtpm-and-secure-boot-uefi/

 

 

 

 

 

 

 

Regards,

 

 

 

Piotr

 

 

 

 

 

 

 

 

 

 

 

From: Pieter Harvey mailto:pieter.har...@icloud.com.INVALID> > >

 

Sent: Friday, December 17, 2021 4:11 PM