On Sun, Oct 11, 2009 at 07:56:12PM -0700, Peter Teoh wrote: > svc:/system/xvm/virtd:default (libvirt management daemon) > State: maintenance since Mon Oct 12 07:26:03 2009 > Reason: Start method failed repeatedly, last exited with status 137. > See: http://sun.com/msg/SMF-8000-KS > See: man -M /usr/share/man -s 1M libvirtd > See: /var/svc/log/system-xvm-virtd:default.log > Impact: This service is not running.
As usual, you can investigate why this service is not starting. Looking at the log file may be useful. Also check that all svcs -a | grep xvm services are online (apart from ipagent and vnc-config). > (xVM) microcode: CPU1 not a capable Intel processor You can ignore this. I strongly recommend upgrading to the latest build, though. > But I can successfully xm create and list: > > xm create xen.winxp 'xm' is not supported. Please use virt-install and virsh. > xm create -c ./xen.winxp > Using config file "././xen.winxp". > Started domain winxp > /usr/lib/xen/bin/xenconsole: Could not read tty from store: No such file or > directory If you'd used virt-install, then it would tell you the way to connect to HVM consoles is via 'vncviewer'. > svcs -a |grep xctl============>nothing output. Very old name - where did you get this from? regards john _______________________________________________ xen-discuss mailing list [email protected]
