launch a vm independently via xen center.
On Wed, Oct 30, 2013 at 1:36 PM, Carlos Reategui <[email protected]>wrote: > Should I try launching a vm independently? or should I try to start one of > the vhds that is in the primary storage? > > > On Wed, Oct 30, 2013 at 1:34 PM, Ahmad Emneina <[email protected]> wrote: > >> outside of cloudstack, can you deploy a vm on your host, to the desired >> storage pool. It looks like the hypervisor host cant connect to its >> storage >> server. >> >> >> On Wed, Oct 30, 2013 at 1:31 PM, Carlos Reategui <[email protected] >> >wrote: >> >> > Here is a link to the log file: >> > http://reategui.com/cloudstack/management-server.log >> > >> > >> > >> > On Wed, Oct 30, 2013 at 12:22 PM, Ahmad Emneina <[email protected] >> >wrote: >> > >> >> can we get the full logs? There should be something simple blocking the >> >> reconnection of the management server to the hosts. I worked past this, >> >> this past weekend against 4.2. So i dont think your results will differ >> >> upgrading to 4.2... >> >> >> >> >> >> On Wed, Oct 30, 2013 at 12:14 PM, Carlos Reategui <[email protected] >> >> >wrote: >> >> >> >> > No replies to my other emails. I really need help getting my CS >> 4.1.1 >> >> > cluster back up. >> >> > >> >> > I basically have a CloudStack console that thinks everything is fine, >> >> but >> >> > looking at the management logs there seems to be a problem >> connecting to >> >> > the hosts. XenCenter does not seem to agree and thinks all is fine >> with >> >> > the hosts. Iptables is disabled on the hosts and the management >> server >> >> so >> >> > not a firewall issue. Primary storage is mounted on the hosts and I >> am >> >> > able to mount secondary storage. >> >> > >> >> > I believe I have the following options: >> >> > 1) Backup all my vhds, reinstall XenServer and CS, import the vhds as >> >> > templates and relaunch my 20+ VMs. I see this as a last resort >> option >> >> that >> >> > I would rather not have to do >> >> > 2) Remove my XS hosts from CS (assuming that wont get rid of my >> >> instances), >> >> > clear tags (or re-install XS), re-add XS hosts and hope for the best. >> >> > 3) Attempt to upgrade to 4.2 and hope my problems go away. >> >> > >> >> > Anyone have any thoughts on how to proceed? >> >> > >> >> > thanks >> >> > Carlos >> >> > >> >> >> > >> > >> > >
