similar to: r48 - trunk/debian

Author: ultrotter Date: 2006-02-17 06:56:29 +0000 (Fri, 17 Feb 2006) New Revision: 9 Modified: trunk/debian/changelog trunk/debian/control Log: Change the version and debian revision, as agreed on the ML Start tracking the bugs that need to be closed on upload Modified: trunk/debian/changelog =================================================================== --- trunk/debian/changelog

Dear All, I''m trying to install Xen on Debian Sarge + testing (halfway updated system). Hardware P-IV, 256M Packages: -------- linux-image-2.6.17-2-xen-686 linux-modules-2.6.17-2-xen-686 xen-docs-3.0 xen-hypervisor-3.0-i386 xen-ioemu-3.0 xen-linux-system-2.6.17-2-xen-686 xen-tools xen-utils-3.0 /boot/grub/menu.lst: -------------------- title Debian Xen 3.0 root

I''ve installed Xen Hypervisor 3.0.3 (CentOS 5.7, i386) inside Virtualbox 4.1.16 (Mageia 1, i686) and have noticed that Dom0 is consuming 85% of the memory allocated to the VM (1GB) so I''d like to reduce this as much as possible in order to make more room for one or two VM''s. Is there a minimum amount of vRAM that can/should be allocated to Dom0 (using the dom0_mem boot

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

# grub.conf generated by anaconda I recently tried installing xen on another machine and I''m getting the "CPU0 is toast rebooting in 5 seconds" message. Reading through past postings, I was hopeful setting the dom0_mem=128M would solve the problem. Unfortunately, it didn''t make a difference. I haven''t fooled with anything on this system -- just a fresh FC4

Hi my friends, I am running into a problem with my NIC. [root@xxxx ~]# ifup eth0 Error for wireless request "Set Encode" (8B2A) : SET failed on device eth0 ; No such device. SIOCGIFFLAGS: No such device Failed to bring up eth0. eth0 is not a wireless device. Below are some information about my host: [root@xxxx ~]# lspci |grep -i ether 00:04.0 Ethernet controller: Intel Corporation

Hi! As dom0 I''m running Ubuntu Hardy withe xen 3.3 from backports. Reason to using xen 3.3 is that I could get Intrepid stock kernel to work as domu with xen 3.2. Now the problem I have is that I can''t passthrough PCI-devices to my domu. If I run lspci in the domu nothing is returned. I''ve tried to use the kernel from Hardy (2.6.24-21-xen) and stock kernel from

Author: acid Date: 2006-02-16 10:45:13 +0000 (Thu, 16 Feb 2006) New Revision: 3 Modified: trunk/changelog trunk/control Log: - Change maintainer and add uploaders field - Prepare changelog for new upload Modified: trunk/changelog =================================================================== --- trunk/changelog 2006-02-15 23:05:09 UTC (rev 2) +++ trunk/changelog 2006-02-16 10:45:13

Domain 0 allocation is too small for kernel image That''s the error message I get after installing FC4 and following the instructions on http://www.fedoraproject.org/wiki/FedoraXenQuickstart running kernel - 2.6.13.1. I partitioned Fedora to have 6GB on a 30GB drive. I have tried adjusting dom0_mem=256M on a system that has 1GB of RAM and still no luck Any thoughts?

Hello Xen Users, I am facing a problem getting my installation of XEN boot up on a Red Hat Linux Guest OS. What''s happening is that the grub loader tries to install Xen but after a while it crashes and starts rebooting recursively. I have tried both the entries listed below. I am using the following entries in the grub.conf file: title Xen-bhatia 3.0 / XenLinux-bhatia 2.6.16

Author: acid Date: 2006-02-20 14:35:23 +0000 (Mon, 20 Feb 2006) New Revision: 36 Modified: trunk/debian/changelog trunk/debian/libxen-dev.install Log: Remove COPYING file from libxen-dev Modified: trunk/debian/changelog =================================================================== --- trunk/debian/changelog 2006-02-20 14:25:21 UTC (rev 35) +++ trunk/debian/changelog 2006-02-20

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 #

Author: ultrotter Date: 2006-02-19 18:38:10 +0000 (Sun, 19 Feb 2006) New Revision: 26 Added: trunk/debian/patches/30xenchangeset.dpatch Modified: trunk/debian/patches/00list trunk/debian/patches/10sysconfig.dpatch trunk/debian/rules Log: Add 10sysconfig.dpatch description Add 30xenchangeset.dpatch to make the xen changeset configurable Force the xen changeset to be the correct one

Hi all, Following instructions at http://wiki.centos.org/QaWiki/Xen4 to setup Xen on CentOS 6.4. Unfortunately after installing Xen and modifying the boot line there is a kernel panic during the boot process causing the host to enter a reboot loop. Console log attached. [<ffffffff81575480>] panic+0xc4/0x1e1 [<ffffffff81054836>] find_new_reaper+0x176/0x180

Hello list, I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this mission failed.. Hope you can help me by finding the reason for my problem. I downloaded the xen sources from http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz and compiled them by running "make" and "./install.sh". This seemed to work. After setting up grub like this,

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) #

The Xen boot option ''ser_baud=<baud>'' has been removed from the unstable tree. If you were still using this obsolete option then the effect is that you will get no serial output when you boot Xen, which may lead you to believe that there is a more serious problem. To fix this you must move to the new boot option: ''com1=<baud>,8n1'' -- Keir

I am having an issue with Megacli when adding or removing virtual disks. I will post a link to fpaste that has the issue shown. In brief whenever i add, or remove, a virtual disk via MegaCli the attempt succeeds and the adapter is configured but the OS remounts dm-0 in read only. dm-0 is my root lv. This issue does not happen if i boot into the default, non Xen, CentOS kernel. On stock

Hello All, I finally compiled xen 3.3.0 using make World, installed it but I cannot get it to Boot, I always get kernel panic, kernel not sync kind of errors, I suppose it''s some hard disk or partition issue, my setup is as follows. CentOS 5.2 x86_64 on a HP ML-115 Grub, menu.list Entries CentOS xen''s line title CentOS (2.6.18-92.1.22.el5xen) root

Hi all This is a strange one. On upgraging to SuSE kernel-2.6.11.4-21.7, I have suddenly found that I loose the video on boot up! The video disappears very early in boot, possibly while Xen hypervisor is starting, printing out the physical memory map. If you are patient and wait for the machine to reach run level 5, the X server starts up and you get a picture back. You can then switch back and