similar to: Problem: xend.log says "VM restarting too fast. Refusing to restart to avoid loops"

Displaying 20 results from an estimated 3000 matches similar to: "Problem: xend.log says "VM restarting too fast. Refusing to restart to avoid loops""

2008 Mar 20
1
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
2008 Jul 25
1
[PATCH]xend: fix dual destroy
After changeset 18030 and 18064 were checked in, I found some issues when creating HVM domains with devices assigned: In XendDomainInfo.py, we have the call trace: the global function create() => vm.start() => _constructDomain(). In _constructDomain(), we invoke xc.test_assign_device() and when the function fails (maybe because iommu=1 is not specified in grub entry since iommu is 0 by
2013 May 24
3
[BUG, PATCH] xen-4.1-3 xend/XendDomainInfo.py#device_configure() TypeError
Hello, I noticed a bug in Xen-4.1-3, which is also still present in xen+git. I know that the Python xend is deprecated, but I''m stuck with xen-4.1 until xen is usable with libvirt, so my patch might still be helpful for others. This is a follow-up to <http://lists.xen.org/archives/html/xen-users/2012-11/msg00069.html>, which still keeps me busy. /xen/xend/server/SrvDomain.py
2008 Mar 26
5
[Xen-users] 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
2006 May 11
2
Problem to run xend
Hello People!! I''ve a problem with the xend service, when i want to run it don'' t show me nothing, so then i tried to run it like these: /usr/sbin/xend start and show me a lot of errors see --> ERROR: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend", line 33, in ?
2007 Feb 27
3
freebsd domu 14, bad address
Hello, I''m trying to get a freebsd virtual machine running following : http://www.yuanjue.net/xen/howto.html But I get : # xm create freebsd_xen_INSTALL -c Using config file "./freebsd_xen_INSTALL". Error: (14, ''Bad address'') Am I missing something? I am using xen 3.0.4. Thanks and regards, Sergi .... log output from xend.log: [2007-02-27 12:46:59
2012 Mar 27
2
domU's being killed - strange?
Hi all Greetings from Patagonia Argentina - this is my first message to this list. I''m having a weird problem: when I reboot some domU, some OTHER domU gets killed. Scenario: > cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 1 > uname -sri Linux 2.6.32.43-0.4-xen x86_64 > rpm -qa | grep xen- kernel-xen-base-2.6.32.43-0.4.1
2009 Jun 21
1
Xen LVM DRBD live migration
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
2011 Aug 03
1
Bug#636552: xen-hypervisor-4.1-i386: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Package: xen-hypervisor-4.1-i386 Version: 4.1.1-1 Severity: important Tags: wheezy I cannot boot a domU with networking after installing the package. root at topsail:~# xm create /etc/xen/udevtest.cfg -c root at topsail:~# Error: Device 0 (vif) could not be connected. Hotplug scripts not working. [2011-08-03 15:56:53 4411] DEBUG (DevController:139) Waiting for devices tap2. [2011-08-03
2007 Sep 19
2
Error: (22, ''Invalid argument'')
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
2009 Mar 19
2
New DomU on older Dom0
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
2007 Jul 13
1
Error 22 on domU creation after installing 3.1 from source
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
2010 Jun 07
1
111b virt-install failure
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
2006 May 18
4
Fail to create hvm domain
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
2010 Jun 06
3
Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1
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 = [
2006 Jan 21
4
Xen Starting DomainU:Error: Device 0 (vif) could not be connected. Hotplug scripts not working
hi, I am trying to start a new domainU but got the error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working I have struggled with it for a long time. I found somebody else report this but can not find a solution. The xen version is xen-3.0 latest version. I do not have a initrd. Domain0 works fine but when I create a new domain, it always gives an error as above. Thanks,
2006 Oct 29
1
Problems installing windows 2003 std and x64 as guest
I am running Pentium D 930 with 2 gigs of ram. Fedora Core 6 with Xen enabled. I am able to start the install and it goes to the first stage of needing to be rebooted. I restart the Domain and it starts to finalize the windows install. And is fine until it starts asking for serial numbers or computer names. Then all of a sudden the guest freezes. The guest CPU goes to zero and so does the
2008 Feb 01
3
Error: Device 0 not connected
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
2010 Dec 21
4
tap2:remus:backup_ip:9000|aio:/path_to_disk.img not working - OSError: [Errno 2] No such file or directory
Hello, I''m using Xen (installed from source - "hg clone http://xenbits.xen.org/xen-4.0-testing.hg") on Debian Lenny. Dom0 kernel is 2.6.32-bpo.5-xen-686. Until now I have successfully ran the Lucid Ubuntu as domU guest, defining disks as (and also as file:): disk = [''tap2:aio:/home/xen/domains/lucid/disk.img,xvda1,w'',
2009 Jan 19
2
Error on xm create: VmError: (38, ''Function not implemented'')
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 =