Re: bhyve: can't to passthru bge(4) card

2014-01-21 Thread Sergey Matveychuk

21.01.2014 8:56, Neel Natu пишет:

I suspect that this is because the function number of the virtual PCI
device and the physical PCI device are different.

Could you try to use the following instead: -s 2:1,passthru,3/0/1


Thank you. It works.

I've tried 3:1,passthru,3/0/1 but it does not work. What rules for a 
slot number to choose?




Alternatively you could try assigning the physical PCI device 3/0/0:
-s 3:0,passthru,3/0/0



3/0/0 is a first network card. I'd like to leave it for the host system.
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

Re: bhyve: can't to passthru bge(4) card

2014-01-21 Thread Neel Natu
Hi Sergey,

 On Jan 21, 2014, at 1:27 AM, Sergey Matveychuk s...@semmy.ru wrote:
 
 21.01.2014 8:56, Neel Natu пишет:
 I suspect that this is because the function number of the virtual PCI
 device and the physical PCI device are different.
 
 Could you try to use the following instead: -s 2:1,passthru,3/0/1
 
 Thank you. It works.
 
 I've tried 3:1,passthru,3/0/1 but it does not work. What rules for a slot 
 number to choose?
 

It depends on the PCI function that you are passing to the guest.

For some, e.g. Intel e1000, it does not matter. You can have it appear on a 
completely different function number in the guest as compared to the host.

For others, e.g. bge, as you discovered, the function numbers in the guest and 
host have to match.

Also, PCI requires that for a multi-function device, function 0 must be 
present. So, it is not possible to assign a device to a function  0 without 
also having some device present at function 0.

Hope that helps.

Best
Neel

 
 Alternatively you could try assigning the physical PCI device 3/0/0:
 -s 3:0,passthru,3/0/0
 
 3/0/0 is a first network card. I'd like to leave it for the host system.
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org

bhyve: can't to passthru bge(4) card

2014-01-20 Thread Sergey Matveychuk

Hi.

I try to passthru bge:
% pciconf -vl
...
ppt0@pci0:3:0:1:class=0x02 card=0x169d103c chip=0x165714e4 
rev=0x01 hdr=0x00

vendor = 'Broadcom Corporation'
device = 'NetXtreme BCM5719 Gigabit Ethernet PCIe'
class  = network
subclass   = ethernet
...
% cat /boot/loader.conf
vmm_load=yes
pptdevs=3/0/1

% bhyve -c ${VM_CPUNUM} -m ${VM_MEMSIZE} -AI -HP -g0 \
-s 0:0,hostbridge \
-s 3:0,passthru,3/0/1 \
-s 2:0,virtio-blk,${VM_DISK} \
-S 31,uart,${VM_CONSOLE} \
${VM_NAME}

And I got this on boot:

bge0: Broadcom unknown BCM5719, ASIC rev. 0x5719001 mem 
0xc001-0xc001,0xc002-0xc002,0xc003-0xc003 irq 36 
at device 3.0 on pci0

bge0: APE FW version: NCSI v1.0.60.0
bge0: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E
bge0: Try again
bge0: Try again
bge0: Try again
bge0: Try again
bge0: attaching PHYs failed
device_attach: bge0 attach returned 6

I used this as an instruction: https://wiki.freebsd.org/bhyve/pci_passthru
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org


Fwd: bhyve: can't to passthru bge(4) card

2014-01-20 Thread Aryeh Friedman
-- Forwarded message --
From: Aryeh Friedman aryeh.fried...@gmail.com
Date: Mon, Jan 20, 2014 at 3:01 PM
Subject: Re: bhyve: can't to passthru bge(4) card
To: Sergey Matveychuk s...@semmy.ru


A question if you make the NIC the bridge device in PetiteCloud (we will
have physical NIC support in the next few tertiary versions but for now
your stuck with something like the manual version above) does it work any
better I suspect you have the networking set up wrong before calling
bhyve


On Mon, Jan 20, 2014 at 2:43 PM, Sergey Matveychuk s...@semmy.ru wrote:

 Hi.

 I try to passthru bge:
 % pciconf -vl
 ...
 ppt0@pci0:3:0:1:class=0x02 card=0x169d103c chip=0x165714e4
 rev=0x01 hdr=0x00
 vendor = 'Broadcom Corporation'
 device = 'NetXtreme BCM5719 Gigabit Ethernet PCIe'
 class  = network
 subclass   = ethernet
 ...
 % cat /boot/loader.conf
 vmm_load=yes
 pptdevs=3/0/1

 % bhyve -c ${VM_CPUNUM} -m ${VM_MEMSIZE} -AI -HP -g0 \
 -s 0:0,hostbridge \
 -s 3:0,passthru,3/0/1 \
 -s 2:0,virtio-blk,${VM_DISK} \
 -S 31,uart,${VM_CONSOLE} \
 ${VM_NAME}

 And I got this on boot:

 bge0: Broadcom unknown BCM5719, ASIC rev. 0x5719001 mem
 0xc001-0xc001,0xc002-0xc002,0xc003-0xc003 irq 36
 at device 3.0 on pci0
 bge0: APE FW version: NCSI v1.0.60.0
 bge0: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E
 bge0: Try again
 bge0: Try again
 bge0: Try again
 bge0: Try again
 bge0: attaching PHYs failed
 device_attach: bge0 attach returned 6

 I used this as an instruction: https://wiki.freebsd.org/bhyve/pci_passthru
 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to freebsd-virtualization-
 unsubscr...@freebsd.org




-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org



-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org


Re: bhyve: can't to passthru bge(4) card

2014-01-20 Thread Neel Natu
Hi Sergey,

On Mon, Jan 20, 2014 at 11:43 AM, Sergey Matveychuk s...@semmy.ru wrote:
 Hi.

 I try to passthru bge:
 % pciconf -vl
 ...
 ppt0@pci0:3:0:1:class=0x02 card=0x169d103c chip=0x165714e4
 rev=0x01 hdr=0x00
 vendor = 'Broadcom Corporation'
 device = 'NetXtreme BCM5719 Gigabit Ethernet PCIe'
 class  = network
 subclass   = ethernet
 ...
 % cat /boot/loader.conf
 vmm_load=yes
 pptdevs=3/0/1

 % bhyve -c ${VM_CPUNUM} -m ${VM_MEMSIZE} -AI -HP -g0 \
 -s 0:0,hostbridge \
 -s 3:0,passthru,3/0/1 \
 -s 2:0,virtio-blk,${VM_DISK} \
 -S 31,uart,${VM_CONSOLE} \
 ${VM_NAME}


I suspect that this is because the function number of the virtual PCI
device and the physical PCI device are different.

Could you try to use the following instead: -s 2:1,passthru,3/0/1

Alternatively you could try assigning the physical PCI device 3/0/0:
-s 3:0,passthru,3/0/0

best
Neel

 And I got this on boot:

 bge0: Broadcom unknown BCM5719, ASIC rev. 0x5719001 mem
 0xc001-0xc001,0xc002-0xc002,0xc003-0xc003 irq 36 at
 device 3.0 on pci0
 bge0: APE FW version: NCSI v1.0.60.0
 bge0: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E
 bge0: Try again
 bge0: Try again
 bge0: Try again
 bge0: Try again
 bge0: attaching PHYs failed
 device_attach: bge0 attach returned 6

 I used this as an instruction: https://wiki.freebsd.org/bhyve/pci_passthru
 ___
 freebsd-virtualization@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
 To unsubscribe, send any mail to
 freebsd-virtualization-unsubscr...@freebsd.org
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
freebsd-virtualization-unsubscr...@freebsd.org