Anybody else got any ideas on this? I Don't really know what else to try! Cheers,
On Mon, Oct 12, 2009 at 2:08 PM, Stephen Ross < [email protected]> wrote: > Hi, > > I am using Xen, sorry should have stated that! > > It's not a resource allocation issue I'm afraid. The machine has 128GB ram > and 24 cores, and only 1 or 2 low spec guest VM's running on it. > > I've restarted both Spacewalk and the Xen server in question to no avail. > > Cheer for the help and quick reply! Any other ideas? > > Cheers, > > On Mon, Oct 12, 2009 at 1:50 PM, Ashok Raj D <[email protected]> wrote: > >> Hi Steve, >> >> >> >> I guess you are using Xen server for virtualization. If so, this could be >> a resource allocation issue. Please verify if the resource allocated (such >> as Memory, CPU ) to all the virtual instance of the Xenserver are okay. >> After confirming it, restart the Xenserver including all its VMs. That >> should fix this issue. >> >> >> >> Thanks & Regards, >> >> *Ashok Raj* >> >> TravelCLICK - OMS Support >> >> Phone No: 877-200-2601 >> >> >> ------------------------------ >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Stephen Ross >> *Sent:* Monday, October 12, 2009 7:43 AM >> *To:* [email protected] >> *Subject:* [Spacewalk-list] Problems starting virtual machines from >> withinSpacewalk >> >> >> >> Hi all, >> >> I'm getting an odd error when trying to start virtual machines from within >> Spacewalk 0.6 when using RHEL 5.4. >> >> When I schedule a machine to start, then do rhn_check -vvv on the client >> side I get the following errors: >> >> D: handle_action {'action': "<?xml >> version='1.0'?>\n<methodCall>\n<methodName>virt.start</methodName>\n<params>\n<param>\n<value><string>daa9ccc17372fcc1e96c05ec1601bafe</string></value>n</param>\n</params>\n</methodCall>\n", >> 'version': 2, 'id': 64} >> D: handle_action actionid = 64, version = 2 >> D: do_call virt.start ('daa9ccc17372fcc1e96c05ec1601bafe',) >> D: Sending back response ((6,), 'Fatal error in Python code occured', {}) >> >> I can provision VM's from a kickstart profile, shutdown, restart, suspend >> or resume VM's fine... just not start them! >> >> Any idea's on things to investigate/check? I'm at a loose end with this >> really.... everything else works fine, cant understand why starting machines >> doesn't.... >> >> Cheers, >> >> Steve >> >> _______________________________________________ >> Spacewalk-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/spacewalk-list >> > >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
