similar to: Bug#682202: xcp-squeezed: race between xenstore initialization and sqeezed

Package: xcp-squeezed Version: 1.3.2-9 Severity: important When trying to start a guest I get: # xe vm-start name-label=squeeze-2 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Failure("The ballooning daemon is not running") If I then manually run "/etc/init.d/xcp-squeezed

I am a consultant needing to learn virtual machines. Using XEN Server 6 as tool. I will put real internet servers on it when stable. Been working fine till it crashed out of the blue. This problem is from a full wipe and reload. Problem: 1. Build XEN Server 6. Works fine after install reboot. 2. Reboot XEN Server. Big message "The underlying Xen xapi is not running"

Package: xcp-xapi Version: 1.3.2-8 Severity: important Tags: patch Found race condition (specific only to slave hosts): xcp-xapi can start earlier than xcp-networkd due lack of dependency in init.d script. Syptoms: After reboot slave's xcp does not work: xe (anything): The host failed to acquire an IP address on its management interface and therefore cannot contact the master. log:

1) Misspelled message ''killing umanaged domain'' (must be killing UNmanaged domain) 2) more serious. I found this message after disappearance of virtual machine created early. I restart XAPI tool stack and machine was killed (not shutdowned, but completely removing). Here log (from machine where domain was resident) Main line in log file I suspect:

hi xen 4.0.1 w/2.6.32.41 Last week dom0 experienced an hard crash and box need to be restarted manually (despite kernel.panic=20). Serial console was not setup, only netconsole. No relevant entries through netconsole, but analyzing logs I see some crashes twenty minutes before fatal hang. Dec 2 01:29:39 xenhost-rack1 kernel: [4437064.011963] Call Trace: Dec 2 01:29:39 xenhost-rack1 kernel:

Package: xcp-xapi Version: 1.3.2-8 Severity: important During startup /etc/init.d/xendomains script is called. That script is installed with xen-utils-common witch xcp-xapi is depends on. That script calls /usr/sbin/xen as xen list &> /dev/null This 'xen' seems to call xapi: xen list ^Z [1]+ Stopped xen list root at lab-xh3:~# ps f PID TTY STAT TIME

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Function wait_for_xapi in /etc/init.d/xcp-xapi does not work as intented. Symptoms: (on slave) /etc/init.d/xcp-xapi restart [....] Restarting The XenAPI server: xapiThe host toolstack is still initialising. Please wait. Cause: Line 'xe pif-scan host-uuid=${INSTALLATION_UUID}' called before xapi is fully synced with master.

I've got a Digium PCI telephone card that I'm trying to use with an AsteriskNow guest, on a CentOS 5.2 host. I've tried setting up the pciback stuff, and think I've done it right, but the card does not show up in the guest. I'm obviously missing something, so any help (including ways to debug this!) would be greatly appreciated. Here's some more info: The guest is

Hi, I am running Xen 3.3.1 built from Source with Debian Lenny as the dom0. Everything works fine so far except pyGRUB. So, what I did was install CentOS (latest version ... 5.3 or something) using qemu to a LVM logical volume and from within CentOS I installed the Xen Kernel. Now pyGRUB shows me 3 grub entries: 1) CentOS (2.6.18-128.1.10.el5xen) <= xen hypervisor 2) CentOS

Hi all! I have installed xen on fc6 with kernel 2.6.18-1.2798.fc6xen with rpm package; i have create 3 guest os (fully virtualization) with virt-manager tool, installed on separated partition: 1 fc6 guest, 1 centos 4.4, 1 windows xp pro; all work pretty fine until this point, i have linked the configuration file of the guests machines to /etc/xen/auto for autostart/autostop, but when

Hi, list.I''m new to xen. I follow this article http://www.virtuatopia.com/index.php/Installing_and_Running_Windows_7_as_a_Xen_HVM_domainU_Guest and install my first windows 7 xen guest. I just change a little to need my fits. And This is my xenwin7.cfg kernel ="/usr/lib/xen-4.1/boot/hvmloader" builder=''hvm'' memory = 1024 # Should be at least 2KB per MB of

Hi all heve been trying (in vain) to get a Solaris b44 DomU (dowloaded from Sun) running on a Linux Xenhost I followed exactly how, and it looked ok when it starts booting... But it never boots . adapted the configfile to boot with -v (that I can see at least something) and this is what I get ===SNIP=== root@Xen-VT02:/export/xc/xvm/solaris-b44# xm create solaris-b44-64.py -c Using config

Hey Guys, when starting a DomU we use iscsi as disks for our vms. When testing throughput I get half the troughput in contrast to tests on the Dom0 itself. For Example: I log in the target on the xenhost (Dom0) itself and get a troughput of 80mb/s. that''s ok Now im starting the VM (DomU) and the same target is now attached as xvdb. When doing troughput tests the speed is about

i didn''t got a response at gedora-xen, so reposting it here ... looks like 3.1 still has stability issues with Networking and Dom0 .. ----- Forwarded by Sven Oehme/Germany/IBM on 06/26/07 05:33 PM ----- Sven Oehme/Germany/IBM 06/17/07 04:12 PM To fedora-xen@redhat.com cc Subject F7 System crash with high network load Hi, i experienced it now a couple of time that my Dom0 will

Hi all, Somebody have tried to run FreeBSD 6.x or 7.x 64 bits under xen as a HVM guest?? Under xenhost 32bits based, freebsd bootloader crash (on Intel platform) and it isn''t possible to install. But what about 64 bits?? FreeBSD bootloader crash too?? Thanks. -- CL Martinez carlopmart {at} gmail {d0t} com _______________________________________________ Xen-users mailing list

Hi, i''m prepering to upgrade my servers from xen 3.0.3 32-bit to 3.2.1 64-bit. The old system: Debian 4.0 i386 with included hypervisor 3.0.3 (pae) and dom0 kernel. The new systen: Debian lenny amd64 with the included hypervisor 3.2.1 and dom0 kernel from Debian 4.0 amd64. My domUs have a self compiled kernel out of the dom0 kernel of the old system (mainly the dom0 kernel but

Hi, All I''m just new to this list, I''m started to dealing with OSS Xen to XCP migration earlier this week, seem the domUs installed via virt-install are function well, but domUs copied via dom0 are failed during bootup process, finally I realize if I could fix this on my OSS Xen will resolve all. Can I have any suggestion from you please ? *Details* *Source XenHost* OS:

Hi All, I am trying to create an initrd for a VM which uses LVM as its root partition. I am running the mkinitrd command a dom0 that also uses LVM - dom0''s volume group is "XenHost" while the VM''s volume group is "VG_VM10" (not sure if that matters). I issue the mkinitrd command from a chroot''d environment so I get the right /lib/modules &

Hi All, I tried again with XAPI on Debian last night and this time things went far smoother... I managed to boot into the Xen kernel, xe is working and the XAPI daemon appears to be running. However, I am having trouble connecting to XAPI from XenCenter... it just says the connection was refused without any meaningful errors and nothing in the logs on either side. I can ping the Xen machine from

OK, so after several weeks of trying to get various versions of Xen running of various distributions, I''m starting to wonder if I''ve got a hardware compatibility problem and as the system never really boots with the Xen kernel I''ve got no log files to tell me where the problem is. I was wondering if there''s a way to compile from source with debug turned on,