what cluster management software to use for linux?

Heartbeat is sort of deprecated and the new “industry standard” will be pacemaker and OpenAIS. They’re very different animals, so be careful to read their roles. Pacemaker is a ‘cluster resource manager’ — the part you asked about in your original question. It can use OpenAIS or Heartbeat as the network layer to manage a … Read more

LVM volume group shared between KVM/libvirt host and guests: is this a bad idea?

Well thought-out question! I’d go with Method 2, but that’s more of a personal preference. To me, the Method 2 Cons aren’t much of an issue. I don’t see the host OS outgrowing its 5-10GB partition, unless you start installing extra stuff on it, which you really shouldn’t. For the sake of simplicity and security, … Read more

Assign individual NIC to KVM guest

Easiest way to assign NICs to the guest is to leave them unconfigured in the host, and use macvtap passthrough mode for the guest NICs. Mind you, without additional, more complex settings, this will block VM live migration. Settings: <devices> … <interface type=”direct”> <source dev=’eth0′ mode=”private”/> </interface> </devices> Or you can go for a full … Read more

What is bridge_fd?

This is the forwarding delay for interfaces joining the bridge. It’s how long it’ll be before the interface will be able to do anything. . During this time the bridge will be discovering other bridges and checking that no loops are created. For a better description and the reason for it you need to read … Read more

Get list of DHCP clients with KVM+libvirt?

This feature was requested a long time ago. Now libvirt supports it by providing two new commands: domifaddr and net-dhcp-leases Usage: domifaddr <domain> [interface] [–full] [–source lease|agent] Example outputs: virsh # domifaddr f20 –source agent Name MAC address Protocol Address ——————————————————————————- lo 00:00:00:00:00:00 ipv4 127.0.0.1/8 – – ipv6 ::1/128 eth0 52:54:00:2e:45:ce ipv4 10.1.33.188/24 – – … Read more

Solidworks: activation license mode is not supported in this virtual environment (Qemu-KVM)

Most current hypervisors that run on Intel hardware use CPUID leaves 0x40000000 et seq. to pass information about the hypervisor from host to guest. KVM, Xen, VMware and Hyper-V all use this method. This is in addition to the hypervisor feature flag set in CPUID leaf 0x1, which indicates that the machine is a virtual … Read more