Hi, Evgeniy
interface type='bridge'
source bridge='eth10'/
/interface
interface type='ethernet'
mac address='00:16:3e:34:21:9e'/
ip
This behaviour contradicts with description found in docs (in which
source tag specify interface in host, not in container). I think,
the previous bridge must be specified as
interface type='bridge'
mac address='00:16:3e:34:21:9e'/
- source bridge='eth10'/
+ target
On Thu, Aug 21, 2008 at 03:18:57PM -0400, David Lively wrote:
Hi -
I'm about to start working on host device enumeration, along the
(HAL-ish) lines of what was discussed back in April:
https://www.redhat.com/archives/libvir-list/2008-April/msg5.html
I know the xml details
Hi Daniel -
I have an implementation underway right now, with both HAL- and
Devkit-based drivers. We have some folks who need this *next week*,
so I'm trying to get the most functionality finished up today and this
weekend.
The generic (HAL/Devkit-agnostic) framework is essentially done and
- Daniel Veillard [EMAIL PROTECTED] wrote:
As promised after we discovered a couple of serious bugs in 0.4.5,
a new release was in order, so I pushed 0.4.6 yesterday evening,
Thanks for your hard work.
I see that 0.4.5 for F9 just made it through bodhi, but there is no F8 build in
bodhi.
On Fri, Sep 26, 2008 at 09:17:43AM -0700, Dale Bewley wrote:
I see that 0.4.5 for F9 just made it through bodhi, but there is no F8 build
in bodhi.
https://admin.fedoraproject.org/updates/F9/FEDORA-2008-7768
Please release a 0.4.6 F8 update for the benefit of us using F8 dom0. I'm
stuck
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Daniel Veillard schreef:
On Fri, Sep 26, 2008 at 09:17:43AM -0700, Dale Bewley wrote:
I see that 0.4.5 for F9 just made it through bodhi, but there is no F8 build
in bodhi.
https://admin.fedoraproject.org/updates/F9/FEDORA-2008-7768
Please
Hello,
I've been trying to dedicated a vnet interface to each virtual machine
in order to be able to monitor their traffic, looking at
http://libvirt.org/formatdomain.html#elementsNICSBridge it says that a
virtual machine could have a specific vnetN specified in the xml
element target, like
Ok, so its kinda creepy now, it works with change the device name to
anything but vnetN.
This is what did work with me..
interface type='bridge'
source bridge='virbr0'/
target dev=vn01/
mac address='00:16:3e:6c:1f:9d'/
/interface
This must be something with libvirtd
