similar to: Bug#661687: xen-utils-common: TOOLSTACK setting not honored

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

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

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'

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}" !=

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}

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

Package: xen-utils-common Version: 4.1.0~rc6-1 Severity: important Currently xend fails to create a fully virtualized vm because it has a different path hardcoded to it. Unable to complete install: 'POST operation failed: xend_post: error from xen daemon: (xend.err "Error creating domain: device model '/usr/lib64/xen/bin/qemu-dm' not found")' The correct path to use

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}

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

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

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:

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

Package: xen-utils-common Version: 4.1.2-7 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, The script /usr/lib/xen-common/bin/xen-toolstack improperly aborts if *either* `xm` or `xl` cannot be found in the xen-dir (/usr/lib/xen-4.0/bin). This means that a default installation (e.g. following Debian wiki on the subject, namely installing xen-linux-system and

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important Tags: security patch When you use xl toolstack, you can't reboot domUs. When you switch back to xm toolstack, than reboot works again. I think the problem with the debian packaged version is the same as in this thread: http://lists.xen.org/archives/html/xen-devel/2011-09/msg01289.html I also think it's a security issue,

On Tue, 2013-10-22 at 11:52 +0200, PASZTOR Gyorgy wrote: > When you use xl toolstack, you can't reboot domUs. > When you switch back to xm toolstack, than reboot works again. > I think the problem with the debian packaged version is the same as in > this thread: > http://lists.xen.org/archives/html/xen-devel/2011-09/msg01289.html > I also think it's a security issue,

Package: xen-utils-common Version: 4.1.2-1 Severity: grave Justification: renders package unusable (Grave because dash is the default /bin/sh) With dash 0.5.5.1-7.4 as /bin/sh, /usr/sbin/xm enters an infinite loop of reexcuting itself. When run with bash, it works correctly. I traced that to /usr/lib/xen-common/bin/xen-toolstack; here's the diff between "/bin/sh -x /usr/sbin/xm"

I''ve migrated my Dom0 host to Xen 4.2.0 + xl toolstack. With ''xm'' toolstack, configs in /etc/xen/auto are autostarted, assuming xend/xendomains services are started. IIUC, when using xl toolstack, those services are not to be started; and, afaict, the installation process for 4.2 has them disabled by default. Now, the configs in /etc/xen/auto are simply ignored. I

I have just installed Xen by following http://wiki.xen.org/wiki/Xen_Beginners_Guide All in all pretty good, however it mentions using the xl toolset but when I first installed only the xm toolset would work. This was great for creating linux based domains but it gave me an error about hvm when I tried creating a Windows domain. I then apt-get install xen-tools-common and edited /etc/default/xen

Hi, "Ian Campbell" <ijc at hellion.org.uk> ?rta 2013-10-22 11:17-kor: > On Tue, 2013-10-22 at 11:52 +0200, PASZTOR Gyorgy wrote: > > When you use xl toolstack, you can't reboot domUs. > > When you switch back to xm toolstack, than reboot works again. > > I think the problem with the debian packaged version is the same as in > > this thread: > >

Hello, Currently it seems that the drbd disk type with Xen''s XL toolstack (vs XM) to get the automatic promotion/demotion behavior of drbd devices is not supported. Is there something I can tweak with the block-drbd script to get this to work? Thanks, Chris _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users