similar to: Xend stop/start

Moi! I upgraded Xen-2.0.1 to Xen-2.0.5 (testing) and everything compiled cleanly. I''m still able to boot dom0 and start domUs but networking doesn''t work anymore. xen-br0 appears in dom0, but vif-interfaces now only when ifconfig -a is used. Interface appears in domU and all seems to be fine, except no any data doesn''t move in any direction. I can''t even ping

I had an issue late yesterday where some windows domU''s were down. The person who "owns" those domUs let windows updates install and then restart, which they failed to restart. When I tried to manually restart them I was getting can''t allocate memory errors. In the past I''ve had can''t allocate memory errors when trying to bring up a new domU.

I''ve been working on a xen-unstable tree from mid-April. I wanted to upgrade to the latest version, so here is what I did: - Clone a fresh copy of xeno-unstable.bk (1.1507) - "make world" - Change the .config of linux-2.6.11-xen0 to include my ethernet card (CONFIG_FORCEDETH=y) - Add localversion files to linux-2.6.11-xen0 and linux-2.6.11-xenU - rm -rf the existing dist

Hi, I''m trying to install Xen on Ubuntu 11.04. I read somewhere (please correct me if this is wrong) that Ubuntu hasn''t had dom0 support since 8.04 LTS, and the recommended action was to grab a dom0-enabled kernel from Debian, so I did. I''m running 2.6.32-5-xen-amd64 and built Xen 4.1.1 from source. After installation and some troubleshooting, I tried to start

# HG changeset patch # User Jim Fehlig <jfehlig@suse.com> # Date 1360861948 -3600 # Node ID 0f9c7503650fa1b1103b769e1129d66ff614b2ad # Parent cffb489a6df37d8d114e7d2d53a7a85d14e8f968 tools/xend: Only add cpuid and cpuid_check to sexpr once When converting a XendConfig object to sexpr, cpuid and cpuid_check were being emitted twice in the resulting sexpr. The first conversion writes

[Patch 4/4]: Xend interface for HVM S3 - extend "xm resume <domid>" to be able to S3 resume HVM domain. - when user issue "xm resume" command for HVM domain, xend will use xc lib API to call HVMOP_s3_resume hypercall. Note: it may not appropriate use xm resume for HVM s3, since xm resume is originally designed for save/restor purpose. It will be fine that

At OLS we had a couple of "Xen Mini Summit" sessions. Although there weren''t any formal minutes, here''s a rough summary of what we discussed/concluded. Status as of 24 July 2005 ========================= Summary: We have a couple of annoying bugs, but things are coming together nicely. x86_32p (PAE 16GB) and x86_64 ports are close to being feature complete with

Hi Guys, I have Debian 6 + Xen 4.1.1 and created a DomU with virt-manager after creation: laptopvm:~# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1024 1 r----- 729.1 centos-4 512 1 0.0 laptopvm:~# Its config file is

Hi, I have installed xen3.0.4.1 from source and every thing works well. Now I need to upgrade to xen-unstable. It is compiled and installed successfully (at least it seems to be) and I''m able to boot and run dom0. But Xend does not work. "xend start" gives no warning or error but running "xm list" I see: Error: Unable to connect to xend: No such file or

After upgrading to 3.0.2 I tried rebooting a domU (a problem sometimes in 3.0.1 related to bug 514) it failed to come back up. This was in my xend.log. ("Refusing to restart to avoid loops." .... ) [2006-04-11 20:53:39 xend.XendDomainInfo] DEBUG (__init__:988) Storing domain details: {''console/ring-ref'': ''223144'', ''console/port'':

Hi, I have compiled xen-unstable (using hg clone http://xenbits.xensource.com/xen-unstable.hg). I have successfully booted into the dom0 kernel. output of xm list: Name ID Mem VCPUs State Time(s) Domain-0 0 932 1 r----- 591.2 But whenever I xm create, I get: # xm create /etc/xen/domu1 Using config file

Hi, this is a repost of a previous question - since then I have tried rebuilding my Xen0 kernel numerous times and trying different configurations, but I haven''t yet ever got a single DomU to boot so I really don''t even know what is supposed to happen, let alone how to start debugging it... Can someone please speculate on how to debug this further? It''s a gentoo

I end up with the same error after building and running xen-stable 3.2-rc4 on both Ubuntu 7.10 and Fedora Core 6. I am using AMD64 builds. I have carefully followed the instruction on the xenbits.xensource.com on building Xen unstable. After booting with the new Xen and dom0 kernel, I cannot use any Xen tools (such as xm) from Dom0. I have tried restarting Xend but it fails with the same errors.

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''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 all, I just compiled an installed the Xen Hypervisor, Tools and a new Kernel from the 3.1 source. The dom0 is running without problem and the xm seems to work fine, too (tried xm info, xm list, xm dmesg). Unforunately on creation of a domU I always get an error using a config file and a domU image that is definitley working (at least with 3.0.4): Using config file

Hi, I''m new to Xen and I''ve set up a few domUs using Debian (I suspect there may be a problem there, see at end). To begin with everything worked OK, I rebooted domUs without any problems, but twice now when I try when I try to restart or shutdown a domain, the xm command locks up. # xm list Error: Device 0 not connected Usage: xm list [options] [Domain, ...] List information

Hi everyone, I generated my own DomU guest using opensuse''s yast dirinstall and stored it on a seperate iscsi target. I created it as a DomU on my Domain0 (2.6.25.16-0.1-xen kernel) successfully, using the following configuration: name = "vm01-opensuse11-base-LAMP" memory = 256 kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root =

Hi, I tried to issue: xm save VMID FILE, and got the following error: Error: Error: [Failure instance: Traceback: twisted.internet.error.ConnectionRefusedError, Connection was refused by other side: 111: Connection refused. xm create works fine, xend is running on domain 0, I can log in the VM through xm console VMID and ssh without problems. I can also stop and restart the domain.

On Tue, Dec 16, 2014 at 10:29:53PM +0200, Pasi K?rkk?inen wrote: > > > > * xend is now disabled by default. You can enable it by running > > chkconfig. xend has been removed from the tree entirely in Xen 4.5, > > so this should (hopefully) serve as a "wake-up-call" for people to > > begin the transition over to xend. > > > > * A lot have