Hi,
I've gotten my 1st VM up & running on Opensuse 11.4 (both Dom0 & Guest)
mostly the way I want it.
I can bring it up/down manually from the shell command line with no
problems, but starting from /etc/xen/auto isn't working. After system
boot only the Dom0 is started, not the Guest.
To troubleshoot I tried:
service xendomains stop
Shutting down Xen domains
WARNING: xend is running! It is not recommended using libxenlight in
conjunction with the legacy xend toolstack. Use -f (force) to override
WARNING: xend is running! It is not recommended using libxenlight in
conjunction with the legacy xend toolstack. Use -f (force) to override
done
service xendomains start
Starting auto Xen domains
mail.cfg: WARNING: xend is running! It is not recommended using
libxenlight in
conjunction with the legacy xend toolstack. Use -f (force) to override
WARNING: xend is running! It is not recommended using libxenlight in
conjunction with the legacy xend toolstack. Use -f (force) to override
failed
At this point there's no Guest launched:
xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 1010 1 r-----
50.0
I 'tail -f /var/log/xen/*log /var/log/messages' to try to see more
detail about what's happening at the 'service xendomains restart', but
there's no output at all. I only get that feedback at the shell where I
exec the command.
Looking online I found this thread by <Jim Fehlig>:
[openFATE 311112] libvirt driver for new xen toolstack
http://lists.opensuse.org/opensuse-features/2011-03/msg00212.html
Which talks about 'libxenlight' & 'legacy' stack on Opensuse. A bit
over my head at this early stage :-/
I have these xen-related packages installed on the Host:
rpm -qa | grep -i xen
xen-tools-4.1.2_01-143.1.x86_64
kernel-xen-2.6.37.6-0.7.1.x86_64
xen-4.1.2_01-143.1.x86_64
kernel-xen-devel-2.6.37.6-0.7.1.x86_64
xen-kmp-default-4.1.2_01_k2.6.37.6_0.7-143.1.x86_64
xen-libs-4.1.2_01-143.1.x86_64
Is this all related to my not being able to auto-launch the Guest? Or
is it something else?
How can I get more, or any, debug information that's useful?
Thanks,
Greg
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
