similar to: Lenny how to compile new kernel

Hi, I want to give direct access to my monitor for my linux domU so that my graphics can run smoothly inside domU which is Ubuntu 8.10 I tried doing the following, but things didn''t work out. 1. I boot my Xen on Debian ( lenny ) using kernel /boot/xen-3.2-1-i386.gz module /boot/vmlinuz-2.6.26-1-xen-686 root=/dev/sdc4 ro console=tty0 pciback.permissive pciback.hide=(00:02.0)

Hello, I can''t solve my problem. I want a 32 bits Lenny domU into a 64 bits Lenny dom0. I plan to use pygrub for that (xen 3.2.1). So, I tried to debootstrap a 32 bits domU into a 64 bits dom0. debootstrap --arch=i386 --include=libc6-xen,firmware-bnx2,linux-image-2.6.26-1-xen-686,linux-modules-xen-686,linux-image-xen-686,grub --components=main,contrib,non-free lenny /mnt/xen

Hello, I guess it possible distro specific issue but is it resolvable? I have one node(testing purpose) ganeti 2.0.1 cluster installed over Debian5 Lenny. Almost everything from distro repositories. Only ganeti 2.0.1 and ganeti-debootstrap are from sources. I have it successful run with vmlinuz-2.6.26-2-xen-686 and initrd.img-2.6.26-2-xen-686 from repositories. Both Dom0 and DomU are use the

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-2 Severity: normal Hi, Take the following config file (standard lenny kernel and initrd, with some customization for iSCSI root): name = "lenny3" kernel = "vmlinuz-2.6.26-2-686-bigmem" ramdisk = "initrd.img-2.6.26-2-686-bigmem" memory = 100 vcpus = 1 vif = [ 'mac=00:16:3e:00:00:17, bridge=br695,

Hi, Recently I have installed Debian Lenny on two different machines (different ram size, disks, Xeon dual and quad core, filesystems both xfs and ext3, etc). Packages versions: Dom0: ii libc6-xen 2.7-18lenny4 GNU C Library: Shared libraries [Xen version] ii libxenstore3.0 3.2.1-2 Xenstore communications

Hi, Before diving into this, I would very pleased to know if someone could yes or no, successfully compile mISDN 1.1.8 on Lenny (latest RC1 or beta2 version) ? Regards After a fresh install on Lenny, I can reproduce at will : apt-get install build-essential linux-headers-2.6.26-1-686 cd /usr/src wget http://www.misdn.org/downloads/mISDN.tar.gz tar xvf mISDN.tar.gz cd mISDN-1_1_8 make ....

I've just done a fresh lenny amd64 install, and taken the xm-debian.cfg example: http://people.debian.org/~joeyh/d-i/images/daily/netboot/xen/xm-debian.cfg and built a 32 bit lenny inside a 64 bit lenny dom0 # xm create -c xm-th2.cfg install=true install-installer=http://people.debian.org/~joeyh/d-i/images/daily/ When I try to boot the domU: # xm create -c xm-debian.cfg it

I am running debian lenny, with the standard Xen 3.2 packages, with the 2.6.18-6-xen-686 kernel as dom0, and 2.6.24-1-xen-686 as domU. Everything is working fine apart from the console and the PCI passthrough. I am getting these errors in the domU on startup: XENBUS: Device with no driver: device/pci/0 XENBUS: Device with no driver: device/console/0 Does this mean the modules are missing?

Good morning, Always the same problem, I did some research but no good news at all Here is my config : title Xen 3.2-1-i386 / Debian GNU/Linux, kernel 2.6.26-1-xen-686 root (hd0,3) kernel /boot/xen-3.2-1-i386.gz module /boot/vmlinuz-2.6.26-1-xen-686 root=/dev/sda4 ro console=tty0 module /boot/initrd.img-2.6.26-1-xen-686 On a fresh Lenny install,

Hello, The email (thread) below from xen-devel mailinglist indicates the changesets that should fix the bug that causes the lenny 2.6.26 xen kernel to crash on newer xen hypervisors. The workaround for this bug has been to use pci=nomsi on the dom0 kernel cmdline, but it would be better to apply the actual fix to the xen kernel in lenny. More information on xen-devel (archives). -- Pasi

Hi, AFAIK, the status of Xen in lenny is currently the following: - no dom0 kernel - domU kernel only for i386 (no domU kernel for amd64) I was told (I don't remember where) that this is because the vanilla kernel only supports domU for i386, and has no dom0 support, so distros have to port the patches to their kernels (please correct me if I'm wrong). However: - etch shipped with dom0

Hi. I have some issues after rebooting the system. First, I would like to show you how I have installed XEN. S.O: Debian Lenny Installation: By default without additional packets So, I installed XEN # aptitude install xen-hypervisor-i386 libc6-xen xen-utils xen-tools bridge-utils # aptitude install xen-linux-system-2.6.26-2-xen-686 # nano /etc/modules loop max_loop=128 # nano

hello all, it''s my first time ever with xen (or even virtualization in general). I installed Xen 3.2 on top of a Debian Lenny kernel 2.6.26-2-686 via apt-get. Boot options are: title Xen 3.2-1-i386 / Debian GNU/Linux, kernel 2.6.26-2-xen-686 root (hd0,0) kernel /xen-3.2-1-i386.gz dom0_mem=512000 module /vmlinuz-2.6.26-2-xen-686 root=/dev/mapper/athena-root ro console=tty0 module

Hi all, i have a CentoOS based Xen Dom0 running gitco xen3.3.1. I''m experiencing problems with debian Lenny FV domU. After some days of perfect working the VM start to consume all cpu and than i can only connect via ssh to VM and nothing work, neither the "top" command! Any idea? Thanks a lot and regards, Francesco

Hi, I''ve been building up a new HA system, running Xen on DRBD devices. Configuration this applies to: Debian Lenny xen-linux-system-2.6.26-2-xen-686 package |**|drbd8-modules-2.6.26-2-686 drbd8-modules-2.6.26-2-xen-686 As I''ve been building the system, I ran into an interesting problem, with two symptoms: 1. running VMs would come back up after a reboot, but would hang on

Hi, While issuing make, I've got: ... CC [M] /usr/src/zaptel-1.4.11~dfsg/kernel/zaptel-base.o /usr/src/zaptel-1.4.11~dfsg/kernel/zaptel-base.c: In function ?zt_register?: /usr/src/zaptel-1.4.11~dfsg/kernel/zaptel-base.c:5230: error: implicit declaration of function ?class_device_create? My system is Lenny and before getting this error, I successfully did : apt-get source libpri zaptel

Hi all!. First of all sorry about my English it''s not very fluid. I have a small server based upon Supermicro X7DBN (Chipset Intel® 5000P) motherboard and Intel Xeon E5320 (1,83Ghz) with 4Gb of FB-DIMM RAM. The OS is Debian Lenny in dom0 (2.6.26-2-xen-amd64) and Debian Lenny in domU (2.6.26-2-xen-amd64). Xen is 3.4.2 compiled from sources. The problem comes when I need to passthrough

Hi all: I am pretty new to xen, but ,thanks to you, I am learning fast :) I have a Dell Poweredge 2950 server running Debian Lenny as Dom0 named Asgard I have configured three DomU (Loki, Hermod and Thor) with DHCP support. All the machines (Dom0 and DomU''s) ask for an IP address to a DHCP server in the Office LAN. The DHCP server is configured to bind certain IP addresses to the Dom0

Hello, I installed Xen 3.2.1 on Debian Lenny from packages. Then created image files with 'xen-create-image --size=2Gb --swap=128Mb --dhcp --dir=/xen --hostname=test'. Now I'm trying to run Debian in PV mode using the following configuration file: kernel = "/boot/vmlinuz-2.6.26-1-xen-686" ramdisk = "/boot/initrd.img-2.6.26-1-xen-686" memory = 128 name =

Trying to set up PCI pass through with xen 3.2.1 on Debian Lenny, with xen Kernel 2.6.26... having no luck. I have the following configured... i) Virtualization and vt-d are both enabled in the bios, I have power cycled after making these changes. ii) I have these option in grub menu; iommu=1 pciback.permissive pciback.hide=(07:01.0)(01:00.0) vtd=1 iii) I have this in my cfg file