similar to: Problem with Xen 3.0 Install script beta

# 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

I am trying to a install Centos 5.1 32-bit Xen HVM DomU onto a Centos 5.1 64bit DomU with the default xen installed and the kickstart hangs at random points during the install process. Sometimes retrieving the image, sometimes formatting the filesystem, sometimes installing the packages,etc. I tried upgrading to xen 3.2 and encounter the same problem before rebuilding back to stock Centos 5.1

I had this happen to me on FC4 using 3.0.2-2 Xen. I updated the various external dependencies and rebuilt xen and tools and was able to sucessfully install FC4 in a hvm. I will give winxp a go later in the afternoon. C ________________________________ From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Rene Purcell Sent: Friday, April

Hi all, I tried to follow the instruction on README. After ''make'' and ''make install'', I did update-grub and got this error message: dpkg: version ''/boot/xen.gz'' has bad syntax: invalid character in version number I searched online but couldn''t find a satisfactory answer to this issue. Does anyone know how to resolve my

Hey folks; I have been happily using shorewall for quite some time so this problem _may_ not be easy to resolve but I am interested in any information regarding your experience with the same setup. I was using FC3 with shorewall 2.2.3 and two NICs setup as a bridge without any issue until I upgraded to FC4. My production system would pass traffic through the bridge but local usage would not

Preamble: dom0: Xen 3.0.4 running on Ubuntu 6.06 x86_64. domU: Xen 3.0.4 or 3.1.0 kernel booting from host pygrub. File backed. ------------- I am having this strange problem getting pygrub to load consistently. When I start a domU, I sometimes get this. Error: Boot loader didn''t return any data! ... and nothing else. When I look in the xend-debug.log log, I see this.

I am running Xen 3.0 (64bit) on CentOS 5.3, and I want to install Ubuntu 10.04 using the steps below: 1. Create a new disk with LVM 2. Downlaod vmlinuz & initrd.gz from http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/ 3. /usr/sbin/xm create -c /etc/xen/ubuntu.cfg install=true 4. Format the whole disk as EXT3, mount as / 5. The installer show some

Hi Has anyone installed Xen 3.0 on Vmware (Fc4) ? It will works well? Thanks for your advice. tournesol _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I attempted to install Ubuntu 10.04 as a domU on my CentOS dom0. The process I used was: wget http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/xm-debian.cfg Edited the config file to use the proper logical volume for its install, and stepped through the install, installed GRUB to the MBR, and all seemed well. However, upon xm create -c NAME

Hi everyone, I''m getting the following boot error, when installing xen-unstable on a dual opteron 246 machine, with a Tyan 2881 Motherboard, 4GB RAM, SATA Drive and ReiserFS filesystem. The machine is a Fedora Core 4. I installed the i386 FC4 on the dual opteron, I didn''t want the 64bit yet. All my binaries are 32bit and I''m compiling it all with 32bit too. After

I''m struggling to get Xen to boot on a FC4 Opteron box. I''ve included the tail of the boot log below [1]. I suspect that the problems relates to the software RAID 1 root and boot partitions, and how it relates to the initrd image. The RAID volumes fail to mount. I compiled the Xen snapshot from the 23rd September, and the only change I''ve made is to enable the

From: pbonzini@redhat.com # HG changeset patch # User Paolo Bonzini <pbonzini@redhat.com> # Date 1319096986 -7200 # Node ID bd1f7361d3d7f4c767af21317fb4ec7ea1372f42 # Parent 1b110e895e285f43f14532e14c77597e54a0bcd2 pygrub will still try the next partition if run_grub exits with a "real" error, thus hiding the root cause from the trace. Defining a separate exception for "no

Following the Fedora Project Xen Wiki in http://www.fedoraproject.org/wiki/FedoraXenQuickstart#head-41a18dc02f3951a8e18a5283d6fcc1879f31c272, I keep increasing the memory number in /boot/grub/grub.conf because each time I reboot into Xen, I get a "not enough memory allocated" error message. I currently have the Xen kernel dom0_mem set to 500000000000 and still am getting memory

Dear, We released New Xenoppix (based on Xen3.0, CD size). Detail HP http://unit.aist.go.jp/itri/knoppix/xen/index-en.html 670MB knoppix_v4.0.2CD_20050923_xen3.0-20060104+IPAFont_cdsize.iso --------------------------------- # New Features * Xen is updated to version 3.0. * Host-Xenoppix(Knoppix on Domain0) boots Guest-Xenoppix(Knoppix on DomainU) with same kernel and same Root

This grub.cfg from a default fedora 19 Beta install caused pygrub failures.The previous pygrub commit fixed taht. So this example file added for reference. Signed-off-by: Marcel Mol <marcel@mesa.nl> --- tools/pygrub/examples/fedora-19.grub2 | 117 +++++++++++++++++++++++++++++++++ 1 files changed, 117 insertions(+), 0 deletions(-) create mode 100644 tools/pygrub/examples/fedora-19.grub2

Hello, I''ve tried to make Xen and LVM snapshots work with RHEL3 (upgraded to FC4 partly, using FC4 kernel 2.6.12-1.1387_FC4, xen-2-20050522 installed from RPM). I had a problem where non-snapshot LVM images worked, but as soon as I create a snapshot of one and tried to use that, I would get a crash like this as soon as I booted up a Xen domain: Freeing unused kernel memory: 160k freed

I have installed dom0 Wheezy 64 bit on Dell PowerEdge T310 with kernel from package and xen-unstable. System is in Uefi mode and booted with grub-efi-amd64. Booting without xen efibootmgr works, while with xen not, efivars kernel module is loaded but show this message: efibootmgr Fatal: Couldn''t open either sysfs or procfs directories for accessing EFI variables. Try ''modprobe

Package: xen-3.0 Version: 3.0.2+hg9697-1 Severity: important Hello, There was a problem while autobuilding your package: > Automatic build of xen-3.0_3.0.2+hg9697-1 on avidan by sbuild/i386 0.49 > Build started at 20060725-0410 > ****************************************************************************** ... > CFLAGS="-O2 -fomit-frame-pointer -DNDEBUG -m32 -march=i686 -Wall

I've Found a page with interesing discussion about images backup http://forums.fedoraforum.org/archive/index.php/t-28255.html This give a "dirty" solucion for remove special thing of ext3 (Selinux remove resize_inode and ext_attr features) witch cause the error in ghost. I hope somebody help with the problem of norton ghost and clone centos 4. :) ----------- sfabkk 2005-07-11,

Hello, I have a very strange access problem, and do not know how to get rid of it. We have a server with a Raid 1 installed running under SuSE 9.2 (Samba 3.0.9-2.3). There are some shares where several users need access to. The permissions of the directories are rwxrwxr-x user1 users when files on that shares are accessed by a Windows Client a strange behaviour occurs. Accessing files