similar to: maxmem configurartion

The changeset ''12803:df5fa63490f4da7b65c56087a68783dbcb7944f8'' added a new hypercall XENMEM_set_memory_map for specifying the e820 mapping. There was a small bug in the userspace side of this change though - the e820 mapping was specified based on the ''memory_static_min'' domain info parameter which means the memory map size is clamped to the value

Hi,    I''ve been using xVM with no problems since 2009.06 release (centos4/5, rhel4/5, sol10 as guests). This was using the 111a version. Just installed a new server with the 111b version and .... virt-install --nographics -p -r 8192 -n CentOS_48_64_92 -f /dev/zvol/dsk/zm0/vm/CentOS_48_64_92 -l ftp://192.168.101.120/pub/CentOS-48 -w bridge=aggr0 --os-type=linux --os-variant=rhel4

Using 3.1.2 c/s 15492 on Unisys ES7000 configured with 32 processors and 128 gb memory, I attempted to start a 160 gb domU. The xm create command hangs, as well as any other xm commands that are issued. If I do ctl-c of the hanging xm create command, I am able to terminate it and then xm commands are once again functional. I expected to get an error that there was not enough memory available

Hi guys, actually i use the following packages from etch-backports: =========================== ii linux-headers-2.6.18-6-xen-vserver 2.6.18.dfsg.1-18etch1 Common header files for Linux 2.6.18 ii linux-headers-2.6.18-6-xen-vserver-amd64 2.6.18.dfsg.1-18etch1 Header files for Linux 2.6.18 on AMD64 ii linux-image-2.6.18-6-xen-vserver-amd64

Hi guys, I cannot get my domU''s to boot. My current setup is as follows: Xen: 4.0.1 Dom0: Debian with custom linux 2.6.32.27 Xen kernel DomU: Same kernel as Dom0 When I try to start the VM, I just get: Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'') And /var/log/xend.log says: [2011-01-23 15:36:01 3201] DEBUG

Hi guys, I cannot get my domU''s to boot. My current setup is as follows: Xen: 4.0.1 Dom0: Debian with custom linux 2.6.32.27 Xen kernel DomU: Same kernel as Dom0 When I try to start the VM, I just get: Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'') And /var/log/xend.log says: [2011-01-23 15:36:01 3201] DEBUG

Hello List, i am trying to get xen 3.3.1+ linux kernel 2.6.18 +drbd 8.3.0 working. Here is my config: ---------------------------------------------- kernel = ''/boot/vmlinuz-2.6.18.8-xenU'' memory = ''128'' root = ''/dev/sda2 ro'' disk = [ ''drbd:pgone-disk,sda2,w'' ] name

When I try to use stubdom-dm in lieu of qemu-dm, the guest domain crashes almost immediately if I specify an emulated NIC (''vif='') in the guest configuration file. If I don''t specify a vif, it works fine. If I use the same configuration with qemu-dm instead of sutbdom-dm, it works fine. Is there some reason QEMU emulated networking doesn''t work with stub domains

Hi, I am able to get Xend running on Fedora 8 but when I try to create any VM it fails. The xm create osc.cfg throws following error - [root@asds174 vm_images]# xm create osc.cfg Modified arg=osc.cfg stop3 Using config file "./osc.cfg". group_id=None [''create'', ''osc.cfg''] Stop 1 None [''vm'', [''name'',

Hullo Everybody ; I am failing to start my new VM and it tells me unkown bootloader . Below are my parameters and output . Could somebody be having an idea of putting right this problem? [root@virtualintranet /]# xe vm-param-list uuid=70645ba3-bcbc-683b-099e-ed197301fcc2 uuid ( RO) : 70645ba3-bcbc-683b-099e-ed197301fcc2 name-label ( RW): PVG1

I was trying to install a guest OS with the following command. $ virt-install -r 1024 --accelerate -n ubuntu-first-test -f /var/lib/libvirt/images/guest.img --cdrom /root/ubuntu-12.04-desktop-i386.iso --hvm and it says the following. Starting install... ERROR POST operation failed: xend_post: error from xen daemon: <Fault 3: ''ubuntu-first-test''> Domain installation

Hello, on my xen host, Debian 5.0 I have few domU''s running, most of them are Lenny''s, a couple is running at Etch (Debian 4.0). All domU''s are running stable except of one (Etch / Debian 4.0). This one crashes almost daily and I wasn''t able figure out the reason why. Inside the domU there is nothing installed except of base system and Zimbra ZCS 5.0 and its

Package: xen-3 Severity: important After testing with waldi, he found out that the kernel arch cant be different as the xen-utils. So when using xen-amd64 with xen-utils-i386 the dom'Us wont work. xm create /etc/xen/test2.cfg gets: VmError: (22, 'Invalid argument') Debug: [2008-10-23 18:01:48 4211] DEBUG (XendDomainInfo:84) XendDomainInfo.create(['vm', ['name',

Hi Guys, my domUs won''t start and i do not know why. i use the acutal version of xen (3.2) from mercurial on a debian etch 64 system. Thanks for any help here the config of a domU: ================================== name = "vadmin89" kernel = "/boot/vmlinuz-2.6-xen" root = "/dev/hda1" memory = 75 disk = [

Howdy, I''ve read on http://revu.tauware.de/revu1-incoming/xen-0604251805/xen-3.0.2/docs/misc/xen_config.html about the maxmem option? What it do? I don''t see any result... I ''ve thought that the memory will automatically scaled to maxmem... but xm top show only 128 mb reserver for the guest machine also during high loads. greetings Fabian

Hello all, I''ve just installed a new dom0 with openSUSE 11.3 (x86_64) and I''m seeing domUs crashes when reading from disks. The problem occours when in domU configuration I use memory=1024 maxmem=2048 My setup is DRBD on LVM on Software RAID 10 and drbd devices are used as disks for domUs, using phy:/dev/drbd0,hda,w phy:/dev/drbd1,hdb,w The domU in test is HVM, I''m

I am trying to allow domains'' memory allocation to be altered by using both the "memory" and "maxmem" options in my config files (i.e. set maxmem to some large value to allow the domain to be resized up to that amount, and memory to set the initial allocation). However I appear to lose potentially quite a large chunk of memory as I use a larger "maxmem"

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: important I'm running a 32-bit Ubuntu 10.04 domU on a 32-bit Debian squeeze dom0. xm create works fine, but whenever I try to reboot this domU it fails with the following traceback in xend.log: [2010-10-23 17:48:58 1679] INFO (XendDomainInfo:2088) Domain has shutdown: name= onini id=2 reason=reboot. [2010-10-23 17:48:58 1679] DEBUG

> > Anyway I don''t know if this is a known (or unknown?) bug (I couldn''t > > find any information about it) or if there''s something wrong with my > > system, so I''m just asking here if anybody ever had similar problems.. > > I think that this is the known (and expected) behaviour and I had > similar issues when I set memory <

Hi, i''m prepering to upgrade my servers from xen 3.0.3 32-bit to 3.2.1 64-bit. The old system: Debian 4.0 i386 with included hypervisor 3.0.3 (pae) and dom0 kernel. The new systen: Debian lenny amd64 with the included hypervisor 3.2.1 and dom0 kernel from Debian 4.0 amd64. My domUs have a self compiled kernel out of the dom0 kernel of the old system (mainly the dom0 kernel but