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-users

[Xen-users] Mysterious crash on SLES11; VMs did not autostart

To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Mysterious crash on SLES11; VMs did not autostart
From: James Pifer <jep@xxxxxxxxxxxxxxxx>
Date: Mon, 14 Dec 2009 13:02:19 -0500
Delivery-date: Mon, 14 Dec 2009 10:03:03 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I have a couple sles11 servers running xen 3.4:
# xm info
host                   : xen03
release                : 2.6.27.19-5-xen
version                : #1 SMP 2009-02-28 04:40:21 +0100
machine                : x86_64
nr_cpus                : 16
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 2533
hw_caps                :
bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 32757
free_memory            : 15432
max_free_memory        : 16966
max_para_memory        : 16962
max_hvm_memory         : 16914
node_to_cpu            : node0:0-15
node_to_memory         : node0:15432
xen_major              : 3
xen_minor              : 4
xen_extra              : .1_19718_04-26.
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64 
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : 19718
cc_compiler            : gcc version 4.3.2 [gcc-4_3-branch revision
141291] (SUSE Linux)
cc_compile_by          : abuild
cc_compile_domain      : 
cc_compile_date        : Wed Oct 14 00:02:21 UTC 2009
xend_config_format     : 4

A little while ago I had a mysterious crash. Nothing
in /var/log/messages except that the server coming back up. That's the
first problem that I guess I'll have to keep an eye on. If it happened
once I assume it will happen again.

Second problem is that none of the domUs automatically started, even
though they are set to. If I do an xm list -l [dumU_name] they are set
to start with:
(on_xend_start start)

If I run virt-manager and look at the details of the domU it shows they
are set for auto start. 

*xend and xendomains are also set to start and looks like they did.
*dom0 is set with dom0_mem=2048M
*ballooning is disabled

Any ideas or suggestions on either issue?

Thanks,
James


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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Mysterious crash on SLES11; VMs did not autostart, James Pifer <=