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] Windows HVM Domain crashing periodically

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Windows HVM Domain crashing periodically
From: "Tait Clarridge" <Tait.Clarridge@xxxxxxxxxxxx>
Date: Tue, 13 May 2008 11:19:16 -0400
Delivery-date: Tue, 13 May 2008 08:20:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aci1DLTB+seFRHeRRtOU5YLFKz9oxA==
Thread-topic: Windows HVM Domain crashing periodically
Hello All,

I was wondering if anyone has run into this problem too. One of my
domains periodically crashes where it becomes unresponsive but is still
listed when 'xm list' is run. 

Dmesg gives me the following:

qemu-dm[7638]: segfault at 0000000000000000 rip 0000000000000000 rsp
0000000041400c18 error 14


And when I search through the qemu-dm logs (for the time in question), I
get this:

domid: 19
qemu: the number of cpus is 2
Watching /local/domain/19/logdirty/next-active
qemu_map_cache_init nr_buckets = 10000
shared page at pfn 7ffff
buffered io page at pfn 7fffd
xs_read(/vm/6cbe6c1a-52bf-21df-3c5c-81439c860d23/rtc/timeoffset): read
error
xs_read(): vncpasswd get error.
/vm/6cbe6c1a-52bf-21df-3c5c-81439c860d23/vncpasswd.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Triggered log-dirty buffer switch
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
xs_write(/vm/6cbe6c1a-52bf-21df-3c5c-81439c860d23/rtc/timeoffset,
rtc/timeoffset): write error
xs_write(/vm/6cbe6c1a-52bf-21df-3c5c-81439c860d23/rtc/timeoffset,
rtc/timeoffset): write error
xs_write(/vm/6cbe6c1a-52bf-21df-3c5c-81439c860d23/rtc/timeoffset,
rtc/timeoffset): write error


uname -a:

Linux *removed* 04 2.6.18-53.1.4.el5xen #1 SMP Fri Nov 30 01:21:23 EST
2007 x86_64 x86_64 x86_64 GNU/Linux

It is a CentOS5 system with the packaged xen kernel installed. Every
other Windows VM on this host works fine and has not crashed. Any ideas
as to why this is happening? The system has roughly 16 GB of memory and
12 Opteron 8220 cores.

Here is the config file:


kernel = '/usr/lib/xen/boot/hvmloader'
builder = 'hvm'
memory = 2048
name = "domain"
vcpus = 2
vif = ['type=ioemu,bridge=xenbr905']
disk = ['file:/disk.img,ioemu:hda,w']
device_model='/usr/lib64/xen/bin/qemu-dm'
boot = 'c'
sdl = 0
pae = 1
acpi = 1
apic = 1
vnc = 1
vncviewer = 1
audio = 0
ne2000 = 0
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'

I thank anyone that can give me some assistance.

Cheers,
Tait


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

<Prev in Thread] Current Thread [Next in Thread>