similar to: Bug#702428: log output

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

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

Hey! I am following the steps at http://wiki.xenproject.org/wiki/XCP_Beginners_Guide for creating a VM. I''ve setup my test VM with 1GiB min/max memory. I''ve assigned 2GiB of memory to dom0 (http://wiki.xen.org/wiki/Xen_Best_Practices) . My box has 12GB of physical memory and runs Ubuntu 13.04. When I do "xe vm-start", I get the following: The server failed to handle

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

1) Misspelled message ''killing umanaged domain'' (must be killing UNmanaged domain) 2) more serious. I found this message after disappearance of virtual machine created early. I restart XAPI tool stack and machine was killed (not shutdowned, but completely removing). Here log (from machine where domain was resident) Main line in log file I suspect:

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

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

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

Thanks, I'll take a look at this. Mike On Sat, Jun 1, 2013 at 12:28 AM, David Su?rez <david.sephirot at gmail.com>wrote: > Source: xen-api > Version: 1.3.2-15 > Severity: serious > Tags: jessie sid > User: debian-qa at lists.debian.org > Usertags: qa-ftbfs-20130529 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages

Source: xen-api Version: 1.3.2-15 Severity: serious Tags: jessie sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20130529 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/?PKGBUILDDIR?' > omake phase1 > omake: Symbol `FamErrlist' has different size

This logfile was recorded while the vm-start was running. -------------- next part -------------- [20120727T14:43:34.919Z| info|vh10|1021 UNIX /var/lib/xcp/xapi|session.logout D:dd291648d150|xapi] Session.destroy trackid=e3179eeb95ba96c64ab771d0cb1557b6 [20120727T14:44:02.180Z|debug|vh10|25|Starting periodic scheduler D:641021a392d0|backgroundscheduler] Adding function Logrotate to queue,

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

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-6 Severity: normal Tags: upstream vbd plug to PV domain cause following error: The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=4 | kind=vbd | devid=51760); backend (domid=0 | kind=vbd | devid=51760)) (same error

Hello XCI developers, I have a HP6930, downloaded xenclient from the git. And by following the instruction in HOWTO, I could get xenclient boot up fine. I try then to start a guest using xenvm.readme as template and nothing shows on the screen for the guest, although xenops shows 2 doms running. Can you point me to how to start a guest. And also, is the tree downloaded from git enough to arrive

Processing commands for control at bugs.debian.org: > severity 702428 important Bug #702428 [xcp-xapi] HVM fails to start with VIF / qemu-dm error Severity set to 'important' from 'serious' > End of message, 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

Hi All I have downloaded the opensource xapi source code. I am not sure what the functins of the follow modules: 1 block_device_io 2 datamodel 3 xiu (I am puzzled by the name "xiu") 4 stats 5 rpc-light 6 rss 7 xb (I think the xapi needs not to talk to xenbus directly) 8 xsrpc (why it writes some "rpc" keys to path of "domain/<domid>" in the

Hi David > Hi all, So I have been playing around with XCP and the static/dynamic > memory parameters. I have a few behavioral questions I would like to > pin down: > > -Is the static-max quantity of free memory on the host always > required before the guest vm can be started? I assume so since you > don''t know a-priori if the guest you are booting supports Xen or

Hello, I am just installing XCP 0.1.1 on a server with 24GB RAM Normally XCP is a 64 bits version but * *uname -a* Linux node012 2.6.27.42-0.1.1.xs0.1.1.737.1065xen #1 SMP Fri Jan 15 16:20:16 EST 2010 i686 i686 i386 GNU/Linux (not a x86_64 version !!!!) * *cat /proc/meminfo* MemTotal: 746496 kB MemFree: 384332 kB Buffers:

Hello All, I was curious to know when would updates to VM Metrics - "*Last shutdown since*" be available in a new XAPI rpm. Any ETA for this ? -- With Regards, Hussain. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel