similar to: Bug#680102: More fixes for xen-api in Wheezy

Package: xcp-xapi Version: 1.3.2-7 Severity: normal xcp-xapi fails to eject host from pool with following error: xe pool-eject host-uuid=a6806a39-442d-f17d-b7a0-59161d18f56f WARNING: Ejecting a host from the pool will reinitialise that host's local SRs. WARNING: Any data contained with the local SRs will be lost. Type 'yes' to continue yes The server failed to handle your request,

Package: xcp-xapi Version: 1.3.2-6 Severity: normal After some time of rebooting and toolstack restart found very funny output in 'xe pif-lis': xe pif-list params=currently-attached,device device ( RO) : vif2.0 currently-attached ( RO): false device ( RO) : vif211.0 currently-attached ( RO): false device ( RO) : eth1

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream vbd plug to PV domain cause following error: The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=4 | kind=vbd | devid=51760); backend (domid=0 | kind=vbd | devid=51760)) (same error

One line summary: Too many files in a top-level UFS-2 filesystem directory will cause a panic on mount. Kern/Critical/High Priority/SW-Bug Which FreeBSD Release You Are Using: 6.3-STABLE Environment (output of "uname -a" on the problem machine): FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb 10 21:13:39 CST 2008

One line summary: Too many files in a top-level UFS-2 filesystem directory will cause a panic on mount. Kern/Critical/High Priority/SW-Bug Which FreeBSD Release You Are Using: 6.3-STABLE Environment (output of "uname -a" on the problem machine): FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb 10 21:13:39 CST 2008

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream /usr/lib/xcp/bin/xe-edit-bootloader failing with following message: /usr/lib/xcp/bin/xe-edit-bootloader -u 19f66083-e776-70d1-1808-3712688ad138 Creating dom0 VBD: 0fdb952e-92ff-4b53-dd49-8d54b2268787 Plugging VBD: Waiting for /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e0: . done

I was wondering if anyone had experienced the following with asterisk stable. After a period of time (can vary), If I stop asterisk and try to run ztcfg -v to reinitialise my quad e1 card, the server will lock up. Sometimes it's a complete lockup, where it won't even return pings, other times it seems to be "partially screwed". -- ==========================================

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream Normally (in 'iso-based' XCP) is possible to attach VDI to dom0. That operation usually looks like: xe vbd-create vdi-uuid=... vm-uuid=(dom0 uuid) device=N xe vbd-plug I done those steps in xcp-xapi and got success (no error), but no xvd* device found. Here operations log: # xe vbd-create

Package: xcp-xapi Version: 1.3.2-6 Severity: important Tags: upstream xe vm-memory-target-set does not write new target to /local/domain/ID/memory/target. Balloon in guest domain is expecting this value to be changed to do selfballooning. This breaks 'dynamic memory control' feature. Steps to reproduce: 1) Setup any PV virtual machine with static-memory-min < static-memory-max 2)

--- src/nv_driver.c | 32 +------------------------------- 1 files changed, 1 insertions(+), 31 deletions(-) diff --git a/src/nv_driver.c b/src/nv_driver.c index 248a151..9606d97 100644 --- a/src/nv_driver.c +++ b/src/nv_driver.c @@ -315,8 +315,6 @@ NVAdjustFrame(int scrnIndex, int x, int y, int flags) /* * This is called when VT switching back to the X server. Its job is * to

Hi all, today i tried to enable HA on xcp 1.6 but when i enable it through xencenter I received the following error in xensource.log: Dec 5 17:56:26 xcp1 xapi: [ info|xcp1|490661|Async.pool.enable_ha R:9119ce88ffcb|xapi_ha] Using statefile: /etc/xensource/static-vdis/0/disk Dec 5 17:56:26 xcp1 xapi: [debug|xcp1|490661|Async.pool.enable_ha R:9119ce88ffcb|xapi_ha]

Package: xcp-xapi Severity: normal Tags: upstream Are there good reasons why xapi by default prefers to bidn to 80 and 443? This will lead to xapi installation/start failure on every server machine that might (and will probably) have apache installed. I know we can remove apache or change its port or change xapi's port (But I've had a hard time to easily find out where to specify the

Accepted: libxenapi-ocaml-dev_1.3.2-9_amd64.deb to main/x/xen-api/libxenapi-ocaml-dev_1.3.2-9_amd64.deb python-xenapi_1.3.2-9_all.deb to main/x/xen-api/python-xenapi_1.3.2-9_all.deb xcp-networkd_1.3.2-9_amd64.deb to main/x/xen-api/xcp-networkd_1.3.2-9_amd64.deb xcp-squeezed_1.3.2-9_amd64.deb to main/x/xen-api/xcp-squeezed_1.3.2-9_amd64.deb xcp-v6d_1.3.2-9_amd64.deb to

When read() return 0, the current code just tries again. But this leads to an infinite loop if QEMU died too soon. Also, retry select if a signal was caught. Signed-off-by: Anthony PERARD <anthony.perard@citrix.com> --- tools/libxl/libxl_qmp.c | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/tools/libxl/libxl_qmp.c b/tools/libxl/libxl_qmp.c index

I applied the florz patch but my problems remain. Now I get all sorts of weird errors on the console and I cannot make outgoing calls. Incoming calls work as expected. I am using a single HFC-S card with BRI. Any clue what these errors below are? Ri = 44651 TEI msg = 3 TEI = 7f Ri = 3800 TEI msg = 3 TEI = 7f Ri = 42399 TEI msg = 3 TEI = 7f Ri = 42409 TEI msg = 3 TEI = 7f Ri = 22078 TEI msg = 3

Hi, I've been trying to fix several bugs in XCP, before the Debian 7 release. It's not bug free yet, but it's going into that direction. I would need some help to fix the remaining! 1/ The new 1.3.2-12 release The Debian release team has already accepted an unblock for this new version that I uploaded in Debian SID. Here's the debian/changelog: * Fixes bashism in

Hi all I need some help on this one: I have a webpage that writes a jpeg into a div when you click on a thumbnail using javascript. I wanted to display an even bigger version of that jpeg if you click on it so I integrated the Lightbox script (uses prototype.js and scriptaculous.js) If I place initLightbox() into the body onload= then the first thumbnail clicked will write the larger jpeg into

Hi, FreeBSD-9 works fine on this Lenovo T400 - except that suspending with no USB devices plugged in result in no ports working after resume. If I have a device plugged in during suspend - on any port - then all the ports work fine after resume. I've attached usbconfig and acpidump output. here's what is logged in the kernel buffer during suspend and resume: Her'es the suspend:

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.

# HG changeset patch # User Roger Pau Monne <roger.pau@entel.upc.edu> # Date 1318335991 -7200 # Node ID 2fb4bf8c16cd35ddc0bf7ddc7ff8fda4b9678211 # Parent 64f17c7e6c33e5f1c22711ae9cbdcbe191c20062 libxl: reimplement buffer for bootloading and drop data if buffer is full. Implement a buffer for the bootloading process that appends data to the end until it''s full. Drop output from