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
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. 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 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 -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] openvz support in libvirt
2008/9/19 Evgeniy Sokolov [EMAIL PROTECTED] Hello. To start with, I have the following questions: Does libvirt support the xml format for openvz driver described in the next thread? http://www.redhat.com/archives/libvir-list/2008-July/msg00312.html (I think, that it does not. But will it support it in future? :)) What libvirt functionality does openvz driver support? (Openvz does not mentioned in http://libvirt.org/hvsupport.html) Hi Anton, OpenVZ uses generic xml format. It is common for all libvirt drivers. one difference is filesystem: filesystem type=template source name=name of template / target dir=// /filesystem example: domain type='openvz' name210/name Does the 'name ' tag specify domain veid or veid is generated automatically? uuid08344fd6-17d6-711f-6ad8-08b85777a2a2/uuid vcpu13/vcpu memory131072/memory os typeexe/type /os devices filesystem type=template source name=centos-4-i386-minimal / target dir=// quota type=size max=1/ quota type=inodes max=20/ /filesystem 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 /devices /domain -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] openvz support in libvirt
2008/9/19 Evgeniy Sokolov [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Hello. To start with, I have the following questions: Does libvirt support the xml format for openvz driver described in the next thread? http://www.redhat.com/archives/libvir-list/2008-July/msg00312.html (I think, that it does not. But will it support it in future? :)) What libvirt functionality does openvz driver support? (Openvz does not mentioned in http://libvirt.org/hvsupport.html) Hi Anton, OpenVZ uses generic xml format. It is common for all libvirt drivers. one difference is filesystem: filesystem type=template source name=name of template / target dir=// /filesystem example: domain type='openvz' name210/name Does the 'name ' tag specify domain veid or veid is generated automatically? You need to specify veid. -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
[libvirt] openvz support in libvirt
Hello. To start with, I have the following questions: Does libvirt support the xml format for openvz driver described in the next thread? http://www.redhat.com/archives/libvir-list/2008-July/msg00312.html (I think, that it does not. But will it support it in future? :)) What libvirt functionality does openvz driver support? (Openvz does not mentioned in http://libvirt.org/hvsupport.html) Anton. -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] openvz support in libvirt
Hi, About libvirt functionality for openVZ. see the struct openvzDriver in libvirt/src/openvz_driver.c (around line 957) http://git.et.redhat.com/?p=libvirt.git;a=blob;f=src/openvz_driver.c Thanks Atsushi SAKAI Anton Protopopov [EMAIL PROTECTED] wrote: Hello. To start with, I have the following questions: Does libvirt support the xml format for openvz driver described in the next thread? http://www.redhat.com/archives/libvir-list/2008-July/msg00312.html (I think, that it does not. But will it support it in future? :)) What libvirt functionality does openvz driver support? (Openvz does not mentioned in http://libvirt.org/hvsupport.html) Anton. -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
