similar to: kernel 2.6.30 xenified --- report - firmware problem

Known bug for 32-bit. Workaround is on the net. http://mulps.wordpress.com/2009/05/29/compiling-xen-kernel-2-6-29-2/ Boris ________________________________ From: Mehdi Sheikhalishahi <mehdi.alishahi@gmail.com> To: bderzhavets@yahoo.com Sent: Sun, January 3, 2010 4:25:00 PM Subject: Xenified linux kernel Hi Dear: I am refering to the

Andy, OSOL 2009.06 been installed in stub domain (hvm domain) at mentioned Dom0 with 2.6.30 xenified kernel via xen-patches-2.6.30-2.tar.bz2 refuse to activate PV drivers. When same Dom0 starts with 2.6.29.4 xenified kernel (xen-patches-2.6.29-6.tar.bz2) kernel OSOL 2009.06 in stub (hvm) domain does activate PV drivers for xdf, xnf . Boris

Is there any real user for this vIRQ? I''m asking because, while debugging a problem that required to add some printk()s that could temporarily issue at a high rate, I ran into the situation that this extra output prevented guest/dom0 boot from making any progress. As I then realized this was due to the tasklet_schedule() called from inside the console handling code, which resulted in

Is there any real user for this vIRQ? I''m asking because, while debugging a problem that required to add some printk()s that could temporarily issue at a high rate, I ran into the situation that this extra output prevented guest/dom0 boot from making any progress. As I then realized this was due to the tasklet_schedule() called from inside the console handling code, which resulted in

Hi all,   I install Xen on a fresh Ubuntu 9.04 from source. During the code runing it shows usually "Warning: not literal format or no paramaters". By "make" linux kernel after 1 hours code running it ends with: (The installation steps is shown below)   --------------------------------------------------------------------------- WARNING: modpost: Found 1 section mismatch(es). To

Setting CONFIG_CMDLINE_BOOL=y in .config allows to assign desired value via make menuconfig: Symbol: CMDLINE [=root=/dev/sda14 ro console=tty0]                                                       Prompt: Built-in kernel command string                                                                       Defined at

  Tne answer is NO. Any vanilla kernel (> 2.6.27) itself allows only to enable PV Guest (paravirtual) mode, but not Xen Dom0 Support. Mainline Linux doesn''t  contain Xen Dom0 Support merged. You have to work on it on your own.   I''ve sent you two links in the very first message. View second one - patching 2.6.30.1 via Andrew''s Lyon rebase patch set :-  

Hi, i try the kernel from [1] and get: WARNING: vmlinux.o (__xen_guest): unexpected non-allocatable section. Did you forget to use "ax"/"aw" in a .S file? Note that for example <linux/init.h> contains section definitions for use in .S files. WARNING: modpost: Found 2 section mismatch(es). To see full details build your kernel with: ''make

I have installed Ubuntu Intrepid Server on bare metal and successfully ran:- # apt-get install ubuntu-xen-server.     It installed several packages on system . Now i can see files /boot/xen-3.3.gz, /etc/init.d/xend, /etc/init.d/xendomains, but no xenified kernel gets in. Attempt  to use vmlinuz-2.6.27-7-server, obviously , fails with system panic.    I do remember recompiling  procedure for Xen

I''ve uploaded updated 2.6.31 and 2.6.32 rebased openSUSE Xen dom0 patches and ebuilds to http://code.google.com/p/gentoo-xen-kernel/downloads/list Notable change is that both include the online resize feature recently posted to xen-devel. Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello,   I can say that I have searched the entire ''world wide web'' and still haven''t found ''complete  and clear answers'' to the often asked question of: Given a Xen (release) build (say 3.2.0), which by default tries to get and build and assume Linux kernel-xen 2.6.18 from the mercurial repository, HOW TO override the build and make it work with a

Following bellow procedure involves Solaris Kernel module debugger to patch OSOL’s (SNV_111b) kernel at booting up to succeed with dhcp lease and to be able proceed with initial install. File /etc/system gets updated via root terminal session before standard reboot to make the patch for kernel permanent

Hi there, I am starting a new thread to try and solve a problem I am having will slow network throughput to the XEN host (not to a domU). I have confirmed my problem occurs with PVOPS ''xen/master'' kernel as well using http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31.6-pvops-dom0-xen-master-x86_64 as the .config. It also occurs with a forward ported xenified kernel

Hi there, I am starting a new thread to try and solve a problem I am having will slow network throughput to the XEN host (not to a domU). I have confirmed my problem occurs with PVOPS ''xen/master'' kernel as well using http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31.6-pvops-dom0-xen-master-x86_64 as the .config. It also occurs with a forward ported xenified kernel

Jup, 64 Bit Kernel build is done now and works, but 32 Bit kernel config is different, as I use 64 Bit in Dom0 and DomU, 32 Bit only in DomU incl. DomU with DVB etc. XEN options are the same, it''s only the selection of drivers... Andrew, any idea? Boris, do you know a safe way to create a 64 Bit config out of a 32 Bit one? Sorry, I am not so used to kernel building... BR, Carsten.

Hi, I just want to know if somebody use 2.6.31.4 xenified kernel (aka OpenSUSE) in production? We have been testing it on new Nehalem Xeon server for few weeks w/o any problem. But as soon we tried it on production machine - after several production domUs started - hard OS failure. We had to switch back to 2.6.18.8 - xen stock kernel. Peter _______________________________________________

Hello all, I compiled the kernel with the xen patch and I seam to have trouble with some kernel modules, like ATI''s proprietary driver. The system seams considerably slower than before, this might be because of the video drivers, or maybe the RAM alocated to dom0 (512Mb instead of it''s usual 1Gb). When I try to run xend, it dies with a SIG 15. I attached the log file. Anyone

Hi Daniel, i''ve tested your kernel with slight modifications to your .config (-> domU only) on 64bit 3.2.1 and 3.3 as guest kernel. Compared to the classic 2.6.18.8 the guests are consuming about 25% more CPU, network IO increased by about 15%, disk IO also. Memory footprint is about 10% less. Maybe there are better caching strategies built into this 2.6.29. I''d like to try

Hi Daniel, i''ve tested your kernel with slight modifications to your .config (-> domU only) on 64bit 3.2.1 and 3.3 as guest kernel. Compared to the classic 2.6.18.8 the guests are consuming about 25% more CPU, network IO increased by about 15%, disk IO also. Memory footprint is about 10% less. Maybe there are better caching strategies built into this 2.6.29. I''d like to try

Just wondering what it will take to get the nvidia binary driver working on a pv_ops kernel. It makes it difficult to debug without the source to the nvidia driver, but I think it should be possible to get it to work without changing the binary driver. If the dom0 kernel had access to all the resources that a bare metal kernel did, then it should work right? I''m using Jeremy''s