https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227880
--- Comment #14 from Conrad Meyer ---
(In reply to Rodney W. Grimes from comment #13)
Yeah, it's a nested hypervisor situation. That was covered in comment #5.
Does not change the fact that vmm.ko load failure results
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227880
Rodney W. Grimes changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227880
--- Comment #12 from Mateusz Piotrowski <0...@freebsd.org> ---
(In reply to Rodney W. Grimes from comment #10)
Fragments of /var/log/messages from the FreeBSD guest:
CPU: AMD Opteron 63xx class CPU (4027.12-MHz K8-class CPU)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227880
--- Comment #11 from Peter Grehan ---
This is a bit of a lose-lose situation :( ppt was a separate kld at one point
but caused even more problems with it not being loaded, having to deal with
separate loads/unloads etc,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227880
--- Comment #10 from Rodney W. Grimes ---
(In reply to Conrad Meyer from comment #8)
Thank you for that insight on kernel modules, I was not aware that we could
have multiple modules in a single file. That helps
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227880
--- Comment #9 from Mateusz Piotrowski <0...@freebsd.org> ---
(In reply to Conrad Meyer from comment #8)
On the system that demonstrates the reported bug:
# kldunload vmm
# kldload ppt
kldload: can't load ppt: No such file or
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227880
--- Comment #8 from Conrad Meyer ---
(In reply to Conrad Meyer from comment #6)
To clarify, there is a distinction between a *module* which is something
declared by (sometimes DRIVER_MODULE ->) DECLARE_MODULE ->
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227880
--- Comment #7 from Conrad Meyer ---
The usual thing to do here is to split vmm.ko into three separate .ko's. I
don't know the history here of why are one file. Possibly just convenience.
If they share significant
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227880
--- Comment #6 from Conrad Meyer ---
I can't explain the fdc driver bug -- that seems unrelated -- but this is the
expected outcome of the vmm.ko *file* containing several modules: vmm, ppt, and
ivhd, and only one of them
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227880
--- Comment #5 from Mateusz Piotrowski <0...@freebsd.org> ---
Machine 1
=
* Laptop (Yoga 3 14)
* FreeBSD 12.0-CURRENT r332889
* Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz
Everything works as expected.
Machine 2
=
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227880
Mateusz Piotrowski <0...@freebsd.org> changed:
What|Removed |Added
Summary|`kldstat -m` does not work |`kldstat
On 2 May 2018 at 19:58, Michael Reifenberger wrote:
>
> Hi,
> Im running a Centos7 bhyve VM under FreeBSD-11 (latest stable).
> The VM boots using UEFI: uefi-edk2-bhyve-0.1
> Centos was installed and ist booting fine: CentOS Linux release 7.3.1611
> (Core)
>
>
What Kernel
Hi,
Im running a Centos7 bhyve VM under FreeBSD-11 (latest stable).
The VM boots using UEFI: uefi-edk2-bhyve-0.1
Centos was installed and ist booting fine: CentOS Linux release
7.3.1611 (Core)
/boot and /boot/efi are on a extra zvol:
...
/dev/vda2 1014M 193M 822M 20%
On 2018-05-01T18:06:38 -0700
Peter Grehan wrote:
> >* rosemary_disk0.lzma (the LZMA compressed zvol)
>
> I was able to boot this image on a 12-current Ryzen system. Debian 9.4
> also installed fine with the netinstall ISO and could boot.
Bizarrely, I am also able
14 matches
Mail list logo