search for: 0004sd

Package: xcp-xapi Version: 1.3.2-15 Severity: important New wheezy box Follow the setup instructions for xcp-xapi, choosing openvswitch networking Only loopback is defined in /etc/network/interfaces (the way it should be for XCP) IP address, router, DNS has been configured statically with pif-reconfigure-ip After reboot, the IP address is assigned correctly on the bridge interface but some

Package: xcp-networkd Severity: important Your package currently depends on the module-init-tools package, which since March 2012 has become a dummy transitional package. Please update your package to depend on kmod, because I want to remove the transitional package. You only need to replace "module-init-tools" with "kmod" in debian/control. -- ciao, Marco --------------

Package: xcp-xapi Version: 1.3.2-11 xe-reset-networking uses Fedora/CentOS-specific paths like /etc/firstboot.d (perhaps /var/lib/xcp/firstboot.d instead? - this is used in other places) and /etc/sysconfig and possibly others. The script doesn't properly reset networking due to this. Regards, Ognyan Kulev -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Package: xen-api Version: 1.3.2-12 Severity: wishlist Tags: patch l10n Dear xen-api package maintainer, Here's Japanese po-debconf template translation (ja.po) file that reviewed by several Japanese Debian developers and users. Could you apply it, please? -- victory http://userscripts.org/scripts/show/102724 -------------- next part -------------- A non-text attachment was

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

Package: xcp-xe Version: 1.3.2-14 Severity: normal I created an LV manually and ran the command: xe sr-create type=ext name-label=myHostSr0 \ device-config:device=/dev/mapper/vg00-sr0 The SR was created, however, I found that it was created as a nested LV, in other words, it appears xe did something like this: pvcreate /dev/mapper/vg00-sr0 vgcreate sr_vg lvcreate sr_vg sr0

Package: xcp-xe Version: 1.3.2-15 after run: xe vm-import filename=debserv.ovf i get messages: The VM could not be imported. msg: INTERNAL_ERROR: [ Failure("int_of_string") ] In /var/log/xcp-xapi.log, i get the lines: |5239 INET 127.0.0.1:80|VM import R:d700155bd1f0|import] Importing (as new VM) |5239 INET 127.0.0.1:80|VM import R:d700155bd1f0|import] Reading XML |5239 INET

Package: xcp-xapi Version: 1.3.2-14 Severity: important I understand that XCP version 1.3 doesn't support IPv6 This blog talks about enabling it in v1.6: http://jeffloughridge.wordpress.com/2013/06/16/ipv6-in-xcp-1-6/ However, one observation that I have made is that the dom0 host, in a default wheezy installation, has kernel IPv6 enabled and appears to have a link-local address on every

Package: xcp-xapi Version: 1.3.2-14 I've expanded the underlying volume for the SR xe sr-scan doesn't seem to detect the new space I've tried various things: - using pvresize so that LVM detects the bigger partition pvresize /dev/sda6 and the pvscan command now shows the correct space. running "xe sr-scan uuid=$UUID" after this failed to detect the space -

Package: xcp-xapi Version: 1.3.2-14 Severity: important I imported a HVM from a legacy xm environment. It is attached to one vif, the xenapi management vif It fails to start: # xe vm-start uuid=f2ba4767-7b4f-b416-3da6-3fe059ebfc37 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: device model

Package: xcp-xe Version: 1.3.2-8 Severity: minor When autocomplete for bash is activated following misbehavior happens: xe pif-list params=device,m[Tab] expected behavior: autocomplete to xe pif-list params=device,management actual behavior: xe pif-list params=management ('device' removed) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500,

Package: xcp-xe Version: 1.3.2-8 Severity: minor XCP 0.5,1.0 and 1.1 provides hints for device-config depends on type field in sr-probe, xcp-xapi (xcp-xe) does not. Difference: XCP 1.1 behavior: xe sr-probe type=nfs device-config:[Tab] device-config: device-config:serverpath= device-config:server= xcp-xe behavior: xe sr-probe type=nfs device-config:[Tab] (nothing) Other arguments

Package: xcp-xe Version: 1.3.2-11 Severity: minor xe did not prove help in autocomplete for xe console command. Steps to reproduce: xe console[tab] Output (help) does not contains xe console command. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores)

Your message dated Sun, 02 Mar 2014 18:42:06 +0000 with message-id <E1WKBKw-0004SD-Mw at franck.debian.org> and subject line Bug#740517: Removed package(s) from unstable has caused the Debian Bug report #710650, regarding xen-api: FTBFS: gcc: error: /home/blank/debian/xen/releases/xen/xen-4.2.1/debian/build/build-utils_amd64/tools/ocaml/libs/xc/../../../../tools/libxc/libxenct...

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: [

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: 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)

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: src:xen-api Severity: wishlist I've tried to configure VLAN using XCP + openvswitch using Wheezy, though it's still not fully working, I think VLAN configuration on dom0 can be better documented. It's fair easy to configure VLAN in Debian. First you need to ensure that your physical switch is in trunk mode, which means it will pass all kinds of VLAN tagged network flow, and

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