Can you advise me a network traffic logger for Windows 2008 R2? It expected to be executed as service and gather simple data "source ip/port, dest ip/port, packets size". I have tried to use ETW Tracing with Winsock AFD provider, but it produces enormous size of data, dropping a lot of packets and its hard to analyze resulting ETL log files.
I have a Windows 2008 R2 Standard host system with the Hyper-V VM hosted (Win 2008 R2 too). Host system has public IP (10.20.30.40 for example) bounded to Hyper-V external virtual network, which is connected to physical network controller. Also I have failover subnet 20.30.40.50/29. Some IPs from this subnet are bound to virtual network controller and works fine. But when I bound some other IPs to VM's NIC - it is not visible nor from outside and hasn't access to Internet. But it is visible from host and can ping host too. Is there any way to bound some other IPs to VM's NIC, so it can be accessible outside? Thanks a lot.
When I have played with KVM using libvirtd/virsh, I disabled section in libvirt's xml configs for VMs an this gives me CPU usage from 7-8% in idle mode per VM to 1-2% for windows guests. This was a great advantage. But how to apply such trick when using Ganeti?
I'm going to create a simple virtual hosts infrastructure using QEMU+KVM. It is expected to be very simple, without clouds or any other cool things. Right now the only requirement is the fault-tolerance for data (hosts' disk images online backup). Live migration welcomed, but is not obligatory. What way do you suggest? Right now I'm thinking about DRBD.
I have a task to store QEMU images in a database and thinking towards developing of the custom block device. Is this a good idea? Where is it better to start from?