similar to: trouble with xennet gplpv in win7x64 xen(xvm)3.4

I have installed the 210 gplpv (debug), when I try to update them with current gplpv I get a BSOD even so when I try to uninstall them. Now I have made a bootentry that specifies NOGPLPV, what gives me a bootable system after such a crash, I found (uninstalling the leftover driver packages after getting bsod during uninstall of the main package) that uninstalling the net driver leads to bsod. Now

Hello, I installed the signed drivers from http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers and I ran into a BSOD on a Windows 2008 Server R2 Enterprise domU with a large number of vcpu''s. The BSOD is related to xennet.sys. After some trials I found that it runs fine up to 15 cores. From 16 or more, the BSOD kicks in when booting the domU. The hardware (4 times

I saw some really bad things happening on our production servers. First dom0: Ubuntu xen1 2.6.24-24-xen Xen 3.4.0 compiled from source. I don''t remember exactly what GPLPV version was installed but I know for sure from early 10.x series. domU: Windows Server 2008 64-bit (Test mode enabled) Second dom0 has almost identical setup, thou on different hardware. When I start copying large

On Sun, Jun 8, 2008 at 3:28 PM, James Harper <james.harper@bendigoit.com.au> wrote: > I''ve just uploaded 0.9.8 to http://www.meadowcourt.org/downloads > > As a reminder, the wiki page is > http://wiki.xensource.com/xenwiki/XenWindowsGplPv > > This release fixes a bug which could be hit under high disk load (high > number of outstanding requests with fragmented

Hi there. I have been dealing with a conundrum off and on with a VPS of mine. Windows 2003 Standard 32 bit on a Xen HVM instance. Been trying to get the GPLPV drivers working to help boost performance but always seem to run into one major issue: The PV network device looks like it works but actual connectivity is non-existant. Everything else in the GPLPV driver suite works fine. What I want to

Hey guys, I''m trying to get a gentoo dom0 running on some new Nehalem boxes. Our dozen or so existing servers run a xenified 2.6.21, but we can''t get the new Intel network chipset working with it. So, I''m giving a pv_ops dom0 from xen-tip/master a go, and Xen 3.4.1 to go with it. rebase/master is a bit too bleeding edge for me. So far, it''s working great.

I''ve just uploaded a prerelease of 0.9.9 to http://www.meadowcourt.org/downloads/ Please read the following before using: It fixes a few disk related bugs... I''ve just been testing it on a Windows Small Business Server 2003 R2 I have just restored from tape into a DomU from a backup of a physical system and it''s working fine - 0.9.8 BSOD''d almost immediately

I''ve just uploaded a prerelease of 0.9.9 to http://www.meadowcourt.org/downloads/ Please read the following before using: It fixes a few disk related bugs... I''ve just been testing it on a Windows Small Business Server 2003 R2 I have just restored from tape into a DomU from a backup of a physical system and it''s working fine - 0.9.8 BSOD''d almost immediately

I have a strange problem with these drivers. I have a host that has 31 VM''s running on it, all windows. They are running the same template, which has the latest GPLPV drivers installed. The problem occurred today when I went to add the 32nd VM, again from the same template. Now when the VM boots up I get a BSOD. I tried a different template to confirm that it was not template

Running GPL PV Windows drivers on Windows 2003 Server Standard Edition SP2 - The current GPL PV Windows xennet driver source found in the repository will BSOD if the option "Large Send Offload" is changed to disabled or if the driver is disabled. Tracked down the issue via WinDbg – If a buffer is in the free list prior to the function XenNet_RxBufferFree() being called via the function

Running GPL PV Windows drivers on Windows 2003 Server Standard Edition SP2 - The current GPL PV Windows xennet driver source found in the repository will BSOD if the option "Large Send Offload" is changed to disabled or if the driver is disabled. Tracked down the issue via WinDbg – If a buffer is in the free list prior to the function XenNet_RxBufferFree() being called via the

Hi, I just tested booting Windows 2008 server 64 bit using GPLPV drivers. It seems to work with qemu traditional, but with Qemu upstream (1.1-stable) there is a BSOD when using the most recent signed GPLPV drivers (paging fault in non-paged area). -- Stay in touch, Mark van Dijk. ,--------------------------------- -----------------------------'' Sat Sep 08 08:14

I''ve just committed a fix to hg that fixes a problem in the bug check code, which mostly explains why crash dumps weren''t always being written out, and I have a suspicion that without the fix there is a chance of filesystem corruption when a crash dump occurs. Can anyone using GPLPV comment on whether they might have seen this? Basically, everything works fine under GPLPV (no

Hi, I am at a complete loss of ideas here: I have a - xen3.3.1 hypervisor compiled from source with - dom0 being 2.6.26-1-xen-amd64 kernel from debian/lenny repository with - windows 2008 64bit as hvm guest. I use the gplpv drivers 0.10.0.69 from James Harper. The included files (xenpci.sys and xennet.sys) are apparently test-signed, so applying test-signing as boot option does enable

Hi, During the install of the univention.de-signed GPLPV drivers (gplpv_Vista2008x64_signed_0.11.0.308.msi) on my Windows 7 guest, I get a BSOD "DRIVER_IRQL_NOT_LESS_OR_EQUAL" in xenvbd.sys. Afterwards, Windows won''t start. I''m now trying to do a System Restore. I will try not installing the VBD driver afterwards and see if the others do work. Full BSOD:

When trying to use the GPL PV drivers with Windows 7 x64 (and testsigning turned on), I get a BSOD with a STOP 0x00000101 error. There''s also an error at the top that says "A clock interrupt was not received on a secondary processor within the allocated time interval." Is this STOP error related to the HPET or other timing adjustments for Xen? Any advice on things I should

Hello, I have Xenserver 5.0. When i install a new VM with Windows Server 2003 X64 Standard (R2) and install all windows-updates, it gives me a BSOD when i install the PV 0.9.12pre3 drivers. Steps to reproduce: - Install Xenserver 5 (light/free or Enterprise/trial) - Install a Windows Server 2003 x64 R2 VM from a ISO or CD - Install all windows updates - Download the GPLPV 0.9.12pre3 .exe file

Hey, I''ve been trying to get the gplpv drivers working with Windows 2008 R2 64-bit on both a stock CentOS 5.8 install and CentOS 5.8 w/ Xen 4.1.2 from the gitco repos. I''m getting a BSOD shortly after boot up and it can be seen at http://techmonkeys.org/xen/ -- along with the qemu log. Has anyone had success with these drivers and Windows 2008 R2 64-bit? If so, what am I

I have set up both Windows XP and Windows 2000 Server clients on Xen under Centos 5.1 and am unable to install an application firewall. I have tried the latest: 1) Agnitum Outpost Commercial Version 2) Comodo Firewall (ver 2 on Windows 2000) 3) Sunbelt Commercial Version With all of these when the firewall starts up it results in a BSOD. With Windows XP and Agnitum I can go back to a previous

Hello. I have encountered a problem with GPLPV drivers for windows. It is similar (if not the same) as http://old-list-archives.xen.org/archives/html/xen-users/2011-02/msg00709.html Host is running 14 virtual machines with Windows XP. When I''m trying to start 15-th windows VM it crashes with code 0x0000007b. Booting to safe mode or with /nogplpv works ok. 15-th VM works fine if