i test the following simple filter
ccbd255f-4be5-4f0f-8835-770ea40cb2c9
but i get strange results (look at the attached output of iptables-save)
for me it looks like the direction='out' filters are attached to every
chain for this domain. additional there are wrong conntrack, stat
On Mi, 2014-02-19 at 09:26 -0700, Eric Blake wrote:
> Libvirt shouldn't have any problems following a symlink, unless the
> symlink resolves to a path that doesn't have proper permissions. Can
> you paste actual terminal transcripts proving that you can manually
> execute /usr/sbin/dnsmasq --vers
We're getting the following error with one or two ESX VMs using libvirt;
I'm only trying to read the domain config here, not make changes:
libvir: error : internal error Invalid or not yet handled value 'Floppy
drive 1' for VMX entry 'floppy0.fileName'
Is there a way I can tell it to ignore
Cole Robinson wrote:
> On 02/18/2014 10:45 PM, Jim Fehlig wrote:
>
>> Cole Robinson wrote:
>>
>>> On 02/18/2014 05:12 AM, Kim Larry wrote:
>>>
>>>
The thing I found today is that if libvirt uses xend driver, shutdown
events
are delivered, but if libvirt uses libxl
On 02/19/2014 08:47 AM, h0rst wrote:
>
2014-02-19 14:11:58.636+: 7075: error : virCommandWait:2376 : internal
error: Child process (LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOME=/root USER=root LOGNAME=root /usr/sbin/dnsmasq --version)
On 02/18/2014 10:45 PM, Jim Fehlig wrote:
> Cole Robinson wrote:
>> On 02/18/2014 05:12 AM, Kim Larry wrote:
>>
>>> The thing I found today is that if libvirt uses xend driver, shutdown events
>>> are delivered, but if libvirt uses libxl drvier, doesn't show up anything.
>>> It
>>> seems there
On Di, 2014-02-18 at 16:06 -0700, Eric Blake wrote:
> There should be no problem upgrading to a newer libvirt. We take great
> pains to ensure that a newer version of libvirt can be reloaded and
> gracefully understand the XML recorded by older versions, with no loss
> to running VMs. While ther
On 02/19/2014 10:01 AM, Niccolo Rigacci wrote:
> On Tue, Feb 18, 2014 at 09:49:06AM -0500, Cole Robinson wrote:
>>
>> What libvirt and qemu version are you using?
>
> I'm on a Debian 7.4 Wheezy (Stable):
>
> libvirt: 0.9.12.3-1
> qemu:1.1.2+dfsg-6a
>
> It seems that Debian has more recent ve
On Tue, Feb 18, 2014 at 09:49:06AM -0500, Cole Robinson wrote:
>
> What libvirt and qemu version are you using?
I'm on a Debian 7.4 Wheezy (Stable):
libvirt: 0.9.12.3-1
qemu:1.1.2+dfsg-6a
It seems that Debian has more recent versions, via the backports
repository. I will test them shortly.
On 12.02.2014 22:29, Franky Van Liedekerke wrote:
...
from git, it contains a lot of fixes (even some from me :-) ). Also
compile libvirtd from source (1.2.1 is very stable with a small
extra patch to talk to older qemu versions), reason for this is that
you can then have more than 20
On 02/19/2014 11:49 AM, arnaud gaboury wrote:
> Hi all,
>
> I can not build from source since a few days. Make left me with this error:
>
> Making install in tools/wireshark
> make[1]: Entering directory
> '/developement/aur/libvirt-git/src/libvirt/tools/wireshark'
> make[2]: Entering directory
>
Hi all,
I can not build from source since a few days. Make left me with this error:
Making install in tools/wireshark
make[1]: Entering directory
'/developement/aur/libvirt-git/src/libvirt/tools/wireshark'
make[2]: Entering directory
'/developement/aur/libvirt-git/src/libvirt/tools/wireshark'
mak
12 matches
Mail list logo
