Just created the first completely new Xen VM with the Virtual Machine Manager after 5.0 became 5.1 and I notice these two differences:
- there's now virbr0 instead of xenbr0. Which means I have now xenbr0 and vitbr0 interfaces running. As virbr0 just the new name for xenbr0? If so, can I just change that name in the older configuration files, so that all use the same interface name?
- there is a (I think) new option for networking. There's virtual network and there's shared device. What's the latter? I don't remember this being available earlier. It doesn't list any devices for me. Does this refer to virtual devices of type eth0:5 etc. on the host?
help is no help for this, it's empty for this section.
Kai
Kai Schaetzl wrote:
Just created the first completely new Xen VM with the Virtual Machine Manager after 5.0 became 5.1 and I notice these two differences:
- there's now virbr0 instead of xenbr0. Which means I have now xenbr0 and
vitbr0 interfaces running. As virbr0 just the new name for xenbr0? If so, can I just change that name in the older configuration files, so that all use the same interface name?
I was confused initially by this too, but it turns out that virbr0 is the libvirt managed interface (dnsmasq and non-xen qemu) and libvirt managed clients use it by default. It should be pre-set with subnet 192.168.122.0/24.
I believe it is set to NAT with peth0.
xenbr0 is the Xen managed bridge and it comes with no default IP and it's characteristics are managed purely through the xend configuration.
- there is a (I think) new option for networking. There's virtual network
and there's shared device. What's the latter? I don't remember this being available earlier. It doesn't list any devices for me. Does this refer to virtual devices of type eth0:5 etc. on the host?
I believe the virtual network is the standard xen network interface config and the shared network is the virbr0 thing, but don't quote me on that, as you said documentation isn't plentiful here.
help is no help for this, it's empty for this section.
This page left intentionally blank?
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
Ross S. W. Walker wrote on Thu, 20 Mar 2008 11:54:30 -0400:
I was confused initially by this too, but it turns out that virbr0 is the libvirt managed interface (dnsmasq and non-xen qemu) and libvirt managed clients use it by default. It should be pre-set with subnet 192.168.122.0/24.
Yes, that is the subnet the VMs get IPs from. I wasn't aware that dnsmasq is on by default, but you are right. But there is no configuration for this subnet in the dnsmasq configuration. But there is configuration for this subnet in /etc/libvirt, so it seems to get the IP not from a dhcp call. (That would also explain why dhcp doesn't work over xenbr0 for me.)
xenbr0 is the Xen managed bridge and it comes with no default IP and it's characteristics are managed purely through the xend configuration.
and no way to get it to do dhcp?
I believe the virtual network is the standard xen network interface config and the shared network is the virbr0 thing, but don't quote me on that, as you said documentation isn't plentiful here.
Well, if I use "virtual network" I get virbr0. I cannot use the "shared network" thing as it doesn't show any devices, so I don't know how it might work :-(
help is no help for this, it's empty for this section.
This page left intentionally blank?
;-). I see that there is some information about libvirt on libvirt.org, but nothing about this. :-(
Kai