similar to: xend (12, ''Cannot allocate memory'')

I''m getting the error: xend (12, ''Cannot allocate memory'') From the command line after the Dom-0 goes through a period of heavy memory usage. I don''t have any hard numbers on how to duplicate it, but I''ll give you the steps I''ve gone through to duplicate the problem. First, some information about my setup. It''s a new setup, and has

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

Hi guys I have few problems with live migration ... and I need some professional help :) I have 2 xen servers ... CentOS 5.3 and I want to have a high available cluster Now let`s begin .... xen0: [root@xen0 ~]# fdisk -l Disk /dev/sda: 218.2 GB, 218238025728 bytes 255 heads, 63 sectors/track, 26532 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start

Next question:- eth0            8000.001c2596e32b       no              peth0 pan0            8000.000000000000       no virbr0          8000.000000000000       yes Presence virbr0 in report seems strange. Direct port  Xen 3.4.2  to F11 doesn''t install daemon libvirtd ( bridge virbr0 ) , unless you wrote xen-3.4.2-(x).fc12.src.rpm  yourself. So , from where bridge virbr0 comes 

Hi, I have a Xen server running OpenSuSE 10.2, with Xen version 3.0.3_11774. It''s happily hosting two DomU''s running the same OS / kernel. Now I tried to create a new DomU running a newer OS - OpenSuSE 11.1. It comes with Xen version 3.3.1_18494_03. Unfortunately for me, it doesn''t work - this is what I get: > xen1:/etc/xen/vm # xm create NEW > Using config file

Hello, It looks like xen 4.1.2* has some problems with solaris 11 iso images too (s. further below log messages) hvm-solaris11.born2b3.net.cfg # --- kernel = ''/usr/lib64/xen-default/boot/hvmloader'' builder = ''hvm'' device_model= ''/usr/lib64/xen-4.1/bin/qemu-dm'' name = ''solaris11hvm.born2b3.net'' acpi =

I''m using FC5 with its Xen 3.0.2-2 package and 2.6.16-1.2118_FC5xen0 kernel. I''ve got a Pentium 9xx chip with virtualization enabled in the BIOS; it appears to be VT-enabled, since xm dmesg includes "(XEN) VMXON is done". I base my config file on example.hvm and on previous emails to this list. Unfortunately, I don''t get very far. xm create winxp.conf

Hello. Im trying to get hvm running on my amd64 am2 socket 2gb ram. 1st it as a Debian amd64 etch. 2st xen 3.0.3-2 debian build (more configs below) 3st acpi=1 apic=1 Problem is I can install winXP but after reboot i get black screen. If i press F8 i get menu of XP but can''t select anything ->frozen again If i try acpi=0 apic=0 and install XP it freezes before it XP boots

I''m not able to start, destroy, or delete a DomU: > xen1:~ # xm start test4 > Error: Domain is already running > Usage: xm start <DomainName> > > Start a Xend managed domain >   -p, --paused                   Do not unpause domain after starting it    >   -c, --console_autoconnect      Connect to the console after the domain   

Hi folks I deploy a two Dell PowerEdge T300 to test Virtualization with kvm+drbd+heartbaet. The KVM drbd and heartbeat work properly. However, I have doubt!! When the primary node has down, the secondary node start the VM that has original running on primary node... So, this required a full stop of hole system... This is not we wish here... Is there something way to live migrate VM from

Hi! Please help me. # xm create win7.hvm Using config file "./win7.hvm". Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1 grep -v ^# /etc/xen/win7.hvm | grep -vx '''' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 name = "win7" vif = [

Hi, I install a guest Fedora inside the host Fedora. When I use the service xend status to check the status of xend. It shows xend is running. However when I use xm create xen1 to start the guest domain xen1, it failed. The corresponding file xen1 is in /etc/xen/xen1. The error msg is as follows: [root@phillis xen]# xm create xen1 Using config file "./xen1". Going to boot Fedora

Hi Everyone, I''m trying to get Xen to use a native DRBD device but it seems it will not create the virtual machine. It does not seem to like the DRBD device type, any ideas on what might be wrong? I''m pretty sure my xen config file is OK and the DRBD device looks fine too. Full details below. xm create centostest Using config file "./centostest".

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 several systems running 64bit SLES11SP1. I''m trying to Live Migrate between a couple of them and it''s not working, although the same VM will run on each one starting it manually. The system are not identical. Would one expect migration to work between these two systems? See below. Thanks, James The first system is a ProLiant DL360 G6: Proc 1:2533 MHz Execution

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, since pinning the cpu cores to Dom0 and the DomUs the shutdown of the VMs doesn''t work anymore. When shutting down or rebooting a DomU the DomU just freezes after the shutdown process but won''t reboot or stop the DomU. The shutdown itself seems to be complete though. We can reproduce this problem on 4 different servers.

Hi, I have some trouble to create hvm machines. Xen just tell me that the domain creation failed: # xm create /etc/xen/xenwin2008 Using config file "/etc/xen/xenwin2008". Error: Creating domain failed: name=xenwin2008 The last time i had this error there was some trouble with ne vif line, but the configuration worked perfectly until I had to restart my system (and change the netmask

Hello everyone, I grabbed xen-3.3.1 sources from the Mercurial repository (xen-3.3-testing.hg, changeset 475:1cf755387728, from Oct. 23, 2008) and built Xen from these sources on a 32-core (8 quad core Barcelona CPUs) SunFire machine, running an Ubuntu 8.04 (Hardyy Heron) distribution. Everything seemed to be going OK until I booted an HVM (also Ubuntu 8.04) domain. That domain boots normally but

Hi All, I am new to xen community. I am trying to setup Xen3.4.2 +FC11 Dom0 environs for lennovo T400. I have installed all prerequisite component for running xen and booted it. while I am trying to create DomU I am getting following error. I tried doing googling but none of suggested solution is working for me. Please guide me through my first experience with xen.for more details please see

Package: xen-hypervisor-3.0-unstable-1-amd64 Version: 3.0-unstable+hg11561-1 Severity: important The HVM domU won't start. The following is the config (comments stripped). --------------------begin-------------------- import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' kernel =