vinu.velayudhan@lsi.com
2009-Jun-27 01:00 UTC
[Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
Hi, I am trying to do a scsi hotplug to a Windows GOS using the xm scsi-attach command. This is my configuration RHEL 5.2 DOM0 with Xen 3.3 32 bit Windows 2k3 GOS with WindowsXenPV-0.9.4 installed. boot.ini has /gplpv added I have a SATA harddisk which I am tryng to hotplug to win GOS. The output of lsscsi is as below #lsscsi [0:0:0:0] disk ATA ST380013AS 3.18 /dev/sda [1:0:0:0] disk ATA WDC WD2500YS-01M 02.0 /dev/sdb and I am using the below command to attach /dev/sdb to GOS # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 512 8 r----- 3381.5 Windows2003 5 256 1 -b---- 35.7 #xm scsi-attach Windows2003 1:0:0:0 1:0:0:0 # As soon as I run the above command, I see a pop up coming in Win2k3 GOS indicating that a xen vscsi device is hotplugged. But when I go to the Device Manager in Windows and look at this device, it appears with an Yellow bang and the driver tab indicates error Code 10 (reinstall driver). I tried this multiple times, but always end up at the same state. Have anyone tried something similar ? Do you know what might going wrong here ? Thanks In Advance, VinuV _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper
2009-Jun-29 22:50 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
> Hi, > > I am trying to do a scsi hotplug to a Windows GOS using the xmscsi-attach> command. > > This is my configuration > RHEL 5.2 DOM0 with Xen 3.3 > 32 bit Windows 2k3 GOS with WindowsXenPV-0.9.4 installed. boot.ini has/gplpv> added > > I have a SATA harddisk which I am tryng to hotplug to win GOS. Theoutput of> lsscsi is as below > #lsscsi > [0:0:0:0] disk ATA ST380013AS 3.18 /dev/sda > [1:0:0:0] disk ATA WDC WD2500YS-01M 02.0 /dev/sdb > > and I am using the below command to attach /dev/sdb to GOS > # xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 512 8r-----> 3381.5 > Windows2003 5 256 1 -b----35.7> > #xm scsi-attach Windows2003 1:0:0:0 1:0:0:0 > # > > As soon as I run the above command, I see a pop up coming in Win2k3GOS> indicating that a xen vscsi device is hotplugged. But when I go to theDevice> Manager in Windows and look at this device, it appears with an Yellowbang and> the driver tab indicates error Code 10 (reinstall driver). > > I tried this multiple times, but always end up at the same state. Haveanyone> tried something similar ? Do you know what might going wrong here ? >It should work, it certainly used to. Can you please run DebugView from sysinternals.com on your windows machine, turn on kernel logging, then try the hotplug? That should capture some debug logging. Email it to me and I''ll have a look. Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Velayudhan, Vinu
2009-Jun-30 00:57 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
Here the Windows debug log, when I do a SCSI hotplug from Dom0. XenPCI --> XenPci_DeviceWatchHandler XenPCI path = device/vscsi/1 XenPCI count = 3 XenPCI Invalidating Device Relations XenPCI IRP_MN_QUERY_DEVICE_RELATIONS XenVbd shadow_min_free = 31 XenPCI BusRelations XenPCI --> XenPci_Pnp_QueryBusRelations XenPCI --> XenPci_SendAndWaitForIrp XenPCI --> XenPci_Pnp_IoCompletion XenPCI <-- XenPci_Pnp_IoCompletion XenPCI <-- XenPci_SendAndWaitForIrp XenPCI <-- XenPci_Pnp_QueryBusRelations XenVbd shadow_min_free = 32 XenPCI --> XenPci_Pnp_QueryBusRelationsCallback XenPCI <-- XenPci_DeviceWatchHandler XenPCI Existing device device/vbd/768 XenPCI Existing device device/vif/0 XenPCI Existing device device/console/0 XenPCI --> XenPci_DeviceWatchHandler XenVbd shadow_min_free = 32 XenPCI New device device/vscsi/1 XenPCI <-- XenPci_Pnp_QueryBusRelationsCallback XenVbd --> XenVbd_Pnp XenVbd Unknown Minor = 7 XenVbd <-- XenVbd_Pnp XenVbd Command = INQUIRY XenVbd (LUN = 0, EVPD = 0, Page Code = 00) XenVbd (Length = 36) XenVbd (Srb->Databuffer = 817b4428) XenVbd shadow_min_free = 31 XenVbd Command = INQUIRY XenVbd (LUN = 0, EVPD = 1, Page Code = 80) XenVbd (Length = 255) XenVbd (Srb->Databuffer = 817b4428) XenPCI --> XenPci_Pnp_Pdo XenVbd shadow_min_free = 31 XenPCI IRP_MN_QUERY_DEVICE_RELATIONS (status = 00000000) XenPCI <-- XenPci_Pnp_Pdo XenVbd --> XenVbd_Pnp XenVbd Unknown Minor = 7 XenVbd <-- XenVbd_Pnp XenNet --> XenNet_Pnp XenNet Unknown Minor 7 XenVbd shadow_min_free = 31 XenPCI --> XenPci_Pnp_Pdo XenPCI IRP_MN_QUERY_DEVICE_RELATIONS (status = c00000bb) XenPCI <-- XenPci_Pnp_Pdo XenNet <-- XenNet_Pnp XenStub --> XenStub_Irp_Pnp XenStub IRP_MN_QUERY_DEVICE_RELATIONS XenPCI --> XenPci_Pnp_Pdo XenVbd shadow_min_free = 32 XenPCI IRP_MN_QUERY_DEVICE_RELATIONS (status = c00000bb) XenPCI <-- XenPci_Pnp_Pdo XenPCI path = device/vscsi/1/state XenStub <-- XenStub_Irp_Pnp XenPCI --> XenPci_Pnp_Pdo XenPCI IRP_MN_QUERY_ID (status = c00000bb) XenPCI BusQueryDeviceID XenPCI Xen\vscsi XenVbd shadow_min_free = 31 XenPCI <-- XenPci_Pnp_Pdo XenPCI --> XenPci_Pnp_Pdo XenPCI IRP_MN_QUERY_CAPABILITIES (status = c00000bb) XenPCI <-- XenPci_Pnp_Pdo XenPCI --> XenPci_Pnp_Pdo XenPCI IRP_MN_QUERY_DEVICE_TEXT (status = c00000bb) XenVbd shadow_min_free = 30 XenPCI DeviceTextDescription XenPCI Xen vscsi device #1 XenPCI <-- XenPci_Pnp_Pdo XenPCI --> XenPci_Pnp_Pdo XenPCI IRP_MN_QUERY_DEVICE_TEXT (status = c00000bb) XenPCI DeviceTextLocationInformation XenPCI Xen Bus XenVbd shadow_min_free = 31 XenPCI <-- XenPci_Pnp_Pdo XenPCI --> XenPci_Pnp_Pdo XenPCI IRP_MN_QUERY_ID (status = c00000bb) XenPCI BusQueryInstanceID XenPCI 01 XenPCI <-- XenPci_Pnp_Pdo XenPCI --> XenPci_Pnp_Pdo XenPCI IRP_MN_QUERY_ID (status = c00000bb) XenVbd shadow_min_free = 32 XenPCI BusQueryHardwareIDs XenPCI Xen\vscsi XenPCI <-- XenPci_Pnp_Pdo XenPCI --> XenPci_Pnp_Pdo XenPCI count = 4 XenPCI IRP_MN_QUERY_ID (status = c00000bb) XenPCI BusQueryCompatibleIDs XenPCI Xen\vscsi XenVbd shadow_min_free = 31 XenPCI <-- XenPci_Pnp_Pdo XenPCI --> XenPci_Pnp_Pdo XenPCI IRP_MN_QUERY_RESOURCE_REQUIREMENTS (status = c00000bb) XenPCI <-- XenPci_Pnp_Pdo XenPCI --> XenPci_Pnp_Pdo XenPCI IRP_MN_QUERY_BUS_INFORMATION (status = c00000bb) XenPCI <-- XenPci_Pnp_Pdo XenVbd shadow_min_free = 32 XenPCI --> XenPci_Pnp_Pdo XenPCI IRP_MN_QUERY_RESOURCES (status = c00000bb) XenPCI <-- XenPci_Pnp_Pdo XenHide --> XenHide_AddDevice XenHide Description = Xen SCSI Driver XenHide <-- XenHide_AddDevice (gplpv == TRUE && bus_type != GUID_BUS_TYPE_PCI) XenSCSI --> XenScsi_Pnp XenSCSI Unknown Minor = 24 XenVbd shadow_min_free = 32 XenPCI --> XenPci_Pnp_Pdo XenPCI Unhandled Minor = 24, Status = c00000bb XenPCI <-- XenPci_Pnp_Pdo XenSCSI <-- XenScsi_Pnp XenSCSI --> XenScsi_Pnp XenSCSI Unknown Minor = 13 XenVbd shadow_min_free = 31 XenPCI --> XenPci_Pnp_Pdo XenPCI Unhandled Minor = 13, Status = 00000000 XenPCI <-- XenPci_Pnp_Pdo XenSCSI <-- XenScsi_Pnp XenSCSI --> XenScsi_Pnp XenSCSI Unknown Minor = 8 XenPCI <-- XenPci_DeviceWatchHandler XenVbd shadow_min_free = 32 XenPCI --> XenPci_Pnp_Pdo XenPCI Unhandled Minor = 8, Status = c00000bb XenPCI <-- XenPci_Pnp_Pdo XenSCSI <-- XenScsi_Pnp XenSCSI --> XenScsi_Pnp XenSCSI IRP_MN_START_DEVICE - DeviceObject = 8140EA40 XenSCSI PFN[0] = 0000596B XenVbd shadow_min_free = 31 XenSCSI Start = 00000000:0596b000, Length = 4096 XenPCI --> XenPci_Pnp_Pdo XenPCI IRP_MN_START_DEVICE (status = c00000bb) XenPCI --> XenPci_Pnp_StartDevice XenPCI pnp_state = NotStarted XenPCI <-- XenBus_AddWatch XenVbd shadow_min_free = 30 XenPCI irq_number = 11 XenPCI irq_level = 00b XenPCI CmResourceTypeInterrupt XenPCI irq_vector = 181 XenPCI irq_level = 7 XenPCI CmResourceTypeMemory XenPCI Start = 0596b000, Length = 4096 XenVbd shadow_min_free = 32 XenPCI --> XenPci_DeviceWatchHandler XenPCI path = device/vscsi/1/backend-id XenPCI count = 4 XenPCI <-- XenPci_DeviceWatchHandler XenPCI --> XenPci_DeviceWatchHandler XenPCI path = device/vscsi/1/backend XenVbd shadow_min_free = 30 XenPCI Still waiting for 2 (currently 0)... XenPCI count = 4 XenPCI <-- XenPci_DeviceWatchHandler XenPCI Backend State Changed to Initialising XenPCI --> XenPci_DeviceWatchHandler XenVbd shadow_min_free = 32 XenPCI path = device/vscsi/1/state XenPCI count = 4 XenPCI <-- XenPci_DeviceWatchHandler XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 31 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 31 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 31 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 31 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 31 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 31 XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 30 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 31 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 31 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 30 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Still waiting for 2 (currently 1)... XenVbd shadow_min_free = 32 XenPCI Timed out waiting for 2! XenPCI <-- XenPci_Pnp_Pdo XenSCSI <-- XenScsi_Pnp XenSCSI --> XenScsi_Pnp XenVbd shadow_min_free = 32 XenSCSI IRP_MN_REMOVE_DEVICE XenPCI --> XenPci_Pnp_Pdo XenPCI IRP_MN_REMOVE_DEVICE (status = c00000bb) XenPCI --> XenPci_Pnp_RemoveDevice XenPCI pnp_state = NotStarted XenPCI --> XenPci_ShutdownDevice XenPCI <-- XenPci_ShutdownDevice XenVbd shadow_min_free = 31 XenPCI Watch not set - can''t remove XenPCI <-- XenPci_Pnp_RemoveDevice (status = 00000000) XenPCI <-- XenPci_Pnp_Pdo XenSCSI <-- XenScsi_Pnp XenPCI --> XenPci_Pnp_Pdo XenPCI IRP_MN_QUERY_RESOURCES (status = c00000bb) XenPCI <-- XenPci_Pnp_Pdo XenVbd shadow_min_free = 32 XenVbd shadow_min_free = 32 Thanks, VinuV> Hi, > > I am trying to do a scsi hotplug to a Windows GOS using the xmscsi-attach> command. > > This is my configuration > RHEL 5.2 DOM0 with Xen 3.3 > 32 bit Windows 2k3 GOS with WindowsXenPV-0.9.4 installed. boot.ini has/gplpv> added > > I have a SATA harddisk which I am tryng to hotplug to win GOS. Theoutput of> lsscsi is as below > #lsscsi > [0:0:0:0] disk ATA ST380013AS 3.18 /dev/sda > [1:0:0:0] disk ATA WDC WD2500YS-01M 02.0 /dev/sdb > > and I am using the below command to attach /dev/sdb to GOS > # xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 512 8r-----> 3381.5 > Windows2003 5 256 1 -b----35.7> > #xm scsi-attach Windows2003 1:0:0:0 1:0:0:0 > # > > As soon as I run the above command, I see a pop up coming in Win2k3GOS> indicating that a xen vscsi device is hotplugged. But when I go to theDevice> Manager in Windows and look at this device, it appears with an Yellowbang and> the driver tab indicates error Code 10 (reinstall driver). > > I tried this multiple times, but always end up at the same state. Haveanyone> tried something similar ? Do you know what might going wrong here ? >It should work, it certainly used to. Can you please run DebugView from sysinternals.com on your windows machine, turn on kernel logging, then try the hotplug? That should capture some debug logging. Email it to me and I''ll have a look. Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper
2009-Jul-02 01:41 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
> > I am trying to do a scsi hotplug to a Windows GOS using the xmscsi-attach> command. > > This is my configuration > RHEL 5.2 DOM0 with Xen 3.3 > 32 bit Windows 2k3 GOS with WindowsXenPV-0.9.4 installed. boot.ini has/gplpv> addedTry using the 0.10.x series of GPLPV drivers. You''ll need to run the uninstall script before installing. I just tested then and it worked fine under 0.10.x. 0.9.4 may only support the pre-release version of pvscsi that never made it into xen. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Velayudhan, Vinu
2009-Jul-11 00:50 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
Hi James, Looks like I am missing something in my test setup. I have tried gplpv_fre_wnet_x86_0.10.0.69.msi. But with these drivers I am not even seeing a hot plug event in Windows GOS when I run the xm scsi-attach in Dom0. With the WinGPLPV-0.9.x, I used to get a hot plug event in Windows. Do I need start any specific component/module in Xen, before hot plugging? I tried this with a Xen 3.3.1 and with fresh Windows GOS image which didn''t had any preinstalled GPL drivers. Thanks, VinuV -----Original Message----- From: James Harper [mailto:james.harper@bendigoit.com.au] Sent: Wednesday, July 01, 2009 6:42 PM To: Velayudhan, Vinu; Xen-users@lists.xensource.com Subject: RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS>> I am trying to do a scsi hotplug to a Windows GOS using the xmscsi-attach> command.>> This is my configuration> RHEL 5.2 DOM0 with Xen 3.3> 32 bit Windows 2k3 GOS with WindowsXenPV-0.9.4 installed. boot.ini has/gplpv> addedTry using the 0.10.x series of GPLPV drivers. You''ll need to run the uninstall script before installing. I just tested then and it worked fine under 0.10.x. 0.9.4 may only support the pre-release version of pvscsi that never made it into xen. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper
2009-Jul-11 02:04 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
> > Looks like I am missing something in my test setup. > > I have tried gplpv_fre_wnet_x86_0.10.0.69.msi. But with these driversI am not> even seeing a hot plug event in Windows GOS when I run the xmscsi-attach in> Dom0. With the WinGPLPV-0.9.x, I used to get a hot plug event inWindows.> > Do I need start any specific component/module in Xen, before hotplugging? I> tried this with a Xen 3.3.1 and with fresh Windows GOS image whichdidn''t had> any preinstalled GPL drivers. >I''ll have an update ready soon that should fix this problem for you. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jose, Manoj
2009-Jul-14 16:57 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
James,
I have tried the latest version (gplpv_chk_wnet_x86_0.10.0.83.msi) on a Xen
3.3.1 system and I am seeing a system crash. I have copied windows debug log for
your reference. I have not seen a crash issue with the previous release of gplpv
driver. Is there a known issue with the latest release? Or any thing extra I
have to do to make it work?
Thanks
Manoj
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \\.\com8
Waiting to reconnect...
Connected to Windows Server 2003 3790 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: C:\WinDDK\6000\share\fw_vmegaraid\win_mfi_client\i386
Executable search path is: C:\WinDDK\6000\share\fw_vmegaraid\win_mfi_client\i386
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntkrnlpa.exe -
Windows Server 2003 Kernel Version 3790 UP Free x86 compatible
Built by: 3790.srv03_sp2_rtm.070216-1710
Kernel base = 0x80800000 PsLoadedModuleList = 0x8089ffa8
System Uptime: not available
XenPCI --> DriverEntry
XenPCI --> XenPci_FixLoadOrder
XenPCI Current Order:
XenPCI System Reserved
XenPCI Dummy Group
XenPCI WdfLoadGroup
XenPCI XenPCI Group
XenPCI Boot Bus Extender
XenPCI System Bus Extender
XenPCI SCSI miniport
XenPCI Port
XenPCI Primary Disk
XenPCI SCSI Class
XenPCI SCSI CDROM Class
XenPCI FSFilter Infrastructure
XenPCI FSFilter System
XenPCI FSFilter Bottom
XenPCI FSFilter Copy Protection
XenPCI FSFilter Security Enhancer
XenPCI FSFilter Open File
XenPCI FSFilter Physical Quota Management
XenPCI FSFilter Encryption
XenPCI FSFilter Compression
XenPCI FSFilter HSM
XenPCI FSFilter Cluster File System
XenPCI FSFilter System Recovery
XenPCI FSFilter Quota Management
XenPCI FSFilter Content Screener
XenPCI FSFilter Continuous Backup
XenPCI FSFilter Replication
XenPCI FSFilter Anti-Virus
XenPCI FSFilter Undelete
XenPCI FSFilter Activity Monitor
XenPCI FSFilter Top
XenPCI Filter
XenPCI Boot File System
XenPCI Base
XenPCI Pointer Port
XenPCI Keyboard Port
XenPCI Pointer Class
XenPCI Keyboard Class
XenPCI Video Init
XenPCI Video
XenPCI Video Save
XenPCI File System
XenPCI Event Log
XenPCI Streams Drivers
XenPCI NDIS Wrapper
XenPCI COM Infrastructure
XenPCI UIGroup
XenPCI PlugPlay
XenPCI PNP_TDI
XenPCI NDIS
XenPCI TDI
XenPCI NetBIOSGroup
XenPCI ShellSvcGroup
XenPCI SchedulerGroup
XenPCI AudioGroup
XenPCI SmartCardGroup
XenPCI NetworkProvider
XenPCI MS_WindowsRemoteValidation
XenPCI MS_WindowsLocalValidation
XenPCI SpoolerGroup
XenPCI NetDDEGroup
XenPCI Parallel arbitrator
XenPCI Extended Base
XenPCI PCI Configuration
XenPCI MS Transactions
XenPCI dummy_group_index = 1
XenPCI wdf_load_group_index = 2
XenPCI xenpci_group_index = 3
XenPCI boot_bus_extender_index = 4
XenPCI SystemStartOptions = NOEXECUTE=OPTOUT FASTDETECT DEBUG
DEBUGPORT=COM1 BAUDRATE=115200 LASTBOOTSTATUS=2
XenPCI PV Devices Active
XenPCI <-- DriverEntry
XenPCI Xen PCI device found - must be fdo
XenPCI --> XenPci_EvtDeviceAdd_XenPci
XenPCI <-- XenPci_EvtDeviceAdd_XenPci
XenPCI --> XenPci_EvtDevicePrepareHardware
XenPCI IoPort Address(c000) Length: 256
XenPCI Private Data: 0x01 0x00 0x00
XenPCI Memory mapped CSR:(d2000000:0) Length:(16777216)
XenPCI Memory flags = 0004
XenPCI Private Data: 0x01 0x01 0x00
XenPCI irq_number = 01c
XenPCI irq_vector = 1a3
XenPCI irq_level = 009
XenPCI irq_mode = LevelSensitive
XenPCI ShareDisposition = CmResourceShareShared
XenPCI <-- XenPci_EvtDevicePrepareHardware
XenPCI --> XenPci_EvtDeviceD0Entry
XenPCI WdfPowerDeviceD3Final
XenPCI --> XenPci_Init
XenPCI base = 0x40000000, Xen Signature = XenVMMXenVMM, EAX = 0x40000002
XenPCI Hypercall area at 817B3000
XenPCI pfn = 17B3
XenPCI shared_info_area_unmapped.QuadPart = d2000000
XenPCI gpfn = d2000
XenPCI hypervisor memory op (XENMAPSPACE_shared_info) ret = 0
XenPCI <-- XenPci_Init
XenPCI --> GntTbl_Init
XenPCI grant_frames = 32
XenPCI grant_entries = 16384
XenPCI <-- GntTbl_Init
XenPCI --> EvtChn_Init
XenPCI --> hvm_set_parameter
XenPCI HYPERVISOR_hvm_op retval = 0
XenPCI <-- hvm_set_parameter
XenPCI hvm_set_parameter(HVM_PARAM_CALLBACK_IRQ, 28) = 0
XenPCI --> EvtChn_AllocIpi
XenPCI <-- EvtChn_AllocIpi
XenPCI --> EvtChn_BindDpc
XenPCI <-- EvtChn_BindDpc
XenPCI pdo_event_channel = 4
XenPCI <-- EvtChn_Init
XenPCI <-- XenPci_EvtDeviceD0Entry
XenPCI --> EvtChn_EvtInterruptEnable
XenPCI <-- EvtChn_EvtInterruptEnable
XenPCI --> XenPci_EvtDeviceD0EntryPostInterruptsEnabled
XenPCI --> XenBus_Init
XenPCI --> hvm_get_parameter
XenPCI HYPERVISOR_hvm_op retval = 0
XenPCI <-- hvm_get_parameter
XenPCI --> hvm_get_parameter
XenPCI HYPERVISOR_hvm_op retval = 0
XenPCI <-- hvm_get_parameter
XenPCI --> EvtChn_BindDpc
XenPCI <-- EvtChn_BindDpc
XenPCI <-- XenBus_Init
XenPCI --> XenPci_SysrqHandler
XenPCI SysRq Value = (null)
XenPCI <-- XenPci_SysrqHandler
XenPCI --> XenPci_ShutdownHandler
Error reading shutdown path - ENOENT
XenPCI <-- XenPci_ShutdownHandler
XenPCI XENMEM_current_reservation = 67551
XenPCI XENMEM_maximum_reservation = 67584
XenPCI XENMEM_maximum_ram_page = 259897
XenPCI Initial Memory Value = 256 (262144)
XenPCI --> XenPci_BalloonThreadProc
XenPCI <-- XenPci_EvtDeviceD0EntryPostInterruptsEnabled
XenPCI --> XenPci_EvtChildListScanForChildren
XenPCI --> XenPci_BalloonHandler
XenPCI target memory value = 256 (262144)
XenPCI <-- XenPci_EvtChildListScanForChildren
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI device = ''vbd'', index = ''768'',
path = ''device/vbd/768''
XenPCI <-- XenPci_EvtChildListCreateDevice
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI device = ''vif'', index = ''0'', path
= ''device/vif/0''
XenPCI <-- XenPci_EvtChildListCreateDevice
XenPCI --> XenPci_EvtChildListCreateDevice
XenPCI device = ''pci'', index = ''0'', path
= ''device/pci/0''
XenPCI <-- XenPci_EvtChildListCreateDevice
XenPCI Xen PCI device not found - must be filter
XenPCI --> XenPci_EvtDeviceAdd_XenHide
XenPCI Installing Filter for Intel(R) 82371SB PCI Bus Master IDE Controller
XenPCI <-- XenPci_EvtDeviceAdd_XenHide
XenPCI --> XenHide_EvtDevicePrepareHardware
XenPCI <-- XenHide_EvtDevicePrepareHardware
XenPCI <-- XenPci_BalloonHandler
*** Fatal System Error: 0x0000007b
(0xF9FDFA98,0xC0000034,0x00000000,0x00000000)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.
A fatal system error has occurred.
Connected to Windows Server 2003 3790 x86 compatible target, ptr64 FALSE
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntkrnlpa.exe -
Loading Kernel Symbols
............................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7B, {f9fdfa98, c0000034, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntkrnlpa.exe ( nt!KeRegisterBugCheckReasonCallback+b85 )
Followup: MachineOwner
---------
nt!DbgBreakPointWithStatus+0x4:
8086cf18 cc int 3
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INACCESSIBLE_BOOT_DEVICE (7b)
During the initialization of the I/O system, it is possible that the driver
for the boot device failed to initialize the device that the system is
attempting to boot from, or it is possible for the file system that is
supposed to read that device to either fail its initialization or to simply
not recognize the data on the boot device as a file system structure that
it recognizes. In the former case, the argument (#1) is the address of a
Unicode string data structure that is the ARC name of the device from which
the boot was being attempted. In the latter case, the argument (#1) is the
address of the device object that could not be mounted.
If this is the initial setup of the system, then this error can occur if
the system was installed on an unsupported disk or SCSI controller. Note
that some controllers are supported only by drivers which are in the Windows
Driver Library (WDL) which requires the user to do a custom install. See
the Windows Driver Library for more information.
This error can also be caused by the installation of a new SCSI adapter or
disk controller or repartitioning the disk with the system partition. If
this is the case, on x86 systems the boot.ini file must be edited or on ARC
systems setup must be run. See the "Advanced Server System
Administrator''s
User Guide" for information on changing boot.ini.
If the argument is a pointer to an ARC name string, then the format of the
first two (and in this case only) longwords will be:
USHORT Length;
USHORT MaximumLength;
PWSTR Buffer;
That is, the first longword will contain something like 00800020 where 20
is the actual length of the Unicode string, and the next longword will
contain the address of buffer. This address will be in system space, so
the high order bit will be set.
If the argument is a pointer to a device object, then the format of the first
word will be:
USHORT Type;
That is, the first word will contain a 0003, where the Type code will ALWAYS
be 0003.
Note that this makes it immediately obvious whether the argument is a pointer
to an ARC name string or a device object, since a Unicode string can never
have an odd number of bytes, and a device object will always have a Type
code of 3.
Arguments:
Arg1: f9fdfa98, Pointer to the device object or Unicode string of ARC name
Arg2: c0000034
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
MODULE_NAME: nt
FAULTING_MODULE: 80800000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 45d69710
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x7B
LAST_CONTROL_TRANSFER: from 80826a2f to 8086cf18
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f9fdf694 80826a2f 00000003 00000000 80087000 nt!DbgBreakPointWithStatus+0x4
f9fdfa2c 80826dc7 0000007b f9fdfa98 c0000034
nt!KeRegisterBugCheckReasonCallback+0xb85
f9fdfa4c 809fe64f 0000007b f9fdfa98 c0000034 nt!KeBugCheckEx+0x1b
f9fdfbb4 80a00b25 80087000 00000000 80087000 nt!NlsOemLeadByteInfo+0x22ce3
f9fdfc04 809fd3e3 80087000 f9fdfc48 00000000 nt!IoReportHalResourceUsage+0x201f
f9fdfc74 809fb5bb 80087000 00000000 817a95a8 nt!NlsOemLeadByteInfo+0x21a77
f9fdfda0 808e098f 80087000 f9fdfddc 809418f4 nt!NlsOemLeadByteInfo+0x1fc4f
f9fdfdac 809418f4 80087000 00000000 00000000
nt!IoSetPartitionInformationEx+0x24b
f9fdfddc 80887f4a 808e0982 80087000 00000000
nt!PsRemoveCreateThreadNotifyRoutine+0x21e
00000000 00000000 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x44a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeRegisterBugCheckReasonCallback+b85
80826a2f e8907c0000 call nt!ZwYieldExecution+0x994 (8082e6c4)
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KeRegisterBugCheckReasonCallback+b85
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlpa.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of James Harper
Sent: Friday, July 10, 2009 10:04 PM
To: Velayudhan, Vinu; Xen-users@lists.xensource.com
Subject: RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
>
> Looks like I am missing something in my test setup.
>
> I have tried gplpv_fre_wnet_x86_0.10.0.69.msi. But with these drivers
I am not> even seeing a hot plug event in Windows GOS when I run the xm
scsi-attach in> Dom0. With the WinGPLPV-0.9.x, I used to get a hot plug event in
Windows.>
> Do I need start any specific component/module in Xen, before hot
plugging? I> tried this with a Xen 3.3.1 and with fresh Windows GOS image which
didn''t had> any preinstalled GPL drivers.
>
I''ll have an update ready soon that should fix this problem for you.
James
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
James Harper
2009-Jul-15 00:07 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
> James, > > I have tried the latest version (gplpv_chk_wnet_x86_0.10.0.83.msi) ona Xen> 3.3.1 system and I am seeing a system crash. I have copied windowsdebug log> for your reference. I have not seen a crash issue with the previousrelease of> gplpv driver. Is there a known issue with the latest release? Or anything> extra I have to do to make it work? >When you first install it, before you reboot, does it find and install the vbd and vif drivers? After installing, but before rebooting, you should see in device manager a GPLPV SCSI controller that hasn''t enumerated any disks, and a network driver that is reporting cable disconnected. If you don''t see these, then do a scan for hardware changes in device manager and see if it finds them. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jose, Manoj
2009-Jul-15 15:28 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
Before it reboots it finds Network Adapter Xen vif Device #0 (With a yellow bang) and SCSI and RAID Controller Xen vbd device #768 (With a yellow bang) This time I tried the same test with Xen 3.4.0 but resulted in the same error! Manoj -----Original Message----- From: James Harper [mailto:james.harper@bendigoit.com.au] Sent: Tuesday, July 14, 2009 8:07 PM To: Jose, Manoj; Velayudhan, Vinu; Xen-users@lists.xensource.com Subject: RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS> James, > > I have tried the latest version (gplpv_chk_wnet_x86_0.10.0.83.msi) ona Xen> 3.3.1 system and I am seeing a system crash. I have copied windowsdebug log> for your reference. I have not seen a crash issue with the previousrelease of> gplpv driver. Is there a known issue with the latest release? Or anything> extra I have to do to make it work? >When you first install it, before you reboot, does it find and install the vbd and vif drivers? After installing, but before rebooting, you should see in device manager a GPLPV SCSI controller that hasn''t enumerated any disks, and a network driver that is reporting cable disconnected. If you don''t see these, then do a scan for hardware changes in device manager and see if it finds them. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jose, Manoj
2009-Jul-16 16:33 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
James, Do you have any idea what is happening here? Can I do any thing further to debug this issue further? Thanks Manoj -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Jose, Manoj Sent: Wednesday, July 15, 2009 11:28 AM To: James Harper; Velayudhan, Vinu; Xen-users@lists.xensource.com Subject: RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS Before it reboots it finds Network Adapter Xen vif Device #0 (With a yellow bang) and SCSI and RAID Controller Xen vbd device #768 (With a yellow bang) This time I tried the same test with Xen 3.4.0 but resulted in the same error! Manoj -----Original Message----- From: James Harper [mailto:james.harper@bendigoit.com.au] Sent: Tuesday, July 14, 2009 8:07 PM To: Jose, Manoj; Velayudhan, Vinu; Xen-users@lists.xensource.com Subject: RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS> James, > > I have tried the latest version (gplpv_chk_wnet_x86_0.10.0.83.msi) ona Xen> 3.3.1 system and I am seeing a system crash. I have copied windowsdebug log> for your reference. I have not seen a crash issue with the previousrelease of> gplpv driver. Is there a known issue with the latest release? Or anything> extra I have to do to make it work? >When you first install it, before you reboot, does it find and install the vbd and vif drivers? After installing, but before rebooting, you should see in device manager a GPLPV SCSI controller that hasn''t enumerated any disks, and a network driver that is reporting cable disconnected. If you don''t see these, then do a scan for hardware changes in device manager and see if it finds them. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper
2009-Jul-17 00:54 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
> > James, > > Do you have any idea what is happening here? Can I do any thingfurther to> debug this issue further? >I''m just uploading a 0.10.0.86 which may or may not fix the problem. If you still get the yellow bang, can you tell me what the failure code is when you look at the properties? Also, if you are running 3.4.x you should get some debug output in /var/log/xen/qemu-dm-<domu name>.log, please send that to me too. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jose, Manoj
2009-Jul-17 15:51 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
James,>I''m just uploading a 0.10.0.86 which may or may not fix the problem.>If you still get the yellow bang, can you tell me what the failure code >is when you look at the properties?I have tried 0.10.0.86 and that also resulted in the same error. Properties of ''Xen vif device #0'' and ''Xen vbd Device #768'' says "This device is not configured correctly (Code 1).>Also, if you are running 3.4.x you should get some debug output in >/var/log/xen/qemu-dm-<domu name>.log, please send that to me too.I am using xen 3.4.0 and I am attaching the log. Thanks Manoj _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper
2009-Jul-17 22:54 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
> > James, > > >I''m just uploading a 0.10.0.86 which may or may not fix the problem. > > >If you still get the yellow bang, can you tell me what the failurecode> >is when you look at the properties? > > I have tried 0.10.0.86 and that also resulted in the same error.Properties of> ''Xen vif device #0'' and ''Xen vbd Device #768'' says "This device is not > configured correctly (Code 1). > > >Also, if you are running 3.4.x you should get some debug output in > >/var/log/xen/qemu-dm-<domu name>.log, please send that to me too. > > I am using xen 3.4.0 and I am attaching the log. >Definitely xenvbd and xennet are not loading correctly or at all. Are you able to give me rdp access to the domU that the drivers are installed on? James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jose, Manoj
2009-Jul-22 18:39 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
James, Thanks for the feedback. I have able to load the gplpv_chk_wnet_x86_0.10.0.86.msi on a freshly installed windows 2003 image. But hot plugging is still not working for me. I have an extra scsi device sdb [0:0:1:0] to test scsi hot plug. I have tried following steps. 1. Started windows 2003 GOS with /gplpv boot option 2. Attached scsi device with following command #xm scsi-attach Windows2003 0:0:1:0 0:0:1:0 I have seen a Xen SCSI Driver under SCSI and RAID Controllers with a Yellow bang. Newly hot plugged device is not seen in Windows 2003 guest OS. My system is in this state right now and I have made the system available in RDP. IP address is 192.19.221.180 and root password is redhat. You can find windows GOS image at /usr directory and Xen config file at /usr/xen-config-file/ directory. Your feed back is very much appreciated. Thanks Manoj -----Original Message----- From: James Harper [mailto:james.harper@bendigoit.com.au] Sent: Friday, July 17, 2009 6:54 PM To: Jose, Manoj; Velayudhan, Vinu; Xen-users@lists.xensource.com Subject: RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS> > James, > > >I''m just uploading a 0.10.0.86 which may or may not fix the problem. > > >If you still get the yellow bang, can you tell me what the failurecode> >is when you look at the properties? > > I have tried 0.10.0.86 and that also resulted in the same error.Properties of> ''Xen vif device #0'' and ''Xen vbd Device #768'' says "This device is not > configured correctly (Code 1). > > >Also, if you are running 3.4.x you should get some debug output in > >/var/log/xen/qemu-dm-<domu name>.log, please send that to me too. > > I am using xen 3.4.0 and I am attaching the log. >Definitely xenvbd and xennet are not loading correctly or at all. Are you able to give me rdp access to the domU that the drivers are installed on? James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper
2009-Jul-23 01:11 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
I''ll try and have a look at it tonight (in about 8 hours from now). James> -----Original Message----- > From: Jose, Manoj [mailto:Manoj.Jose@lsi.com] > Sent: Thursday, 23 July 2009 04:39 > To: James Harper; Velayudhan, Vinu; Xen-users@lists.xensource.com > Subject: RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS > > James, > > Thanks for the feedback. I have able to load the > gplpv_chk_wnet_x86_0.10.0.86.msi on a freshly installed windows 2003image.> But hot plugging is still not working for me. > > I have an extra scsi device sdb [0:0:1:0] to test scsi hot plug. Ihave tried> following steps. > 1. Started windows 2003 GOS with /gplpv boot option > 2. Attached scsi device with following command > #xm scsi-attach Windows2003 0:0:1:0 0:0:1:0 > > I have seen a Xen SCSI Driver under SCSI and RAID Controllers with aYellow> bang. Newly hot plugged device is not seen in Windows 2003 guest OS.My system> is in this state right now and I have made the system available inRDP. IP> address is 192.19.221.180 and root password is redhat. > > You can find windows GOS image at /usr directory and Xen config fileat> /usr/xen-config-file/ directory. > > Your feed back is very much appreciated. > > Thanks > Manoj > > -----Original Message----- > From: James Harper [mailto:james.harper@bendigoit.com.au] > Sent: Friday, July 17, 2009 6:54 PM > To: Jose, Manoj; Velayudhan, Vinu; Xen-users@lists.xensource.com > Subject: RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS > > > > > James, > > > > >I''m just uploading a 0.10.0.86 which may or may not fix theproblem.> > > > >If you still get the yellow bang, can you tell me what the failure > code > > >is when you look at the properties? > > > > I have tried 0.10.0.86 and that also resulted in the same error. > Properties of > > ''Xen vif device #0'' and ''Xen vbd Device #768'' says "This device isnot> > configured correctly (Code 1). > > > > >Also, if you are running 3.4.x you should get some debug output in > > >/var/log/xen/qemu-dm-<domu name>.log, please send that to me too. > > > > I am using xen 3.4.0 and I am attaching the log. > > > > Definitely xenvbd and xennet are not loading correctly or at all. > > Are you able to give me rdp access to the domU that the drivers are > installed on? > > James_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jose, Manoj
2009-Jul-29 15:07 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
I have a debug log during scsi hotplug failure. Here is what I have done 1. Started windows 2003 GOS with /gplpv boot option 2. Installed windows GPLPV 0.10.0.86 3. Attached scsi device with following command #xm scsi-attach Windows2003 0:0:1:0 0:0:1:0 Debug log shows following critical messages(full debug log attached). XenPCI Backend State Changed to Initialising (/local/domain/0/backend/vscsi/6/0/state) XenPCI Still waiting for 2 (currently 1)... XenPCI Timed out waiting for 2! XenPCI Still waiting for 2 (currently 1)... XenPCI Timed out waiting for 2! Am I doing something wrong or is there any issue with the scsi-attach? Thanks Manoj -----Original Message----- From: James Harper [mailto:james.harper@bendigoit.com.au] Sent: Wednesday, July 22, 2009 9:12 PM To: Jose, Manoj; Velayudhan, Vinu; Xen-users@lists.xensource.com Subject: RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS I''ll try and have a look at it tonight (in about 8 hours from now). James> -----Original Message----- > From: Jose, Manoj [mailto:Manoj.Jose@lsi.com] > Sent: Thursday, 23 July 2009 04:39 > To: James Harper; Velayudhan, Vinu; Xen-users@lists.xensource.com > Subject: RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS > > James, > > Thanks for the feedback. I have able to load the > gplpv_chk_wnet_x86_0.10.0.86.msi on a freshly installed windows 2003image.> But hot plugging is still not working for me. > > I have an extra scsi device sdb [0:0:1:0] to test scsi hot plug. Ihave tried> following steps. > 1. Started windows 2003 GOS with /gplpv boot option > 2. Attached scsi device with following command > #xm scsi-attach Windows2003 0:0:1:0 0:0:1:0 > > I have seen a Xen SCSI Driver under SCSI and RAID Controllers with aYellow> bang. Newly hot plugged device is not seen in Windows 2003 guest OS.My system> is in this state right now and I have made the system available inRDP. IP> address is 192.19.221.180 and root password is redhat. > > You can find windows GOS image at /usr directory and Xen config fileat> /usr/xen-config-file/ directory. > > Your feed back is very much appreciated. > > Thanks > Manoj > > -----Original Message----- > From: James Harper [mailto:james.harper@bendigoit.com.au] > Sent: Friday, July 17, 2009 6:54 PM > To: Jose, Manoj; Velayudhan, Vinu; Xen-users@lists.xensource.com > Subject: RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS > > > > > James, > > > > >I''m just uploading a 0.10.0.86 which may or may not fix theproblem.> > > > >If you still get the yellow bang, can you tell me what the failure > code > > >is when you look at the properties? > > > > I have tried 0.10.0.86 and that also resulted in the same error. > Properties of > > ''Xen vif device #0'' and ''Xen vbd Device #768'' says "This device isnot> > configured correctly (Code 1). > > > > >Also, if you are running 3.4.x you should get some debug output in > > >/var/log/xen/qemu-dm-<domu name>.log, please send that to me too. > > > > I am using xen 3.4.0 and I am attaching the log. > > > > Definitely xenvbd and xennet are not loading correctly or at all. > > Are you able to give me rdp access to the domU that the drivers are > installed on? > > James_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper
2009-Jul-29 21:55 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
> > I have a debug log during scsi hotplug failure. Here is what I havedone> > 1. Started windows 2003 GOS with /gplpv boot option > 2. Installed windows GPLPV 0.10.0.86 > 3. Attached scsi device with following command > #xm scsi-attach Windows2003 0:0:1:0 0:0:1:0 > > Debug log shows following critical messages(full debug log attached). > XenPCI Backend State Changed to Initialising > (/local/domain/0/backend/vscsi/6/0/state) > XenPCI Still waiting for 2 (currently 1)... > XenPCI Timed out waiting for 2! > XenPCI Still waiting for 2 (currently 1)... > XenPCI Timed out waiting for 2! > > Am I doing something wrong or is there any issue with the scsi-attach? >Is the scsibk module definitely loaded in dom0? Does it work under a Linux DomU? (sorry if I''ve asked these questions before - I''ve got a lot on at the moment) James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jose, Manoj
2009-Jul-30 19:32 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
James, I did not had xen-scsibk, with that driver loaded in DOM0 every thing works perfectly. Thank you very much for the tip. Is there any other way to attach scsi devices dynamically to the GOS other than using GPLPV driver? Thanks Manoj -----Original Message----- From: James Harper [mailto:james.harper@bendigoit.com.au] Sent: Wednesday, July 29, 2009 5:56 PM To: Jose, Manoj; Velayudhan, Vinu; Xen-users@lists.xensource.com Subject: RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS> > I have a debug log during scsi hotplug failure. Here is what I havedone> > 1. Started windows 2003 GOS with /gplpv boot option > 2. Installed windows GPLPV 0.10.0.86 > 3. Attached scsi device with following command > #xm scsi-attach Windows2003 0:0:1:0 0:0:1:0 > > Debug log shows following critical messages(full debug log attached). > XenPCI Backend State Changed to Initialising > (/local/domain/0/backend/vscsi/6/0/state) > XenPCI Still waiting for 2 (currently 1)... > XenPCI Timed out waiting for 2! > XenPCI Still waiting for 2 (currently 1)... > XenPCI Timed out waiting for 2! > > Am I doing something wrong or is there any issue with the scsi-attach? >Is the scsibk module definitely loaded in dom0? Does it work under a Linux DomU? (sorry if I''ve asked these questions before - I''ve got a lot on at the moment) James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper
2009-Jul-31 01:08 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
> James, > > I did not had xen-scsibk, with that driver loaded in DOM0 every thingworks> perfectly. Thank you very much for the tip.It would be nice if the scsi-attach command could tell you if the module wasn''t loaded. Would have saved you a bit of trouble. I think the blkback and netback drivers suffer the same problem if you load them as modules.> > Is there any other way to attach scsi devices dynamically to the GOSother> than using GPLPV driver? >I don''t think any of the other PV drivers support scsi passthrough. a later version of qemu might support it but it would be slow. Btw, what is GOS? James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jose, Manoj
2009-Jul-31 02:49 UTC
Re: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
Yeah it would be nice if scsi/block attach can tell missing modules. Or is it possible to add a small paragraph to your gplpv documentation. My GOS is going to be >win2k3 Thanks Manoj On Jul 30, 2009, at 9:08 PM, "James Harper" <james.harper@bendigoit.com.au > wrote:>> James, >> >> I did not had xen-scsibk, with that driver loaded in DOM0 every thing > works >> perfectly. Thank you very much for the tip. > > It would be nice if the scsi-attach command could tell you if the > module > wasn''t loaded. Would have saved you a bit of trouble. I think the > blkback and netback drivers suffer the same problem if you load them > as > modules. > >> >> Is there any other way to attach scsi devices dynamically to the GOS > other >> than using GPLPV driver? >> > > I don''t think any of the other PV drivers support scsi passthrough. a > later version of qemu might support it but it would be slow. > > Btw, what is GOS? > > James_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper
2009-Jul-31 02:56 UTC
RE: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
> > Yeah it would be nice if scsi/block attach can tell missing modules. > Or is it possible to add a small paragraph to your gplpvdocumentation.> > My GOS is going to be >win2k3 >My question was that I don''t know what a ''GOS'' is. I know of a Linux distribution by that name but that doesn''t make sense in this context. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jose, Manoj
2009-Jul-31 03:37 UTC
Re: [Xen-users] Hotplugging SCSI device to Windows 2k3 GOS
:) ohhh it is Guest Operating System. I used that to mention DOMU. Sorry for the confusion. Thanks Manoj On Jul 30, 2009, at 10:56 PM, "James Harper" <james.harper@bendigoit.com.au > wrote:>> >> Yeah it would be nice if scsi/block attach can tell missing modules. >> Or is it possible to add a small paragraph to your gplpv > documentation. >> >> My GOS is going to be >win2k3 >> > > My question was that I don''t know what a ''GOS'' is. I know of a Linux > distribution by that name but that doesn''t make sense in this context. > > James_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users