thr3ads.net - Xen devel - [Xen-devel] XCP Windows PV Driver Problem [Nov 2009]

If this information is useful, please help other people find it:
Share via:

Keith Coleman

2009-Nov-03 18:19 UTC

[Xen-devel] XCP Windows PV Driver Problem

Looks like the XCP Win PV drivers are retagged from some version of
the Citrix XenServer Windows PV drivers. I get a bsod after installing
them on 2k3 enterprise sp2 32bit. I tried several tips found on the
Citrix forums but still cannot boot the PV drivers. The same setup
runs fine if I boot into safe mode or uninstall the PV drivers.

I''m attaching the qemu log file from an attempted boot with these
drivers enabled:

domid: 25
qemu: the number of cpus is 1
Watching /local/domain/0/device-model/25/logdirty/next-active
Watching /local/domain/0/device-model/25/command
char device redirected to /dev/pts/1
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = beb41d16-d5d1-ebf5-40a0-eb18f0fb287d
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
xs_read(/vm/beb41d16-d5d1-ebf5-40a0-eb18f0fb287d/log-throttling): read error
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/25/xen_extended_power_mgmt): read error
medium change watch on `hdc'' (index: 1): /root/isos/win2003entR2.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
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.
Citrix Windows PV drivers loaded in guest
PV driver build 20719
gpe_sts_write: addr=0x1f68, val=0x0.
gpe_sts_write: addr=0x1f69, val=0x0.
gpe_sts_write: addr=0x1f6a, val=0x0.
gpe_sts_write: addr=0x1f6b, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x0.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x0.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_sts_write: addr=0x1f68, val=0x0.
gpe_sts_write: addr=0x1f69, val=0x0.
gpe_sts_write: addr=0x1f6a, val=0x0.
gpe_sts_write: addr=0x1f6b, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x8.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c3, val=0x0.
ACPI PCI hotplug: read addr=0x10c4, val=0x0.
ACPI PCI hotplug: read addr=0x10c5, val=0x0.
ACPI PCI hotplug: read addr=0x10c6, val=0x0.
ACPI PCI hotplug: read addr=0x10c7, val=0x0.
ACPI PCI hotplug: read addr=0x10c8, val=0x0.
ACPI PCI hotplug: read addr=0x10c9, val=0x0.
ACPI PCI hotplug: read addr=0x10ca, val=0x0.
ACPI PCI hotplug: read addr=0x10cb, val=0x0.
ACPI PCI hotplug: read addr=0x10cc, val=0x0.
ACPI PCI hotplug: read addr=0x10cd, val=0x0.
ACPI PCI hotplug: read addr=0x10ce, val=0x0.
ACPI PCI hotplug: read addr=0x10cf, val=0x0.
ACPI PCI hotplug: read addr=0x10d0, val=0x0.
ACPI PCI hotplug: read addr=0x10d1, val=0x0.
ACPI PCI hotplug: read addr=0x10d2, val=0x0.
ACPI PCI hotplug: read addr=0x10d3, val=0x0.
ACPI PCI hotplug: read addr=0x10d4, val=0x0.
ACPI PCI hotplug: read addr=0x10d5, val=0x0.
ACPI PCI hotplug: read addr=0x10d6, val=0x0.
ACPI PCI hotplug: read addr=0x10d7, val=0x0.
ACPI PCI hotplug: read addr=0x10d8, val=0x0.
ACPI PCI hotplug: read addr=0x10d9, val=0x0.
ACPI PCI hotplug: read addr=0x10da, val=0x0.
ACPI PCI hotplug: read addr=0x10db, val=0x0.
ACPI PCI hotplug: read addr=0x10dc, val=0x0.
ACPI PCI hotplug: read addr=0x10dd, val=0x0.
ACPI PCI hotplug: read addr=0x10de, val=0x0.
ACPI PCI hotplug: read addr=0x10df, val=0x0.
ACPI PCI hotplug: read addr=0x10e0, val=0x0.
ACPI PCI hotplug: read addr=0x10e1, val=0x0.
[NOTICE][XENUTIL] Registered suspend handler 82165490
(xenevtchn_suspend_handler)
[NOTICE][XEVTCHN] Initialized tracing provider
[NOTICE][XENUTIL] KERNEL: 5.2 (build 3790) platform WIN32_NT
[NOTICE][XENUTIL] SP: 2.0 ()
[NOTICE][XENUTIL] SUITES:
[NOTICE][XENUTIL] - ENTERPRISE
[NOTICE][XENUTIL] - TERMINAL
[NOTICE][XENUTIL] - SINGLEUSERTS
[NOTICE][XENUTIL] TYPE: SERVER
[NOTICE][XENUTIL] PV driver build 20719
[NOTICE][XENUTIL] Registered suspend handler 821CB128 (HvmResume)
[NOTICE][XENUTIL] 32-bit HVM
[NOTICE][XENUTIL] Registered suspend handler 821C33D0 (EvtchnRecoverFromSuspend)
[NOTICE][XENUTIL] Registered suspend handler 82157138 (GnttabResume)
[NOTICE][XENUTIL] Registered suspend handler 82165740 (XenbusResumeEarly)
[NOTICE][XENUTIL] Registered suspend handler 821C3588 (XenbusResumeLate)
[CRITICAL][XENUTIL] XenEnterprise copyright string missing!
[WARNING][XENUTIL] Watch thread exitting.
[NOTICE][XENUTIL] Gnttab cleanup with 8 grant references outstanding
against main pool.
[NOTICE][XENUTIL] Returning to using our own interrupt vector 0.
[NOTICE][XENVBD] XENVBD in NORMAL mode.
[WARNING][XENUTIL] bugcheck callback already installed
[WARNING][XENUTIL] Multiple handlers for port 2?
[CRITICAL][XENUTIL] XenEnterprise copyright string missing!
[WARNING][XENUTIL] Watch thread exitting.
[ERROR][XENVBD] FindAdapter: XenevtchnInitXenbus failed 0
[NOTICE][XENUTIL] Gnttab cleanup with 8 grant references outstanding
against main pool.
[NOTICE][XENUTIL] Returning to using our own interrupt vector 0.
[CRITICAL][XENUTIL]
c:\sfu\local\scratch\build_root_20719c_2009_10_28_05_26_55_6560\windows\xenutil\evtchn.c:436:
Bug check.
[CRITICAL][XENUTIL] Assertion !is_null_EVTCHN_PORT(eport) failed at
c:\sfu\local\scratch\build_root_20719c_2009_10_28_05_26_55_6560\windows\xenutil\evtchn.c:436.
reset requested in cpu_handle_ioreq.
Issued domain 25 reboot

I''m running xen 3.4.1 on the official xen 2.6.18 kernel. Could the
drivers be failing intentionally because they''re not running on
XenServer? Has anyone else used them?


Keith Coleman

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

Keir Fraser

2009-Nov-03 19:14 UTC

head link

Re: [Xen-devel] XCP Windows PV Driver Problem

On 03/11/2009 18:19, "Keith Coleman" <list.keith@scaltro.com>
wrote:
> [CRITICAL][XENUTIL] XenEnterprise copyright string missing!
Could be significant, although I think the string check was made
non-essential.
> [CRITICAL][XENUTIL]
>
c:\sfu\local\scratch\build_root_20719c_2009_10_28_05_26_55_6560\windows\xenuti
> l\evtchn.c:436:
> Bug check.
> [CRITICAL][XENUTIL] Assertion !is_null_EVTCHN_PORT(eport) failed at
>
c:\sfu\local\scratch\build_root_20719c_2009_10_28_05_26_55_6560\windows\xenuti
> l\evtchn.c:436.
This crash in the PV drivers may be unrelated to the copright string
message, and is presumably the cause of the BSOD.

I don''t know how tested PV drivers are against OSS Xen, dom0, and
tools.
There''s probably some incompatibility, somewhere.

 -- Keir



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

Ian Pratt

2009-Nov-04 09:54 UTC

head link

RE: [Xen-devel] XCP Windows PV Driver Problem

> Looks like the XCP Win PV drivers are retagged from some version of
> the Citrix XenServer Windows PV drivers. I get a bsod after installing
> them on 2k3 enterprise sp2 32bit. I tried several tips found on the
> Citrix forums but still cannot boot the PV drivers. The same setup
> runs fine if I boot into safe mode or uninstall the PV drivers.
What are you trying to run the drivers on, XCP or stock xen-unstable/3.4?

If the latter, I believe there are a couple of minor protocol differences that
may cause problems. XCP should work fine. The protocol differences look like
useful improvements so it should be possible to get them upstreamed in some
backward compatible fashion over the next few weeks.

In the meantime, if you''re using xen-unstable/3.4 it might be worth
trying the following:

Create the key
HKLM\System\CurrentControlSet\Services\xevtchn\Parameters, and then create a
DWORD value called SetFlags in there and set it to 0x10000000.

I haven''t verified this works but it should get further.

Ian


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

Keith Coleman

2009-Nov-04 19:37 UTC

head link

Re: [Xen-devel] XCP Windows PV Driver Problem

On Wed, Nov 4, 2009 at 4:54 AM, Ian Pratt <Ian.Pratt@eu.citrix.com>
wrote:>> Looks like the XCP Win PV drivers are retagged from some version of
>> the Citrix XenServer Windows PV drivers. I get a bsod after installing
>> them on 2k3 enterprise sp2 32bit. I tried several tips found on the
>> Citrix forums but still cannot boot the PV drivers. The same setup
>> runs fine if I boot into safe mode or uninstall the PV drivers.
>
> What are you trying to run the drivers on, XCP or stock xen-unstable/3.4?
stock xen 3.4.1
>
> If the latter, I believe there are a couple of minor protocol differences
that may cause problems. XCP should work fine. The protocol differences look
like useful improvements so it should be possible to get them upstreamed in some
backward compatible fashion over the next few weeks.
>
> In the meantime, if you''re using xen-unstable/3.4 it might be
worth trying the following:
>
> Create the key
> HKLM\System\CurrentControlSet\Services\xevtchn\Parameters, and then create
a DWORD value called SetFlags in there and set it to 0x10000000.
>
> I haven''t verified this works but it should get further.
>
I assume you meant xenevtchn above. I still get a bsod during boot but
the log file is much more interesting.

Qemu log and bsod image are attached.


Keith Coleman



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

Paul Durrant

2009-Nov-05 09:50 UTC

head link

Re: [Xen-devel] XCP Windows PV Driver Problem

Well, your problem starts with this line from the log:

[ERROR][XENVBD] Failed to set frontend key for data/scsi/target/0 
(device/vbd/768, c0000022)

This means that for some reason xenstore did not like our attempt to set 
a key data/scsi/0 with our frontend VBD path. The error was EACCES; my 
guess is because the data key has not been created under /local/domain/X 
by the open source toolstack.
The crash is then:

[NOTICE][XENUTIL] Bugcheck: 7b F8856A98, C0000034, 00000000, 00000000

(which does not match the BSOD, which is an ASSERTion failure)

This indicates, unsurprisingly, that Windows has no boot device.

Could you bring up your Windows and pause the boot (hit F8 or something) 
and then go in and create the data key (using xenstore_write and 
xenstore_chmod, to give the domain write perms.) from dom0 and then let 
Windows continue booting. This should hopefully allow the domain to then 
come up.

   Paul

-- 
==============================Paul Durrant, Software Engineer

Citrix Systems (R&D) Ltd.
First Floor, Building 101
Cambridge Science Park
Milton Road
Cambridge CB4 0FY
United Kingdom

TEL: x35957 (+44 1223 225957)
==============================
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Keith Coleman

2009-Nov-05 14:53 UTC

head link

Re: [Xen-devel] XCP Windows PV Driver Problem

On Thu, Nov 5, 2009 at 4:50 AM, Paul Durrant <paul.durrant@citrix.com>
wrote:> Could you bring up your Windows and pause the boot (hit F8 or something)
and
> then go in and create the data key (using xenstore_write and
xenstore_chmod,
> to give the domain write perms.) from dom0 and then let Windows continue
> booting. This should hopefully allow the domain to then come up.
>
Thanks Paul, you were correct.


Keith Coleman

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

Pasi Kärkkäinen

2009-Nov-19 15:50 UTC

head link

Re: [Xen-devel] XCP Windows PV Driver Problem

On Thu, Nov 05, 2009 at 09:50:56AM +0000, Paul Durrant
wrote:> Well, your problem starts with this line from the log:
> 
> [ERROR][XENVBD] Failed to set frontend key for data/scsi/target/0 
> (device/vbd/768, c0000022)
> 
> This means that for some reason xenstore did not like our attempt to set 
> a key data/scsi/0 with our frontend VBD path. The error was EACCES; my 
> guess is because the data key has not been created under /local/domain/X 
> by the open source toolstack.
> The crash is then:
> 
> [NOTICE][XENUTIL] Bugcheck: 7b F8856A98, C0000034, 00000000, 00000000
> 
> (which does not match the BSOD, which is an ASSERTion failure)
> 
> This indicates, unsurprisingly, that Windows has no boot device.
> 
> Could you bring up your Windows and pause the boot (hit F8 or something) 
> and then go in and create the data key (using xenstore_write and 
> xenstore_chmod, to give the domain write perms.) from dom0 and then let 
> Windows continue booting. This should hopefully allow the domain to then 
> come up.
> 
So I guess this means the normal Xen 3.4.x and xen-unstable toolstacks
should be patched to allow these XCP Windows PV drivers to be used? 

-- Pasi


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

Paul Durrant

2009-Nov-19 16:51 UTC

head link

Re: [Xen-devel] XCP Windows PV Driver Problem

Pasi Kärkkäinen wrote:> 
> So I guess this means the normal Xen 3.4.x and xen-unstable toolstacks
> should be patched to allow these XCP Windows PV drivers to be used? 
> 
That would certainly be helpful.

   Paul

-- 
==============================Paul Durrant, Software Engineer

Citrix Systems (R&D) Ltd.
==============================
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Keith Coleman

2009-Nov-19 18:54 UTC

head link

Re: [Xen-devel] XCP Windows PV Driver Problem

On Thu, Nov 19, 2009 at 11:51 AM, Paul Durrant <paul.durrant@citrix.com>
wrote:> Pasi Kärkkäinen wrote:
>>
>> So I guess this means the normal Xen 3.4.x and xen-unstable toolstacks
>> should be patched to allow these XCP Windows PV drivers to be used?
>
> That would certainly be helpful.
>
The XCP Windows PV drivers are closed source so we are completely
reliant on citrix fixing bugs, etc in a timely fashion. The GPLPV
Windows drivers are working quite well on xen 3.4.2 so I''m less
interested in the XCP ones at the moment.

About two weeks ago I created a patch to allow the XCP winpv drivers
to run on xen 3.4.1. I didn''t test live migration but save and restore
mostly worked. On restore the windows clock was reset to 1970, which
is presumably related to the PV drivers trying to trigger an ntp
update. At the moment I prefer adding functionality to the GPLPV
drivers rather than bending xen/tools around closed source drivers
that may not be maintained.

I will see if my current patch applies cleanly to 3.4.2 then consider
submitting as it''s unobtrusive.

Keith Coleman

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

Pasi Kärkkäinen

2009-Nov-19 18:59 UTC

head link

Re: [Xen-devel] XCP Windows PV Driver Problem

On Thu, Nov 19, 2009 at 01:54:33PM -0500, Keith Coleman
wrote:> On Thu, Nov 19, 2009 at 11:51 AM, Paul Durrant
<paul.durrant@citrix.com> wrote:
> > Pasi Kärkkäinen wrote:
> >>
> >> So I guess this means the normal Xen 3.4.x and xen-unstable
toolstacks
> >> should be patched to allow these XCP Windows PV drivers to be
used?
> >
> > That would certainly be helpful.
> >
> 
> The XCP Windows PV drivers are closed source so we are completely
> reliant on citrix fixing bugs, etc in a timely fashion. The GPLPV
> Windows drivers are working quite well on xen 3.4.2 so I''m less
> interested in the XCP ones at the moment.
> 
> About two weeks ago I created a patch to allow the XCP winpv drivers
> to run on xen 3.4.1. I didn''t test live migration but save and
restore
> mostly worked. On restore the windows clock was reset to 1970, which
> is presumably related to the PV drivers trying to trigger an ntp
> update. At the moment I prefer adding functionality to the GPLPV
> drivers rather than bending xen/tools around closed source drivers
> that may not be maintained.
> 
I agree. It''s better to develop GPLPV drivers. Then again it''s
good to
have other option to bechmark and test against/with :)
> I will see if my current patch applies cleanly to 3.4.2 then consider
> submitting as it''s unobtrusive.
> 
Yep. Please do that :)

-- Pasi


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

Xen devel - Nov 2009 - XCP Windows PV Driver Problem

[Xen-devel] XCP Windows PV Driver Problem

Re: [Xen-devel] XCP Windows PV Driver Problem

RE: [Xen-devel] XCP Windows PV Driver Problem

Re: [Xen-devel] XCP Windows PV Driver Problem

Re: [Xen-devel] XCP Windows PV Driver Problem

Re: [Xen-devel] XCP Windows PV Driver Problem

Re: [Xen-devel] XCP Windows PV Driver Problem

Re: [Xen-devel] XCP Windows PV Driver Problem

Re: [Xen-devel] XCP Windows PV Driver Problem

Re: [Xen-devel] XCP Windows PV Driver Problem