similar to: linux-2.6.18-xen.hg

I have been trying to track down a problem that occurs when my GPLPV drivers give Windows a packet with the NdisPacketTcpChecksumSucceeded flag set. The problem is that the machine locks hard. After some tedious work with the debugger, I have found that Windows makes a call to a routine called RtlPrefetchMemoryNonTemporal, which looks like this: 8088e579 mov eax,dword ptr

Hi I have a problem with mercurail repository (with compiling source tree of xen 3.3.0): Trying to "make world" command (first time) I obtain the following: select-repository: Searching `.:..'' for linux-2.6.18-xen.hg select-repository: Ignoring `.'' Unable to determine path to Linux source tree. Falling back to linux-2.6.18-xen Mercurial repository. Cloning

''xm block-attach'' doesn''t let me assign the same backend device anymore, even if I use ''r!'' or ''w!''. I think this has changed since 3.1.1 (or maybe since 3.1.0). Is this the way it is supposed to work? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi all, When I make the ram disk for xen-3.3.0, I encounter a problem. $mkinitrd -v -f initrd-2.6.18.8-xen.img 2.6.18-xen ... No module pata_marvell found for kernel 2.6.18.8-xen, aborting. Compared part of source code between linux-2.6.18-xen.hg/driver/* and linux-2.6.18/driver/*(from kernel.org), I found that linux-2.6.18-xen.hg/driver/ata doesn''t exist. ( some source code of module

I really need to have the ability to tie event channel port''s to interrupts for my gplpv drivers under Windows. Is anyone working on anything like this? Does MSI allow more than one interrupt per PCI device? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I am having problems with save/restore under 3.3.1 in the GPLPV drivers. I call hvm_shutdown(xpdd, SHUTDOWN_suspend), but as soon as I lower IRQL (enabling interrupts), qemu goes to 100% CPU and the DomU load goes right up too. Xentrace is showing a whole lot of this going on: CPU0 200130258143212 (+ 770) hypercall [ rip = 0x000000008020632a, eax = 0xffffffff ] CPU0 200130258151107 (+

Hi, I downloaded xen-3.3.0.tar.gz and linux-2.6.18-xen-3.3.0.tar.gz from http://www.xen.org/download. when I executed "hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg", there was an error. Prompt was: destination directory: linux-2.6.18-xen.hg abort: error: Temporary failure in name resolution How can fix this problem? Thanks, Jeff.Gu

I''ve recently noticed that my windows crash dumps fail at around 40-50% under GPLPV. ''xm dmesg'' shows the following: (XEN) grant_table.c:350:d0 Iomem mapping not permitted ffffffffffffffff (domain 865) At first I thought that the cause was just a bug in my grant ref code but it just occurred to me that this could be happening when Windows tries to write out the

I''m just doing some testing on the gplpv drivers with different ways of handling interrupts, and I''m trying a scheme where each xen device (eg vbd/vif) driver attaches to the same IRQ as the pci driver, and each handles it in sequence. In testing though, I noticed the following when logging what each ISR is doing: 60.32381439 - evtchn event on port 5 60.32384109 - port 5

How should I be detecting a block-configure operation done in Dom0 in a HVM DomU? Under Debian Lenny''s Xen 3.2.1, when I execute such a command, Dom0 writes to the backend values ''params'' and ''type'', twice, but doesn''t update the ''sectors'' value to match the new device, or initiate a state change. Given that, the best I can

The attached patch fixes the save/restore issue seen with 32bit Windows guest VMs. The root cause is that current Xen doesn''t intercept SYSENTER-related MSRs for 32bit guest VMs. As a result, the guest_sysenter_xxx fields contain incorrect values and shouldn''t be used for save/restore. This patch checks the LMA bit of EFER register in the save/restore code path. Please apply it

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

lspci shows MSI enabled for PCI device. PCI passthrough works fine. However, as soon as the MSI driver for card is insmodded, kernel panics. This is on xen-unstable. Tried the same with xen-3.3.0 which is supposed to have MSI passthrough, but the same guest shows MSI as disabled. Any else seen this bug, or know of a workaround ? Trace is as follows : ------------[ cut here ]------------

I am currently running kernel 2.6.18-6-686 on Debian Etch 40r3. I am trying to install xen on it. I tried installing linux-image-2.6.18-6- xen-686, but when I restarted, it doesn''t boot instead shows a kernel panic. I ran #apt-get install linux-image-2.6.18-6-xen-686 and changed /boot/grub/menu.lst file to point to current xen kernel. While rebooting it showed kernel panic and

I just about have my PV block device drivers booting, except just before the login screen appears I get a message that the registry couldn''t be written out. I''m pretty sure that this is because some data from the int13 interface provided by the qemu intel ide driver that has been written, hasn''t actually made it to the block device (lvm volume in my case). I''ve

I have just uploaded a new testing version of GPL PV drivers for Windows. Have a look for 0.10.0.97-dontuse at http://www.meadowcourt.org/downloads (the -dontuse bit is to scare people away who haven''t read this email :) As usual, please test thoroughly on a test DomU and make sure you have a backup before installing on a non-test system. In particular, I''m only testing with Xen

I have just uploaded a new testing version of GPL PV drivers for Windows. Have a look for 0.10.0.97-dontuse at http://www.meadowcourt.org/downloads (the -dontuse bit is to scare people away who haven''t read this email :) As usual, please test thoroughly on a test DomU and make sure you have a backup before installing on a non-test system. In particular, I''m only testing with Xen

Hello List, I have a small problem with the ring when transferring blocks the id on the response is different from the request. This is the boot up read, count 0. The guest requests block 0, it has to be located at 7c00. I go ahead and create a REQUEST with this data: ring_req = RING_GET_REQUEST(priv,priv->req_prod_pvt); ring_req->id = 9; ring_req->nr_segments=1; ring_req->operation

I''ve just uploaded a couple of .bat files to http://www.meadowcourt.org/downloads/gplpv_uninstall_bat.zip that will manually (and forcibly) uninstall GPLPV from your computer, which seems to be necessary before doing upgrades from some versions. Run the uninstaller, reboot, then install. There is a 0.9.x and a 0.10.x uninstaller, which differ slightly, but the basic steps performed are: