All of lore.kernel.org
 help / color / mirror / Atom feed
* GPLPV
@ 2013-02-18  9:13 Erwan RIGOLLOT
  2013-02-18 10:01 ` GPLPV James Harper
  0 siblings, 1 reply; 8+ messages in thread
From: Erwan RIGOLLOT @ 2013-02-18  9:13 UTC (permalink / raw)
  To: xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 1112 bytes --]

Hi,

I have some difficulties with drivers GPLPV. When I try to install the
GPLPV on windows 7 and 2008 R2.
I have tried some version:
gplpv_Vista2008x64_signed_0.11.0.308.msi
gplpv_Vista2008x64_signed_0.11.0.356.msi

During installation, I obtained a BSOD about IRQ. I suppose that is block
device drivers cause troubles.

On windows XP, I try :
gplpv_XP_signed_0.11.0.308.msi
gplpv_XP_signed_0.11.0.356.msi
gplpv_XP_signed_0.11.0.356.msi

I obtained for Block device "this peripheral cannot start error 10".

What is the best way to troubleshoot that ?


Did i forget something anything in file configuration of domu?

builder='hvm'
memory = 2048
name = "Windows2008R2"
vif = [ 'type=ioemu, mac=00:16:3e:00:00:13, bridge=br0' ]
disk = [ 'file:/home/VM/Volumes/win2008R2.img,hda,w', 'file:/home/Soft/ISO
Microsoft/fr_windows_server_2008_r2_with_sp1_x64_dvd_617591.iso,hdc:cdrom,r'
,'file:/home/VM/Volumes/GPLPV.iso,hdd:cdrom,r' ]
boot="dc"
sdl=0
opengl=1
vnc=1
vnclisten="127.0.0.1"
vncpasswd='???????'
stdvga=0
serial='pty'
tsc_mode="default"
keymap='fr'


Thanks for you help and sorry for my english.

Erwan

[-- Attachment #1.2: Type: text/html, Size: 1902 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: GPLPV
  2013-02-18  9:13 GPLPV Erwan RIGOLLOT
@ 2013-02-18 10:01 ` James Harper
  2013-02-18 10:41   ` GPLPV Erwan RIGOLLOT
  0 siblings, 1 reply; 8+ messages in thread
From: James Harper @ 2013-02-18 10:01 UTC (permalink / raw)
  To: Erwan RIGOLLOT, xen-devel

> Hi,
> 
> I have some difficulties with drivers GPLPV. When I try to install the GPLPV
> on windows 7 and 2008 R2.
> I have tried some version:
> gplpv_Vista2008x64_signed_0.11.0.308.msi
> 
> gplpv_Vista2008x64_signed_0.11.0.356.msi
> 
> During installation, I obtained a BSOD about IRQ. I suppose that is block
> device drivers cause troubles.
> 
> On windows XP, I try :
> gplpv_XP_signed_0.11.0.308.msi
> 
> gplpv_XP_signed_0.11.0.356.msi
> gplpv_XP_signed_0.11.0.356.msi
> 
> 
> I obtained for Block device "this peripheral cannot start error 10".
> 
> What is the best way to troubleshoot that ?
> 
> 
> Did i forget something anything in file configuration of domu?
> 
> builder='hvm'
> memory = 2048
> name = "Windows2008R2"
> vif = [ 'type=ioemu, mac=00:16:3e:00:00:13, bridge=br0' ]
> disk = [ 'file:/home/VM/Volumes/win2008R2.img,hda,w',
> 'file:/home/Soft/ISO
> Microsoft/fr_windows_server_2008_r2_with_sp1_x64_dvd_617591.iso,hdc:
> cdrom,r' ,'file:/home/VM/Volumes/GPLPV.iso,hdd:cdrom,r' ]
> boot="dc"
> sdl=0
> opengl=1
> vnc=1
> vnclisten="127.0.0.1"
> vncpasswd='???????'
> stdvga=0
> serial='pty'
> tsc_mode="default"
> keymap='fr'
> 
> Thanks for you help and sorry for my english.
> 

That all looks okay. Can you try installing the debug version and then send me the output of /var/log/xen/qemu-dm-<domu-name>.log

James

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: GPLPV
  2013-02-18 10:01 ` GPLPV James Harper
@ 2013-02-18 10:41   ` Erwan RIGOLLOT
  2013-02-18 10:56     ` GPLPV James Harper
  0 siblings, 1 reply; 8+ messages in thread
From: Erwan RIGOLLOT @ 2013-02-18 10:41 UTC (permalink / raw)
  To: James Harper; +Cc: xen-devel

[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]

Le 18/02/2013 11:01, James Harper a écrit :
>> Hi,
>>
>> I have some difficulties with drivers GPLPV. When I try to install the GPLPV
>> on windows 7 and 2008 R2.
>> I have tried some version:
>> gplpv_Vista2008x64_signed_0.11.0.308.msi
>>
>> gplpv_Vista2008x64_signed_0.11.0.356.msi
>>
>> During installation, I obtained a BSOD about IRQ. I suppose that is block
>> device drivers cause troubles.
>>
>> On windows XP, I try :
>> gplpv_XP_signed_0.11.0.308.msi
>>
>> gplpv_XP_signed_0.11.0.356.msi
>> gplpv_XP_signed_0.11.0.356.msi
>>
>>
>> I obtained for Block device "this peripheral cannot start error 10".
>>
>> What is the best way to troubleshoot that ?
>>
>>
>> Did i forget something anything in file configuration of domu?
>>
>> builder='hvm'
>> memory = 2048
>> name = "Windows2008R2"
>> vif = [ 'type=ioemu, mac=00:16:3e:00:00:13, bridge=br0' ]
>> disk = [ 'file:/home/VM/Volumes/win2008R2.img,hda,w',
>> 'file:/home/Soft/ISO
>> Microsoft/fr_windows_server_2008_r2_with_sp1_x64_dvd_617591.iso,hdc:
>> cdrom,r' ,'file:/home/VM/Volumes/GPLPV.iso,hdd:cdrom,r' ]
>> boot="dc"
>> sdl=0
>> opengl=1
>> vnc=1
>> vnclisten="127.0.0.1"
>> vncpasswd='???????'
>> stdvga=0
>> serial='pty'
>> tsc_mode="default"
>> keymap='fr'
>>
>> Thanks for you help and sorry for my english.
>>
> That all looks okay. Can you try installing the debug version and then send me the output of /var/log/xen/qemu-dm-<domu-name>.log
>
> James
I try gplpv_Vista2008x64_signed_0.11.0.356_debug.msi on a windows 7 64 bits.
Look attachement for logs.

Thanks
Erwan


[-- Attachment #2: qemu-dm-Windows7GPLPV.log --]
[-- Type: text/plain, Size: 2262 bytes --]

domid: 102
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
Strip off blktap sub-type prefix to /home/VM/Volumes/win7GPLPV.img (drv 'aio')
Using file /home/VM/Volumes/win7GPLPV.img in read-write mode
Strip off blktap sub-type prefix to /home/Soft/ISO Microsoft/fr_windows_7_ultimate_with_sp1_x64_dvd_u_677299.iso (drv 'aio')
Using file /home/Soft/ISO Microsoft/fr_windows_7_ultimate_with_sp1_x64_dvd_u_677299.iso in read-only mode
Strip off blktap sub-type prefix to /home/VM/Volumes/GPLPV.iso (drv 'aio')
Using file /home/VM/Volumes/GPLPV.iso in read-only mode
Watching /local/domain/0/device-model/102/logdirty/cmd
Watching /local/domain/0/device-model/102/command
Watching /local/domain/102/cpu
char device redirected to /dev/pts/6
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = f8f93756-91be-4adb-8ae4-620c482abf4b
xen be core: xen be core: can't open gnttab device
can't open gnttab device
xen be core: xen be core: can't open gnttab device
can't open gnttab device
xen be core: xen be core: can't open gnttab device
can't open gnttab device
xen be core: xen be core: can't open gnttab device
can't open gnttab device
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/102/xen_extended_power_mgmt): read error
medium change watch on `hdc' (index: 1): aio:/home/Soft/ISO Microsoft/fr_windows_7_ultimate_with_sp1_x64_dvd_u_677299.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
medium change watch on `hdd' (index: 2): aio:/home/VM/Volumes/GPLPV.iso
Log-dirty: no command yet.
vcpu-set: watch node error.
xs_read(/local/domain/102/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/102/log-throttling'
medium change watch on `/local/domain/102/log-throttling' - unknown device, ignored
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.

[-- Attachment #3: qemu-dm-Windows7GPLPV.log.1 --]
[-- Type: text/plain, Size: 18712 bytes --]

domid: 101
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
Strip off blktap sub-type prefix to /home/VM/Volumes/win7GPLPV.img (drv 'aio')
Using file /home/VM/Volumes/win7GPLPV.img in read-write mode
Strip off blktap sub-type prefix to /home/Soft/ISO Microsoft/fr_windows_7_ultimate_with_sp1_x64_dvd_u_677299.iso (drv 'aio')
Using file /home/Soft/ISO Microsoft/fr_windows_7_ultimate_with_sp1_x64_dvd_u_677299.iso in read-only mode
Strip off blktap sub-type prefix to /home/VM/Volumes/GPLPV.iso (drv 'aio')
Using file /home/VM/Volumes/GPLPV.iso in read-only mode
Watching /local/domain/0/device-model/101/logdirty/cmd
Watching /local/domain/0/device-model/101/command
Watching /local/domain/101/cpu
char device redirected to /dev/pts/7
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = b8a888ad-9a5e-44d2-86b9-170f46cebb44
xen be core: xen be core: can't open gnttab device
can't open gnttab device
xen be core: xen be core: can't open gnttab device
can't open gnttab device
xen be core: xen be core: can't open gnttab device
can't open gnttab device
xen be core: xen be core: can't open gnttab device
can't open gnttab device
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/101/xen_extended_power_mgmt): read error
medium change watch on `hdc' (index: 1): aio:/home/Soft/ISO Microsoft/fr_windows_7_ultimate_with_sp1_x64_dvd_u_677299.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
medium change watch on `hdd' (index: 2): aio:/home/VM/Volumes/GPLPV.iso
Log-dirty: no command yet.
vcpu-set: watch node error.
xs_read(/local/domain/101/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/101/log-throttling'
medium change watch on `/local/domain/101/log-throttling' - unknown device, ignored
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.
13005657181814: XenPCI --> XenPci_InitialBalloonDown
13005657181814: XenPCI     base = 0x40000000, Xen Signature = XenVMMXenVMM, EAX = 0x40000002
13005657181814: XenPCI     Hypercall area at FFFFFA80010E1000
13005657181814: XenPCI     XENMEM_maximum_reservation = 262400
13005657181814: XenPCI     XENMEM_current_reservation = 261113
13005657181814: XenPCI     Trying to give 5148 KB (5 MB) to Xen
13005657182032: XenPCI <-- XenPci_InitialBalloonDown
13005657182032: XenPCI     KeInitializeCrashDumpHeader status = c00000f2, size = 8192
13005657182032: XenPCI GPLPV 0.10.0.356
13005657182032: XenPCI --> XenPci_FixLoadOrder
13005657182032: XenPCI     dummy_group_index = -1
13005657182032: XenPCI     wdf_load_group_index = 2
13005657182032: XenPCI     xenpci_group_index = -1
13005657182032: XenPCI     boot_bus_extender_index = 3
13005657182032: XenPCI <-- XenPci_FixLoadOrder
13005657182032: XenPCI     SystemStartOptions =  NOEXECUTE=OPTIN
13005657182032: XenPCI <-- DriverEntry
13005657182032: XenPCI     Xen PCI device found - must be fdo
13005657182032: XenPCI --> XenPci_EvtDeviceAdd_XenPci
13005657182032: XenPCI <-- XenPci_EvtDeviceAdd_XenPci
13005657182048: XenPCI --> XenPci_EvtDevicePrepareHardware
13005657182048: XenPCI     IoPort Address(c000) Length: 256
13005657182048: XenPCI     Private Data: 0x01 0x00 0x00
13005657182048: XenPCI     Memory mapped CSR:(f2000000:0) Length:(16777216)
13005657182048: XenPCI     Memory flags = 0084
13005657182048: XenPCI     Private Data: 0x01 0x01 0x00
13005657182048: XenPCI     irq_number = 01c
13005657182048: XenPCI     irq_vector = 0b2
13005657182048: XenPCI     irq_level = 00b
13005657182048: XenPCI     irq_mode = LevelSensitive
13005657182048: XenPCI     ShareDisposition = CmResourceShareShared
13005657182048: XenPCI <-- XenPci_EvtDevicePrepareHardware
13005657182048: XenPCI --> XenPci_EvtDeviceD0Entry
13005657182048: XenPCI     WdfPowerDeviceD3Final
13005657182048: XenPCI --> XenPci_Init
13005657182048: XenPCI     base = 0x40000000, Xen Signature = XenVMMXenVMM, EAX = 0x40000002
13005657182048: XenPCI     Hypercall area at FFFFFA80010CC000
13005657182048: XenPCI     shared_info_area_unmapped.QuadPart = f2000000
13005657182048: XenPCI     gpfn = f2000
13005657182048: XenPCI     hypervisor memory op (XENMAPSPACE_shared_info) ret = 0
13005657182048: XenPCI <-- XenPci_Init
13005657182048: XenPCI --> GntTbl_Init
13005657182048: XenPCI     grant_frames = 32
13005657182048: XenPCI     grant_entries = 16384
13005657182048: XenPCI     pfn = 3f0fb
13005657182048: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f0fb
13005657182064: XenPCI     decreased 1 pages for grant table frame 0
13005657182064: XenPCI     pfn = 3f0fc
13005657182064: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f0fc
13005657182079: XenPCI     decreased 1 pages for grant table frame 1
13005657182079: XenPCI     pfn = 3f0fd
13005657182079: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f0fd
13005657182079: XenPCI     decreased 1 pages for grant table frame 2
13005657182079: XenPCI     pfn = 3f0fe
13005657182079: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f0fe
13005657182079: XenPCI     decreased 1 pages for grant table frame 3
13005657182079: XenPCI     pfn = 3f0ff
13005657182079: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f0ff
13005657182079: XenPCI     decreased 1 pages for grant table frame 4
13005657182079: XenPCI     pfn = 3f100
13005657182079: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f100
13005657182079: XenPCI     decreased 1 pages for grant table frame 5
13005657182079: XenPCI     pfn = 3f101
13005657182079: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f101
13005657182079: XenPCI     decreased 1 pages for grant table frame 6
13005657182079: XenPCI     pfn = 3f102
13005657182079: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f102
13005657182079: XenPCI     decreased 1 pages for grant table frame 7
13005657182079: XenPCI     pfn = 3f103
13005657182079: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f103
13005657182079: XenPCI     decreased 1 pages for grant table frame 8
13005657182079: XenPCI     pfn = 3f104
13005657182079: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f104
13005657182079: XenPCI     decreased 1 pages for grant table frame 9
13005657182079: XenPCI     pfn = 3f105
13005657182079: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f105
13005657182095: XenPCI     decreased 1 pages for grant table frame 10
13005657182095: XenPCI     pfn = 3f106
13005657182095: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f106
13005657182095: XenPCI     decreased 1 pages for grant table frame 11
13005657182095: XenPCI     pfn = 3f107
13005657182095: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f107
13005657182095: XenPCI     decreased 1 pages for grant table frame 12
13005657182095: XenPCI     pfn = 3f108
13005657182095: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f108
13005657182095: XenPCI     decreased 1 pages for grant table frame 13
13005657182095: XenPCI     pfn = 3f109
13005657182095: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f109
13005657182095: XenPCI     decreased 1 pages for grant table frame 14
13005657182095: XenPCI     pfn = 3f10a
13005657182095: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f10a
13005657182095: XenPCI     decreased 1 pages for grant table frame 15
13005657182095: XenPCI     pfn = 3f10b
13005657182095: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f10b
13005657182095: XenPCI     decreased 1 pages for grant table frame 16
13005657182095: XenPCI     pfn = 3f10c
13005657182095: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f10c
13005657182095: XenPCI     decreased 1 pages for grant table frame 17
13005657182095: XenPCI     pfn = 3f10d
13005657182095: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f10d
13005657182095: XenPCI     decreased 1 pages for grant table frame 18
13005657182095: XenPCI     pfn = 3f10e
13005657182095: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f10e
13005657182095: XenPCI     decreased 1 pages for grant table frame 19
13005657182095: XenPCI     pfn = 3f10f
13005657182095: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f10f
13005657182110: XenPCI     decreased 1 pages for grant table frame 20
13005657182110: XenPCI     pfn = 3f110
13005657182110: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f110
13005657182110: XenPCI     decreased 1 pages for grant table frame 21
13005657182110: XenPCI     pfn = 3f111
13005657182110: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f111
13005657182110: XenPCI     decreased 1 pages for grant table frame 22
13005657182110: XenPCI     pfn = 3f112
13005657182110: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f112
13005657182110: XenPCI     decreased 1 pages for grant table frame 23
13005657182110: XenPCI     pfn = 3f113
13005657182110: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f113
13005657182110: XenPCI     decreased 1 pages for grant table frame 24
13005657182110: XenPCI     pfn = 3f114
13005657182110: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f114
13005657182110: XenPCI     decreased 1 pages for grant table frame 25
13005657182110: XenPCI     pfn = 3f115
13005657182110: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f115
13005657182110: XenPCI     decreased 1 pages for grant table frame 26
13005657182110: XenPCI     pfn = 3f116
13005657182110: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f116
13005657182110: XenPCI     decreased 1 pages for grant table frame 27
13005657182110: XenPCI     pfn = 3f117
13005657182110: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f117
13005657182110: XenPCI     decreased 1 pages for grant table frame 28
13005657182110: XenPCI     pfn = 3f118
13005657182110: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f118
13005657182110: XenPCI     decreased 1 pages for grant table frame 29
13005657182110: XenPCI     pfn = 3f119
13005657182110: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f119
13005657182126: XenPCI     decreased 1 pages for grant table frame 30
13005657182126: XenPCI     pfn = 3f11a
13005657182126: XenPCI     Calling HYPERVISOR_memory_op - pfn = 3f11a
13005657182126: XenPCI     decreased 1 pages for grant table frame 31
13005657182126: XenPCI --> GntTbl_Map
13005657182126: XenPCI <-- GntTbl_Map
13005657182126: XenPCI <-- GntTbl_Init
13005657182126: XenPCI --> EvtChn_Init
13005657182126: XenPCI --> _hvm_set_parameter
13005657182126: XenPCI HYPERVISOR_hvm_op retval = 0
13005657182126: XenPCI <-- _hvm_set_parameter
13005657182126: XenPCI     hvm_set_parameter(HVM_PARAM_CALLBACK_IRQ, 28) = 0
13005657182126: XenPCI --> EvtChn_AllocIpi
13005657182126: XenPCI <-- EvtChn_AllocIpi
13005657182126: XenPCI --> EvtChn_BindDpc
13005657182126: XenPCI <-- EvtChn_BindDpc
13005657182126: XenPCI     pdo_event_channel = 5
13005657182126: XenPCI <-- EvtChn_Init
13005657182126: XenPCI <-- XenPci_EvtDeviceD0Entry
13005657182126: XenPCI --> EvtChn_EvtInterruptEnable
13005657182126: XenPCI <-- EvtChn_EvtInterruptEnable
13005657182126: XenPCI --> XenPci_EvtDeviceD0EntryPostInterruptsEnabled
13005657182126: XenPCI --> XenBus_Init
13005657182142: XenPCI --> _hvm_get_parameter
13005657182142: XenPCI HYPERVISOR_hvm_op retval = 0
13005657182142: XenPCI <-- _hvm_get_parameter
13005657182142: XenPCI --> _hvm_get_parameter
13005657182142: XenPCI HYPERVISOR_hvm_op retval = 0
13005657182142: XenPCI <-- _hvm_get_parameter
13005657182142: XenPCI --> EvtChn_BindDpc
13005657182142: XenPCI <-- EvtChn_BindDpc
13005657182142: XenPCI <-- XenBus_Init
13005657182142: XenPCI     suspend event channel = 6
13005657182142: XenPCI --> EvtChn_BindDpc
13005657182142: XenPCI <-- EvtChn_BindDpc
13005657182142: XenPCI --> XenPci_SysrqHandler
13005657182142: XenPCI     SysRq Value = (null)
13005657182142: XenPCI <-- XenPci_SysrqHandler
13005657182142: XenPCI --> XenPci_ShutdownHandler
13005657182142: XenPCI     Initial Memory Value = 1040384 (1040384)
13005657182142: XenPCI     Shutdown value = 
13005657182142: XenPCI <-- XenPci_ShutdownHandler
13005657182142: XenPCI --> XenPci_DeviceWatchHandler
13005657182142: XenPCI <-- XenPci_DeviceWatchHandler
13005657182142: XenPCI <-- XenPci_EvtDeviceD0EntryPostInterruptsEnabled
13005657182142: XenPCI --> XenPci_EvtChildListScanForChildren
13005657182142: XenPCI --> XenPci_BalloonHandler
13005657182142: XenPCI     Found path = device/vbd/768
13005657182142: XenPCI     Found path = device/vbd/5632
13005657182142: XenPCI     Found path = device/vbd/5696
13005657182142: XenPCI     Found path = device/vif/0
13005657182142: XenPCI <-- XenPci_EvtChildListScanForChildren
13005657182142: XenPCI --> XenPci_EvtChildListCreateDevice
13005657182142: XenPCI     device = 'vbd', index = '768', path = 'device/vbd/768'
13005657182142: XenPCI <-- XenPci_EvtChildListCreateDevice
13005657182142: XenPCI --> XenPci_EvtChildListCreateDevice
13005657182142: XenPCI     device = 'vbd', index = '5632', path = 'device/vbd/5632'
13005657182142: XenPCI <-- XenPci_EvtChildListCreateDevice
13005657182157: XenPCI --> XenPci_EvtChildListCreateDevice
13005657182157: XenPCI     device = 'vbd', index = '5696', path = 'device/vbd/5696'
13005657182157: XenPCI <-- XenPci_EvtChildListCreateDevice
13005657182157: XenPCI --> XenPci_EvtChildListCreateDevice
13005657182157: XenPCI     device = 'vif', index = '0', path = 'device/vif/0'
13005657182157: XenPCI <-- XenPci_EvtChildListCreateDevice
13005657182157: XenPCI     target memory value = 1040384 (1040384)
13005657182157: XenPCI --> XenPci_BalloonThreadProc
13005657182157: XenPCI     low_mem_event = FFFFFA8000D00430, state = 0
13005657182204: XenPCI <-- XenPci_BalloonHandler
13005657182204: XenPCI     Got balloon event, current = 1040384, target = 1040384
13005657182204: XenPCI     No change to memory
13005657184201: XenVbd --> DriverEntry
13005657184201: XenVbd     IRQL = 0
13005657184201: XenVbd     DriverObject = FFFFFA80014EA490, RegistryPath = FFFFFA800146A000
13005657184201: XenVbd <-- DriverEntry
13005657184201: XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
13005657184216: XenPCI     device/vbd/768
13005657184216: XenPCI     CmResourceTypeMemory (0)
13005657184216: XenPCI     Start = f2000000, Length = 0
13005657184216: XenPCI     pfn[0] = 0000cf91
13005657184216: XenPCI     New Start = 000000000cf91000, Length = 4096
13005657184216: XenPCI     CmResourceTypeMemory (1)
13005657184216: XenPCI     Start = f2000001, Length = 0
13005657184216: XenPCI <-- XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE
13005657184216: XenPCI --> XenPciPdo_EvtDevicePrepareHardware
13005657184216: XenPCI <-- XenPciPdo_EvtDevicePrepareHardware
13005657184216: XenPCI --> XenPciPdo_EvtDeviceD0Entry
13005657184216: XenPCI     path = device/vbd/768
13005657184216: XenPCI     WdfPowerDeviceD3Final
13005657184216: XenPCI --> XenPci_GetBackendAndAddWatch
13005657184216: XenPCI <-- XenPci_GetBackendAndAddWatch
13005657184216: XenPCI --> XenConfig_InitConfigPage
13005657184216: XenPCI     fdo_driver_object = FFFFFA80014EA490
13005657184216: XenPCI     fdo_driver_extension = 0000000000000000
13005657184216: XenPCI     fdo_driver_object = FFFFFA80022A0B20
13005657184216: XenPCI     fdo_driver_extension = 0000000000000000
13005657184216: XenPCI <-- XenConfig_InitConfigPage
13005657184216: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
13005657184216: XenPCI --> XenPci_ChangeFrontendStateMap
13005657184216: XenPCI <-- XenPci_ChangeFrontendStateMap
13005657184216: XenPCI --> XenPci_ChangeFrontendStateMap
13005657184216: XenPCI <-- XenPci_ChangeFrontendStateMap
13005657184216: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers
13005657184216: XenPCI <-- XenPciPdo_EvtDeviceD0Entry
13005657184216: XenVbd --> XenVbd_VirtualHwStorFindAdapter
13005657184216: XenVbd     IRQL = 0
13005657184216: XenVbd     xvdd = FFFFFA800146E008
13005657184216: XenVbd     BusInterruptLevel = 28
13005657184216: XenVbd     BusInterruptVector = 01c
13005657184216: XenVbd     NumberOfAccessRanges = 1
13005657184216: XenVbd     RangeStart = 0cf91000, RangeLength = 00001000
13005657184232: XenVbd --> XenVbd_InitConfig
13005657184232: XenVbd     XEN_INIT_TYPE_13
13005657184232: XenVbd     XEN_INIT_TYPE_VECTORS
13005657184232: XenVbd     XEN_INIT_TYPE_11
13005657184232: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
13005657184232: XenPCI     XEN_INIT_TYPE_RING - ring-ref = FFFFFA800147D000
13005657184232: XenPCI     XEN_INIT_TYPE_RING - ring-ref = 16383
13005657184232: XenPCI --> XenPci_UpdateBackendState
13005657184232: XenPCI     XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 7
13005657184232: XenPCI     Backend State Changed to Initialising
13005657184232: XenPCI <-- XenPci_UpdateBackendState
13005657184232: XenPCI --> XenPci_DeviceWatchHandler
13005657184232: XenPCI <-- XenPci_DeviceWatchHandler
13005657184232: XenPCI --> EvtChn_BindDpc
13005657184232: XenPCI <-- EvtChn_BindDpc
13005657184232: XenPCI --> XenPci_ChangeFrontendStateMap
13005657184232: XenPCI --> XenPci_ChangeFrontendState
13005657184232: XenPCI --> XenPci_DeviceWatchHandler
13005657184232: XenPCI <-- XenPci_DeviceWatchHandler
13005657184232: XenPCI --> XenPci_DeviceWatchHandler
13005657184232: XenPCI <-- XenPci_DeviceWatchHandler
13005657185246: XenPCI --> XenPci_UpdateBackendState
13005657185246: XenPCI     state unchanged
13005657185246: XenPCI     Still waiting for 4 (currently 1)...
13005657186260: XenPCI --> XenPci_UpdateBackendState
13005657186260: XenPCI     state unchanged
13005657186260: XenPCI     Timed out waiting for 4!
13005657186260: XenPCI <-- XenPci_ChangeFrontendStateMap
13005657186260: XenPCI     Error
13005657186260: XenPCI --> XenPci_ChangeFrontendState
13005657186260: XenPCI --> XenPci_DeviceWatchHandler
13005657186260: XenPCI <-- XenPci_DeviceWatchHandler
13005657187274: XenPCI --> XenPci_UpdateBackendState
13005657187274: XenPCI     state unchanged
13005657187274: XenPCI     Still waiting for 2 (currently 1)...
13005657188288: XenPCI --> XenPci_UpdateBackendState
13005657188288: XenPCI     state unchanged
13005657188288: XenPCI     Timed out waiting for 2!
13005657188288: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers, status = c0000001
13005657188288: Failed to complete device configuration (c0000001)
13005657188288: XenVbd <-- XenVbd_InitConfig
13005657188288: XenVbd <-- XenVbd_VirtualHwStorFindAdapter
XenPCI     Bug check 0x000000D1 (0x0000000000000040, 0x0000000000000002, 0x0000000000000001, 0xFFFFF880031E03C0)
reset requested in cpu_handle_ioreq.
Issued domain 101 reboot

[-- Attachment #4: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: GPLPV
  2013-02-18 10:41   ` GPLPV Erwan RIGOLLOT
@ 2013-02-18 10:56     ` James Harper
  2013-02-18 13:14       ` GPLPV Erwan RIGOLLOT
  0 siblings, 1 reply; 8+ messages in thread
From: James Harper @ 2013-02-18 10:56 UTC (permalink / raw)
  To: Erwan RIGOLLOT; +Cc: xen-devel


> I try gplpv_Vista2008x64_signed_0.11.0.356_debug.msi on a windows 7 64
> bits.
> Look attachement for logs.
> 

I think the problem might be related to this:

xen be core: xen be core: can't open gnttab device

but I don't know how to fix it. Maybe start a new thread with that as the subject?

James

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: GPLPV
  2013-02-18 10:56     ` GPLPV James Harper
@ 2013-02-18 13:14       ` Erwan RIGOLLOT
  2013-02-18 22:42         ` GPLPV James Harper
  0 siblings, 1 reply; 8+ messages in thread
From: Erwan RIGOLLOT @ 2013-02-18 13:14 UTC (permalink / raw)
  To: James Harper; +Cc: xen-devel


[-- Attachment #1.1: Type: text/plain, Size: 763 bytes --]

I have resoled this problem.
The kernel module xen_gntdev wasn't loaded. It was built as a module....

Now, the install of GPLPV has done successfuly and all is good in device
manager with VL drivers.

Thanks you !!!!!

I have a question, is it still necessary to put GPLPV option at windows
boot?
(LOADOPTIONS "GPLPV" or /GPLPV)

What is the objective of that?

Thanks

Erwan


2013/2/18 James Harper <james.harper@bendigoit.com.au>

>
> > I try gplpv_Vista2008x64_signed_0.11.0.356_debug.msi on a windows 7 64
> > bits.
> > Look attachement for logs.
> >
>
> I think the problem might be related to this:
>
> xen be core: xen be core: can't open gnttab device
>
> but I don't know how to fix it. Maybe start a new thread with that as the
> subject?
>
> James
>

[-- Attachment #1.2: Type: text/html, Size: 2103 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: GPLPV
  2013-02-18 13:14       ` GPLPV Erwan RIGOLLOT
@ 2013-02-18 22:42         ` James Harper
  0 siblings, 0 replies; 8+ messages in thread
From: James Harper @ 2013-02-18 22:42 UTC (permalink / raw)
  To: Erwan RIGOLLOT; +Cc: xen-devel

> 
> I have resoled this problem.
> The kernel module xen_gntdev wasn't loaded. It was built as a module....
> 
> Now, the install of GPLPV has done successfuly and all is good in device
> manager with VL drivers.
> 

Hmm... I'll see if I can test that and make sure GPLPV doesn't actually crash. I might need a way to indicate this problem to the user though as in the absence of a crash the user might think it was working without knowing it wasn't.

> I have a question, is it still necessary to put GPLPV option at windows boot?
> (LOADOPTIONS "GPLPV" or /GPLPV)
> 
> What is the objective of that?
> 

That information is old. You would use /NOGPLPV to disable the drivers but in the absence of any options they would be disabled.

James

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: GPLPV
  2011-06-09 20:17 GPLPV Jonathan Tripathy
@ 2011-06-09 22:25 ` Todd Deshane
  0 siblings, 0 replies; 8+ messages in thread
From: Todd Deshane @ 2011-06-09 22:25 UTC (permalink / raw)
  To: Jonathan Tripathy; +Cc: xen-users mailing list

On Thu, Jun 9, 2011 at 4:17 PM, Jonathan Tripathy <jonnyt@abpni.co.uk> wrote:
> Hi Everyone,
>
> Does Xen 4.1.0 work ok with the current stable release of the GPLPV drivers
> for Windows DomUs?
>

This is a much better question for the xen-users mailing list. I've
added that list to the CC and moved xen-devel to BCC.

See also http://wiki.xensource.com/xenwiki/AskingXenDevelQuestions

Thanks,
Todd

> Thanks
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>



-- 
Todd Deshane
http://www.linkedin.com/in/deshantm
http://www.xen.org/products/cloudxen.html
http://runningxen.com/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* GPLPV
@ 2011-06-09 20:17 Jonathan Tripathy
  2011-06-09 22:25 ` GPLPV Todd Deshane
  0 siblings, 1 reply; 8+ messages in thread
From: Jonathan Tripathy @ 2011-06-09 20:17 UTC (permalink / raw)
  To: xen-devel

Hi Everyone,

Does Xen 4.1.0 work ok with the current stable release of the GPLPV 
drivers for Windows DomUs?

Thanks

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2013-02-18 22:42 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-02-18  9:13 GPLPV Erwan RIGOLLOT
2013-02-18 10:01 ` GPLPV James Harper
2013-02-18 10:41   ` GPLPV Erwan RIGOLLOT
2013-02-18 10:56     ` GPLPV James Harper
2013-02-18 13:14       ` GPLPV Erwan RIGOLLOT
2013-02-18 22:42         ` GPLPV James Harper
  -- strict thread matches above, loose matches on Subject: below --
2011-06-09 20:17 GPLPV Jonathan Tripathy
2011-06-09 22:25 ` GPLPV Todd Deshane

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.