similar to: Bug#702428: HVM fails to start with VIF / qemu-dm error

Displaying 20 results from an estimated 1000 matches similar to: "Bug#702428: HVM fails to start with VIF / qemu-dm error"

2013 Mar 17
2
Bug#702428: HVM networking tap/vif bug (Debian bug 702428)
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
2013 Mar 05
1
Bug#702338: can't create network from xe command line
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
2013 Mar 07
0
Bug#702428: log output
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
2013 Mar 05
1
Bug#702337: xen-xapi / Open vSwitch not really working
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
2012 Jun 24
1
Bug#678723: xcp-xapi: vif-interfaces added to database as PIF's
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
2013 Aug 06
1
Bug#718864: wrong default route
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
2013 Mar 05
1
Bug#702340: xe sr-create creates nested PV/VG
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
2013 Jul 08
1
Bug#715333: IPv6 security risks with XCP dom0
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
2013 Oct 07
1
Bug#725676: resizing SR fails
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 -
2012 Jun 11
5
xcp + ubuntu + openvswitch VLAN problem
hi all , i use ubuntu 12.04 with xcp , all config run very well except vlan i use xe network-create and xe vlan-create to build vlan 3000 then startup a vm in this network, xapi0 fakebridge and vif1.0 all looks well, use ovs-vsctl list port i can see xapi0 and vif1.0 have beed taged with 3000 but i can not access the internent~~~ somebody can help me with this? thanks.
2013 Mar 15
1
Bug#702428: raising to serious
My impression of this bug is that HVM networking is not possible with XCP, or at least it is not possible without some undocumented configuration setting or missing dependency package If there is a workaround from upstream, I would propose lowering the severity to important again. I am happy to test any proposed work around and provide quick feedback. The log output in my previous post suggests
2012 Jun 05
1
need your help with xcp vlan
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
2012 Sep 11
1
Bug#687284: /usr/lib/xcp/bin/xe-reset-networking uses Fedora-specific paths
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.
2012 Nov 09
1
Bug#692841: xen-api: [INTL:ja] New Japanese translation
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
2013 Dec 31
1
Bug#733694: please do not depend on module-init-tools
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 --------------
2013 Feb 24
1
Bug#701554: xcp-xapi: bashism in /bin/sh script
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
2013 Dec 08
1
Bug#731718: after run: xe vm-import filename=... The VM could not be imported
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
2010 Jul 13
3
[Xen-API] XCP - ddk network
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
2012 Jul 06
1
Bug#680500: xcp-xe: Tab in autocomple of params for 'xe pif-list params=' erase some arguments
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,
2012 Jul 06
1
Bug#680511: xcp-xe: autocomplete for sr-probe type=nfs does not provide hints for device-config
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