Re: [D] template download failedfrom AWS s3 bucket [cloudstack]

2024-08-02 Thread via GitHub
GitHub user anjanahkarthic added a comment to the discussion: template download failedfrom AWS s3 bucket I used the public AWS S3 bucket link over HTTPS to download the template. After upgrading ACS to a newer version and live-patching the system VM, I encountered a certificate issue when att

Re: [D] PCI Slot changes for hot plugged devices after reboot/restart of VM [cloudstack]

2024-08-02 Thread via GitHub
GitHub user saikrm04 added a comment to the discussion: PCI Slot changes for hot plugged devices after reboot/restart of VM Hi @zap51 Please find the text file below, somehow text is not visible. sorry for inconvenience. GitHub link: https://github.com/apache/cloudstack/discussions/9479#disc

Re: [D] PCI Slot changes for hot plugged devices after reboot/restart of VM [cloudstack]

2024-08-02 Thread via GitHub
GitHub user saikrm04 deleted a comment on the discussion: PCI Slot changes for hot plugged devices after reboot/restart of VM FIRST NIC HOTADD NIC 1 NIC After R

Re: [D] PCI Slot changes for hot plugged devices after reboot/restart of VM [cloudstack]

2024-08-02 Thread via GitHub
GitHub user saikrm04 added a comment to the discussion: PCI Slot changes for hot plugged devices after reboot/restart of VM [NIC.odt](https://github.com/user-attachments/files/16471553/NIC.odt) GitHub link: https://github.com/apache/cloudstack/discussions/9479#discussioncomment-1022 ---

Re: [D] PCI Slot changes for hot plugged devices after reboot/restart of VM [cloudstack]

2024-08-02 Thread via GitHub
GitHub user saikrm04 added a comment to the discussion: PCI Slot changes for hot plugged devices after reboot/restart of VM FIRST NIC HOTADD NIC 1 NIC After Reb

Re: [D] PCI Slot changes for hot plugged devices after reboot/restart of VM [cloudstack]

2024-08-02 Thread via GitHub
GitHub user zap51 added a comment to the discussion: PCI Slot changes for hot plugged devices after reboot/restart of VM The text or images you pasted is not visible. GitHub link: https://github.com/apache/cloudstack/discussions/9479#discussioncomment-10224315 This is an automatically s

Re: [D] PCI Slot changes for hot plugged devices after reboot/restart of VM [cloudstack]

2024-08-02 Thread via GitHub
GitHub user saikrm04 added a comment to the discussion: PCI Slot changes for hot plugged devices after reboot/restart of VM Hi @zap51, Here is the dumpxml before and after reboot NIC Before Reboot FIRST NIC HOTADD NIC 1

Sharing of templates/ISOsDomains

2024-08-02 Thread Alex Dietrich
Hello All, When operating a domain with one or more sub-domains, I found that ISOs/Templates created at the parent domain which are not shared publicly are not available to the sub-domain. Where this becomes a challenge is in a scenario where you may want to create an instance in the parent dom

Re: Upgrade to 4.19.1.0 from 4.15.1 - Issues

2024-08-02 Thread Biswajit Banerjee
Yes , there are 23 KVM hosts ,  all has been upgraded . FYI we are still using Centos7.9 on all hosts . On 8/2/24 18:14, Wei ZHOU wrote: Have you upgraded all cloudstack-agent (if you use kvm) ? -Wei On Fri, Aug 2, 2024 at 2:33 PM Biswajit Banerjee wrote: After destroying the VM , it gets a

Re: Best steps to deploy a working KVM cluster with RHEL

2024-08-02 Thread Rohit Yadav
Except the way you configure Linux bridges, using nmcli, on EL9 more or less all steps apply as earlier EL distros. I've my old notes here - https://gist.github.com/rohityadavcloud/fc401a0fe8e8ea16b4b3a4e3d149ce0c#file-el9-or-rhel9-acs CloudStack-Ceph users have easily used 100-1000s of TB of s

Re: Upgrade to 4.19.1.0 from 4.15.1 - Issues

2024-08-02 Thread Wei ZHOU
Have you upgraded all cloudstack-agent (if you use kvm) ? -Wei On Fri, Aug 2, 2024 at 2:33 PM Biswajit Banerjee wrote: > > After destroying the VM , it gets automatically recreated . I presume > that is what is expected . > > Let me Know if any thing else is required . > > Also about " 'readyFo

Re: Upgrade to 4.19.1.0 from 4.15.1 - Issues

2024-08-02 Thread Biswajit Banerjee
After destroying the VM , it gets automatically recreated . I presume that is what is expected . Let me Know if any thing else is required . Also about  " 'readyForShutdown' either does not exist, is not available for user. Unable to proceed " Please guide me On 8/2/24 17:59, Biswajit B

Re: Upgrade to 4.19.1.0 from 4.15.1 - Issues

2024-08-02 Thread Biswajit Banerjee
Yes destroyed CPVM Many times but did not work . On 8/2/24 13:16, Wei ZHOU wrote: Hi, Have you destroy/recreate the CPVM ? -Wei On Fri, Aug 2, 2024 at 12:55 AM Biswajit Banerjee wrote: Hello, We have Upgraded ACS 4.15.1 to 4.19.1.0 . Every thing are fine apart from 2 issues 1. We are ge

Re: Upgrade to 4.19.1.0 from 4.15.1 - Issues

2024-08-02 Thread Wei ZHOU
Hi, Have you destroy/recreate the CPVM ? -Wei On Fri, Aug 2, 2024 at 12:55 AM Biswajit Banerjee wrote: > > Hello, > > We have Upgraded ACS 4.15.1 to 4.19.1.0 . Every thing are fine apart > from 2 issues > > 1. We are getting repeated error on ACS webUI with admin users saying " > The given