similar to: How to view actual physical memory available on xen host

Hey all, just compiled xen 3.4.2 and linux 2.6.31.12. I followed the instructions on the Xen wiki to get the install running. my issue here is that in my grub memnu config i set dom0_mem=512M when i login to the dom0 and i do a free -m i get that the system only has 432 under the total section. booting into the stock debian kernel 2.6.26-2-amd64 kernel gives me 8192 free memory for i did

Hello, I have some dom0 which have 8GB RAM, but when I look with xm list, it just shows me 6GB, I need to setup some new VM, each with 1GB, so I should have with 3VM still 5GB free, but im only seeing 3GB. Can I just create 2 new VM with each 1GB and still have 3GB for the dom0? #xm top xentop - 11:31:17 Xen 3.1.0-53.1.14.el5 4 domains: 1 running, 3 blocked, 0 paused, 0 crashed, 0 dying, 0

You need to add dom0_mem=XXXm to xen or scale back the memory of domain0 with using "xm mem-set <DomId> <Mem>" command. Your domain0 used up almost all physical mem. >total_memory : 1023 >free_memory : 62 Thanks Yunfeng >-----Original Message----- >From: xen-devel-bounces@lists.xensource.com

Hello list, I have two differents installation Xen Hypervisor on two identical physical server, on the same switch : The problem is on my new server (Xen 4.0.1 with pvops kernel 2.6.32.24), I have bad performance on bandwidth I have test with a files copy and "iperf". Result iperf average: Transfert Bandwidth XEN-A -> Windows

Hi All, Debian squeeze, Xen 4.0, 2.6.32-5 I successfully installed opensolaris, but when trying to convert to pygrub it just hangs. root@vhost2:/var/log/xen# xm create /etc/xen/opensolaris.cfg -c Using config file "/etc/xen/opensolaris.cfg". root@vhost2:/etc/xen# xm list Name ID Mem VCPUs State Time(s) Domain-0

Hello Community, I successfully installed and run xen (xm list and xm info can output appropriately). However, while I was installing domU image by using virt-install -p at domU OS. I encountered an error information" Host does not support virtualization type ''xen'' ". I built xen from source. Some of my friends have the same issue, but if they use pre-build xen, the

hi all i am trying to boot from rhel5.1 x86_64 image. with the following configuration kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 3048 name = "rhel51" vcpus=1 cpus = "" vif = [ ''type=ioemu, bridge=xenbr0'' ] disk = [ ''phy:/dev/cciss/c0d0p7,ioemu:hda,w'',

Hi Guys, Now I am using Xen-4.0.0. I need to attach CDROM from ISO files to vitual machines when they are running. The VMs contain RHEL4.6, Windows Server 2003 32bit and Windows Server 2006 64bit. The disk configuration of the VMs is: disk = [ ''tap:vhd:/guest/SS_test/vhd/hmi-100130.vhd,hda,w''] (1) When I attach a CDROM to RHEL4.6 VM with the command: virsh

Hi Guys, Now I am using Xen-4.0.0. I need to attach CDROM from ISO files to vitual machines when they are running. The VMs contain RHEL4.6, Windows Server 2003 32bit and Windows Server 2006 64bit. The disk configuration of the VMs is: disk = [ ''tap:vhd:/guest/SS_test/vhd/hmi-100130.vhd,hda,w''] (1) When I attach a CDROM to RHEL4.6 VM with the command: virsh

This patch modifies the physinfo hcall to export NUMA CPU and Memory topology information. The new physinfo hcall is integrated into libxc and xend (xm info specifically). Included in this patch is a minor tweak to xm-test''s xm info testcase. The new fields in xm info are: nr_nodes : 4 mem_chunks : node0:0x0000000000000000-0x0000000190000000

Hello, Earlier this week I installed a test server with CentOS 5.6 with Virtualization enabled during the installer. Today I installed another server using the same method (they are identical servers). I just did a yum update and I found something curious. Both servers have a different kernel. Server 1 is at 9.1 version and server 2 at 5.1. How can this be? How to I get the latest version on

Hi there, Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2. My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,

Hi there, Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2. My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,

Hello, I am not sure if this is the correct Mailing list for the issue I have. I have a new system with 18GB of Physical memory on the system. I loaded CentOS 6.4. But when I boot into Dom0, I only see (xm info) 2GB of total memory? I set 1GB for Dom0, but I am not sure why the hypervisor does not see all the memory. [root at barbaro images]# xm info host :

Hello! I have new xen-3.3.0 installed and working on latest Ubuntu Hardy, with Linux 2.6.18-xen from xen.org. When I run "xm new" I got this error: root@hyper02:~# xm li Name ID Mem VCPUs State Time(s) Domain-0 0 512 1 r----- 1869.9 vsrv65 4 1024 1

I am trying to install CentOS from an ISO image file but the installer does not see a CD-ROM drive. The VNC viewer works but the CentOS installer indicates "Unable to find any devices of the type needed for this installation type." Then it prompts with "[Select driver] [Use a driver disk] [Back]". I have tried several variations of the "disk" paramater, all

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0