> This gives me the idea to try a different driver version in Linux...
Tried the same driver version in Linux as in FreeBSD. The driver seems
to talk to the card now, but not sure whether I can call this progress:
[0.536988] PCI host bridge to bus :00
[0.537291] pci_bus :00:
On 2017-01-08 19:04, Peter Grehan wrote:
> There's some additional info at
> https://github.com/pr1ntf/iohyve/issues/228 -
>> grub> ls
>> (hd0) (cd0) (host)
>> grub> ls (hd0)
>> Device hd0: No known filesystem detected - Total size 16777216 sectors
> ... so it looks like grub isn't able to
Hey,
I want you to cast your mind back to the first time we met, take a look at
the it here http://olimpia.redwineenterprise-llc.com/0c0d
Warm regards, bunkertor
___
freebsd-virtualization@freebsd.org mailing list
> That's a different issue - it's unlikely, if not impossible, to
> configure bhyve with enough RAM to hit 37 bits worth where that would
> become a problem. No need to worry about that.
Well, there may be peripheral cards that have less bits... Anyway, I
see what you mean: memory manager
> > Removing another signature of detecting virtualization and increasing
> > compatibility would be negligible gain? Just asking...
> I don't think we are going to try and defeat the NVidia virtualization
> checks, and I can probably assure you that they would patch them as
> fast as we
> I hope you keep it up or at least figure out what the driver is doing.
Not in my plans at the moment. I prefer AMD GPUs over nV for OpenCL.
nVidia did (and does) serve me well for the last 10 year with their
excellent FreeBSD graphics driver: I had very few problems with it;
it's stable and
I hope you keep it up or at least figure out what the driver is doing. If
they haven't explicitly put in the license terms that virtualization is
forbidden for consumer cards, there's nothing wrong with hot patching the
driver ... assuming that they don't do things like Skype does where it
I had a bit more play with nVidia and FreeBSD guest.
First, `nvidia-smi -q` output diff [0] is interesting. It suggests that
the card may be in some incompletely initialized state: notice the
"Unknown Error" instead of real UUID, and the P8 power state. Could it
be that the driver doesn't
>
> > Hi,
> >
> > >> The problem appears to be in the area of assigning memory-mapped
> > >> I/O ranges by bhyve for the VGA card to a region outside of the
> > >> CPU's addressable space; i.e., bhyve does not check CPUID's
> > >> 0x8008 AL value (0x27 for my CPU, which is 39 bits -- while
>
> Hi,
>
> >> The problem appears to be in the area of assigning memory-mapped
> >> I/O ranges by bhyve for the VGA card to a region outside of the
> >> CPU's addressable space; i.e., bhyve does not check CPUID's
> >> 0x8008 AL value (0x27 for my CPU, which is 39 bits -- while
> >> bhyve
> IIRC the 367.44 version of the nvidia drivers do NOT support the
> Quadro 2000, you need to be using the 340.xx version of them. I
> ran into problems on native hardware.
I pulled the Quadro 2000 out of my workstation [and put the 600 in],
which is running fine with the latest driver from
> As far as I can tell it's the Hypervisor extension flags list. The lack
> of these extensions/optimisations might explain why your FreeBSD VM
> runs slow
The guest isn't slow, actually -- just the `nvidia-smi` tool was
much slower than normal to produce output. CPU speed in the guest
is less
Hi,
There doesn't seem to be support for CPUID 0x4001 in bhyve either.
What is it supposed to do?
As far as I can tell it's the Hypervisor extension flags list. The lack
of these extensions/optimisations might explain why your FreeBSD VM runs
slow but their presence also causes the
Is the VM checking documented in the driver notes somewhere? I have a Titan
X that I need to run CUDA on and would be much happier if I didn't have to
actually switch back and forth between FreeBSD and Ubuntu on my desktop.
Are we new fairly certain that this won't work? (Yet another reason to go
On 11/01/2017 02:01, sor...@cydem.org wrote:
Dom wote:
There doesn't seem to be support for CPUID 0x4001 in bhyve either.
What is it supposed to do?
As far as I can tell it's the Hypervisor extension flags list. The lack
of these extensions/optimisations might explain why your FreeBSD
IIRC the 367.44 version of the nvidia drivers do NOT support the
Quadro 2000, you need to be using the 340.xx version of them. I
ran into problems on native hardware.
Also before you attempt to get VGA passthrough working it is best
to make sure you can run native, have you tried running your
Hi,
The problem appears to be in the area of assigning memory-mapped
I/O ranges by bhyve for the VGA card to a region outside of the
CPU's addressable space; i.e., bhyve does not check CPUID's
0x8008 AL value (0x27 for my CPU, which is 39 bits -- while
bhyve assigns 0xd0 & above for
17 matches
Mail list logo
