similar to: Processed: severity of xen-api bug 702428 is important

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

errors from /var/log/xcp-xapi.log: 652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xapi] creating device emulator 652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops] Device.Dm.start domid=10 661Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops] qemu-dm: should be running in the background (stdout redirected to syslog) 661Z|debug||1227 UNIX

Processing commands for control at bugs.debian.org: > severity 702428 serious Bug #702428 [xcp-xapi] HVM fails to start with VIF / qemu-dm error Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 702428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702428 Debian Bug Tracking System Contact owner at

Processing commands for control at bugs.debian.org: > severity 675052 normal Bug #675052 [xcp-xapi] xcp-xapi: xe vm-memory-target-set does not write target to xenstore Severity set to 'normal' from 'important' > severity 678923 normal Bug #678923 [xcp-xapi] xcp-xapi: host-disable and host-reboot make host disable forever Severity set to 'normal' from

Hi, I've been testing the Debian packages ahead of the Debian 7 release (which is very imminent) I believe this is a serious bug[1] in the package, as it appears that HVM networking is broken, or at the very least, requires some undocumented configuration step Specifically: - I can start the HVM domU without any vif - if I attach a vif, the domU will not start Looking at

Processing commands for control at bugs.debian.org: > severity #674137 wishlist Bug #674137 [xcp-xapi] xcp-xapi: default ports in xapi Severity set to 'wishlist' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 674137: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674137 Debian Bug Tracking System Contact owner at

Processing commands for control at bugs.debian.org: > severity 655303 wishlist Bug #655303 [xcp-xapi] xcp-xapi: document network configuration in README.Debian Severity set to 'wishlist' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 655303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655303 Debian Bug Tracking

Processing commands for control at bugs.debian.org: > severity 682979 normal Bug #682979 [xcp-xapi] xcp-xapi: VM not starting, tasks not cancellable Severity set to 'normal' from 'grave' > End of message, stopping processing here. Please contact me if you need assistance. -- 682979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682979 Debian Bug Tracking System Contact

Processing commands for control at bugs.debian.org: > severity 702337 important Bug #702337 [xcp-xapi] xen-xapi / Open vSwitch not really working Severity set to 'important' from 'serious' > thanks! Unknown command or malformed arguments to command. > I don't think this bug should be RC. Even without openvswitch, XCP works Unknown command or malformed arguments to

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

Processing commands for control at bugs.debian.org: > retitle 655301 xend shouldn't start if TOOLSTACK is not xm Bug #655301 [xcp-xapi] xcp-xapi fails to start Changed Bug title to 'xend shouldn't start if TOOLSTACK is not xm' from 'xcp-xapi fails to start' > reassign 655301 xen-utils-common Bug #655301 [xcp-xapi] xend shouldn't start if TOOLSTACK is not xm Bug

Processing commands for control at bugs.debian.org: > reassign #680528 xen-utils-common Bug #680528 [xcp-xapi] xcp-xapi: /etc/init.d/xendomains cause xapi to hand during boot Bug reassigned from package 'xcp-xapi' to 'xen-utils-common'. No longer marked as found in versions xen-api/1.3.2-8. Ignoring request to alter fixed versions of bug #680528 to the same values previously

libxenapi-ocaml-dev_1.3.2-2_amd64.deb to main/x/xen-api/libxenapi-ocaml-dev_1.3.2-2_amd64.deb python-xenapi_1.3.2-2_all.deb to main/x/xen-api/python-xenapi_1.3.2-2_all.deb (new) xcp-networkd_1.3.2-2_amd64.deb extra admin daemon to manage network configuration for xcp-xapi The Xen Cloud Platform (XCP) is an open source enterprise-ready server virtualization and cloud computing platform, with

Processing commands for control at bugs.debian.org: > retitle 674137 Please make bind port configurable Bug #674137 [xcp-xapi] xcp-xapi: default ports in xapi Changed Bug title to 'Please make bind port configurable' from 'xcp-xapi: default ports in xapi' > severity 674137 wishlist Bug #674137 [xcp-xapi] Please make bind port configurable Ignoring request to change severity

Processing commands for control at bugs.debian.org: > severity 695221 important Bug #695221 [xcp-xapi] xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet netmask Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 695221:

Processing commands for control at bugs.debian.org: > reassign 677614 xen-utils-common 4.1.2-6 Bug #677614 [xcp-xapi] xcp-xapi: someone should create /etc/default/xen Bug reassigned from package 'xcp-xapi' to 'xen-utils-common'. No longer marked as found in versions xen-api/1.3.2-6. No longer marked as fixed in versions 4.1.2-7. Bug #677614 [xen-utils-common] xcp-xapi: someone

Processing commands for control at bugs.debian.org: > fixed 673743 1.3.2-6 Bug #673743 [xcp-xapi] xen-api: smbfs does not exist any more, move to cifs-utils Marked as fixed in versions xen-api/1.3.2-6. > End of message, stopping processing here. Please contact me if you need assistance. -- 673743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673743 Debian Bug Tracking System Contact

Processing commands for control at bugs.debian.org: > tags #680588 pending Bug #680588 [xcp-xapi] xcp-xapi: startup race condition between xcp-xapi and xcp-networkd on slave Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 680588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680588 Debian Bug Tracking System Contact owner

The log snippet doesn''t have the detail in it - have a look in /var/log/SMlog - you might find something more useful in there. Jon On 5 Apr 2012, at 10:23, Dimitar Kazakov wrote: > Hi, > have permanent failure when try to create VDI on local SR type=file or > type=ext. On both types it failed with the same error: > SR_BACKEND_FAILURE_78 > VDI Creation failed

Hi, I''ve installed XCP 0.5 and I''m following these steps: http://xenbits.xen.org/xapi/install.html to install ddk VM. But I can''t get network working. I tried to create a vif under xenbr0 then assigned mannually a IP address and to create a vif under xapi0. But in both cases I can ping only dom0 IP. What am I doing wrong? Thanks in advance. -- Sergio Roberto