similar to: Getting "Unrecognized Image Format" errors.

I''ve been brainstorming... I want to create a 2-node HA active/active cluster (In other words I want to run a handful of DomUs on one node and a handful on another). In the event of a failure I want all DomUs to fail over to the other node and start working immediately. I want absolutely no single-points-of-failure. I want to do it with free software and no special hardware. I want

I have Xen3 installed on Ubuntu 6.10 server, $ sudo xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 250 8 r----- 748.2 but whenever i try to create a new domain with anything listed for kernel at all, i get this: $ sudo xm create domu1 Using config file "domu1". Xend has probably crashed!

I am running Xen 3.0.1 with Gentoo for Dom0 and when I create a DomU with Debian, the kernel or system does not seem to recognize the volume I have created for swap on the DomU and will not mount it during boot or after. here is the disk section of the xen config for the DomU: disk = [ ''phy:xen-disks/disk-root,hda1,w'',''phy:xen-disks/disk-swap,hda2,w'' ]

I have been playing with Xen 3.0.1 for some days now, using debian sarge for dom0 and domU''s, and it works like a charm. But, I have a problem with rebooting domU''s. Here is the output from /var/log/xend.log [2006-03-30 13:44:58 xend.XendDomainInfo] INFO (XendDomainInfo:823) Domain has shutdown: name=vmintraweb1 id=5 reason=reboot . [2006-03-30 13:44:58 xend.XendDomainInfo]

Package: xen-hypervisor-3.0-i386 Version: 3.0.2+hg9681-1 Severity: important Have been trying to get NetBSD to run under debian unstable with the debian supplied hypervisor. Using the 3.0.2-2 hypervisor supplied by XenSource, it works just fine. Because the install process overrides other things, reverified with debian hypervisor afterwards and symptom continues. Attaching the netbsd.cfg and the

----- Forwarded message from pakrat <pakrat@private.neotoma.org> ----- Forwarding to list without attachments. From: pakrat <pakrat@private.neotoma.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD X-Neotoma-Consulting-MailScanner: Found to be clean X-Neotoma-Consulting-MailScanner-From:

Hi I''m using Xen on my AMD64 / Ubuntu 7.10 server which I recently upgraded, and my 2 VMs are decidedly flaky. They seem to be blocked for most of the time, and networking doesn''t work properly. How can I debug this and get them online reliably? Any tips gratefully received! * I can log in via console or ssh, can ping the server''s NICs but can''t ping the

Hi, I got this error when starting a domU on Centos 5.1 i386, Device 0 (vif) could not be connected. Hotplug scripts not working. Why is this happening ? I should restart the machine to see if this still happends after a fresh network bridge. But it's somehow a production server, I would like not to restart it, if possible. No domU is currently running. I could start domUs a week ago.

Hi all, my domU guests stop booting in my new 3.2 (kernel 2.6.18.8) xen installation when run perfectly in my other 3.0.2 (2.6.16) xen server. whe i start the domU with "xm create" i get these messages: Using config file "./debian.4-0.xen3.cfg". Started domain debian.4-0 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Severity: normal If quagga is running, and I start & stop a domain, the VIF interface doesn't go down properly (in addition to other problems). Here's what I do: 1. Boot the computer. By default, quagga is running (zebra + ospfd). 2. xm create test7.cfg, wait until the domU starts. 3. xm shutdown test7, wait until the domU

Hi all, I am running Xen 3.0.2-2 (taken from XenSource) with Linux kernel 2.6.16 (taken from Debian Sid), I compiled Xen and 2 kernels (dom0 and domU). Here is the ascii-art of my setup: ------------ ------------- | LAN |------------------------| waste | 192.168.0.94/24 ------------ ------------- | ·····························

Hi, I have 2 partition o my HD: /dev/hda1 e /dev/hda2 . In /dev/hda2 there is Suse_10.1, /dev/hda1 is empty, and in the MBR there is Grub. Normally, FreeBSD can be installed from a CD or a floppy, but I haven't neither a cd device nor a floppy device. So, I want run the installation of FreeBSD_6.2 from a floppy image. In this thread there is an idea, but I didn't understand it.

Hello, I have a RedHat Linux 7.2 system with a /boot partition on /dev/hda1. The grub config mounts the boot partition on /boot and root on /dev/hda2. However, when I try to boot from a syslinux floppy and mount the root filesystem on /dev/hda2, the system seems to load the kernel and mount the the root filesystem, but then stops. There is no error message, but init does not proceed load.

On Wed, Dec 9, 2015 at 1:07 PM, Emilio Lazo Zaia via Syslinux <syslinux at zytor.com> wrote: > I thought I've found three bugs on syslinux 6.03: Just to be clear, is this only affecting vesamenu.c32? > (1) With sample config file as is, i.e. leaving commented MENU VSHIFT and > MENU COLOR UNSEL but uncommented MENU COLOR SEL: > > A black "border" is displayed

Hi all, I just compiled an installed the Xen Hypervisor, Tools and a new Kernel from the 3.1 source. The dom0 is running without problem and the xm seems to work fine, too (tried xm info, xm list, xm dmesg). Unforunately on creation of a domU I always get an error using a config file and a domU image that is definitley working (at least with 3.0.4): Using config file

Hello fellow xenophiles and happy new year! I''ve documented the install procedure for a prototype server here since I found no similar document Anywhere on the net. It''s a Sarge-based Domain0 on linux root raid from scratch, using LVM to store the data for the domU mail server and its mailstore. I humbly submit my notes in the hope that they are useful to some weary traveller.

greetings. i have been three days now trying to add ext3 to an existing suse-7.3 machine. i am using suse's own 2.4.13 kernel source. here is what i have done: following install, i ran tune2fs -j /dev/hda2 (also hda3 and hda4). .journal files were created on each partition, apparently uneventfully. wishing to avoid ai irreversable situation, i initially edited /etc/fstab thusly:

Background: This is a dual boot (Windows XP and CentOS 5.2 (32 bit) box. There were four (4) NTFS partitions. The C partition got full. I deleted the 4 NTFS partitions and did a clean install of Windows XP, into one (1) NTFS partition. I knew that I would need to install GRUB again and I did that, using the CentOS 5 Installation DVD. When I tried to boot into Linux, no joy. this is the GRUB error

Hi List, please excuse that this post is again about networking with XEN. Even though I googled and checked other posts for some days now I did not manage to get my installation working. Following some advises I used the late binding of pci. So I created a /etc/modprobe.de/local and added: options pciback hide=(03:00.0)(04:00.0) install e1000 /sbin/modprobe pciback ; /sbin/modprobe

I am running a fairly new box, Athlon 1.4Ghz, 512 Mb RAM, RedHat 7.3, rsync rsync version 2.5.4 protocol version 26, it's disk layout is; bash-2.05a# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda6 372M 338M 15M 96% / /dev/sda1 45M 8.9M 34M 21% /boot /dev/sda5 703M 218M 449M 33% /home none 251M 0