When I open the VM console I get the following: Cleaning up temporary files.... modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32-5-686-bigmem/kernel/drivers/crypto/padlock-sha.ko): No such device
INIT: Sending processes the TERM signal Using makefile-style concurrent boot in runlevel 6. cat: /var/run/xe-daemon.pid: No such file or directory Stopping xe daemon: kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] Failed Stopping cloud-early-config...done. Stopping web server: apache2. done. All processes ended within 1 seconds....done. Stopping enhanced syslogd: rsyslogd already stoppedSaving the system clock. Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. Deconfiguring network interfaces...done. Cleaning up ifupdown.... Deactivating swap...done. Have anyone seen something like this? On Mon, Apr 7, 2014 at 10:15 AM, Rafael Weingartner < rafaelweingart...@gmail.com> wrote: > I am using Xen server instead of KVM. > I tried to ping the VM's internal address, however it does not respond. > > > On Mon, Apr 7, 2014 at 10:13 AM, Wido den Hollander <w...@widodh.nl>wrote: > >> >> >> On 04/07/2014 03:10 PM, Rafael Weingartner wrote: >> >>> By agent you mean CS management server? I am running CS 4.1.1. >>> >> >> No, in the KVM Agent. The hypervisor. >> >> /var/log/cloudstack/agent/agent.log >> >> >> would the command cloudstack-ssh work, if the VM does not respond on its >>> ip >>> addresses? >>> >> >> It probably has it's local 169.X.X.X address, so that should work. >> >> >> Wido >> >> >>> >>> >>> On Mon, Apr 7, 2014 at 10:01 AM, Wido den Hollander <w...@widodh.nl> >>> wrote: >>> >>> >>>> >>>> On 04/07/2014 02:20 PM, Rafael Weingartner wrote: >>>> >>>> Thanks man ;). >>>>> By any chance if a system VM does not get its ip assigned, would there >>>>> be >>>>> any way to debug and check what is going on? I mean, if after it is >>>>> running >>>>> on the physical host it does respond on the IP that was assigned to it. >>>>> >>>>> >>>>> I say check the agent's log (set to debug!) and try to SSH into the >>>> SSVM >>>> with the cloudstack-ssh command. >>>> >>>> Wido >>>> >>>> >>>> >>>> On Mon, Apr 7, 2014 at 9:14 AM, Wido den Hollander <w...@widodh.nl> >>>>> wrote: >>>>> >>>>> >>>>> >>>>>> On 04/07/2014 12:33 AM, Rafael Weingartner 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. >>>>>>> >>>>>>> >>>>>>> Via a local virtio socket from the hypervisor in KVM mode. The VM >>>>>>> boots >>>>>>> >>>>>> and via that local serial socket it gets the IP-address. >>>>>> >>>>>> >>>>>> 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. >>>>>>> >>>>>>> >>>>>>> The management server sends this information to the KVM agent. User >>>>>> Instances get the IP address via DHCP from the VR, System VMs via the >>>>>> local >>>>>> serial socket. >>>>>> >>>>>> Wido >>>>>> >>>>>> >>>>>> >>>>>> Does anyone here know how it works? >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>> >>>>> >>> >>> > > > -- > Rafael Weingärtner > -- Rafael Weingärtner
