similar to: xend.log

Hi *, when I try to start this config kernel = "/boot/vmlinuz-2.6.11-xenU" memory = 128 name = "Virtual1" vif = [ ''mac=aa:00:00:00:00:11, bridge=xen-br0'' ] disk = [ ''phy:vg00/domu01_lv,sda1,w'' ] root = "/dev/sda1 ro" extra = "4" I get this errors in xend.log (tried two times): [2005-05-23 13:37:22 xend] INFO

Pardon me for a long detailed post but this looks pretty serious. The bottom line is that, when I attempt to shut down or reboot my simple xen-2.0.7 server running FC3 with two domUs, shutting down xendomains appears to send python into an infinite loop. This may be due to a serious misconfiguration on my part but it is certainly a big problem. If we shutdown the domUs manually first, the

Hello: I just gave 3 tries at compiling a xen kernel. I managed to get the networking in the host to work ok on the third try, unfortuately xend gives me the following errors in my xend.log and will not start. Any ideas? It fails to start with the following error ---------------------------------------------------- /usr/sbin/xend [root@localhost ~]# /usr/sbin/xend start Traceback (most recent

Xend lifecycle changes -- basic functionality. xend/XendDomain.py | 287 ++++++++++++++++++++++++++++++++++---------- xend/XendDomainInfo.py | 203 +++++++++++++++++++++++-------- xend/XendRoot.py | 8 + xend/server/XMLRPCServer.py | 2 xm/create.py | 4 xm/main.py | 29 +++- xm/new.py | 68 ++++++++++ 7

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

Hi, I try to start a DomU with xm create endian -c and got the following error message Xend has probably crashed! Invalid or missing HTTP status code. I''ve tested the DomU with nearly the same system at VMWare (Windows) and it works normaly, but on my server I get this error message. I useing gentoo as Dom0. I tried also a gentoo DomU with the same result. Thanks.

Hi, every one: I had problem creating domU on diskless device by using xen-unstable. Following, please find out details. BTW, the same configuration works fine on device with hard disk (1) Xen, dom0 kernel and dom0 root file system are loaded/mounted over via eth0 (2) DomU root file system is created in a file-backed virtual block device(VBD). The file-backed VBD locates at some directory on

Hi all, one of my servers crashed last sunday just right after a startup and I need to understand what was going on. I am running Windows 2008 R2 Standard Edition on Oracle VM 3.1 - Xen 4.1.2-OVM On sunday a scheduled task shutted down cleanly the vm. the shutdown started at Sun Jun 16 10:00:33 and it ended at 2013-06-16 10:00:46.938. xend.log says: [2013-06-16 10:00:45 7228] INFO

Dear All, am new to xen and recently implemented it. i had some issues initially but googling arround and some wise replies from you guys out there managed to clear them. now I have 2 virtual machines on my xen domains one is windows 2003 and other windows2008 both the virtual machines were working fine for about a week jus 2 days back we had a change in our network . i mean we rearanged the

I am seeing a strange issue while running Mini-OS on the changeset 9906:a95e677073c1. This is on both i386 and x86_64. The only difference being on i386 if I stop printing to the console, this issue is not manifested. But with x86_64 it happens all the time. Bringing up Mini-OS for the first time causes xm to hang on certain commands like "list, destroy". Other commands like

Hi I tried building xen on my IA64 machine. It builds and installs smoothly. But I have not been able to start xend. I get the error in /var/log/xen/xend.log as below: [2007-06-14 05:02:01 xend 26504] WARNING (XendAuthSessions:27) python-pam is required for XenAPI support. [2007-06-14 05:02:01 xend 26520] INFO (SrvDaemon:322) Xend Daemon started [2007-06-14 05:02:01 xend 26520] INFO

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'',

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''ve got a system with 3 nics. eth0 is down, eth1 is external and eth2 is internal. (This is in a "lab" so the "external" is a 10.x.x.x address.) Before starting xen, the broadcast for eth2 is 192.168.1.255, after starting it becomes 0.0.0.0 - which sure doesn''t look right to me - plus I''m getting networking problems. Been digging for a while and

Hi all, I am trying the pci-passthrough on xen 3.3.0. I binded the pci slot to pciback using late binding. But xend fails to allocate this slot to domU. linux-242:/home/xen-3.3.0 # xm create -c pci=08:01.0 /etc/xen/xen3.3_guest1 Using config file "/etc/xen/xen3.3_guest1". Error: [Errno 2] No such file or directory: ''/sys/bus/pci/devices/0000:06:00.0/config''

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

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

An error displayed while running virt-manager or virt-install [root@HPCNL-SR-2 init.d]# virt-install ERROR    unable to connect to ''localhost:8000'': Connection refused Traceback (most recent call last):   File "/usr/sbin/virt-install", line 780, in <module>     main()   File "/usr/sbin/virt-install", line 530, in main     conn =

delete xend entry when destroying pv usb host controller of a guest os which has no pv-frontend driver loaded. -James (Song Wei) Signed-off-by: James (Song Wei) <jsong@novell.com> diff -r f42ff98a2cdc tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py Thu Mar 25 09:32:21 2010 +0000 +++ b/tools/python/xen/xend/XendDomainInfo.py Fri Mar 26 13:27:25