WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Python version

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Python version
From: Sean Atkinson <sean@xxxxxxxxxxxxxx>
Date: Fri, 19 Mar 2004 14:07:03 +0100
Cc: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 19 Mar 2004 13:15:55 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1B4G8k-0000HH-00@xxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Organization: Netproject
References: <E1B4G8k-0000HH-00@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Hi,

> I'm afraid the nightly build failed last night due to lack of
> disk space. I've cranked the handle manually so it should be
> there now.

My RPM now builds fine with the new tarball - thanks.

However I'm getting new errors using it.  First:

# xc_dom_create.py
Parsing config file '/etc/xc/defaults'
VM image           : "/boot/xenolinux.gz"
VM ramdisk         : ""
VM memory (MB)     : "64"
VM IP address(es)  : "169.254.1.1"
VM block device(s) : ""
VM cmdline         :
"ip=169.254.1.1:169.254.1.0:192.168.1.1:255.255.255.0::eth0:off
root=/dev/nfs nfsroot=/tmp/root "
Traceback (most recent call last):
  File "/usr/bin/xc_dom_create.py", line 332, in ?
    (current_id, current_port) = make_domain()
  File "/usr/bin/xc_dom_create.py", line 245, in make_domain
    xend_response = xenctl.utils.xend_control_message(cmsg)
  File "/usr/lib/python2.2/site-packages/xenctl/utils.py", line 198, in
xend_control_message
    ctl.sendto(message, '/var/run/xend/management_sock')
socket.error: (2, 'No such file or directory')

So I issue "xend start", but then another error finishes:

  File "/usr/lib/python2.2/site-packages/xenctl/utils.py", line 198, in
xend_control_message
    ctl.sendto(message, '/var/run/xend/management_sock')
socket.error: (111, 'Connection refused')

Am I misusing xend somehow?

> BTW: Within the tar ball, I'm thinking of renaming the
> 'xeno-unstable.bk' directory to something based on the MD5KEY of
> the repository e.g. 'xeno-unstable-d7f7a767b78c50a7d2dd.bk' and
> create a soft link from xeno.bk to the new name. The idea behind
> this change is that when we receive patches we'd be able to
> easily tell what version of the repository the patch is against. 
> Any objections?

Seems sensible to me, but wouldn't a date & time stamp be easier than an
MD5?

Cheers,

Sean.

-- 
Sean Atkinson <sean@xxxxxxxxxxxxxx>
Netproject



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel