In recently switching to e1000 for my KVM VMs because of instability in virtio, I've ran into a small issue I was hoping someone else had a quick fix for.
Unlike virtio which starts as up, the e1000 driver appears to have a small delay in bringing the interface eth0 within the VM up.
Messages include:
eth0: Link is not ready
eth0: Link becomes ready
This is enough of a delay to prevent nfs auto mounts in /etc/fstab from coming up. While I could just sleep and mount within a rc.local file, I'd rather a solution that isn't so slipjack.
I already tried setting the pass to 2 but no luck. Note: My VM eth0's are within a bridge to a vlan sub interface on the host (e.g. vmbr10->eth0.10).
Thanks,
David
Unlike virtio which starts as up, the e1000 driver appears to have a small delay in bringing the interface eth0 within the VM up.
Messages include:
eth0: Link is not ready
eth0: Link becomes ready
This is enough of a delay to prevent nfs auto mounts in /etc/fstab from coming up. While I could just sleep and mount within a rc.local file, I'd rather a solution that isn't so slipjack.
I already tried setting the pass to 2 but no luck. Note: My VM eth0's are within a bridge to a vlan sub interface on the host (e.g. vmbr10->eth0.10).
Thanks,
David
