Wojciech Kusiak
2012-Sep-22 20:51 UTC
GPLPV .356/2008 R2 x64/xennet.sys - interfaces don''t work, bluescreens if xenvbd also installed
Good evening. I am in a bit of a weird situation here, so let me apologize up front if this will turn out to be a waste of everyone''s time. I have up to date Win 2008 R2 x64 SP1 VMs running at a Xen-based provider not of my choosing. After installing GPLPV rev. 356 (signed from Univention) and rebooting, I''m getting a bluescreen in xennet.sys a few seconds after boot. The VMs have 2 vCPUs each, so it may or may not be related to the 16-cpu issue reported on this list earlier. I have no idea how the underlying Xen host is configured, or what versions it runs. The provides it quite unhelpful (once again - I have no say in the matter of provider choice). In short: Originally, on a test machine, I''ve installed the whole pack (that being xenpci, xennet, xenvbd, xenscsi, xenusb). It started to bluescreen right after reboot (usually a few seconds after the "Press C+A+D to log on" prompt appeared. The bluescreen was IRQL_NOT_LESS_OR_EQUAL in xennet.sys, but I did not note the hexcodes then. I''ve undone the setup, tried to install just the xenpci + shutdownmon, cleared the registry for the emulated RTL8139 NICs to reappear, and gave up. Right now I''m testing on a different VM - and I see the following: * xenpci + xennet = no bluescreen, Xen Net adapters appear, but zero network connectivity (the packets in/out counters stay at 0, DHCP info not obtained, etc.) * xenpci + xennet + xenvbd = bluescreen _in xennet.sys_. DRIVER_IRQL_NOT_LESS_OR_EQUAL, happens variously between a few seconds and about 2 minutes after boot. *** STOP 0x000000D1 (0x00000000000000028,0x0000000000000002,0x0000000000000000,0xFFFF8800F9A104) *** xennet.sys - Address FFFF8800F9A104 base at FFFF8800F9700, DateStamp 4f6b1e83 Any hints about what to do to get the xennet adapters running? I don''t really need xenvbd - the disks are fast enough without it - but considering this bluescreen happens after installing xenvbd but in xennet, and that the xennet alone doesn''t crash but the adapters don''t work, I''m reporting these issues together. My main reason for trying to get xennet to work again is that the RTL8139 NICs are causing massive interrupts spam (whole CPU in kernelmode, Process Explorer blames interrupts, network I/O topping around 20 MBit/s). If they shouldn''t do that, and there''s a way to make them stop doing that, I''d accept that as a "solution". You probably will need additional information - please tell me what''s necessary. In case of host information, please be precise - I''ll be having a hard time convincing the provider to obtain them, it''d take even longer if they wouldn''t understand what we want from them. Best regards, Wojciech Kusiak