Xen users - Sep 2013 - Unable to launch VM's seeing this error POST operation failed: xend_post: error from xen daemon: <Fault 3

HI All.,
         I ran into this issue recently, where, every time I try to launch
a VM, it fails with an error message saying "POST operation failed:
xend_post: error from xen daemon: <Fault 3"
Here is what I see in the xen logs., Is there a way to fix this issue with
out rebooting the node( I did an init 6 on the node and once the node
rebooted, I was able to launch VM as usual)


=== Fault 3 Log message ==File
"/usr/lib64/python2.6/site-packages/libvirt.py", line 2490, in
createXML#012    if ret is None:raise
libvirtError(''virDomainCreateXML()
failed'', conn=self)#012libvirtError: POST operation failed: xend_post:
error from xen daemon: <Fault 3:
''dff50270-0845-4d53-af8f-eb79023bfe42''>
=== End of Fault 3 Error Message ==

===== Output from qemu-dm-.log ====domid: 626
config qemu network with xen bridge for  tap-dff5c90 brdff5c90
Using xvda for guest''s hda
Using file /root/centos.img in read-write mode
Using xvdb for guest''s hdb
Using file /mnt/vol1.raw in read-write mode
Using xvdc for guest''s hdc
Using file /mnt/vol2.raw in read-write mode
Using xvdd for guest''s hdd
Using file /mnt/vol3.raw in read-write mode
Using xvde for guest''s hde
*qemu: drive `xvde'' out of range*
Watching /local/domain/0/device-model/626/logdirty/cmd
Watching /local/domain/0/device-model/626/command
Watching /local/domain/626/cpu
char device redirected to /dev/pts/12
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = dff5c9d4-b38a-41d1-a132-52f2f09d9aa0
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
state.
xs_read(/local/domain/0/device-model/626/xen_extended_power_mgmt): read
error
xs_read(): vncpasswd get error.
/vm/dff5c9d4-b38a-41d1-a132-52f2f09d9aa0/vncpasswd.
*bind() failed*

===== End of Output ======

====== Log messages from Xend log ====
DEBUG (DevController:97) DevController: writing {''domain'':
''dff5c9d4-b38a-41d1-a132-52f2f09d9aa0'',
''frontend'':
''/local/domain/626/device/console/0'',
''uuid'':
''9fd7c222-4c08-e172-255c-8e7e206e7878'',
''frontend-id'': ''626'',
''state'': ''1'',
''location'': ''4'', ''online'':
''1'', ''protocol'': ''vt100''}
to
/local/domain/0/backend/console/626/0.
WARNING (image:551) domain dff5c9d4-b38a-41d1-a132-52f2f09d9aa0:* device
model failure: pid 27995: exited with nonzero status 1*; see
/var/log/xen/qemu-dm-dff5c9d4-b38a-41d1-a132-52f2f09d9aa0.log
WARNING (XendDomainInfo:2131) *Domain has crashed*:
name=dff5c9d4-b38a-41d1-a132-52f2f09d9aa0 id=626.
ERROR (XendDomainInfo:2265) VM dff5c9d4-b38a-41d1-a132-52f2f09d9aa0
restarting too fast (Elapsed time: 0.430789 seconds). Refusing to restart
to avoid loops.


====== End of Xend logs =======
I had another VM failing with similar error message

=== Start of Log ===DEBUG (DevController:97) DevController: writing
{''domain'': domain
dff50270-0845-4d53-af8f-eb79023bfe42: *device model failure: pid 14977:
malfunctioning (closed sentinel), killed*; see
/var/log/xen/qemu-dm-dff50270-0845-4d53-af8f-eb79023bfe42.log
WARNING (XendDomainInfo:2131) Domain has crashed:
name=dff50270-0845-4d53-af8f-eb79023bfe42 id=703.
 ERROR (XendDomainInfo:2265) VM dff50270-0845-4d53-af8f-eb79023bfe42
restarting too fast (Elapsed time: 0.519913 seconds). Refusing to restart
to avoid loops.

=== End of Log =====

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users