similar to: forgot ARCH=xen

I am trying to build xen on x86_64 SLES 9 SP2 box this morning and am getting this error: arch/xen/kernel/built-in.o(.text+0x1bd6): In function `__do_suspend'': : undefined reference to `HYPERVISOR_vcpu_pickle'' make[4]: *** [.tmp_vmlinux1] Error 1 make[4]: Leaving directory `/tmp/xen-unstable.hg/linux-2.6.12-xen0'' make[3]: *** [build] Error 2 make[3]: Leaving directory

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

As promised, here''s what I did to get iSCSI root running under XenU under Debian 3.1 (Sarge): Be running linux 2.6 under XenU. Build XenU with SCSI disk support (I did them as modules) Get linux-iscsi 4.0.1.8 from http://sourceforge.net/projects/linux-iscsi/ Build it according to the instructions there (i found it a bit tricky) and install under your XenU Get iscsi-init 4.0.1 from

Hello, All, Today one of our servers was crashed, after I rebooted the server, one vps can not boot up, and it needs fsck, after I run fsck command, a lot of files lost, and also some file content was changed. Not sure how could it happen, do you have any advice that can avoid this or recover the data? Thanks. _______________________________________________ Xen-users mailing list

''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

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

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 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, DomU is a Win2008 R2 64 When i install the GPLPV drivers the network latency goes from 15ms to random numbers up to 1200ms and eventually dies. If you run a ping from the DomU to another host the network stays alive but the high latency is still there. Further more if i try and uninstall the network driver i am unable to use the old one (realtek) as it cannot detect the device.

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

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

Well, I seem to have developed a strange issue with the GPL PV drivers in Windows. I''m running Xen 3.2 on SLES 10 SP2 and running some Windows XP HVM domUs. Most (12-15) of my Windows machines work just fine. Two of them, though, have started exhibiting a strange behavior with intermittent network connectivity. Basically, the network starts up and connects initially. After some

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:

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:

A user has pointed out a problem with GPLPV under Xen 4.2 when using PoD. I''m using the difference between XENMEM_maximum_reservation and XENMEM_current_reservation to tell me how much I should balloon down to account for PoD, but when the user has ballooned down to 1G (from 4Gb or 8GB), GPLPV logs the following: 13005008825593: XenPCI XENMEM_maximum_reservation = 262400

So I successfully installed the GPLPV drivers in a Windows installation I have running under Xen. Turns out SP2 is needed - I wish this was slightly better documented somewhere, as the machine ended up bluescreening and I had to use /NOGPLPV to get it to boot again so I could upgrade it to SP2. My question is this: I ended up using ''disable'' in device manager for the rtl8139 and

Hi all, when running Windows 2008 SBS on Xen 4.0.0, it disappears after some time (longest time I had it running was 20 minutes). In /var/log/xen/qemu-dm-win1.log I find: xc_map_foreign_batch: mmap failed: Cannot allocate memory xc_map_foreign_bulk error 12 Anyone any idea how to troubleshoot this? The Hypervisor has 16 GB of RAM, currently 2 GB are allocated to Dom0. This specific DomU has 8

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

Has anyone had any success with the HP T/R2200 G2? I have used the T/R2200 with nut a few times before and it works great, but the G2 doesn't want to talk to me. I have tried bcmxcp from 2.0.4, 2.2.2, and svn, as well as the usb drivers. Maybe the G2 isn't a rebadged powerware unit? Thanks James