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

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[Xen-devel] Re: win-pv assertion failed while migrating

from [alice wan] [Permanent Link][Original]
To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: win-pv assertion failed while migrating
From: alice wan <wanjia19870902@xxxxxxxxx>
Date: Mon, 14 Feb 2011 14:11:19 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 13 Feb 2011 22:12:57 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=f3vdVwQJCq7EcsVygRHq8hiTaZ0IOtkdb4rwEL9G/tE=; b=rtsgM0bMPhHgMocT9H+mDYdnv6s8R7862UKHn03Y9K3fkmlRD7S0C7abitNbLmo1Gm uZOeB9Bf/9hcvXyq88zA3r3BNbWQS82+ombIo9e/iBrgnrehuef4CL+ZrTLreLh/ltae fiUy84M73EQ/xfycRsmDpEZacKWOGo0QGqBaU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=emPOLFbsqmaCy65GLe3kAInoEHRCJO+EbRf4Rj5JMc1Q8ZQ446pshfrH9KUqj2xrA+ 0UXG19QKmoeSyULdNkvkXRFbTPR0M/Frj5OTdP8lpv52xq56IuIIMZdkIR5mmzeWfhVU Ssa8TSZDWgb/oL2AK+58HNo4kBIFO4I8N3gbM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01C554C2@trantor>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTi=0_Lago4q7vnj67rB_yZLhaJeSKGnL5zSK71iv@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01C55475@trantor> <AANLkTin33XbNLUaJTQBQee+u0w4FOw_aMRRx3o3juDij@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01C554C2@trantor>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
yes, windows 2003-32.
 
my test is migrate vm between host A and host B continually(xen4.0.0.0+2.6.31.13)
 
Almost after automatic migrate script ran for one day, this problem appeared
 
maybe i can also do some test on xen4.0.1+2.6.32.x to check whether it matters kernel or pv driver.

2011/2/14 James Harper <james.harper@xxxxxxxxxxxxxxxx>
>
> i upgrade to the latest version(changeset 849),  assertion failure
still
> exists. due to some reason, my env must be xen4.0.0, 2.6.31.13.
> if there's some patches about xen,dom0 to deal with this problem, i
can
> backport to current version
>

I don't have machines that are similar enough to be able to actually
test migration, so the best I can do is test suspend/restore. Can you
try doing that and see if you can reproduce the problem under those
circumstances?

Also, what OS are you using? Is it Windows 2003?

James

> XenNet --> XenNet_SuspendResume
> XenNet     New state SR_STATE_RESUMING
> XenNet <-- XenNet_SuspendResume
> XenPCI --> EvtChn_PdoEventChannelDpc
> XenPCI <-- EvtChn_PdoEventChannelDpc
> XenPCI     waiting...
> XenPCI     waiting...
> XenNet --> XenNet_Resume
> XenNet --> XenNet_TxResumeStart
> XenNet <-- XenNet_TxResumeStart
> XenNet --> XenNet_RxResumeStart
> XenNet <-- XenNet_RxResumeStart
> XenNet --> XenNet_ConnectBackend
> XenNet     XEN_INIT_TYPE_13
> XenNet     XEN_INIT_TYPE_VECTORS
> XenNet     XEN_INIT_TYPE_DEVICE_STATE - 81F2CFB4
> XenNet     XEN_INIT_TYPE_RING - tx-ring-ref = FFA99000
> XenNet     XEN_INIT_TYPE_RING - rx-ring-ref = FFA98000
> XenNet     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 8
> XenNet     XEN_INIT_TYPE_READ_STRING - mac = 00:16:3e:e0:00:00
> XenNet     XEN_INIT_TYPE_READ_STRING - feature-sg = 1
> XenNet     XEN_INIT_TYPE_READ_STRING - feature-gso-tcpv4 = 1
> XenNet     XEN_INIT_TYPE_17
> XenNet <-- XenNet_ConnectBackend
> XenNet --> XenNet_RxResumeEnd
> XenNet <-- XenNet_RxResumeEnd
> XenNet --> XenNet_TxResumeEnd
> XenNet <-- XenNet_TxResumeEnd
> XenNet     *Setting suspend_resume_state_fdo = 2
> XenNet --> XenNet_SuspendResume
> XenNet     New state SR_STATE_RESUMING
> XenNet <-- XenNet_SuspendResume
> XenNet --> XenNet_Resume
> XenNet     *Notifying event channel 5
> XenNet --> XenNet_TxResumeStart
> XenNet <-- XenNet_Resume
> XenPCI     EVT_ACTION_TYPE_SUSPEND
> XenPCI --> EvtChn_PdoEventChannelDpc
> XenPCI <-- EvtChn_PdoEventChannelDpc
> XenPCI     fdo state set to 2
> XenNet <-- XenNet_TxResumeStart
> XenPCI <-- XenPci_Pdo_ChangeSuspendState
> XenNet --> XenNet_RxResumeStart
> XenPCI --> XenPci_Pdo_ChangeSuspendState
> XenNet <-- XenNet_RxResumeStart
> XenPCI     setting pdo state to 0
> XenNet --> XenNet_ConnectBackend
> XenPCI     Notifying event channel 5
> XenNet     XEN_INIT_TYPE_13
> XenPCI     EVT_ACTION_TYPE_SUSPEND
> XenNet     XEN_INIT_TYPE_VECTORS
> XenNet --> XenNet_SuspendResume
> XenNet     XEN_INIT_TYPE_DEVICE_STATE - 81F2CFB4
> XenNet     New state 2
> XenNet     XEN_INIT_TYPE_RING - tx-ring-ref = FFA99000
> XenNet     Notifying event channel 5
> XenNet <-- XenNet_SuspendResume
> XenNet     XEN_INIT_TYPE_RING - rx-ring-ref = FFA98000
>
> *** Assertion failed: xi->rx_ring_pbs[id] != (USHORT)0xFFFF
> ***   Source File: e:\win-pvdrivers.hg\xennet\xennet_rx.c, line 640
>
> XenPCI     EVT_ACTION_TYPE_SUSPEND
> Log-dirty command enable
> XenVbd --> DriverEntry
> XenVbd     IRQL = 31
> XenVbd     DriverObject = 00000000, RegistryPath = 00000000
> XenVbd --> XenVbd_HwScsiFindAdapter
> XenVbd     IRQL = 31
> XenVbd     xvdd = 81973300
> XenVbd     BusInterruptLevel = 28
> XenVbd     BusInterruptVector = 01c
> XenVbd     NumberOfAccessRanges = 1
> XenVbd     RangeStart = 1f928000, RangeLength = 00001000
> XenVbd     XEN_INIT_TYPE_VECTORS
> XenVbd     XEN_INIT_TYPE_DEVICE_STATE - 81FB93CC
> XenVbd     XEN_INIT_TYPE_RING - ring-ref = FFA9B000
> XenVbd     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
> XenVbd     XEN_INIT_TYPE_READ_STRING - device-type = disk
> XenVbd     device-type = Disk
> XenVbd     XEN_INIT_TYPE_READ_STRING - mode = w
> XenVbd     mode = w
> XenVbd     XEN_INIT_TYPE_READ_STRING - sectors = 104857600
> XenVbd     XEN_INIT_TYPE_READ_STRING - sector-size = 512
> XenVbd     XEN_INIT_TYPE_GRANT_ENTRIES - entries = 11
> XenVbd     qemu_hide_flags_value = 3
> XenVbd     aligned_buffer_data = 81975274
> XenVbd     aligned_buffer = 81976000
> XenVbd     ConfigInfo->MaximumTransferLength = 4096
> XenVbd     ConfigInfo->NumberOfPhysicalBreaks = 0
> XenVbd     ConfigInfo->CachesData was initialised to 0
> XenVbd     Dma64BitAddresses not supported
> XenVbd <-- XenVbd_HwScsiFindAdapter
> XenVbd --> XenVbd_HwScsiInitialize
> XenVbd     IRQL = 31
> XenVbd     dump_mode = 1
> XenVbd <-- XenVbd_HwScsiInitialize
> XenVbd     Command = INQUIRY
> XenVbd --> XenVbd_HwScsiResetBus
> XenVbd     IRQL = 31
> XenVbd <-- XenVbd_HwScsiResetBus
> XenVbd     Command = SCSIOP_START_STOP_UNIT
> XenVbd     Command = READ_CAPACITY
> XenVbd <-- DriverEntry
> XenVbd     max_dump_mode_blocks = 8
> XenVbd     max_dump_mode_length = 4096
>
> *** Assertion failed: srb != NULL
> ***   Source File: e:\win-pvdrivers.hg\xenvbd\xenvbd_scsiport.c, line
988
>
> XenNet --> XenNet_Shutdown
> XenNet <-- XenNet_Shutdown
> XenPCI     Bug check 0x0000008E (0x80000003, 0x80878113, 0xF885993C,
> 0x00000000)
>
>
>
> 2011/2/12 James Harper <james.harper@xxxxxxxxxxxxxxxx>
>
>
>       Changeset 841 fixed quite a few things to do with suspend and
resume.
>       Try the very latest version.
>
>       James
>
>
>       > -----Original Message-----
>       > From: alice wan [mailto:wanjia19870902@xxxxxxxxx]
>       > Sent: Saturday, 12 February 2011 20:09
>       > To: James Harper
>       > Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>       > Subject: win-pv assertion failed while migrating
>       >
>       > hi all
>       >
>       > i migrated a guest os with win-pv driver (changset 820) ,
xc_save
>       process hung
>       > like that
>       >
>       > (gdb) bt
>       > #0  0x0000003482ec5f3b in read () from /lib64/libc.so.6
>       > #1  0x00007f53b42754cf in read_exact () from
>       /usr/lib64/libxenctrl.so.4.0
>       > #2  0x00007f53b427b283 in xc_evtchn_pending () from
>       > /usr/lib64/libxenctrl.so.4.0
>       > #3  0x00007f53b404b5e7 in xc_await_suspend () from
>       > /usr/lib64/libxenguest.so.4.0
>       > #4  0x0000000000401305 in suspend ()
>       > #5  0x00007f53b404f684 in suspend_and_state () from
>       > /usr/lib64/libxenguest.so.4.0
>       > #6  0x00007f53b4051d4f in xc_domain_save () from
>       /usr/lib64/libxenguest.so.4.0
>       > #7  0x0000000000401539 in main ()
>       >
>       > the pv debug info in qemu log is as following:
>       >
>       > XenPCI <-- XenPci_DeviceWatchHandler
>       > XenNet --> XenNet_Resume
>       > XenPCI --> XenPci_DeviceWatchHandler
>       > XenNet --> XenNet_TxResumeStart
>       > XenPCI <-- XenPci_DeviceWatchHandler
>       > XenNet <-- XenNet_TxResumeStart
>       > XenPCI --> XenPci_UpdateBackendState
>       > XenNet --> XenNet_RxResumeStart
>       > XenNet <-- XenNet_RxResumeStart
>       > XenPCI     state unchanged
>       > XenNet --> XenNet_ConnectBackend
>       > XenPCI --> XenPci_DeviceWatchHandler
>       > XenNet     XEN_INIT_TYPE_13
>       > XenPCI <-- XenPci_DeviceWatchHandler
>       > XenNet     XEN_INIT_TYPE_VECTORS
>       > XenNet     XEN_INIT_TYPE_DEVICE_STATE - 81F40FB4
>       > XenNet     XEN_INIT_TYPE_RING - tx-ring-ref = FFB1F000
>       > XenNet     XEN_INIT_TYPE_RING - rx-ring-ref = FFB1E000
>       > XenNet     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
>       > XenNet     XEN_INIT_TYPE_READ_STRING - mac = 00:16:3e:e0:00:13
>       > XenNet     XEN_INIT_TYPE_READ_STRING - feature-sg = 1
>       > XenNet     XEN_INIT_TYPE_READ_STRING - feature-gso-tcpv4 = 1
>       > XenNet     XEN_INIT_TYPE_17
>       > XenNet <-- XenNet_ConnectBackend
>       > XenNet --> XenNet_RxResumeEnd
>       > XenNet <-- XenNet_RxResumeEnd
>       > XenNet --> XenNet_TxResumeEnd
>       > XenNet <-- XenNet_TxResumeEnd
>       > XenNet     *Setting suspend_resume_state_fdo = 2
>       > XenNet --> XenNet_SuspendResume
>       > XenNet     New state SR_STATE_RESUMING
>       > XenNet <-- XenNet_SuspendResume
>       > XenNet --> XenNet_Resume
>       > XenNet     *Notifying event channel 5
>       > XenNet --> XenNet_TxResumeStart
>       > XenNet <-- XenNet_Resume
>       > XenPCI     EVT_ACTION_TYPE_SUSPEND
>       > XenPCI --> EvtChn_PdoEventChannelDpc
>       > XenPCI <-- EvtChn_PdoEventChannelDpc
>       > XenPCI     fdo state set to 2
>       > XenNet <-- XenNet_TxResumeStart
>       > XenPCI <-- XenPci_Pdo_ChangeSuspendState
>       > XenNet --> XenNet_RxResumeStart
>       > XenPCI --> XenPci_Pdo_ChangeSuspendState
>       > XenNet <-- XenNet_RxResumeStart
>       > XenPCI     setting pdo state to 0
>       > XenNet --> XenNet_ConnectBackend
>       > XenPCI     Notifying event channel 5
>       > XenNet     XEN_INIT_TYPE_13
>       > XenPCI     EVT_ACTION_TYPE_SUSPEND
>       > XenNet     XEN_INIT_TYPE_VECTORS
>       > XenNet --> XenNet_SuspendResume
>       > XenNet     XEN_INIT_TYPE_DEVICE_STATE - 81F40FB4
>       > XenNet     New state 2
>       > XenNet     Notifying event channel 5
>       > XenNet     XEN_INIT_TYPE_RING - tx-ring-ref = FFB1F000
>       > XenNet <-- XenNet_SuspendResume
>       > XenPCI     EVT_ACTION_TYPE_SUSPEND
>       >
>       > *** Assertion failed: xi->rx_ring_pbs[id] != (USHORT)0xFFFF
>       > ***   Source File:
c:\projects\win-pvdrivers.hg\xennet\xennet_rx.c,
>       line 639
>       >
>       > XenNet     XEN_INIT_TYPE_RING - rx-ring-ref = FFB1E000
>       > XenVbd --> DriverEntry
>       > XenVbd     IRQL = 31
>       > XenVbd     DriverObject = 00000000, RegistryPath = 00000000
>       > XenVbd --> XenVbd_HwScsiFindAdapter
>       > XenVbd     IRQL = 31
>       > XenVbd     xvdd = 819F5300
>       > XenVbd     BusInterruptLevel = 28
>       > XenVbd     BusInterruptVector = 01c
>       > XenVbd     NumberOfAccessRanges = 1
>       > XenVbd     RangeStart = 1f98a000, RangeLength = 00001000
>       > XenVbd     XEN_INIT_TYPE_VECTORS
>       > XenVbd     XEN_INIT_TYPE_DEVICE_STATE - 81F96AB4
>       > XenVbd     XEN_INIT_TYPE_RING - ring-ref = 81F3C000
>       > XenVbd     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
>       > XenVbd     cached_use_other = 1
>       > XenVbd     XEN_INIT_TYPE_READ_STRING - device-type = disk
>       > XenVbd     device-type = Disk
>       > XenVbd     XEN_INIT_TYPE_READ_STRING - mode = w
>       > XenVbd     mode = w
>       > XenVbd     XEN_INIT_TYPE_READ_STRING - sectors = 104857600
>       > XenVbd     XEN_INIT_TYPE_READ_STRING - sector-size = 512
>       > XenVbd     XEN_INIT_TYPE_GRANT_ENTRIES - entries = 11
>       > XenVbd     qemu_hide_flags_value = 3
>       > XenVbd     aligned_buffer_data = 819F7274
>       > XenVbd     aligned_buffer = 819F8000
>       > XenVbd     ConfigInfo->MaximumTransferLength = 4096
>       > XenVbd     ConfigInfo->NumberOfPhysicalBreaks = 0
>       > XenVbd     Dma64BitAddresses not supported
>       > XenVbd <-- XenVbd_HwScsiFindAdapter
>       > XenVbd --> XenVbd_HwScsiInitialize
>       > XenVbd     IRQL = 31
>       > XenVbd     dump_mode = 1
>       > XenVbd <-- XenVbd_HwScsiInitialize
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > Log-dirty command enable
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd --> HwScsiStartIo (Suspending/Resuming)
>       > XenVbd <-- HwScsiStartIo (Suspending/Resuming)
>       > XenVbd ScsiPortInitialize failed with status 0xc0000001
>       > XenVbd <-- DriverEntry
>       > XenNet --> XenNet_Shutdown
>       > XenNet <-- XenNet_Shutdown
>       > XenPCI     Bug check 0x0000008E (0x80000003, 0x80878113,
0xF885AAF4,
>       > 0x00000000)
>       > reset requested in cpu_handle_ioreq.
>       > Issued domain 473 reboot
>       >
>       > environment: xen 4.0.0 +2.6.31.13,
windows2003+win-pv(changeset 820)
>       >
>       > i need your help ,thanks in advance
>       >
>
>


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Xen-devel] Re: Unable to single step HVM guest, Daniel J Mathew
Next by Date:  [Xen-devel] RE: win-pv assertion failed while migrating, James Harper
Previous by Thread:  [Xen-devel] RE: win-pv assertion failed while migrating, James Harper
Next by Thread:  [Xen-devel] RE: win-pv assertion failed while migrating, James Harper
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy