Thank you Wei - since I am testing it on a different architecture, is there a way of creating my own templates (similar to Centos templates) ?
On Sun, Apr 28, 2024 at 2:08 PM Wei ZHOU <ustcweiz...@gmail.com> wrote: > Hi Rishi, > > The systemvm template is not used for user vms. As you have noticed, > the network interfaces are configured by cloudstack , dhcp does not > work. > You can test with the built-in Centos 5 templates. You can also try > the templates on http://dl.openvm.eu/cloudstack/ (provided by NuxRo) > > -Wei > > On Sun, Apr 28, 2024 at 7:30 PM Rishi Misra <rishi.investig...@gmail.com> > wrote: > > > > Hi there, > > > > I am trying to understand why a VM instance created by Cloudstack does > not > > get an IP address in "Basic network" configuration. Interestingly, unter > > the "instances" page UI shows an IP assigned to my VM instance. > > Furthermore, the router VM adds an entry for my VM/IP in its "/etc/hosts" > > entry. > > > > However, when I try to ping/access the VM it does not have any IP > > associated with it. It almost looks like it never picked up an IP from > the > > DHCP server running on the router. > > > > After investigating a bit I found that new VM instances use default.sh > > < > https://github.com/apache/cloudstack/blob/main/systemvm/debian/opt/cloud/bin/setup/default.sh > > > > as part of initialization which does not define any interfaces which in > > turn causes this issue. I can get around it by manually adding an entry > in > > the "/etc/networking/interface" file which works well, however the > > interface is reset once the machine is rebooted (as part of cloud init). > > > > What could be going on here? I am using the same qcow2 image for SystemVM > > and User template. > > > > Thanks. >
