[Xen-users] Traceback on xm create "No such process"

[Matthew Palmer <mpalmer@xxxxxxxxxxx>]

Running xen-unstable downloaded about 4 hours ago on an amd64 system,
everything seems happy enough until this:

root@host:~# xm create /etc/xen/oscar.xm 
Using config file "/etc/xen/oscar.xm".
Traceback (most recent call last):
  File "/usr/sbin/xm", line 10, in ?
    main.main(sys.argv)
  File "/usr/lib/python/xen/xm/main.py", line 724, in main
    handle_xend_error(argv[1], args[0], ex)
  File "/usr/lib/python/xen/xm/main.py", line 162, in handle_xend_error
    raise ex
xen.xend.XendProtocol.XendError: (3, 'No such process')

The config file is (in useful part):

----->8------

kernel = "/boot/vmlinuz-2.6.12-xenU"
memory = 512
name = "oscar"
vif = [ 'mac=aa:00:07:6b:22:b4, bridge=xen-br0' ]
disk = [ 'phy:xens/oscar-root,sda1,rw',
         'phy:xens/oscar-swap,sda2,rw' ]
root = "/dev/sda1 ro"

-----8<-----    

Is this likely to be a problem with Xen unstable, or is there something more
generally FUBAR with my config?  I've run a few 2.0 Xen servers before on
x86_32 without a problem, so I'm leaning toward amd64 or unstable breakage,
but it may be a config difference with 3.0 that I've hit.

I've googled and searched the list archives without success.

Help!

- Matt

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users