Hi,
I am trying to pass an mPCIe device to a guest bhyve VM. I have the device
set to use the ppt driver:
# devctl set driver pci0:2:0:0 ppt
pciconf -lv gives me the following output:
ppt0@pci0:2:0:0: class=0x028000 card=0x197d103c chip=0x817910ec rev=0x01
hdr=0x00
vendor = 'Realtek Sem
On Wed, Sep 6, 2017 at 3:53 PM, Jason Tubnor wrote:
> On 6 September 2017 at 22:15, tech-lists wrote:
>
>>
>>
>> Have you encountered anything on openbsd in a bhyve that you've found
>> not to work?
>>
>>
> As Thomas mentioned, there is/was a bug with certain CPUs, but this was due
> to the stric
Hi Farhan,
bhyve: PCI device at 2/0/0 is not using the ppt(4) driver.
Just noticed this myself: looks like a regression :( I'll see if I can
work it out and get a fix in.
later,
Peter.
___
freebsd-virtualization@freebsd.org mailing list
https://l
> Hi Farhan,
> > bhyve: PCI device at 2/0/0 is not using the ppt(4) driver.
>
> Just noticed this myself: looks like a regression :( I'll see if I can
> work it out and get a fix in.
What is the state of bhyve in 10.4? Do we need to fire off some
quick tests
--
Rod Grimes
I would not mind sending you on-going feedback or debugging information if
it helps.
Could it be a chipset issue? This is a lower-end laptop. It can do
virtualization, but the passthrough issue seemed to fail. I was on FreeBSD
11.1.
--
Farhan Khan
PGP Fingerprint: 782F 342B 5B08 0D2F F4E8 82C3 FF
I would not mind sending you on-going feedback or debugging information > if it helps.> > Could it be a chipset issue? This is a lower-end
laptop. It can do > virtualization, but the passthrough issue seemed to
fail. I was on > FreeBSD 11.1.
It may be due to this (and also my issue which was on
Hi Rod,
Hi Farhan,
bhyve: PCI device at 2/0/0 is not using the ppt(4) driver.
Just noticed this myself: looks like a regression :( I'll see if I can
work it out and get a fix in.
What is the state of bhyve in 10.4? Do we need to fire off some
quick tests
Always worth some quick t
On 8 September 2017 at 00:28, Alan Somers wrote:
>
>
> Do you have a semiautomated way to move bhyve instances between
> different hosts? Without such a feature, we can't replace all of our
> ESXi machines.
>
We are not using bhyve for those workloads (yet). Our vsphere environment
still has l
