similar to: XEN 3.4.2 /proc/xen/balloon doesn''t exist

Hi there, I am starting a new thread to try and solve a problem I am having will slow network throughput to the XEN host (not to a domU). I have confirmed my problem occurs with PVOPS ''xen/master'' kernel as well using http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31.6-pvops-dom0-xen-master-x86_64 as the .config. It also occurs with a forward ported xenified kernel

Hi there, I am starting a new thread to try and solve a problem I am having will slow network throughput to the XEN host (not to a domU). I have confirmed my problem occurs with PVOPS ''xen/master'' kernel as well using http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.31.6-pvops-dom0-xen-master-x86_64 as the .config. It also occurs with a forward ported xenified kernel

A pv guest will not reboot after migration, the guest itself does everything right, including the shutdown, but xl does not recreate the guest, it just shuts it down. This goes for 2.6.39 and 3.0.4 guest kernels, havent tried different ones. I also haven tried different xen versions. Dont know if this would affect hvm, probably not since qemu leaves the guest running and does a

Hi everyone, I am trying to do a Cold Migration with Xen, Ubuntu 12.04 and virtual machines with Ubuntu 10.04. This is my cfg file to create the VM on the primary node: # cat ubuntu.c cat: ubuntu.c: Arquivo ou diretório não encontrado root@cloud9:/etc/xen# cat ubuntu.cfg name = "ubuntu" memory = 256 disk = [''phy:/dev/vg_datastore/lv_datastore,xvda,w''] vif = [''

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,

On a fresh reboot free: total used free shared buffers cached Mem: 3371340 448156 2923184 0 5328 77840 ---------- top: Mem: 3371340k total, 449044k used, 2922296k free, 5344k buffers ---------- xentop - 01:44:00 Xen 3.4.3-rc4-pre 1 domains: 1 running, 0 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown Mem: 4160828k total, 4022996k used, 137832k free CPUs: 4

Hi. How I can see what happend in my domU??? dom0 Debian Lenny domU FreeBSD6.4 xen 3.2-1 -------- Xen 3.2-1 :/etc/xen# xm create tttt.cfg Using config file "./tttt.cfg". Started domain freebsd -------- /etc/xen# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2969 4 r----- 48.0 freebsd

I''m testing how xen and grub2 can work together. I''m using xen 3.4.2 and grub2 1.97+20091115-1 from debian sid. After many failed attempts I''ve discovered that on my system the first argument that grub2 should pass to the linux kernel is lost. This is my working grub2 configuration: menuentry "Xen 3.4.0 / Debian GNU/Linux, Linux 2.6.31-1-xen-amd64" {

I''m testing how xen and grub2 can work together. I''m using xen 3.4.2 and grub2 1.97+20091115-1 from debian sid. After many failed attempts I''ve discovered that on my system the first argument that grub2 should pass to the linux kernel is lost. This is my working grub2 configuration: menuentry "Xen 3.4.0 / Debian GNU/Linux, Linux 2.6.31-1-xen-amd64" {

I''ve recently installed Debian Lenny witch Xen (xen-utils, xen.tools and xen-linux-system-2.6.26-2-xen-amd64). I want to virtualize some windows servers, but I''m unable to connect to localhost VNC when I start the vm (xm create) to proceed with windows instalation. The VM config is: import os, re arch = os.uname()[4] if re.search(''64'', arch):

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

[root@localhost onkar]# which xend /usr/sbin/xend [root@localhost onkar]# uname -a Linux localhost.localdomain 2.6.31.12 #1 SMP Wed Mar 31 09:51:44 IST 2010 i686 i686 i386 GNU/Linux [root@localhost onkar]# xend start ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend",

[root@localhost onkar]# which xend /usr/sbin/xend [root@localhost onkar]# uname -a Linux localhost.localdomain 2.6.31.12 #1 SMP Wed Mar 31 09:51:44 IST 2010 i686 i686 i386 GNU/Linux [root@localhost onkar]# xend start ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend",

Hello All, I have been having a very difficult time getting any template to work on xen. Here is what I am running root@personal:/etc/xen-tools# xm info host : personal release : 2.6.22-14-xen version : #1 SMP Tue Feb 12 09:27:26 UTC 2008 machine : i686 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1

Hey folks, I created a DomU, installed Linux, and then realized I''d only given it 1 NIC so brought it down to edit the cfg file to give it another NIC. Originally I just had : vif = [''''] And so I guess the defaults worked for the 1 NIC. So I changed it to : vif =

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: normal Tags: upstream When creating Xen DomU's, at some point xend invokes the oom-killer and the entire machine restarts: Sep 5 12:04:59 arbiter kernel: [259697.101212] __ratelimit: 136 callbacks suppressed Sep 5 12:04:59 arbiter kernel: [259697.101218] xend invoked oom-killer: gfp_mask=0x200da, order=0, oom_adj=0 Sep 5

I am using a Asus M2A-VM mainboard with Athlon X2 2300 cpu. The mainboard features a AMD 690G chipset. I thought this hardware is amd-v compatible. While using xen with hvm I get the message: root@pluto:/etc/xen# xm create /etc/xen/win.cfg -c Using config file "/etc/xen/win.cfg". Error: HVM guest support is unavailable: is VT/AMD-V supported by your CPU and enabled in your BIOS?

Hi, I''ve run into the following error when trying to create a domU: root@jupiter:/etc/xen# xm create node0-mgmt -c Using config file "node0-mgmt". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. root@jupiter:/etc/xen# Excerpt from xend.log: [2006-09-25 14:55:48 xend 2015] DEBUG (DevController:110) DevController: writing

Hi all!. First of all sorry about my English it''s not very fluid. I have a small server based upon Supermicro X7DBN (Chipset Intel® 5000P) motherboard and Intel Xeon E5320 (1,83Ghz) with 4Gb of FB-DIMM RAM. The OS is Debian Lenny in dom0 (2.6.26-2-xen-amd64) and Debian Lenny in domU (2.6.26-2-xen-amd64). Xen is 3.4.2 compiled from sources. The problem comes when I need to passthrough