similar to: Build win-pv Error

Hi, I tried using win-pvdrivers 0.8.4 on German Windows XP Pro SP2. Xen is 3.1, comes with Ubuntu 7.10. Everything seems to work well except the shutdown monitor. If I run shutdownmon.exe on the command line, windows gives an error message stating it could not initialize shutdownmon.exe correctly. Parameters passed to shutdownmon.exe don''t have any influence on the error. The original

> Hello James, > > first of all thanks for your effort in writing the PV drivers for Windows. > Shame that there are at least 3 working PV drivers sets from different > vendors > but none open-source. > > I am looking for a solution of graceful shutdown of Windows domains and > found > your drivers. I''m wondering if installing the ShutdownMon service is

Signed-off-by: Paul Durrant <paul.durrant@citrix.com> --- xen/include/public/hvm/pvdrivers.h | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/xen/include/public/hvm/pvdrivers.h b/xen/include/public/hvm/pvdrivers.h index 4c6b705..77994d2 100644 --- a/xen/include/public/hvm/pvdrivers.h +++ b/xen/include/public/hvm/pvdrivers.h @@ -38,10 +38,12 @@ * indicate

Hi All, I am using samba-common-3.0.10-1.4E.9 on a RHEL4_U4 x86 machine. The ADS server is WS03 sp1 running in Windows Server 2003 interim mode. In general thing are working well. However, when winbind caching is enabled (default), group membership does not appear to update, i.e. "wbinfo -r bob" and "groups bob" don't reflect changes in ADS group membership.

Hello I have a Supermicro system with Intel XEON cpu with VT enabled. HVM, without Windows PV driver, works great. I am trying to use Windows PV driver from XCP 0.5, it is in the .iso file of XCP 0.5 Filename: windows-pvdrivers-xensetup.exe I have tried - XEN 3.4.3 (Linux 2.6.18.8) - XEN 4.0.1-rc6-pre (Linux 2.6.31.x and Linux 2.6.32.x from Jeremys GIT) and - XEN 4.0.1-rc6 (Linux 2.6.31.x and

Hi James and Xen folks, Apparently when I said the GPLPV net driver was sending and receiving packets, I was not quite correct. I am having the following issues: 1) It successfully receives packets and passes them to the net stack by calling NdisMIndicateReceivePacket(). However, something must be wrong because the packets (incl DHCP offer) are not registering with the OS and it ends up with a

This patch cleans up some 80-odd warnings I was seeing when compiling the xenpci driver, all completely trivial. It also replaces the use of asm for calling cpuid with the __cpuid compiler intrinsic, and modifies calling code accordingly. I''m pretty sure my mailer going to mangle the inline patch (below) so I''m attaching the pristine version. (will try to fix for next time) --

hi james, the win2008r2 vm crash problem while migration seems related about the AllocatePage. according to the previous BSOD info, we modified code to test if page address after AllocatePage is FFFFFA8000000000 or FFFFFA8000000002. if FFFFFA8000000000 , then free it immediately, and allocate again. the test result shows 12948535073500: XenPCI --- AllocatePages IRQL = 0, Buf =

Hi James. I go through the patch, since all its changes happens inside __xen_evtchn_do_upcall(), so I apply the patch into my 2.6.31.kernel by manual. (I was failed to merge a usable, 2.6.38dom0, since quite a lot branch needed, such as blkback, netback) But still, the blue screen shows up. Log attached. Is the timeout better than before? Beside, I think I need find some to examine my

I''m been busily converting the xenpci and xenvbd drivers from WDF to WDM to resolve a few issues including potential licensing problems with the Microsoft WDF and to (hopefully) allow them to function as boot drivers when doing install and system recovery. It was a fairly major rewrite of xenpci, and xenvbd, which are now working (booting and running without crashes so far). I

I''m been busily converting the xenpci and xenvbd drivers from WDF to WDM to resolve a few issues including potential licensing problems with the Microsoft WDF and to (hopefully) allow them to function as boot drivers when doing install and system recovery. It was a fairly major rewrite of xenpci, and xenvbd, which are now working (booting and running without crashes so far). I

Dear List, I?m trying to figure out *memory page sharing***using HVM on Xen 4.0.1, but I?m not really able to find some useful information or sources about this issue. I just found two links porviding these sources: http://knol.google.com/k/learning-grant-tables http://blog.chinaunix.net/space.php?uid=20286427&do=blog&id=109114 Both are not working.. I think they are made for an older

Kathy, Thank you very much! Peter Olson Alcatel-Lucent Member of Technical Staff Services Technologies 1960 Lucent Lane Rm 7G334 Naperville, IL 60566 peterolson@alcatel-lucent.com Phone: 630 979 0573 Mobile: 630 430 6926 -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of xen-users-request@lists.xensource.com Sent:

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 all, I try to use kernel 2.6.36.1 in HVM but building the drivers xen-blkfront, xenfs, platform-pci. I used Xen 4.0.2-rc1-pre and a DomU is a ubuntu 10.04 and I try with ubuntu 10.10. In boot I receive error "Cannot find a root partition /dev/xvda2" and a prompt (initramfs) appear. In dmesg (initramfs) appear: blkfront: xvda: barriers enabled (tag) xvda: xvda1 vbd vbd-51712: 16

Hi all, I try to use kernel 2.6.36.1 in HVM but building the drivers xen-blkfront, xenfs, platform-pci. I used Xen 4.0.2-rc1-pre and a DomU is a ubuntu 10.04 and I try with ubuntu 10.10. In boot I receive error "Cannot find a root partition /dev/xvda2" and a prompt (initramfs) appear. In dmesg (initramfs) appear: blkfront: xvda: barriers enabled (tag) xvda: xvda1 vbd vbd-51712: 16

Dear Xen users! In case you were struggling with recent version of th gplpv drivers, I''ve possibly found an LVM related bug in it, and reported to James Harper. Thats''s the point: I''ve tested the mentioned version of your driver on top of 32bit xen-3.2.1 32bit xen-3.3.0 and 64bit xen xen-3.3.0 hypervisors, dom0 was always an appropriate version of a 32bit PAE kernel,

Hi, I just played with the new GPL PV driver release a bit, and there''s a problem when running the included install.bat from a read-only device (pvdriver.zip was extracted, and "burned" to virtual CD) Cause of this problem: During installation dpinst.exe is copied to the matching driver directory (located on the install media) and executed there. Unfortunately this fails

I'm seeing a bunch of failures on AArch64 after updating this morning. These are NOT failing on x86-64. These all seem to be caused by segfaults (example backtrace below). Is anyone else seeing this? -David LLVM :: DebugInfo/symbolize-no-debug-str.test LLVM :: tools/gold/X86/comdat.ll LLVM :: tools/gold/X86/visibility.ll LLVM ::

Hi Is it true that the GPLPV drivers is incompatible with QCOW images? The Windows DomU works fine with raw standard "file:/" images, and paravirtualized Linux DomU works fine with QCOW and raw images. If i use QCOW images with my Windows DomU''s i get a stop error: 0x00000007b (inaccessible boot device). It looks like the blkback.3.hda process, that normally starts with