Re: [libvirt] openvz support in libvirt
Hi, Evgeniy interface type='bridge' source bridge='eth10'/ /interface interface type='ethernet' mac address='00:16:3e:34:21:9e'/ ip address=192.168.122.3 / /interface First, this should be interface type='bridge' mac address='00:16:3e:34:21:9e'/ source bridge='eth10'/ /interface interface type='ethernet' ip address=192.168.122.3 / /interface instead. mac address is optional field. mac is useless for ethernet type. For bridge mac is taken into account. Second. If I understood it right, the following description interface type='bridge' mac address='00:16:3e:34:21:9e'/ source bridge='eth10'/ /interface will result in the (approximataly) following: # vzctl --netiff_add eth10,00:16:3e:34:21:9e yes. 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 dev='eth10'/ /interface You are right. It is bug. -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] [PATCH] fix creating of openvz bridge device
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 dev='eth10'/ /interface You are right. It is bug. Well, here is the patch, that fixes that behaviour. P.S. Are someone going to implement interface type='bridge' ... source bridge=... ... /interface part of openvz driver? :) libvirt_openvz_change_bridge_name_to_target_dev.patch Description: Binary data -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] anyone implementing host device enumeration?
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 haven't been fully fleshed out, but there seems to be agreement that it will be a fairly direct mapping from (a subset of the) HAL info to the details that we need in the xml. Doubtless it will take a while to figure out exactly what subset suffices (and, for that matter, if everything needed is available via HAL ...), but I think the work is well-defined for some of the obvious details (discussed in the above thread) on which there's broad agreement. Is anyone working on such an implementation? Did you ever start any work on this project ? The oVirt guys really want this done asap, so if you've not started on it, or have a partial start to work from, I plan to make time to look at it next week Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] anyone implementing host device enumeration?
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
tested (except for a few odds and ends like some missing virsh fns).
The HAL-based driver is ~80% done. The Devkit-based driver isn't very
capable yet, mostly because of the limited Devkit functionality
available (also, there are some serious naming issues to discuss).
I haven't yet implemented virNodeDevice{Create,Destroy}, nor am I
registering for HAL/Devkit events. We don't need this functionality
right away, so I may wait 'til next week to implement them. The
underlying virNodeDevice infrastructure is ref-counted and accessed via
a conn-lock-protected virHashTable (like connections, domains, etc.),
so concurrent access shouldn't be a problem.
I'll post a patch (with some TODOs ...) on Sunday or Monday morning.
Dave
On Fri, 2008-09-26 at 14:15 +0100, Daniel P. Berrange wrote:
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 haven't been fully fleshed out, but there seems
to be agreement that it will be a fairly direct mapping from (a subset
of the) HAL info to the details that we need in the xml. Doubtless it
will take a while to figure out exactly what subset suffices (and, for
that matter, if everything needed is available via HAL ...), but I think
the work is well-defined for some of the obvious details (discussed in
the above thread) on which there's broad agreement.
Is anyone working on such an implementation?
Did you ever start any work on this project ? The oVirt guys really want
this done asap, so if you've not started on it, or have a partial start
to work from, I plan to make time to look at it next week
Regards,
Daniel
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Release of libvirt-0.4.6
- 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. 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 on non-HVM hardware for the foreseeable future, so KVM isn't an option for me. And F9 isn't an option for me since there is no dom0 support. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Release of libvirt-0.4.6
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 on non-HVM hardware for the foreseeable future, so KVM isn't an option for me. And F9 isn't an option for me since there is no dom0 support. Well it wasn't clear that the new release would really fixes things for the Xen users (which is as we all expect the community still using Fedora 8), is there anything in particular you were looking for in this specific release ? It was looking more risky than potentially useful to update there. Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ [EMAIL PROTECTED] | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Release of libvirt-0.4.6
-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 release a 0.4.6 F8 update for the benefit of us using F8 dom0. I'm stuck on non-HVM hardware for the foreseeable future, so KVM isn't an option for me. And F9 isn't an option for me since there is no dom0 support. Well it wasn't clear that the new release would really fixes things for the Xen users (which is as we all expect the community still using Fedora 8), is there anything in particular you were looking for in this specific release ? It was looking more risky than potentially useful to update there. - From your position; is there currently anything in the pipeline so Xen users soon can work without XenD (aka the big memoryleak)? Several solutions could implemented this, the patches that qemu does xen, or that libvirt talks to the hypervisor directly I'm really hopeing for that kind of change. Stefan -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREKAAYFAkjdS5sACgkQYH1+F2Rqwn3sEgCfUle50POAJ+9PeUhyOR7TL+Nj B8AAn1tU4nJzmmEVpk+qKqy25hqeA89Z =5Nqr -END PGP SIGNATURE- -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] Overriding vnetN with the target element in xml configuration not working
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 target dev='vnet7'/ . Unfortunately its not working and still it comes with vnet(current+1), here's my configuration for a qemu-kvm guest. interface type='bridge' source bridge='virbr0'/ target dev='vnet7'/ mac address='00:16:3e:6c:1f:9d'/ /interface I'm running on F9 x86_64, libvirt-0.4.4-2.fc9.x86_64 libvirt-python-0.4.4-2.fc9.x86_64 kvm-65-7.fc9.x86_64 qemu-0.9.1-6.fc9.x86_64 I haven't yet tested this with a RHEL box to know if it is version specific issue to open a bugzilla report, any input is appreciated. /* || Thanks, Ahmed Medhat || ultimatetux [at] gmail [dot] com || +2-012-4184768 || In a world without walls and fences, who needs Windows and Gates? */ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] Re: Overriding vnetN with the target element in xml configuration not working
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 code handling this specific element directive. I will wait for someone to do any input for a while then fire up a bug report. /* || Thanks, Ahmed Medhat || ultimatetux [at] gmail [dot] com || +2-012-4184768 || In a world without walls and fences, who needs Windows and Gates? */ On Sat, Sep 27, 2008 at 2:32 AM, Ahmed Medhat [EMAIL PROTECTED] wrote: 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 target dev='vnet7'/ . Unfortunately its not working and still it comes with vnet(current+1), here's my configuration for a qemu-kvm guest. interface type='bridge' source bridge='virbr0'/ target dev='vnet7'/ mac address='00:16:3e:6c:1f:9d'/ /interface I'm running on F9 x86_64, libvirt-0.4.4-2.fc9.x86_64 libvirt-python-0.4.4-2.fc9.x86_64 kvm-65-7.fc9.x86_64 qemu-0.9.1-6.fc9.x86_64 I haven't yet tested this with a RHEL box to know if it is version specific issue to open a bugzilla report, any input is appreciated. /* || Thanks, Ahmed Medhat || ultimatetux [at] gmail [dot] com || +2-012-4184768 || In a world without walls and fences, who needs Windows and Gates? */ -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
