broken image after installworld/installkernel

2014-01-12 Thread Sergey Matveychuk

Hi.

My VM image has broken twice after I did installworld/installkernel 
inside VM.


First time I installed FreeBSD-10 from this ISO-image: 
ftp://ftp.ru.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/10.0/FreeBSD-10.0-RC4-amd64-disc1.iso


It worked well, but after I did 'svn co' buildworld/buildkernel 
installworld/installkernel kernel even did not boot.


Second time I install FreeBSD-10 from the same ISO and after the same 
action I have:


Copyright (c) 1992-2014 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.0-PRERELEASE #0 r260554: Sun Jan 12 21:54:44 MSK 2014
root@avim-new:/usr/obj/usr/src/sys/GENERIC amd64
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
CPU: Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz (2294.33-MHz K8-class CPU)
  Origin = GenuineIntel  Id = 0x206d7  Family = 0x6  Model = 0x2d 
Stepping = 7


Features=0x8f83ab7fFPU,VME,DE,PSE,TSC,MSR,PAE,CX8,APIC,SEP,PGE,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,SS,PBE

Features2=0x82be6257SSE3,PCLMULQDQ,DTES64,DS_CPL,SMX,SSSE3,CX16,xTPR,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,AESNI,HV
  AMD Features=0x24100800SYSCALL,NX,Page1GB,LM
  AMD Features2=0x1LAHF
  TSC: P-state invariant
real memory  = 1073741824 (1024 MB)
avail memory = 1012215808 (965 MB)
Event timer LAPIC quality 400
ACPI APIC Table: BHYVE  BVMADT  
panic: AP #1 (PHY# 1) failed!
cpuid = 0
KDB: stack backtrace:
#0 0x808ed7a0 at kdb_backtrace+0x60
#1 0x808b5175 at panic+0x155
#2 0x80c854f5 at cpu_mp_start+0x625
#3 0x808fa85d at mp_start+0x3d
#4 0x80866528 at mi_startup+0x118
#5 0x802d4cac at btext+0x2c
Uptime: 1s

Any suggestions?
___
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


bhyve: reboot stops vm

2014-01-20 Thread Sergey Matveychuk

Hi.

Is it expected behaviour?

sem@vm0[17]% sudo reboot
Jan 21 07:27:51 vm0 reboot: rebooted by sem
Jan 21 07:27:51 vm0 syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...2 0 done
All buffers synced.
Uptime: 1m17s
Rebooting...
cpu_reset: Stopping other CPUs
root@bhyve[36]#
___
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 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

Can't boot with FreeBSD-11.0-STABLE-amd64.raw

2017-02-07 Thread Sergey Matveychuk

Hi.

I'm using FreeBSD 10.0 as a host system.

% fetch 
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/11.0-STABLE/amd64/Latest/FreeBSD-11.0-STABLE-amd64.raw.xz

...
% unxz FreeBSD-11.0-STABLE-amd64.raw.xz
% sudo sh /usr/share/examples/bhyve/vmrun.sh -d 
FreeBSD-11.0-STABLE-amd64.raw vm0

Launching virtual machine "vm0" ...
Consoles: userboot

FreeBSD/amd64 User boot, Revision 1.1
(root@bhyve, Tue Jan 21 04:32:50 MSK 2014)
\
can't load 'kernel'

Type '?' for a list of commands, 'help' for more detailed help.
OK

What's wrong?

Thanks.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: bhyve passthrough problem after updated host to 10.3

2017-02-25 Thread Sergey Matveychuk

25.02.2017 6:42, Sergey Matveychuk пишет:

Hi.

After updating my host from 10.0-RELEASE to 10.3-RELEASE-p11 I've got
problem with my network card passthrought:



I've upgraded both host and guest to 11.0 but the problem still there.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

bhyve passthrough problem after updated host to 10.3

2017-02-24 Thread Sergey Matveychuk

Hi.

After updating my host from 10.0-RELEASE to 10.3-RELEASE-p11 I've got 
problem with my network card passthrought:


pci0:0:3:0: failed to read VPD data.
bge0:  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

pciconf on the host system:
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

I run my VM this call:
/bin/sh /usr/share/examples/bhyve/vmrun.sh -c ${VM_CPUNUM} -m 
${VM_MEMSIZE} -p 3/0/1 -d ${VM_DISK} ${VM_NAME}


How to fix it, please?
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


getty[...]: login_tty /dev/console: Inappropriate ioctl for device

2017-02-25 Thread Sergey Matveychuk

Hi.

I see many subj messages after updating gost from 10.0 to 10.3 and 11.0. 
It does not make me big problem except non-convinient work in console 
but I wonder to know what is it?


I see in google I'm not first with these messaages. But no answers found.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: bhyve passthrough problem after updated host to 10.3

2017-02-26 Thread Sergey Matveychuk

25.02.2017 6:42, Sergey Matveychuk пишет:

Hi.

After updating my host from 10.0-RELEASE to 10.3-RELEASE-p11 I've got
problem with my network card passthrought:

pci0:0:3:0: failed to read VPD data.
bge0:  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

pciconf on the host system:
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


Oh, I found my message when I tried passthrough for a first time:
https://lists.freebsd.org/pipermail/freebsd-virtualization/2014-January/001973.html
For 3 year I forgot how I fixed it.

Now, after experiments I can say the card can work only on 2 slot and 
function=function on host.


Example:
-s 2:1,passthrough,3/0/1
-s 2:3,passthrough,3/0/3

It does not work on slot 3 and function 0 as vmrun.sh does. I have no 
idea why.

So, current vmrun.sh is not an option for me.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Re: bhyve passthrough problem after updated host to 10.3

2017-02-26 Thread Sergey Matveychuk

27.02.2017 3:09, Peter Grehan пишет:

Hi Sergey,


Now, after experiments I can say the card can work only on 2 slot and
function=function on host.

Example:
-s 2:1,passthrough,3/0/1


It's even worse I thought.
The network card work only if spare slot with a disk device (may be any
device, I did not try).
So, it works:
-s 2:1,passthru,3/0/1 -s 2:0,virtio-blk,mydisk

and it does not work:
-s 2:1,passthru,3/0/1 -s 3:0,virtio-blk,mydisk


 Guests in general won't probe non-zero functions if function 0 is not
present. Putting something at function 0 allows the device probe to be
extended to the non-zero functions you have configured.


Bingo! Thank you for explain it.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"