Excerpts from Peter Grehan's message from Tue 22-Dec-15 13:09:
> > I pass trough a PCI device (USB controller) to a Linux guest. It works
> > properly. Then I halt the VM, make sure that bhyve destroyed it and run
> > Windows guest with the same PCI device passed-through.
> >
> > Windows device man
Excerpts from Anish's message from Mon 21-Dec-15 21:48:
> >ppt0@pci0:0:20:0: class=0x0c0330 card=0x21f317aa chip=0x1e318086
> Passthrough stub driver, part of vmm, controls the USB controller.
>
> Can you share output of /usr/sbin/devinfo from FreeBSD host, highlighting
> the usb mass/flash
>ppt0@pci0:0:20:0: class=0x0c0330 card=0x21f317aa chip=0x1e318086
Passthrough stub driver, part of vmm, controls the USB controller.
Can you share output of /usr/sbin/devinfo from FreeBSD host, highlighting
the usb mass/flash device in tree?
Regards,
Anish
On Mon, Dec 21, 2015 at 7:44 PM,
Excerpts from Trent Thompson's message from Mon 21-Dec-15 20:48:
> I've seen some success passing through devices that have their driver
> disabled in the FreeBSD kernel.
> See the USB 3.0 pass through that Eresia set up in iohyve.
> https://github.com/pr1ntf/iohyve/wiki/USB-3.0-PCI-Controller-Pass
Sergey,
I've seen some success passing through devices that have their driver
disabled in the FreeBSD kernel.
See the USB 3.0 pass through that Eresia set up in iohyve.
https://github.com/pr1ntf/iohyve/wiki/USB-3.0-PCI-Controller-Pass-through
When he disabled the kernel module in FreeBSD, he can
Excerpts from Peter Grehan's message from Tue 22-Dec-15 13:09:
> Hi Sergey,
>
> > This is pretty reproducible:
> >
> > I pass trough a PCI device (USB controller) to a Linux guest. It works
> > properly. Then I halt the VM, make sure that bhyve destroyed it and run
> > Windows guest with the same
Hi Sergey,
This is pretty reproducible:
I pass trough a PCI device (USB controller) to a Linux guest. It works
properly. Then I halt the VM, make sure that bhyve destroyed it and run
Windows guest with the same PCI device passed-through.
Windows device manager does show the device, however, e.
Excerpts from Sergey Manucharian's message from Sat 19-Dec-15 22:36:
> Excerpts from Peter Grehan's message from Sun 20-Dec-15 15:18:
> > >>> # bhyve -S ... -s 7,passthru,0/20/0 ...
> >
> > That's the bhyve command line (if that's the one you meant). You also
> > have to pass '-S' when invoking
Excerpts from Peter Grehan's message from Sun 20-Dec-15 15:18:
> >>> # bhyve -S ... -s 7,passthru,0/20/0 ...
> >>>
> >>Make sure you are also passing the '-S' option to grub-bhyve to force
> >> wiring of memory.
> >
> > Sure! I showed it in the command line above.
>
> That's the bhyve comman
Hi Sergey,
# bhyve -S ... -s 7,passthru,0/20/0 ...
Make sure you are also passing the '-S' option to grub-bhyve to force
wiring of memory.
Sure! I showed it in the command line above.
That's the bhyve command line (if that's the one you meant). You also
have to pass '-S' when invoking
Excerpts from Peter Grehan's message from Sun 20-Dec-15 15:02:
> >
> > # bhyve -S ... -s 7,passthru,0/20/0 ...
> >
> Make sure you are also passing the '-S' option to grub-bhyve to force
> wiring of memory.
Sure! I showed it in the command line above. Without that bhyve says:
"passthru require
Hi Sergey,
I have a working Linux guest in bhyve (Debian). Trying to pass through a
PCI device (USB controller) by adding a couple of options:
# bhyve -S ... -s 7,passthru,0/20/0 ...
That causes bhyve termination right away with error:
Unable to setup memory (17)
Exactly the same option with p
12 matches
Mail list logo
