Ok, thanks. I actually already new that. What I do not know it how the System VM that has been started on some physical host gets the parameters that were sent to the hypervisor and sets its IP addresses (have I been clear?). That is why I also sent the email to the dev list.
I would like to understand the complete picture. Because in our Cloud for some odd reason that we do not know yet, the system VMs are going up on the physical host (hypervisor), but it is now getting its network interfaces up. So, the CS cannot access them. If we try to ping them from the host they are running, they do not respond. It seems that the ip address was not set on the VM. We checked the logs on /var/log/syslog and xcp-api.log, but apparently there was no problem with the VM start up process. On Sun, Apr 6, 2014 at 8:43 PM, Fred Newtz <[email protected]> wrote: > > It takes them from the available public IP addresses you configure when > setting up the zone. > > > > On Sun, Apr 6, 2014 at 5:33 PM, Rafael Weingartner < > [email protected]> wrote: > > > Hi folks, > > I was wondering how a system vm gets an IP address. I know they are the > > first things that CS needs in order to start up others VMs, so when they > > start there is no virtual router to assign IP addresses via DHCP. > > > > I also noticed that on the physical hosts with the VM.Start command CS > > sends some extra data that includes the IPs that the VM should get. > > However, I have no idea how it actually gets those parameters and set its > > IP. > > > > Does anyone here know how it works? > > > > -- > > Rafael Weingärtner > > > > > > -- > > Zobotek, LLC > 7941 Katy Freeway #256 > Houston, TX 77024 > > 281-216-0488 - Main Number > > http://www.zobotek.com > http://www.stonemountainhosting.com -- Rafael Weingärtner
