[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] XML network model type stripped on define.

Daniel P. Berrange schrieb:
On Wed, Apr 15, 2009 at 12:00:34PM -0500, Adrian Garay wrote:
virsh --version returns 0.3.3

Yes, that's too old to support the NIC model setting.

You should be able to build the current libvirt release as an RPM for
RHEL-5 though.

I too use RHEL5 (5.1 at work and 5.3 at home).
I use KVM-84 built from sourceforge-source.
I built libvirt-0.6.2 with the patch for RHEL5/CentOS5 issued yesterday, but:

- migration (live) does not work
- migration (unlive) of a live domain works, but i have to suspend and resume the domain on the target host and i boots up fine - migration of a domain doesn't work if the domain is defined on the target host, but if it isn't define back-migration is not possible and the libvirt-daemon of the target-host hangs endless and must be rebooted. - i have configured bridged lan via /etc/sysconfig/network-scripts/ifcfg-eth[01] and /etc/sysconfig/network-scripts/ifcfg-sw[01] respectively, virsh start for a domain only works if the fd was invoked by a kvm on the commandline, otherwise i get "failed to add tap interface 'vnet%d' to bridge 'sw1' : invalid parameter" - need to get back to work tomorrow to get more specific - specifying <target dev='vnet7'/> for a domain doesn't work, if i define the domain this parameter is stripped and is vanished if i do a dumpxml of the specific domain afterwards - i thought i could evade the vnet%d with this, but if i try to start the domain and do a dumpxml afterwards a <target dev='vnet%d'/> is in the domain-specification

I think i should bundle this all into one new thread tomorrow when i am at work. This is a show-stopper for a productive scenario (okay, devel-releases should not go productive), i think i would use kvm with command-line-script until this works - it is a pitty the RH Enterprise Virtualization Hypervisor is not out yet and no release-path is announced - i can not wait since my new servers are installed next week or the following one and i didn't like to use xen anymore and would definitely not go for VMWare with its fat TCO-footprint.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]