search for: xapi1

...66e4|xapi] Vmops.start_paused caught: INTERNAL_ERROR: [ Device.Ioemu_failed("qemu-dm exitted unexpectedly") ] and more from /var/log/daemon.log: xcp-fe: qemu-dm-10[9169]: domid: 10 xcp-fe: qemu-dm-10[9169]: -c config qemu network with xen bridge for xcp-fe: qemu-dm-10[9169]: tap10.0 xapi1 xcp-fe: qemu-dm-10[9169]: can't add tap10.0 to bridge xapi1: Operation not supported xcp-fe: qemu-dm-10[9169]: /etc/xen/scripts/qemu-ifup: could not launch network script xcp-fe: qemu-dm-10[9169]: Could not initialize device 'tap' The message about "can't add tap10.0 to b...

...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 openxenmanager, selecting `Internal Network'. Now it appears in openxenmanager and it is visible from the command line (as xapi1 this time)

hi all, im peter, i found the post here http://www.gossamer-threads.com/lists/xen/users/229738 i build a small test env, with 2 vm in 1 server with xcp 1.1.0 i use xe network-create and xe vlan-create to build the vlan for each vm. then i got 2 bridge like xapi1 and xapi2, and in the ovs-vsctl list port i can see all these info about fake-bridge and vlan tag is correct. but when i start 2 vms, and try to ping the dom0 ip , i got fault, all iptables in dom0 and vms are closed. do you know what is the reson of this? thanks for your help. _______________...

...VM 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 /var/log/daemon.log, I notice: xcp-fe: qemu-dm-10[9169]: can't add tap10.0 to bridge xapi1: Operation not supported while the output from dmesg suggests that the interface vif10.0 was created. It appears there is confusion between the vifX.Y and tapX.Y naming schemes. Can anybody comment on this? Is this hardcoded into some config that I should inspect? Is it hard coded in the qemu-...

...to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: device model failed to initialise: qemu-dm exitted unexpectedly I've seen exactly the same error when I attach another Linux HVM to an internal network (i.e. xapi0, xapi1, ...). Removing the vif, it is possible to boot these HVMs I notice that the xcp host only has a small number of qemu packages installed: # dpkg --list | grep qemu ii qemu-keymaps 1.1.2+dfsg-5 all QEMU keyboard maps ii qemu-utils...

xe vm-start vm=debian Your license has expired. Please contact your support representative. Network and Management Interface XCP 0.5.900-36486c I was seriously under the impression we fixed this, now all my images are offline is there any way to fix this without reinstalling everything ? _______________________________________________ Xen-users mailing list