similar to: Bug#702428: raising to serious

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

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

I''m using Xen 4.1 and here''s what I did: 1.comment network-script and vif-script about bridge in /etc/xen/xend-config.sxp, uncomment the lines about nat 2.set vm config, add something like vif = [ ''mac=00:16:3e:00:00:11, ip=10.0.0.1'' ] 3.set /etc/network/interfaces in domU, add lines as follows: auto eth0 iface eth0 inet static address 10.0.0.1 gateway

Package: xcp-xapi Version: 1.3.2-14 Severity: important I chose the Open vSwitch (ovs) networking mode when I installed XCP # cat /etc/xcp/network.conf openvswitch Whenever I boot a VM, I notice that the vif interface is created (e.g. vif1.0) on dom0, and the vif is added to the ovs bridge (I can see it in the output of ovs-vsctl show) However, there is no connectivity, I can't ping the

I''m using Xen 4.1 and here''s what I did: 1.comment network-script and vif-script about bridge in /etc/xen/xend-config.sxp, uncomment the lines about nat 2.set vm config, add something like vif = [ ''mac=00:16:3e:00:00:11, ip=10.0.0.1'' ] 3.set /etc/network/interfaces in domU, add lines as follows: auto eth0 iface eth0 inet static address 10.0.0.1 gateway

control: severity +2 serious I would call this an RC bug (serious), but not critical It would be critical if the user lost data from some unrelated application, etc It is serious because a) it makes the package and the whole system unusable for all but one very specific network configuration (users with a /24) b) using good old `xm' style Xen I never experienced any issue like this,

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

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

Hi! Please help me. # xm create win7.hvm Using config file "./win7.hvm". Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1 grep -v ^# /etc/xen/win7.hvm | grep -vx '''' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 name = "win7" vif = [

Package: release.debian.org Severity: normal The current README.Debian is quite old It gives some advice that will lead to people having a broken system (e.g. no networking). It describes a procedure for configuring networking that is completely opposite to what has been described more recently on the upstream mailing list http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702337 I'm happy

Just a brief update, the XCP entry in my blog appears to be one of the most popular pages on my site on a recurring basis I think this is a sign that (surprise surprise) people are using Debian for servers, they want to continue doing so in the cloud/virtualization era and the ability to run XCP this way is something they specifically want - big thanks are due to all those who have made it

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

I've created a blog entry about my XCP on Debian wheezy experiences http://danielpocock.com/migrating-to-xen-cloud-platform-on-debian-wheezy Please let me know if anything is inaccurate or could be explained better. I'm quite happy to add links out to other resources that are up to date.

I migrated a CentOS7 VM (the fedrtc.org site) from an XCP environment to a libvirt/KVM environment. This involved using qemu-img to convert the image from VHD to qcow2 and then using virt-install --import to define the VM in libvirt. Three problems occurred during boot: a) on the first boot, the BIOS screen and grub screen don't appear at all, the screen is blank for a couple of seconds and

Package: xcp-xapi Version: 1.3.2-13 Severity: critical I get this bug when installing XCP and configuring the network portion of it. When I issue the following command: xe pif-reconfigure-ip uuid=$PIF_UUID mode=static IP=10.0.0.10 netmask=255.255.255.240 gateway=10.0.0.1 DNS=10.5.1.2,10.5.1.3 My network interface looks like this (Broken): eth2 Link encap:Ethernet HWaddr 00:50:ec:24:c7:43

hi all, i just found a bug from xapi code network_utils.ml: let is_physical name = try let link = Unix.readlink (getpath name "device") in (* filter out device symlinks which look like /../../../devices/xen-backend/vif- *) not(List.mem "xen-backend" (String.split ''/'' link)) with _ -> false i use xcp + ubuntu 12.04, in my /sys/class/net/ dir it

i just found a bug from xapi code network_utils.ml: let is_physical name = try let link = Unix.readlink (getpath name "device") in (* filter out device symlinks which look like /../../../devices/xen-backend/vif- *) not(List.mem "xen-backend" (String.split '/' link)) with _ -> false i use xcp + ubuntu 12.04, in my /sys/class/net/ dir it looks like:

Package: xcp-xe Version: 1.3.2-14 Severity: important I created an internal network using xe network-create name-label='Private NAT network' Looking with brctl, I could see xapi0 had been created by the tools. However, the network does not appear in openxenmanager. I even restarted openxenmanager, it still didn't appear. Then I deleted the network and created it again from

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-3 Severity: important Hi, I have some domUs with two network interfaces, eth0 and eth1. eth0 is not configured in /etc/network/interfaces and so is not brought up at boot time. eth0 is on the host's external network bridge and eth1 is on the host's local network bridge. On dom0 I get messages like 'vif vif-10-0 vif10.0: draining TX

I've been using XenServer / XCP (with the "xe" toolset) for a number of years for hosting servers used for development and free software projects and I'm now looking at migrating all those environments to libvirt / KVM. I had a look at the wiki[1] already and didn't see XenServer mentioned there. Could anybody help comment on or explain a few things: - comparison between