search for: unexceptional

Hi, I'm not able to create lxc domains anymore with libvirt 1.2.0-1. The current arch linux package is affected by this bug: https://bugs.archlinux.org/task/38007). vm.xml: <domain type="lxc"> <name>test</name> <memory unit="GiB">2</memory> <os> <type>exe</type> <init>/sbin/init</init> </os>

On 12/11/2013 11:56 AM, Florian Klink wrote: > Hi, > > I'm not able to create lxc domains anymore with libvirt 1.2.0-1. > > > > # virsh create vm.xml What does 'virsh uri' output? My guess is that your older version of libvirt was built with JUST lxc support, and that your new version has BOTH lxc and qemu support. By not specifying an explicit connection,

...re's a race hiding. I always thought all TableGen commands were run before the main sources got compiled, but at 32 threads perhaps that doesn't matter so much. Has this just started since AArch64 was added, or have you only recently started building at -j32? As far as I can see AArch64 is unexceptional in its dependencies, except for being lexicographically the first target. I'd be interested in your results if AArch64 was disabled. There's clearly some issue though. I've only got 4 cores (+ 4 faked) here so I'm not optimistic about reproducing any races you're seeing, though...

Hi all, After many complaints (including car manufacturers saying the american prompts are unexceptable, EEEK) I started on a quest for real "English" asterisk prompts. The only one I have found is here >> http://www.g7ltt.com/VoIP/vmfiles.html <http://www.g7ltt.com/VoIP/vmfiles.html> And no nothing else on the WIKI looked helpful (e.g. only American voice actors etc)

Hi, I'm getting a "random" build failure related to AArch64 when building with cmake. The build is running with -j32 so it seems that there is some dependency issue that causes the build to fail when things build in a certain order. Is anyone else seeing this problem? paul 3008 make[2]: *** No rule to make target `lib/Target/AArch64/AArch64GenDAGISel.inc', needed by

...I always thought all TableGen commands >were run before the main sources got compiled, but at 32 threads >perhaps that doesn't matter so much. > >Has this just started since AArch64 was added, or have you only >recently started building at -j32? As far as I can see AArch64 is >unexceptional in its dependencies, except for being lexicographically >the first target. I'd be interested in your results if AArch64 was >disabled. I can't say for sure if this is a new problem but we've been building on this machine for a few weeks now. I commented out AArch64 from LLVM_ALL...