Displaying 20 results from an estimated 2000 matches similar to: "Bug#674137: xcp-xapi: default ports in xapi"
2012 Sep 05
3
Bug#686778: xcp-xapi: what user should xapi run as
Package: xcp-xapi
Version: 1.3.2-11
Severity: normal
We need to have a separate user/group privilege for xapi and its dependent processes. At the moment, everything runs as root
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux
2012 Jan 10
2
Bug#655302: xcp-xapi: init script will slow down boot process
Package: xcp-xapi
Version: 1.3-15
Severity: wishlist
The current initscript has the possibility of slowing down the boot process by 50 seconds. If this is required, it probably
should be backgrounded.
# Wait for xapi to write its "init complete" cookie: after here it's safe to modify templates.
wait_for_xapi() {
MAX_RETRIES=50
RETRY=0
while [ ${RETRY} -lt ${MAX_RETRIES}
2012 May 23
2
Bug#674132: xcp-xapi: backend check error
Package: xcp-xapi
Severity: important
The README doc mentions:
4/ Configuring Xen and XCP
--------------------------
4.1/ Switch using xl instead of xm and xend to control Xen
As of writing, you should do that:
sed -i "s/TOOLSTACK=/TOOLSTACK=xl/" /etc/default/xen
Where as the init script checks for:
# Exit cleanly if TOOLSTACK != xapi
if [ "${TOOLSTACK}" !=
2012 Jan 10
2
Bug#655301: xcp-xapi fails to start
Package: xcp-xapi
Version: 1.3-15
Severity: normal
My packages were initially installed from the deb repository at download.xensource.org.
Eventually, I upgraded them to the debian repository ones.
Right now, xcp-xapi fails to start with the following messages.
lnx200-39:~# /etc/init.d/xcp-xapi start
Error: Connection refused (calling connect )
lnx200-39:~#
-- System Information:
Debian
2012 Jan 10
2
Bug#655303: xcp-xapi: document network configuration in README.Debian
Package: xcp-xapi
Version: 1.3-15
Severity: normal
By default, xapi listens on the loopback interface. To make it available over the network, its inventory needs to be updated with
the bridged interface details. For example, if xenbr0 is the bridged interface, it needs to be set it:
lnx200-39:~# cat /etc/xcp/inventory
BUILD_NUMBER='0'
CURRENT_INTERFACES='xenbr0'
2011 Jun 30
4
XCP and OpenXenCenter
I just noticed OpenXenCenter (aka OpenXenManager) that is an open source
replacement for Citrix's XenCenter. This tool works with XenServer.
But as per the blog entry:
http://blog.xen.org/index.php/2010/02/09/xen-cloud-platform-installation/
it is also supposed to work with Xen Cloud Platform. XCP is licensed
GPL2 and is a combination of multiple packages.
Has the team looked at the
2013 Aug 30
1
Bug#721345: xcp-xapi: xl pci-attach is called by xapi in a PCI passthrough attempt. An error is raised due to the use of xapi and the PCI device cannot be attached to the VM.
Package: xcp-xapi
Version: 1.3.2-15
Severity: normal
I am trying to pass an SRIOV virtual function in a virtual machine but the attempt fails with the following errors shown in the xcp-xapi.log
[20130829T19:29:17.909Z|debug|sriov1|314 UNIX /var/lib/xcp/xapi|VM.start R:9e8e10bd31bb|pciops] PCI devices from other-config:pci to attach: 0/0000:04:00.1
[20130829T19:29:18.012Z|debug|sriov1|314 UNIX
2012 Jul 06
1
Bug#680499: xcp-xapi: Http_client.Http_request_rejected during upgrade
Package: xcp-xapi
Version: 1.3.2-8
Severity: minor
During upgrade from 1.3.2-7 to 1.3.2-8 got follwing message on slave host (upgrade was simulatanious on slave and master):
...
Setting up xcp-xapi (1.3.2-8) ...
The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.
message: INTERNAL_ERROR: [
2012 Jun 24
1
Bug#678723: xcp-xapi: vif-interfaces added to database as PIF's
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
2012 May 29
1
Bug#675052: xcp-xapi: xe vm-memory-target-set does not write target to xenstore
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)
2013 Feb 24
1
Bug#701554: xcp-xapi: bashism in /bin/sh script
Package: xcp-xapi
Version: 1.3.2-14
Severity: important
User: debian-release at lists.debian.org
Usertags: goal-dash
Hello maintainer,
While performing an archive wide checkbashisms (from the 'devscripts'
package) check I've found your package containing a /bin/sh script making
use of a bashism.
checkbashisms' output:
>possible bashism in ./usr/lib/xcp/lib/host-restore line
2012 May 29
3
Bug#675055: xcp-xapi: xe-edit-bootloader does not compatible with new /dev/sm
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
2012 Jun 15
1
Bug#677614: xcp-xapi: someone should create /etc/default/xen
Package: xcp-xapi
Version: 1.3.2-6
Severity: important
Looks like on Wheezy, /etc/default/xen is not created by xen-utils-common. Since xcp-xapi depends on its existence and further declaration of the toolstack in it, it should take extra care to ensure that it is present.
root at debian:~# aptitude install xcp-xapi
The following NEW packages will be installed:
blktap-dkms{a} blktap-utils{a}
2012 Sep 05
1
Bug#686779: xcp-networkd: unneeded dependency on openvswitch
Package: xcp-networkd
Version: 1.3.2-11
Severity: normal
Given that openvswitch is one of the networking modes, it should be in the Recommends: than being in the Depends:
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64
2012 Dec 01
1
Bug#694891: xcp-guest-templates: unowned files after purge (policy 6.8, 10.8): /usr/lib/xen-common/xapi/CREATE_TEMPLATES_STAMP
Package: xcp-guest-templates
Version: 0.1-4
Severity: important
User: debian-qa at lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):
http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails
Filing this as important as having a piuparts
2009 Sep 10
6
[Bug 23832] New: extended display not working
http://bugs.freedesktop.org/show_bug.cgi?id=23832
Summary: extended display not working
Product: xorg
Version: 7.4
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau at lists.freedesktop.org
ReportedBy:
2012 Feb 29
2
Bug#655301: Status check for Wheezy
There's no date defined yet, but Wheezy freeze will happen soon. How do
we plan on concluding on this bug report?
Recap for the actual bug I reported: If you want to start xapi, execute
the following steps:
1) Start /etc/init.d/xend
2) Stop /etc/init.d/xend
3) Start /etc/init.d/xcp-xapi
Step 1 is required because you need access to /proc/xen/
Step 2 is required because xapi cannot run
2012 Jul 07
1
Bug#680588: xcp-xapi: startup race condition between xcp-xapi and xcp-networkd on slave
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:
2013 Feb 06
2
[XCP] recompiling xapi rpm changes version and licensing details.
Hi there. I needed to recompile xapi to fix a bug that was resolved regarding vdi-create not setting the sharable flag. I used the sources provided in the source-1.iso from xen.org. Everything is good in this regard, and creating a vdi that has "sharable=true" is possible, but I had a problem that forced me to revert to the older copy of the xapi binary because my XCP box was now being
2010 Oct 22
2
[XCP] port usage for XAPI
Good day.
Which ports are used by xapi? I suddenly found it using tcp/13993 and
I''m slightly concern about possible collision between xapi and my own
application, running on dom0 on XCP...
Thanks.
---
wBR, George.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users