Alexander Ivanov
2009-Dec-18 22:34 UTC
[Xen-devel] Win2003x64 VM unexpected reboot - PV disk driver?
Hello, I have this VM running for couple of days with pretty low load, today''s the first time there were some real activity (SQL server bulk data import), after about 2 hours of pretty good activity (disk/CPU) VM restarted. I''m running Xen3.4.2 on Centos 5.4, 2.6.18-164.6.1.el5xen #1 SMP Tue Nov 3 16:48:13 EST 2009 x86_64 x86_64 x86_64 GNU/Linux with GPLPV (0.10.0.143_debug). Xend log only have this: [2009-12-18 15:44:21 7186] INFO (XendDomainInfo:1903) Domain has shutdown: name=cin-cope id=7 reason=reboot. [2009-12-18 15:44:21 7186] DEBUG (XendDomainInfo:2732) XendDomainInfo.destroy: domid=7 [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2207) Destroying device model [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2214) Releasing devices [2009-12-18 15:44:22 7186] INFO (image:556) cin-cope device model terminated [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2227) Removing vif/0 [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2227) Removing vbd/768 [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768 [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2227) Removing vbd/832 [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/832 [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2227) Removing vbd/5632 [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632 [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2227) Removing vfb/0 [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0 [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2227) Removing console/0 [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0 [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2212) No device model [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2214) Releasing devices And Qemu log (last few lines) is here: TcpIpChecksumNdisTask V4Transmit.IpOptionsSupported = 0 V4Transmit.TcpOptionsSupported = 1 V4Transmit.TcpChecksum = 1 V4Transmit.UdpChecksum = 0 V4Transmit.IpChecksum = 0 V4Receive.IpOptionsSupported = 0 V4Receive.TcpOptionsSupported = 0 V4Receive.TcpChecksum = 1 V4Receive.UdpChecksum = 0 V4Receive.IpChecksum = 0 V6Transmit.IpOptionsSupported = 0 V6Transmit.TcpOptionsSupported = 0 V6Transmit.TcpChecksum = 0 V6Transmit.UdpChecksum = 0 V6Receive.IpOptionsSupported = 0 V6Receive.TcpOptionsSupported = 0 V6Receive.TcpChecksum = 0 V6Receive.UdpChecksum = 0 TcpLargeSendNdisTask MaxOffLoadSize = 61440 MinSegmentCount = 4 TcpOptions = 0 IpOptions = 0 XenNet (BUFFER_TOO_SHORT 152 > 0) Get Unknown OID 0x10117 XenPCI --> XenPci_EvtDeviceUsageNotification XenPCI notification_type = Paging, flag = 1 XenPCI <-- XenPci_EvtDeviceUsageNotification XenPCI --> XenPciPdo_EvtDeviceUsageNotification XenPCI path = device/vbd/768 XenPCI notification_type = Paging, flag = 1 XenPCI <-- XenPciPdo_EvtDeviceUsageNotification XenNet (BUFFER_TOO_SHORT 152 > 0) AFD: AfdPprThreshold value queried from transport: 2960 Set OID_802_3_MULTICAST_LIST Length = 12 Entries = 2 Get Unknown OID 0xd010122 XenPCI --> XenPci_EvtDeviceFileCreate XenPCI --> XenBus_DeviceFileInit XenPCI <-- XenBus_DeviceFileInit XenPCI <-- XenPci_EvtDeviceFileCreate XenPCI --> XenPci_IoWatch XenPCI found pending read - MinorFunction = 0, length = 1024 XenPCI <-- XenBus_ProcessReadRequest XenPCI <-- XenPci_IoWatch Package ''Microsoft SQL Management Studio Package'' failed to load. XenVbd --> DriverEntry XenVbd IRQL = 31 XenVbd DriverObject = 00000000, RegistryPath = 00000000 XenVbd --> XenVbd_HwScsiFindAdapter XenVbd IRQL = 31 XenVbd xvdd = 89F1A300 XenVbd BusInterruptLevel = 28 XenVbd BusInterruptVector = 01c XenVbd NumberOfAccessRanges = 1 XenVbd RangeStart = 0f9ba000, RangeLength = 00001000 XenVbd XEN_INIT_TYPE_VECTORS XenVbd XEN_INIT_TYPE_DEVICE_STATE - 8AABB3CC XenVbd XEN_INIT_TYPE_RING - ring-ref = 8AAA8000 XenVbd XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 9 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 = 25165824 XenVbd XEN_INIT_TYPE_READ_STRING - sector-size = 512 XenVbd XEN_INIT_TYPE_GRANT_ENTRIES - entries = 11 XenVbd Dma64BitAddresses 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 Xen Operation returned error XenVbd Operation = Write XenVbd Sector = 00085577, Count = 64 XenVbd Command = REQUEST_SENSE XenVbd Xen Operation returned error XenVbd Operation = Write XenVbd Sector = 00085577, Count = 64 XenVbd Command = REQUEST_SENSE XenVbd Xen Operation returned error XenVbd Operation = Write XenVbd Sector = 00085577, Count = 64 XenVbd Command = REQUEST_SENSE XenNet --> XenNet_Shutdown XenNet <-- XenNet_Shutdown XenPCI Bug check 0x0000000A (0x000004DC, 0x000000FF, 0x00000000, 0x80A5C250) reset requested in cpu_handle_ioreq. Issued domain 7 reboot Looks like disk problem? Thanks Alex _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Alexander Ivanov
2009-Dec-18 22:43 UTC
[Xen-devel] Re: Win2003x64 VM unexpected reboot - PV disk driver?
Correction - that was x32 win VM. On Fri, Dec 18, 2009 at 5:34 PM, Alexander Ivanov <apivanov@gmail.com>wrote:> Hello, > I have this VM running for couple of days with pretty low load, today''s the > first time there were some real activity (SQL server bulk data import), > after about 2 hours of pretty good activity (disk/CPU) VM restarted. I''m > running Xen3.4.2 on Centos 5.4, 2.6.18-164.6.1.el5xen #1 SMP Tue Nov 3 > 16:48:13 EST 2009 x86_64 x86_64 x86_64 GNU/Linux with GPLPV > (0.10.0.143_debug). > > Xend log only have this: > > [2009-12-18 15:44:21 7186] INFO (XendDomainInfo:1903) Domain has shutdown: > name=cin-cope id=7 reason=reboot. > [2009-12-18 15:44:21 7186] DEBUG (XendDomainInfo:2732) > XendDomainInfo.destroy: domid=7 > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2207) Destroying device > model > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2214) Releasing devices > [2009-12-18 15:44:22 7186] INFO (image:556) cin-cope device model > terminated > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2227) Removing vif/0 > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:1134) > XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2227) Removing vbd/768 > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:1134) > XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768 > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2227) Removing vbd/832 > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:1134) > XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/832 > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2227) Removing vbd/5632 > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:1134) > XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/5632 > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2227) Removing vfb/0 > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:1134) > XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0 > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2227) Removing console/0 > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:1134) > XendDomainInfo.destroyDevice: deviceClass = console, device = console/0 > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2212) No device model > [2009-12-18 15:44:22 7186] DEBUG (XendDomainInfo:2214) Releasing devices > > > And Qemu log (last few lines) is here: > > TcpIpChecksumNdisTask > V4Transmit.IpOptionsSupported = 0 > V4Transmit.TcpOptionsSupported = 1 > V4Transmit.TcpChecksum = 1 > V4Transmit.UdpChecksum = 0 > V4Transmit.IpChecksum = 0 > V4Receive.IpOptionsSupported = 0 > V4Receive.TcpOptionsSupported = 0 > V4Receive.TcpChecksum = 1 > V4Receive.UdpChecksum = 0 > V4Receive.IpChecksum = 0 > V6Transmit.IpOptionsSupported = 0 > V6Transmit.TcpOptionsSupported = 0 > V6Transmit.TcpChecksum = 0 > V6Transmit.UdpChecksum = 0 > V6Receive.IpOptionsSupported = 0 > V6Receive.TcpOptionsSupported = 0 > V6Receive.TcpChecksum = 0 > V6Receive.UdpChecksum = 0 > TcpLargeSendNdisTask > MaxOffLoadSize = 61440 > MinSegmentCount = 4 > TcpOptions = 0 > IpOptions = 0 > XenNet (BUFFER_TOO_SHORT 152 > 0) > Get Unknown OID 0x10117 > XenPCI --> XenPci_EvtDeviceUsageNotification > XenPCI notification_type = Paging, flag = 1 > XenPCI <-- XenPci_EvtDeviceUsageNotification > XenPCI --> XenPciPdo_EvtDeviceUsageNotification > XenPCI path = device/vbd/768 > XenPCI notification_type = Paging, flag = 1 > XenPCI <-- XenPciPdo_EvtDeviceUsageNotification > XenNet (BUFFER_TOO_SHORT 152 > 0) > AFD: AfdPprThreshold value queried from transport: 2960 > Set OID_802_3_MULTICAST_LIST > Length = 12 > Entries = 2 > Get Unknown OID 0xd010122 > XenPCI --> XenPci_EvtDeviceFileCreate > XenPCI --> XenBus_DeviceFileInit > XenPCI <-- XenBus_DeviceFileInit > XenPCI <-- XenPci_EvtDeviceFileCreate > XenPCI --> XenPci_IoWatch > XenPCI found pending read - MinorFunction = 0, length = 1024 > XenPCI <-- XenBus_ProcessReadRequest > XenPCI <-- XenPci_IoWatch > Package ''Microsoft SQL Management Studio Package'' failed to load. > XenVbd --> DriverEntry > XenVbd IRQL = 31 > XenVbd DriverObject = 00000000, RegistryPath = 00000000 > XenVbd --> XenVbd_HwScsiFindAdapter > XenVbd IRQL = 31 > XenVbd xvdd = 89F1A300 > XenVbd BusInterruptLevel = 28 > XenVbd BusInterruptVector = 01c > XenVbd NumberOfAccessRanges = 1 > XenVbd RangeStart = 0f9ba000, RangeLength = 00001000 > XenVbd XEN_INIT_TYPE_VECTORS > XenVbd XEN_INIT_TYPE_DEVICE_STATE - 8AABB3CC > XenVbd XEN_INIT_TYPE_RING - ring-ref = 8AAA8000 > XenVbd XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 9 > 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 = 25165824 > XenVbd XEN_INIT_TYPE_READ_STRING - sector-size = 512 > XenVbd XEN_INIT_TYPE_GRANT_ENTRIES - entries = 11 > XenVbd Dma64BitAddresses 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 Xen Operation returned error > XenVbd Operation = Write > XenVbd Sector = 00085577, Count = 64 > XenVbd Command = REQUEST_SENSE > XenVbd Xen Operation returned error > XenVbd Operation = Write > XenVbd Sector = 00085577, Count = 64 > XenVbd Command = REQUEST_SENSE > XenVbd Xen Operation returned error > XenVbd Operation = Write > XenVbd Sector = 00085577, Count = 64 > XenVbd Command = REQUEST_SENSE > XenNet --> XenNet_Shutdown > XenNet <-- XenNet_Shutdown > XenPCI Bug check 0x0000000A (0x000004DC, 0x000000FF, 0x00000000, > 0x80A5C250) > reset requested in cpu_handle_ioreq. > Issued domain 7 reboot > > Looks like disk problem? > > Thanks > Alex > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel