Date: Mon, 18 Jun 2018 20:11:38 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 220453] [Hyper-V] need to update Mellanox ConnectX-3 VF driver to support Live Migration Message-ID: <bug-220453-27103-N1WQyoYfdD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220453-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-220453-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220453 --- Comment #10 from pete@twisted.org.uk --- Just a quick one, will try and add more detail tomorrow. I am using r334458 on STABLE-11 which was more or less the point where 11_2 branched I believe. I can't see anything in 11_2 after that point which is mlx4en or linuxkbi related. I can try doing an update tomorrow to the latest STABLE and see though. Will try and prepare a box just for testing this. The compile has the following in src.conf # All our Intel machines are post-Core2 CPUTYPE?=3Dcore2 # We are using exim and cups WITHOUT_SENDMAIL=3Dtrue WITHOUT_LPR=3Dtrue and the following in make.conf # Build ports in local WRKDIRPREFIX=3D/usr/local/port-build # Use new format packages WITH_PKGNG=3Dyes DISABLE_VULNERABILITIES=3Dyes # If we install cups it overwrites the base CUPS_OVERWRITE_BASE=3Dyes I switched the interface over to accelerated networking and rebooted, but it still came up using hn0. So I added a 'mlx4en_load=3D"YES"' to loader.conf = and rebooted - which gave me the panic. I tried many times, it panicked every t= ime. The only oddity in the setup is I am booting off ZFS instead of UFS. Drive = is GPT partitioned, and I have the following in loader.conf boot_serial=3D"YES" comconsole_speed=3D"115200" console=3D"comconsole" vfs.mountroot.timeout=3D"300" kern.geom.label.disk_ident.enable=3D"0" kern.geom.label.gptid.enable=3D"0" ahci_load=3D"YES" aesni_load=3D"YES" cryptodev_load=3D"YES" zfs_load=3D"YES" vfs.zfs.arc_max=3D"1G" vfs.zfs.prefetch_disable=3D"1" vfs.zfs.txg.timeout=3D"5" vfs.zfs.vdev.cache.size=3D"10M" vfs.zfs.vdev.cache.max=3D"10M" Don't know if any of that is significant at all - I assume adding the line = to loader.conf is the right thing to do, yes ? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220453-27103-N1WQyoYfdD>