join ##fpga

anyone using bhyve here? I followed the tutorial and got windows installed as the guest. but now I can't get it to boot after restarting. where's the info on exit codes? log doesn't show anything specifically failing.

jnewt: Which tutorial did you follow? Also, have you taken a look at the FBSD wiki info at wiki.freebsd.org/bhyve/Windows ?

ek: Not that one, got it to boot though. it worked with a relative disk path for install on the disk, but apparently requires an absolute path to boot. fine, fixed. that tutorial is way more complicated that the route i took (boot with the iso loaded, the go to the menu and choose the boot file to get it to go). either way, i'm running, but have no network on the guest side. public switch is ok, tap0 created on boot, but no

adapter in the client (maybe this is diff than vbox), looking through docs now

you still need to bridge tap0 to your nic

vm-public under ifconfig shows groups: bridge vm-switch viid-4c918@

so you're using vm-bhyve? good

i don't recognize viid, and if the vm isn't running tap0 wouldn't be there anyhow

tap0 is there, and the vm is running

currently connected to it via vnc

i may have lost something with a reboot, something missing from rc.conf or boot...not sure what though

you have the vm_ lines in rc.conf ?

and the network still isn't working?

onlything i have is vm_enable and vm_dir in rc.conf

switch created via vm switch add public em0

sorry, #vm switch create public #vm switch add public em0

from the quick start on vm-bhyve. is that separate from the bridge? I though em0 and tap0 are connected through public, but i'm not sure if that's something separate from the "bridge" you mention

what config lines in the vm config tell the client there's an adapter? ihve network0_type and network0_switch, but i don't have any hardware info in there. does it need something else?

you can create tell vm-bhyve to create the bridge, or create it yourself and hand it over

if you want a host to boot automatically, you'll need a vm_enable="myvm myothervm" line also

have i told vm-bhyve to create the bridge by vm add public em0 or is that something different?

no, that sounds correct

but you're saying, no connectivity?

no nic in the guest os. there's an unknown device in windows device manager, but there are no drivers for it.

i've tried the e1000, i'm going to load the virtio iso and switch the nic to virtio and see if i can load the driver.

i used e1000 on windows 10 and windows server 2008 and it didn't need a driver

this is windows 10 and it's not happening. idk what could be different

try virtio-net

which i have used and also did not need a driver iirc

rtprio: I can't imagine that any misconfig of the routing on the host could cause adapter driver issues on the guest, idk what could be different.

rtprio, doesn't work. and neither does my cd rom config apparently, even though I used it to install windows initially.

well, i guess you could try to have windows locate the driver

this was a fresh win10 install? not some sort of conversion or something

and you could check that h/w ids make sense (device manager, device properties, details, hardware ids)

fresh install. from an official windows 10 iso

e1000 has been built in in windows since like win7

the weird thing is that the virtual-disk shows with vm-info but it's just not there in windows

and it's the same one i loaded the windows iso in to get this thing started

ok, perhaps paste the win10.conf you have in vm-bhyve

nothing there looks out of the ordinary

it says virtio-net, not e1000?

either should work fine

i thought he tried both

well, i had to install drivers on win10 for virtio-net, so I doubt it would work OOB

i don't remember doing that

but sure, install the drivers

You absolutely need to install the 3rd party virtio drivers for Windows. It's fairly painless, but it is required.

Hello, my freebsd just freezes on "Initialized 1915"

I have installed latest firmware following this guide docs.freebsd.org/en/books/handbook/x11/#x-configuration-intel

the firmware got initilized succesfully but it just freezes for some reason

GhostInTheShell, 1915 or i915?

whoops

ghodawalaaman_: are you on 14.2, is it i915 or i915kms? there is errata for drm-kmod.

specifically, drm-61-kmod freezes display output (the system is still up and you can reboot), if you use the packages built against 14.1. building from ports or using older drm-54-kmod work fine

i915's a shared memory video chip, correct?

i915 is the generic name for Intel graphics, it was the name for some CPU in the early 2000s

I think you're confusing the i910, which is a full motherboard chipset that included shared graphics, ethernet, and I think sound maybe.

OK, it's some chipset we've all forgotten. The name of the driver is irrelevant to the question asked.

has anyone here tried chimera linux? if so what did you like and dislike about it compared to freebsd?

I guess it's late for thanksgiving, but kudos to the releng team for 14.2! <3

mfisher: Thanksgiving is over, but no worries, you can still donate to FreeBSD Foundation