similar to: Bug#671750: Configuration of domain save/restore broken

I updated to b129 and now I get this error in dmesg on boot. Dec 15 06:26:05 nas svc.startd[9]: [ID 652011 daemon.warning] svc:/system/xvm/domains:default: Method "/lib/svc/method/xvm-domains start" failed with exit status 1. Dec 15 06:26:07 nas last message repeated 2 times Dec 15 06:26:07 nas svc.startd[9]: [ID 748625 daemon.error] system/xvm/domains:default failed: transitioned to

Hi This is my first question.. (sorry for my poor english.. ) Is this right way to ask something about installing xen, build kernel ...etc using mailing list?? I want know "How or Where can I ask something & How can I get your smart answers" I have followed this tutorial " http://wiki.xen.org/xenwiki/Fedora13Xen4Tutorial" exactly on my Core 2 Dou. after config the

Hi This is my first question.. (sorry for my poor english.. ) Is this right way to ask something about installing xen, build kernel ...etc using mailing list?? I want know "How or Where can I ask something & How can I get your smart answers" I have followed this tutorial " http://wiki.xen.org/xenwiki/Fedora13Xen4Tutorial" exactly on my Core 2 Dou. after config the

Hi I tried the SSH patch from Anthony.. using the following test code. It seems that it works only once... I mean for executing only one command over the established channel/connection. Any ideas... code from xmlrpclib import Transport from xen.util.xmlrpclib2 import ServerProxy server = ServerProxy("ssh://root@192.168.0.102/RPC2", None, None, 1, 1) l = server.xend.domains(1)

I have a test environment. Three node HCI cluster. CentOS8 build. Gluster as file system with standard cockpit deploy of HCI. Converted to CentOS Streams which seemed to go fine. Did a yum update and no issues. Did a reboot.. and now engine will no longer start. So I can no longer start my Virtual machines. I posted as bug https://bugzilla.redhat.com/show_bug.cgi?id=1911910 I posted to

Hi, I am building xen debs with dh_make. I have the problem, that I have wrong directories compiled in, that reference to the source tree where xen has been built. Has anybody got an idea, what might have gone wrong? Thanks in advance, Johnny xen_changeset : Fri Mar 24 17:48:03 2006 +0100 9435:11fee62328cc # xm dmesg Unexpected error: xml.parsers.expat.ExpatError Please report to

Hi koonz I noticed that you are using the cdrom parameter in the config file I believe that''s no longer used in recent versions of Xen. I am running debian etch here atm and am trying to virtualize windows guests aswell I am able to boot up windows with the following configs although they do tend to hang at some point during the installation. ----- Config windows xp ----- import os,

I''ve attached a python script that collects stats from DomUs (HVM and PVM). I hope this would be useful for somebody else. See comments for more info. regards, Diego -- -------------- Diego Woitasen XTECH _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello, I am forwarding this from the xen-api mailing-list, because it seems to be quite dormant. I hope someone here might be able to answer the following question. Cheers, Stephan ---------- Forwarded message ---------- From: stephan nies <nies.stephan@googlemail.com> Date: Nov 22, 2007 7:30 PM Subject: how do i use xen api with key and cert? To: xen-api@lists.xensource.com Hello, I

Hi, I found minor bugs in xm restore command. 1) When I gave a wrong check point file, a return code of command was 0. # touch /tmp/dummy # xm restore /tmp/dummy Error: not a valid guest state file: signature read # echo $? 0 2) When Xend had been stopping, I saw the following traceback message. # xend stop # xm restore /xen/save.vm1 Unexpected error: exceptions.AttributeError Please

Hello all. I''m trying to figure out vastSky on xcp1.0 beta. As we all know, it has been integrated to the xcp. That''s just about all one can find about the matter. Been trying to google a lot, but with no luck. I''ll write here what information I''ve gathered, what I tried and how far I managed to get with this. I include information about my hardware, in case it

I am getting the following error with "xm list" on a x86_64 SLES10 Beta system running changeset 9435:11fee62328cc. I am able to bring up DomUs and I am able to do "xm info" without issues. But I am seeing similar "OverflowError: int exceeds XML-RPC limits" with "xm shutdown" and "xm destroy". My python version is 2.4.2. Any way I can get around

Xen patchbot -unstable wrote: > # HG changeset patch > # User emellor@leeni.uk.xensource.com > # Node ID da24df1ea484cf72dc9d367d52e828777e0e20cd > # Parent c1bb4eb565296bdb00aed84fcc877befbcebd8e9 > Improve error handling, in particular fixing the ProtocolError that is thrown > when a domain is specified by the user that does not exist. Added a few > error codes -- many

There is some ugliness in the current version (4.4.1-2) although it doesn't seem to actually break anything in my case. From /var/log/boot: /etc/init.d/xendomains: line 128: domains: bad array subscript Starting Xen domain (from /etc/xen/auto/dnsmaster.cfg).../etc/init.d/xendomains: line 135: domains: bad array subscript

Package: xen-utils-common Version: 4.0.0-1 Severity: important The xm utility requires python-xml but the package does not depend on it. # xm new --help_vars Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-4.0/bin/xm", line 8, in <module>

Package: xen-utils-common Version: 4.0.0-1 Severity: normal Hi, On system shutdown the 'xendomains' script appears to detect wrong guests: | Stopping libvirt management daemon: libvirtd. | Clearing ebtables rulesets: filter nat broute done. | Shutting down Xen domains: bev-d6x02(save).Error: Domain '1024' does not exist. | !(shut).Error: Domain '1024' does not exist. |

Dear Xen Users, at first, sorry for my bad english and in fact my post is wrong here, please light me the way to the right board. My Xen Host runs since two years without a problem. As of today, some v-servers was not reachable anymore. I did a short xm top and got dozen of erros. I did a reboot of the Host. Thereafter i get the same error messages when trying to start xend (/etc/init.d/xend

Hi, While booting I am getting Failed to start Xendomains - start and stop guests on boot and shutdown. See ''systemctl status xendomains.service'' for details. When tried to start manually, its also fails service xendomains restart Redirecting to /bin/systemctl restart xendomains.service Job failed. See system journal and ''systemctl status'' for

On Thu, Apr 7, 2016 at 5:46 PM, exvito here <ex.vitorino at gmail.com> wrote: > Hello all, > > I'm addressing the mailing list following the suggestion of gwd on > #centos-virt @freenode IRC. > > The subject says most of it. Here are the details : > > - Was running 4.4.x and configured such that /etc/xen/auto domUs would be > saved/restored on dom0

Hi all! I have installed xen on fc6 with kernel 2.6.18-1.2798.fc6xen with rpm package; i have create 3 guest os (fully virtualization) with virt-manager tool, installed on separated partition: 1 fc6 guest, 1 centos 4.4, 1 windows xp pro; all work pretty fine until this point, i have linked the configuration file of the guests machines to /etc/xen/auto for autostart/autostop, but when