Re: [D] System VMs fail to start – “Unable to create a deployment for VM instance [cloudstack]

GitHub user yann1ck-oder-so edited a comment on the discussion: System VMs fail to start – “Unable to create a deployment for VM instance Is this more usefull? ```java 2025-10-24 06:51:38,464 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-24:[ctx-11397d36, job-236/job-2298

Re: [D] System VMs fail to start – “Unable to create a deployment for VM instance [cloudstack]

GitHub user rajujith added a comment to the discussion: System VMs fail to start – “Unable to create a deployment for VM instance @yann1ck-oder-so make sure you grep the log file for 2025-10-24 GitHub link: https://github.com/apache/cloudstack/discussions/11903#discussioncomment-14789405

Re: [D] System VMs fail to start – “Unable to create a deployment for VM instance [cloudstack]

GitHub user yann1ck-oder-so added a comment to the discussion: System VMs fail to start – “Unable to create a deployment for VM instance I have no output, if I execute this command: grep "job-2298)" management-server.log GitHub link: https://github.com/apache/cloudstack/discuss

Re: [D] System VMs fail to start – “Unable to create a deployment for VM instance [cloudstack]

GitHub user rajujith added a comment to the discussion: System VMs fail to start – “Unable to create a deployment for VM instance https://docs.cloudstack.apache.org/en/latest/adminguide/troubleshooting.html GitHub link: https://github.com/apache/cloudstack/discussions/11903#discussioncomment

Re: [D] System VMs fail to start – “Unable to create a deployment for VM instance [cloudstack]

GitHub user weizhouapache added a comment to the discussion: System VMs fail to start – “Unable to create a deployment for VM instance the full log of job-2298 would be better GitHub link: https://github.com/apache/cloudstack/discussions/11903#discussioncomment-14769533 This is an

Re: [D] System VMs fail to start – “Unable to create a deployment for VM instance [cloudstack]

GitHub user yann1ck-oder-so added a comment to the discussion: System VMs fail to start – “Unable to create a deployment for VM instance Is this more usefull? 2025-10-24 06:51:38,464 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-24:[ctx-11397d36, job-236/job-2298]) (logid

Re: [D] System VMs fail to start – “Unable to create a deployment for VM instance [cloudstack]

GitHub user rajujith added a comment to the discussion: System VMs fail to start – “Unable to create a deployment for VM instance @yann1ck-oder-so 'InsufficientServerCapacityException' is a generic error; there must be a specific error in the logs preceding this error. GitHub li

Re: [D] System VMs fail to start – “Unable to create a deployment for VM instance [cloudstack]

GitHub user yann1ck-oder-so edited a discussion: System VMs fail to start – “Unable to create a deployment for VM instance Hi everyone, I’m running a management server and currently have two KVM hosts, both on Ubuntu. The basic configuration is complete, and both hosts are successfully added

[D] Cloudstack System VMs does not work [cloudstack]

GitHub user yann1ck-oder-so created a discussion: Cloudstack System VMs does not work Hi everyone, I’m running a management server and currently have two KVM hosts, both on Ubuntu. The basic configuration is complete, and both hosts are successfully added to the cluster. The problem: My

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user alsko-icom closed a discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack4.20.1.alsko.log](https://github.com/user-attachments/files/21118669/cloudstack4.20.1.alsko.log) Hello team, We decided to test out latest xcp-ng 8.3 hosts

Re: [D] Custom routes for System VMs [cloudstack]

You can add a static route manually on the system VMs, But seems is not possible to make it permanent. As soon you reboot the SystemVM even the settings on the interface following debian documentation, after a systemVM reboot all settings are replaced. We did try several options that @wei

Re: [D] Custom routes for System VMs [cloudstack]

GitHub user daviftorres added a comment to the discussion: Custom routes for System VMs Hey @mahdiadnan , I raised similar issues before: - https://github.com/apache/cloudstack/issues/11020 - https://github.com/apache/cloudstack/discussions/11562#discussioncomment-14305414 There is a way to

[D] Custom routes for System VMs [cloudstack]

GitHub user mahdiadnan created a discussion: Custom routes for System VMs Hi, I've noticed that there's no way "or a clean way" to add custom routes to System VMs. System VMs, when trying to reach other Infrastructure services like Secondary Storage or a reverse proxy f

Re: POSSIBLE SSL ERROR ON SYSTEM VMS - POSSÍVEL ERRO DE SSL NAS SYSTEM VMS

25 2:04 PM To: [email protected] Subject: Re: POSSIBLE SSL ERROR ON SYSTEM VMS - POSSÍVEL ERRO DE SSL NAS SYSTEM VMS These logs are from this morning. I rebuilt my CloudStack environment and now the System VMs have connectivity, so much so that I can access the VMs via SSH and ping th

Re: POSSIBLE SSL ERROR ON SYSTEM VMS - POSSÍVEL ERRO DE SSL NAS SYSTEM VMS

These logs are from this morning. I rebuilt my CloudStack environment and now the System VMs have connectivity, so much so that I can access the VMs via SSH and ping the management, public, and storage networks through it. I solved the logs you sent me by simply rebuilding the environment

Re: POSSIBLE SSL ERROR ON SYSTEM VMS - POSSÍVEL ERRO DE SSL NAS SYSTEM VMS

hat works - You can ssh to systemVM's on vmware using the steps here The System VM Template — Apache CloudStack 4.20.1.0 documentation<https://docs.cloudstack.apache.org/en/latest/adminguide/systemvm.html#accessing-system-vms> The System VM Template — Apache CloudStack 4.20.1.0 docume

POSSIBLE SSL ERROR ON SYSTEM VMS - POSSÍVEL ERRO DE SSL NAS SYSTEM VMS

*IN ENGLISH* Hello, I've rebuilt my CloudStack environment to VMware and I'm having a problem. It appears my System VMs are powered on, have connectivity, and are pinging all networks, but the System VM services (SSVM and CPVM) aren't working. The evidence images and

Re: SYSTEM VMS DOES NOT BOOT - SYSTEM VMS NÃO BOOTAM

ramdisk file it could be issue with systemVm template or the OS type defined ( I see this set to other linux 64bit). Thanks Prashanth From: Kayo Henrique Sent: Wednesday, August 6, 2025 6:44 PM To: [email protected] Subject: Re: SYSTEM VMS D

Re: SYSTEM VMS DOES NOT BOOT - SYSTEM VMS NÃO BOOTAM

from all your management servers? From: Kayo Henrique Sent: Wednesday, August 6, 2025 2:44 PM To: [email protected] Subject: Re: SYSTEM VMS DOES NOT BOOT - SYSTEM VMS NÃO BOOTAM *IN ENGLISH* Hello, Below is the link with image evidence of our

Re: SYSTEM VMS DOES NOT BOOT - SYSTEM VMS NÃO BOOTAM

? From: Kayo Henrique Sent: Wednesday, August 6, 2025 2:44 PM To: [email protected] Subject: Re: SYSTEM VMS DOES NOT BOOT - SYSTEM VMS NÃO BOOTAM *IN ENGLISH* Hello, Below is the link with image evidence of our environment's status. https://drive.onexdatacenter.com

Re: SYSTEM VMS DOES NOT BOOT - SYSTEM VMS NÃO BOOTAM

ue with the above , please share a link to the management server logs from the affected environment Thanks Prashanth From: Kayo Henrique Sent: Tuesday, August 5, 2025 7:08 PM To: [email protected] Subject: SYSTEM VMS DOES NOT BOOT - SYSTEM

Re: SYSTEM VMS DOES NOT BOOT - SYSTEM VMS NÃO BOOTAM

the management server logs from the affected environment Thanks Prashanth From: Kayo Henrique Sent: Tuesday, August 5, 2025 7:08 PM To: [email protected] Subject: SYSTEM VMS DOES NOT BOOT - SYSTEM VMS NÃO BOOTAM *IN ENGLISH* Hello, I rece

SYSTEM VMS DOES NOT BOOT - SYSTEM VMS NÃO BOOTAM

is is normal). Anyway, my problem is that when I start the zone, CloudStack generates the two System VMs (CPVM and SSVM), but they don't start (they don't boot). I seeded the System VM template normally, and so far the template appears in the NFS pool (looking directly at vCenter).

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user DaanHoogland added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs I know there is a configuration option for nfs mounts, but would not know what is wrong in your case, glad it works now. GitHub link: https://github.com

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user DaanHoogland added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs @alsko-icom please checkt the template as @Pearl1594 suggests. Why do you think the mount of the nfs share is the problem? GitHub link: https

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user weizhouapache added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs > The team noticed some errors during deployment regarding NFS SR being unable > to mount on the xcp-ng hosts. So if nfs mount failed, there was

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user alsko-icom added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs After going in the Netapp NFS configuration with the storage team to check settings you asked me, i witnessed them turning off the v4 and v4.1-4.2 support

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user DaanHoogland added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs @alsko-icom , what type of NFS server are you running and what options are turned on on it? (squash_root, nfs version, …?) See [this part of the docs

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user Pearl1594 added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs @alsko-icom can you please confirm if the systemvm template has been registered / seeded? GitHub link: https://github.com/apache/cloudstack/discussions

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user alsko-icom added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs added the file to my personal nextcloud server and as a gist too. https://gist.github.com/alsko-icom/c835b6f4ad87a27bd3ca96604dcf9c4c and the nextcloud

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user alsko-icom added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs Regarding the nfs storage it has been mounted on the xcp hosts This is the df - h output https://github.com/user-attachments/assets/f1acb786-3612-4c2b-92d4

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user alsko-icom added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs pasting here screenshot of the seed command for your reference https://github.com/user-attachments/assets/c7cf5b66-ea2d-4e04-9714-2bc884bb0bf4"; /&

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user DaanHoogland added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs it is now zero bytes, @alsko-icom . can you create a gist or use some other upload/ftp service? GitHub link: https://github.com/apache/cloudstack

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user alsko-icom added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs ok we will review the nfs behavior a bit more. Regarding the prep, should we add the xcp-ng hosts to the pool through cloudstack or through xen orchestrator

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user DaanHoogland added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs No @alsko-icom , unless there are some setting on the nfs server preventing it, all servers should be able to share the NFS storage. GitHub link: https

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user DaanHoogland added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs @alsko-icom , I think you can add it to the pool and add the pool-master. please check though. GitHub link: https://github.com/apache/cloudstack

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user alsko-icom added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack4.20.1.alsko.txt](https://github.com/user-attachments/files/21119285/cloudstack4.20.1.alsko.txt) reuploaded file with txt extension. GitHub link

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user DaanHoogland added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs @alsko-icom , the logs are not visible. GitHub link: https://github.com/apache/cloudstack/discussions/11346#discussioncomment-13933523 This is an

Re: [D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user alsko-icom added a comment to the discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs Excuse my late reply, somehow i missed the notification of your update! Is there a problem that we have all 4 xcp-ng hosts connecting to the nfs? Not sure

[D] Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack]

GitHub user alsko-icom created a discussion: Attempt to deploy fresh 4.20.1 utilizing xcp-ng 8.3 fails to deploy system VMs [cloudstack4.20.1.alsko.log](https://github.com/user-attachments/files/21118669/cloudstack4.20.1.alsko.log) Hello team, We decided to test out latest xcp-ng 8.3 hosts

Re: [D] IPv6 for System VMs (4.19.3) [cloudstack]

GitHub user MejdiB closed the discussion with a comment: IPv6 for System VMs (4.19.3) @weizhouapache Hi Wei, thank you very much for the clarification. I will close the disussion. GitHub link: https://github.com/apache/cloudstack/discussions/10698#discussioncomment-13036097 This is an

Re: [D] IPv6 for System VMs (4.19.3) [cloudstack]

GitHub user MejdiB closed a discussion: IPv6 for System VMs (4.19.3) According to the docs there are specific System VM Templates (in my case KVM) which shall support IPv6, cite "Use the System VM Template exclusively designed to support IPv6. Download the System VM Template from

Re: [D] IPv6 for System VMs (4.19.3) [cloudstack]

GitHub user weizhouapache added a comment to the discussion: IPv6 for System VMs (4.19.3) > @MejdiB , I think all IPv6 is merged (as far as applicable) now. > > maybe @weizhouapache or @wido can expand on that? @MejdiB 4.19.3 uses the 4.19.1 systemvm template IPv6 is only enabl

Re: [D] IPv6 for System VMs (4.19.3) [cloudstack]

GitHub user DaanHoogland added a comment to the discussion: IPv6 for System VMs (4.19.3) @MejdiB , I think all IPv6 is merged (as far as applicable) now. maybe @weizhouapache or @wido can expand on that? GitHub link: https://github.com/apache/cloudstack/discussions/10698#discussioncomment

Re: [D] Launching system vms fails during installation [cloudstack]

GitHub user SammyOina closed a discussion: Launching system vms fails during installation ### problem I am following the installation guide https://docs.cloudstack.apache.org/en/latest/quickinstallationguide/qig.html However it fails at the end with system vms failing to launch ![Image

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user vishnuvs369 closed a discussion: Unable to Secure CloudStack System VMs with Dynamic URL # ISSUE TYPE * Other # COMPONENT NAME `System VM's ` # CLOUDSTACK VERSION `4.19.0.1 ` # SUMMARY I'm facing difficulties securing CloudStack System VMs

Re: [D] Launching system vms fails during installation [cloudstack]

GitHub user shwstppr added a comment to the discussion: Launching system vms fails during installation @UAnton Check logs where an exception was seen for the latest system vm. It must be having log line like the following at the start of the flow, VM start attempt #1 If your system vm

Re: [D] Launching system vms fails during installation [cloudstack]

GitHub user shwstppr added a comment to the discussion: Launching system vms fails during installation @SammyOina I think @weizhouapache means you need to re-upload management server logs for the latest failures. Last logs indicated cluster was in disabled state. Maybe it was some other

Re: [D] Launching system vms fails during installation [cloudstack]

GitHub user UAnton added a comment to the discussion: Launching system vms fails during installation Have same problem GitHub link: https://github.com/apache/cloudstack/discussions/10330#discussioncomment-12148870 This is an automatically sent email for [email protected]. To

Re: [D] Launching system vms fails during installation [cloudstack]

GitHub user SammyOina added a comment to the discussion: Launching system vms fails during installation > [@SammyOina](https://github.com/SammyOina) can you upload the logs of another > system vm ? ![Image](https://github.com/user-attachments/assets/8756ec68-95c7-4c14-8b90-161caa

Re: [D] Launching system vms fails during installation [cloudstack]

GitHub user weizhouapache added a comment to the discussion: Launching system vms fails during installation @SammyOina can you upload the logs of another system vm ? GitHub link: https://github.com/apache/cloudstack/discussions/10330#discussioncomment-12070584 This is an automatically

Re: [D] Launching system vms fails during installation [cloudstack]

GitHub user SammyOina added a comment to the discussion: Launching system vms fails during installation   As far

Re: [D] Launching system vms fails during installation [cloudstack]

GitHub user SammyOina added a comment to the discussion: Launching system vms fails during installation ```shell 2025-02-03 23:18:59,575 ERROR [c.c.c.ClusterServiceServletImpl] (Cluster-Worker-3:[ctx-c6c2a092]) (logid:1cd75554) Exception from : https://127.0.0.1:9090/clusterservice, method

Re: [D] Launching system vms fails during installation [cloudstack]

GitHub user Pearl1594 added a comment to the discussion: Launching system vms fails during installation @SammyOina it seems that the systemVMs aren't able to find a suitable host, based on these logs: ``` 2025-02-03 23:19:00,662 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Work-Job-Exe

Re: [D] Launching system vms fails during installation [cloudstack]

GitHub user boring-cyborg[bot] added a comment to the discussion: Launching system vms fails during installation Thanks for opening your first issue here! Be sure to follow the issue template! GitHub link: https://github.com/apache/cloudstack/discussions/10330#discussioncomment-12070580

How to manually update Cloudstack system vms to new template?

Hi, any idea, how to manually update/re-create Cloudstack system storage and console vms from newer template 4.15.2, if Cloudstack cannot manage hypervisor hosts? (I can manage hosts via XenCenter) (Hosts are at Alert state due "Monitor ComputeCapacityListener says there is an error in the c

DHCP + System VMs

Ls, During installation / configuration, ACS requires you to provide two IP ranges. One for Public Traffic Network and one for System Reserved IP addresses. When it creates the zone, it starts the two system VMs (Console VM and Secondary Storage VM) using the first two available IP addresses

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

order. Best regards, Jordan On Thu, Jun 20, 2024 at 8:51 PM weizhouapache (via GitHub) wrote: > > GitHub user weizhouapache added a comment to the discussion: Unable to > Secure CloudStack System VMs with Dynamic URL > > > @weizhouapache Ports 443 and 8443 are listening in

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user weizhouapache added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL > @weizhouapache Ports 443 and 8443 are listening in CPVM...and IP are > reachable > ![image](https://private-user-images.githubusercontent.com/54799446/324764500

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user vishnuvs369 added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL @weizhouapache No errors found on CPVM..  GitHub link: https://github.com

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user weizhouapache added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL > @weizhouapache No errors found on CPVM.. > ![image](https://private-user-images.githubusercontent.com/54799446/324770823-acecd838-7019-4474-97fb-a7a9975e2b19.p

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user DaanHoogland added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL > @weizhouapache I tried a telnet to 443 and 8443443 is not connected > ![image](https://private-user-images.githubusercontent.com/54799446/324776677-26027310-5031-440

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user weizhouapache added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL > @weizhouapache I tried a telnet to 443 and 8443443 is not connected > ![image](https://private-user-images.githubusercontent.com/54799446/324776677-26027310-503

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user vishnuvs369 added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL @weizhouapache Ports 443 and 8443 are listening in CPVM...and IP are reachable ![image](https://github.com/apache/cloudstack/assets/54799446/70144f4d-2818-42d5-b297-d767d79f56bc

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user weizhouapache added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL > @weizhouapache I restarted management server and destoyed system vm's, still > its not working. @vishnuvs369 is the DNS name resolvable ? check if ip and port 4

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user sureshanaparti added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL > > @weizhouapache I tried a telnet to 443 and 8443443 is not connected > > ![image](https://private-user-images.githubusercontent.com/54799446/324776677-2

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user vishnuvs369 added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL @weizhouapache I'm able to telnet 443/8443 from public IP and 127.0.0.1 but not able to telnet 443 from domain name where as 8443 is working. where i have gone wrong? ![

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user vishnuvs369 added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL @weizhouapache I tried a telnet to 443 and 8443443 is not connected ![image](https://github.com/apache/cloudstack/assets/54799446/26027310-5031-4405-9aea-b21db0d3ac9c

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user weizhouapache added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL > @weizhouapache I enabled the following settings in global settings > consoleproxy.ssl True secstorage.encrypt.copy True > > Also Added domains in the

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user weizhouapache added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL @vishnuvs369 what are the related globals settings ? check https://www.shapeblue.com/securing-cloudstack-4-11-with-https-tls/ GitHub link: https://github.com/apache

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user vishnuvs369 added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL @weizhouapache I restarted management server and destoyed system vm's, still its not working. GitHub link: https://github.com/apache/cloudstack/discussions

Re: [D] Unable to Secure CloudStack System VMs with Dynamic URL [cloudstack]

GitHub user vishnuvs369 added a comment to the discussion: Unable to Secure CloudStack System VMs with Dynamic URL @weizhouapache I enabled the following settings in global settings consoleproxy.ssl True secstorage.encrypt.copy True Also Added domains in the below fields

Re: Choose system VMs network ?

hat comes to my mind is somehow make the SVMs pod ip ( >> 10.10.11.0/24) to take the role of the public interface instead but i >> dont know if that is possible at all. >> >> Best regards, >> Jordan >> >> On Thu, Dec 15, 2022 at 6:51 PM Nux wrote: >>

Re: Choose system VMs network ?

; 10.10.11.0/24) to take the role of the public interface instead but i > dont know if that is possible at all. > > Best regards, > Jordan > > On Thu, Dec 15, 2022 at 6:51 PM Nux wrote: > >> Hello, >> >> Then I do not think there is a setting to help you. &

Choose system VMs network ?

Dear all, I have the following setup. ACS 4.17.1 + XCP-NG 8.2.1 with network bridge + Advanced network with security groups. Because Security Groups are enabled there is no public network in the zone so instead system VMs use the user network. The setup has multiple such networks so SSVMs use

Re: Error migrate System VMs after upgrageing to 4.17

Hi Chris, The deployment fails because CS cannot find a free IP address to allocate for the system VM. Can you check if you explicitly added a range for the system VMs, or you can check with this `select * from user_ip_address where forsystemvms = 1;` If you don't have any ranges, you ca

Re: Error migrate System VMs after upgrageing to 4.17

Hi Slavka, no, i am not using any kind of custome offerings. I try to provide a more detailled log this time. Situation: v-83-VM was the "broken" consoleproxy. So the following log starts with it's expunging. Afterwards the new consoleproxy shall be deployed - v-85-VM. This first deployment (log

Re: Error migrate System VMs after upgrageing to 4.17

Thanks, Chris, for the information! Are you using custom offerings for the system VMs? Can you share more info if yes? About the log, it's not the complete log from where the deployment started. The deployment begins a bit earlier than what you shared. Can you search the management log for

Re: Error migrate System VMs after upgrageing to 4.17

6 Uhr schrieb Slavka Peleva < [email protected]>: > Hi Chris, > > I mean to recreate the system VMs by destroying them. > > On Mon, Aug 29, 2022 at 12:38 PM [email protected] wrote: > >> Hi Slavka, >> >> didn't tried to restart the SystemVMs. Reading

Re: Error migrate System VMs after upgrageing to 4.17

Hi Chris, I mean to recreate the system VMs by destroying them. On Mon, Aug 29, 2022 at 12:38 PM [email protected] wrote: > Hi Slavka, > > didn't tried to restart the SystemVMs. Reading through the docs i had the > impression that "live-patching" would be enough for thi

Re: Error migrate System VMs after upgrageing to 4.17

cJobManagerImpl$5.run(AsyncJobManagerImpl.java:568) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at j

Re: Error migrate System VMs after upgrageing to 4.17

Hi Chris, Did you recreate the system VMs? In the 4.17 version, the `systemvm.iso` is deprecated. In its place, you should have the file on agents `/usr/share/cloudstack-common/vms/agent.zip`. Can you share the complete log if the system VMs are newly created after the upgrade? Best regards

Error migrate System VMs after upgrageing to 4.17

Hi everyone, faceing some challanges again after upgradeing to 4.17. Did as explained in the docs. Afterwards I am now not able to migrate system VMs to different hosts. Getting the error "Exception during migrate: org.libvirt.LibvirtException: Cannot access storage file '/usr/share/

Re: system vms

Please destroy > any hard copies and delete this message. > -Original Message- > From: Andrey Smirnov > Sent: 16 August 2022 18:42 > To: [email protected] > Subject: system vms > > Hi, > > Could anyone help with this question? > > Which IP address

RE: system vms

on or reliance on its contents. Please destroy any hard copies and delete this message. -Original Message- From: Andrey Smirnov Sent: 16 August 2022 18:42 To: [email protected] Subject: system vms Hi, Could anyone help with this question? Which IP address space should be use

Re: system vms

a very crude answer Andrey, An SSVM needs access to the management network, the storage network and to the (public) internet. On Tue, Aug 16, 2022 at 7:42 PM Andrey Smirnov wrote: > Hi, > > Could anyone help with this question? > > Which IP address space should be used for system

system vms

Hi, Could anyone help with this question? Which IP address space should be used for system VMs for a zone -- I cannot find any documentation related to storage VMs networking, they start with two sets of IP addresses -- private and not private -- but I cannot find any references -- how

Re: Zone not ready to launch system VMs though they are already running...

: Re: Zone not ready to launch system VMs though they are already running... Hi Peter, Could you please check /etc/cloudstack/usage/db.properties, it should be a symlink to /etc/cloudstack/management/db.properties -Wei On Wed, 1 Dec 2021 at 16:25, Peter Stine wrote: Hi Slavka, I c

Re: Zone not ready to launch system VMs though they are already running...

rg.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:144) > at > org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:85) > at com.cloud.usage.UsageServer.start(UsageServer.java:52) > at c

Re: Zone not ready to launch system VMs though they are already running...

"Wei ZHOU" Sent: 11/30/21 1:00 PM To: users , [email protected] Subject: Re: Zone not ready to launch system VMs though they are already running... Hi Peter, This seems to be caused by database connection problems. Try to restart cloudstack management service, and also mari

Re: Zone not ready to launch system VMs though they are already running...

Hi Peter, This seems to be caused by database connection problems. Try to restart cloudstack management service, and also mariadb if it still doesn't work. -Wei On Tue, 30 Nov 2021 at 18:37, Peter Stine wrote: > Hello everyone, > > I was getting a warning for high CPU usage on my management se

Zone not ready to launch system VMs though they are already running...

Hello everyone, I was getting a warning for high CPU usage on my management servers and found that the spikes were in line with the cloudstack logs showing a message that the Zone is not prepared to launch the consoleproxy and secondary storage VMs. 2021-11-30 09:40:58,957 DEBUG [o.a.c.s.Second

Re: System Vms

Hi, I have another question : Since I implement cloudstack on a local IP (192.168.xxx.xxx), for instance can I assign a public IP? I want to assign a public IP for instance because I want to access the version using ssh by another PC but in the same LAN On 2020/12/24 05:04:50, Vivek Kumar wrot

Re: System Vms

You can check the logs from systemVM/Management Server. You will get idea why your agent state is not coming up. Vivek Kumar Manager - Cloud & DevOps IndiQus Technologies 24*7 O +91 11 4055 1411 | M +91 7503460090 www.indiqus.com This message is intended only for the

System Vms

Hi all, I already deploy Cloudstack but I dont know the reason agent state of Secondary Storage VM has no signal. And Cloudstack I deploy based on local IP address such as : 192.168.xxx.xxx. Can i assign public IP for instance or not ? Thank you.

Re: VirtIO Network Adapter for system vms on KVM Hypervisor

troller: Red Hat, Inc Virtio network device > 00:09.0 Ethernet controller: Red Hat, Inc Virtio network device > > > -Original Message- > From: Andrija Panic > Sent: Saturday, May 16, 2020 7:12 AM > To: users > Subject: Re: VirtIO Network Adapter for system vms on KVM

RE: VirtIO Network Adapter for system vms on KVM Hypervisor

Adapter for system vms on KVM Hypervisor Thanks for the feedback on that one, Rafal. Regards On Sat, 16 May 2020 at 12:58, Rafal Turkiewicz wrote: > Just for a record > > I have tested this with Debian GNU/Linux 7.0 (64-bit) OS Type and it > also worked. It basically breaks as soon as I

Re: CloudStack - Ubuntu/KVM (all in one management-server/host) - OS Upgrade w/o updating System VMs

database? > > 2. In the UI there's an HVM checkbox (that's defaulted to checked), but > the documentation (above) doesn't specifically refer to it. So for my > clarity (hopefully I just need to be remided), leave it checked or > unchecked? Does it matter in the context of the

Re: CloudStack - Ubuntu/KVM (all in one management-server/host) - OS Upgrade w/o updating System VMs

n HVM checkbox (that's defaulted to checked), but the documentation (above) doesn't specifically refer to it. So for my clarity (hopefully I just need to be remided), leave it checked or unchecked? Does it matter in the context of the system VMs? Thanks! David David Merrill Senior Syste

Re: CloudStack - Ubuntu/KVM (all in one management-server/host) - OS Upgrade w/o updating System VMs

o downgrade the database connector or it will not work > > > > Sent from Yahoo Mail on Android > > > > On Sun, May 17, 2020 at 3:47 PM, David Merrill< > [email protected]> > > wrote: Hi All, > > > > I&#

  1   2   3   4   5   >