similar to: unpack list of wrong size

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

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]

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

Hey everyone, Thanks for the quick help resonses once again, We got some mail saying that RAM disks were not the way to go. So we re-installed, made several partitions to use, and rebuilt xen. However, we''re still having trouble mounting partitions when xeno-linux boots. We give a physical grant of one of our newly made paritions (/dev/hda14 in particular) to the domain. But when

I posted this to the Fedora-test list but I''ll try here. If I need to ditch fedora rpms and move to building directly from src before posting here, please let me know and I''ll do so (apologies in advance if this is the case). I have the following Fedora RPMS installed: kernel-xen0-2.6.10-1.1155_FC4 kernel-xenU-2.6.10-1.1155_FC4 xen-2-20050222 I can

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 all I''ve taken the plunge and decided to set up Xen on my AMD64 machine. I want to use amd64 debian as the domain 0 O/S, then install a full amd64 debian dev kit and a couple of 32-bit linuxes on top. I''ve got an install of debian amd64 running as domain0, which boots up just fine. I boot it with dom0_mem=131072 (the machine has 1Gb of RAM). I then created some disk

Hi, I have set up an ubuntu edgy guest domain on a fiesty host domain. The installation was successful but on running xm create -c baseimage, I get the following error message: Error: (22, ''Invalid argument'') The problem seems very similar to the one here: http://lists.xensource.com/archives/html/xen-users/2007-07/msg00361.html but I''m not able to figure out what the

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.

Hi, I''m setting up my first xen machine, and I''m trying to setup two Virtual Machines, each mapped to a physical adapter on a different network. The virtual machine mapped to xen-br0 and eth0 works fine. However, when I bring up a VM with this configuration file: ----------------- name = "test77" kernel = "/boot/vmlinuz-2.6.11.12-xenU" root =

Hello everybody, i am a newbie in using Xen. The first three tries to install Xen on my Gentoo box aren''t very successfull. But now i know how to get the dom0 Domain running. So my Xentoo (Xen + Gentoo = Xentoo) ist coming up. My system is configures like this: /dev/hda1 = /boot /dev/hda2 = / /dev/hda3 = LVM-Partition /dev/hda4 = SWAP /dev/vg01/SYSP = Gentoo System for dom1

Good evening all, I''ve all but finished installing Xen 2.0.5, XenLinux 2.6.10 and Debian GNU/Linux 3.0r4 into /boot on a colo box currently (and temporarily) running CentOS. I''ve chrooted into the debian install (chroot /boot /bin/bash) and was able to set everything up, install requisite packages, install xen, etc. Now I''m at the last step and I''ve run into

Hi, I have Xen 3.3.1 dom0 on Debian with 2.6.26-2-xen-amd64 kernel and I had to "xm destroy" my domU. Now when I try to start it again it fails like this: # xm list | grep n39 # # xm create -c /xen/conf/n39 Using config file "/xen/conf/n39". ROOT xen1:~> Error: Device 4 (vbd) could not be connected. losetup -r /dev/loop1 /xen/iso/amd64-netbsd-6.iso failed # losetup -a

I''ve seen this happen before, not sure why. I changed ''phy:'' to ''file:'' and it worked. I later rebooted and ''phy:'' worked again. So you might try ''file:'' rather than ''phy:''. -- Ray -----Original Message----- From: xen-users-bounces@lists.xensource.com

Greetings! Trying to to run a xen3 domU on a xen4 dem0 I run into problems. The xen server ''XEN1''(dom0) is openSUSE-11.3 (kernel 2.6.34) and xen-4.0.1. With qemu I created an image ''M08.raw'' from the SUSE-9.3 (kernel 2.6.11) and XEN-3.0 installation CD''s. The XEN modules were included in the installation. In M08.raw/boot I configured grub/menu.lst:

Hello, I have a xen server that needs to run a domU on a different vlan than xen''s. I have configured my switch (a cisco catalyst) to tag every untagged packet to the default vlan (the one in which is dom0) and to accept tagged packets (for that domU). I have xenbr0 linked with the eth0, the default network. Then I run * vconfig add eth0 101 -> To create a virtual interface with

Once last night and the night before a XenU go into a Zombie state, requiring a reboot. I''m not quite sure what is happening, and am looking for advise on how to diagnose the problem. .. While writing this email, it crashed again. This time I had an ''xm console calcutta'' capturing the output. I read a suggestion in these archives suggesting that I can just

I cannot boot domU: # xm create inhouse Using config file "inhouse". Started domain inhouse # xm list Name ID Mem(MiB) CPU VCPUs State Time(s) Domain-0 0 123 0 1 r----- 27.4 inhouse 8 2048 0 1 ------ 11.4 # xm console inhouse Linux version 2.6.12.6-xenU ( root@xen1) (gcc version 4.0.2 20050901 (prerelease)

Hi all, I want to do live migration of domains using DRBD block devices for synchronisation between the two Xen hosts with Xen 2.0.7. I''ve written a script ( block-drbd ) which binds / unbinds DRBD devices for specific domains (with DRBD, only one host can write on a drbd device at the same time). This script sets the current host as master (bind) or secondary (unbind) in a DRBD

Hi, I run an Ubuntu Breezy Dom0 under Xen 3.0.1 (official Xen 2.6.12.6 kernels from xen-3.0.1-install.tgz). In the machine i''ve got 2 IDE ATA discs, hda and hdc. The Dom0 runs on hda1 (a big / partition), hda2 is swap. hdc is totally unused (an empty disc, exactly the same model that hda). 8 to 10 domU run from .img files located in /vserver without problems (unmodified kernel