similar to: DMA not enabled in Xen Kernel?

Hi, I am using centos4 and am trying to build a source kernel dom0 with xen. I cloned a copy of the xen repository and did the following hg clone http://xenbits.xensource.com/xen-2.0.hg cd xen-2.0.hg/xen make dist cd linux-2.6.11-xen0 make ARCH=xen oldconfig make modules make modules_install make install After which point I get the following error : CC drivers/xen/balloon/balloon.o

Attached patch makes the balloon driver arch-neutral (compiles on ia64... look ma, no #ifdef''s!). Please apply to xen-unstable. One change should be eyeballed, line 257 in balloon.c, because phys_to_machine_mapping[pfn] is not identical to pfn_to_mfn (different by sign bit, should be OK?) Signed-off by: Dan Magenheimer <dan.magenheimer@hp.com> diff -r 0255f48b757f

hi I try to understand the code of balloon ,and got confused about the following parts of code: static int decrease_reservation(unsigned long nr_pages) { .... if (!PageHighMem(page)) { v = phys_to_virt(pfn << PAGE_SHIFT); scrub_pages(v, 1); ret = HYPERVISOR_update_va_mapping( (unsigned long)v, __pte_ma(0), 0);

Hi all, I am using Xen 2.0.7. I have Broadcom NetXtreme BCM5704 Gigabit Ethernet (rev 02) cards which support frames greater than 1500. However when I boot into Xen and try to set the MTU to anything higher than 1500 (e.g., 4000, 8000 etc) I get a segmentation fault. After this fault, every command fails with a segmentation fault. I saw a similar bug report posted here:

Hi, Here is the third version of memory hotplug support for Xen guests patch. This one cleanly applies to git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git repository, xen/memory-hotplug head. On Fri, Aug 06, 2010 at 04:03:18PM +0400, Vasiliy G Tolstov wrote: [...] > Testing on sles 11 sp1 and opensuse 11.3. On results - send e-mail.. Thx. On Fri, Aug 06, 2010 at 12:34:08PM

Hi! i notice a serious regression with 3.5 as Dom0 kernel (3.4 was rock stable): 1st: only the GPU PCI Passthrough works, the PCI USB Controller is not recognized within the DomU (HVM Win7 64) Dom0 cmdline is: ro root=LABEL=dom0root xen-pciback.hide=(08:00.0)(08:00.1)(00:1d.0)(00:1d.1)(00:1d.2)(00:1d.7) security=apparmor noirqdebug nouveau.msi=1 Only 8:00.0 and 8:00.1 get passed through

Hi, Is there any tool out there that can help me analyze a coredump? Thanks, David. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Our newly build xen kernel does not boot. The error message is : Invalid or unsupported executable format. I have build xen from the xen-2.0.4 source (make world, make install) on a debian sarge system. I have not changed any of the kernel configurations, I did make an initrd image. The entry in my menu.lst is : title Debian GNU/Linux, kernel 2.6.10-xen0 root (hd0,0) #

Hi guys I have few problems with live migration ... and I need some professional help :) I have 2 xen servers ... CentOS 5.3 and I want to have a high available cluster Now let`s begin .... xen0: [root@xen0 ~]# fdisk -l Disk /dev/sda: 218.2 GB, 218238025728 bytes 255 heads, 63 sectors/track, 26532 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start

I am installing Xen on a remote server. I left the other kernels on the grub.conf and made xen the default to boot from. The box didn''t boot into Xen on reboot but I''m not sure why. Here is my Xen config file: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that #

Hi How do I make an initrd for xen. I''m trying to boot rhel3 in fc4, and it keeps getting stuck at Freeing unused kernel memory. I''ve created the device files, but it still doesn''t boot up. I''m pretty sure that the solution lies in makeing an initrd file. Currently my xenU kernel is 2.6.11-1.1369_FC4xen0. Can someone please tell me how to do this? Many

We saw these issues in recent ChangeSet: 1. Reboot fail in Guest OS: Reboot in guest will close current qemu windows but does not create a new qemu window to restart 32bit HV/xen0: 2. 4 LTP math cases(float_bessel, float_exp_log, float_power and float_trigo) sometime fail. (775) 3. Kernel build in VMX may meet kernel panic. It complains like: "<0> Kernel panic - not syncing:

I''m a newbie. :) I followed the steps written by Jerone Young: http://sourceforge.net/mailarchive/message.php?msg_id=10562241 but i found an error at the 17th step: 17. mkinitrd /boot/initrd-2.6.10-xen0.img 2.6.10-xen0 it said:"No module ata_piix found for kernel 2.6.10-xen0, aborting." so I commented the line of "module /boot/initrd-2.6.10-xen0.img" in the

Hello, I am getting kernel panic while trying to xm create a domU. Xen version 3.0 Linux kernel 2.6.12.6 Grub entry for dom0: title Xen 3.0 / XenLinux 2.6 kernel /boot/xen- 3.0.gz console=vga module /boot/vmlinuz-2.6-xen0 root=LABEL=/ ro console=tty0 module /boot/initrd-2.6.12.6-xen0.img For domU, my xm file contains: kernel = "/boot/vmlinuz-2.6.12.6-xenU "

When compiling a 2.6.10-xen0 kernel I get the following error: CC drivers/xen/balloon/balloon.o drivers/xen/balloon/balloon.c: In function `balloon_process'': drivers/xen/balloon/balloon.c:209: error: `phys_to_machine_mapping'' undeclared (first use in this function) drivers/xen/balloon/balloon.c:209: error: (Each undeclared identifier is reported only once

Hello, I''m trying to build XenLinux 2.4.30 on debian. I get the following error for make linux24 make[2]: *** No rule to make target `skbuff.c'',needed by `/usr/src/xen-2.0/linux-2.4.30-xen0/include/linux/modules/skbuff.ver''. Stop. Could somebody help me resolve this error. Or if this is some problem with the system configuration that I''m using, could

With today''s build, my domain 0 crashes during boot when it tries to bring eth0 up (it''s an E100). cb->prev (eax) is NULL in e100_exec_cb() (e100.c:827). Just from code inspection, I don''t see how this can be. e100_alloc_cbs() was just called, which looks like it should have correctly linked up all the cb->prev/cb->next pointers. It happens regardless of

Hi all, A number of people have posted to the Xen lists recently wanting to network-boot Xen on machines whose NICs are not supported by GRUB. I''ve been writing a module for PXELINUX that will allow it to boot Xen directly over the network on PXE-enabled machines, without relying on any hacks (mbootpack, &c.), or needing to write/port any device drivers. I have a version of it

Hello, I have a big startproblem with the dom0 kernel. I use the latest stable xen with the 2.6.10 kernel. menu.lst: --- title Xen 2.05 / XenLinux 2.6.10 kernel /boot/xen.gz dom0_mem=512M noreboot module /boot/vmlinuz-2.6.10-xen0 root=/dev/sda1 ro console=tty0 --- Starterror: --- (XEN) Initial guest OS requires too much space (XEN) (8MB is greater than 0MB limit) --- System: I use an fresh

Hi List, I run XEN 2 since some month (unfortunatly installed by a fiend of mine). Recently I bought some new hardware and tried to get XEN 3 running on a Debian Sarge 3.1. I installed via the Debian installer a RAID 1 with LVM. even though there are some devfs_mk_dir errors systems comes up. Now I installed XEN but system doe not boot as the boot device seems not to be recocnized by the