[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Win 2k3 VM restarting continuously.
Hello, We have a dom0 system running Xen v4.1. There are two virtual machines running on this platform one is a windows 2003 server and other is a RHEL server. We have installed PV drivers(0.9.11.13) on Windows server. Issue is that Windows server keeps restarting every 30 Min with the event "unexpected shutdown occurred". A dump is created C:\windows\memory.dmp when system restarts. When I open the dump in WinDbg and execute command !analyze -v output as below is produced. I have the dump if someone wants to have a look at it I can send it to him/her. When we attempted to install 0.11.0.373 version of drivers system was not coming up and entire setup had to be re-installed. I would appreciate any help or guidance in resolving this issue. Command output: ================================================================================ ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: xennet FAULTING_MODULE: e0800000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4954cba2 EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid FAULTING_IP: nt!RtlUnwind+d9b e0878abb cc int 3 TRAP_FRAME: e089a0a0 -- (.trap 0xffffffffe089a0a0) ErrCode = 00000000 eax=00000002 ebx=e089a188 ecx=e0873810 edx=00000056 esi=e0873811 edi=00000002 eip=e0878abc esp=e089a114 ebp=e089a128 iopl=0 nv up ei pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000206 nt!RtlUnwind+0xd9c: e0878abc 5b pop ebx Resetting default scope DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x8E CURRENT_IRQL: 0 ASSERT_DATA: total_length <= xi->config_mtu + XN_HDR_SIZE ASSERT_FILE_LOCATION: c:\projects\win-pvdrivers.hg\xennet\xennet_rx.c at Line 744 LAST_CONTROL_TRANSFER: from e082d820 to e0827c83 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. e089a128 e0878b31 00000002 e0873810 00000056 nt!RtlUnwind+0xd9c e089a144 e08720bc e089a158 e089a160 f50a0600 nt!RtlUnwind+0xe11 e089a168 e08738ec e0873810 e089a188 00000002 nt!DbgPrompt+0x3c e089a45c f509acf9 f50a0600 f50a0520 000002e8 nt!RtlAssert+0x5c e089a5a8 e0832110 fd416984 fd413000 00000000 xennet+0x6cf9 e089a600 e088de4f 00000000 0000000e 00000000 nt!ZwYieldExecution+0x248c e089db40 00000000 e089db48 e089db48 e089db50 nt!KiDispatchInterrupt+0x32f STACK_COMMAND: .trap 0xffffffffe089a0a0 ; kb FOLLOWUP_IP: xennet+6cf9 f509acf9 c785ccfeffff00000000 mov dword ptr [ebp-134h],0 SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: xennet+6cf9 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: xennet.sys FAILURE_BUCKET_ID: 0x8E_xennet+6cf9 BUCKET_ID: 0x8E_xennet+6cf9 Followup: MachineOwner _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |