AW: AW: AW: AW: AW: Problem with virtio network boot

[Denny Bortfeldt]

Hello everyone,

I could fix the problem. And here's the solution if you also got the problem:

VirtIO driver is included in the initrd, but when the VM boot into dracut the 
"dhclient" command fails. This happens, because of bad checksums with special 
software.
Currently we use qemu/kvm on out virtualization host and create the vms with 
"virt-install" and parameter "--pxe" for netboot. 
During netboot our DHCP-Server (dnsmasq) give the client an IP and this 
dnsserver got a little bug which was fixed in isc-dhcp already (standard dhcp 
in fai-installation). So nearly everyone should not have the same problem.

There are some solutions to fix the bad checksums bug:
- use isc-dhcp
- use e1000 driver instead during installation
- use an iptables-rule on the virtualization host(!!)
-- iptables -A POSTROUTING -t mangle -p udp --dport 68 -j CHECKSUM 
--checksum-fill

Bug-Links:
- https://forge.univention.org/bugzilla/show_bug.cgi?id=33160 & 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717215

A special thanks to Thomas, who helped me a lot with nice hints!

Best regards,
Denny

Re: AW: AW: AW: AW: Problem with virtio network boot

[Thomas Lange]

> On Tue, 14 Jun 2016 16:23:41 +, Denny Bortfeldt 
>  said:

> Default timeout are 20 seconds, this is way enough. DHCPOFFERS will be 
send out but VM don't respect them.
> This problem only occur with Dracut and virtio network card.
You can test the nfsroot from http://fai-project.org/download/misc/.
This should work. I do not have any problems with virtio and dracut.

I'm using the fai-kvm command to start my virtual machines. This works
nicely. What are you using?

-- 
regards Thomas

AW: AW: AW: AW: Problem with virtio network boot

[Denny Bortfeldt]

Default timeout are 20 seconds, this is way enough. DHCPOFFERS will be send out 
but VM don't respect them.
This problem only occur with Dracut and virtio network card.

With FAI 3 everything worked fine.