02:37:35 join ##fpga 03:39:26 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. 03:53:02 jnewt: Which tutorial did you follow? Also, have you taken a look at the FBSD wiki info at https://wiki.freebsd.org/bhyve/Windows ? 03:57:28 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 03:57:28 adapter in the client (maybe this is diff than vbox), looking through docs now 03:58:01 you still need to bridge tap0 to your nic 03:59:19 vm-public under ifconfig shows groups: bridge vm-switch viid-4c918@ 03:59:53 so you're using vm-bhyve? good 04:00:11 i don't recognize viid, and if the vm isn't running tap0 wouldn't be there anyhow 04:00:33 tap0 is there, and the vm is running 04:00:46 currently connected to it via vnc 04:02:27 i may have lost something with a reboot, something missing from rc.conf or boot...not sure what though 04:03:11 you have the vm_ lines in rc.conf ? 04:03:40 and the network still isn't working? 04:04:15 onlything i have is vm_enable and vm_dir in rc.conf 04:04:41 switch created via vm switch add public em0 04:05:21 sorry, #vm switch create public #vm switch add public em0 04:06:25 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 04:12:55 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? 04:34:43 you can create tell vm-bhyve to create the bridge, or create it yourself and hand it over 04:35:07 if you want a host to boot automatically, you'll need a vm_enable="myvm myothervm" line also 04:35:53 have i told vm-bhyve to create the bridge by vm add public em0 or is that something different? 04:36:44 no, that sounds correct 04:38:34 but you're saying, no connectivity? 04:39:45 no nic in the guest os. there's an unknown device in windows device manager, but there are no drivers for it. 04:40:20 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. 04:41:21 i used e1000 on windows 10 and windows server 2008 and it didn't need a driver 04:41:53 this is windows 10 and it's not happening. idk what could be different 04:42:21 try virtio-net 04:42:31 which i have used and also did not need a driver iirc 04:45:57 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. 04:56:21 rtprio, doesn't work. and neither does my cd rom config apparently, even though I used it to install windows initially. 05:03:20 well, i guess you could try to have windows locate the driver 05:04:19 this was a fresh win10 install? not some sort of conversion or something 05:04:47 and you could check that h/w ids make sense (device manager, device properties, details, hardware ids) 05:04:49 fresh install. from an official windows 10 iso 05:05:09 e1000 has been built in in windows since like win7 05:05:39 the weird thing is that the virtual-disk shows with vm-info but it's just not there in windows 05:06:01 and it's the same one i loaded the windows iso in to get this thing started 05:06:05 ok, perhaps paste the win10.conf you have in vm-bhyve 05:10:01 https://pastebin.com/BPSYpzqy 05:10:51 nothing there looks out of the ordinary 05:19:08 it says virtio-net, not e1000? 05:23:16 either should work fine 05:23:27 i thought he tried both 05:29:43 well, i had to install drivers on win10 for virtio-net, so I doubt it would work OOB 05:30:21 i don't remember doing that 05:30:26 but sure, install the drivers 06:19:12 You absolutely need to install the 3rd party virtio drivers for Windows. It's fairly painless, but it is required. 11:20:04 Hello, my freebsd just freezes on "Initialized 1915" 11:20:29 I have installed latest firmware following this guide https://docs.freebsd.org/en/books/handbook/x11/#x-configuration-intel 11:21:06 the firmware got initilized succesfully but it just freezes for some reason 18:51:12 GhostInTheShell, 1915 or i915? 18:53:54 whoops 18:56:51 ghodawalaaman_: are you on 14.2, is it i915 or i915kms? there is errata for drm-kmod. 18:58:18 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 18:58:25 i915's a shared memory video chip, correct? 19:03:03 i915 is the generic name for Intel graphics, it was the name for some CPU in the early 2000s 19:23:42 I think you're confusing the i910, which is a full motherboard chipset that included shared graphics, ethernet, and I think sound maybe. 19:29:13 OK, it's some chipset we've all forgotten. The name of the driver is irrelevant to the question asked. 20:21:01 has anyone here tried chimera linux? if so what did you like and dislike about it compared to freebsd? 21:44:51 I guess it's late for thanksgiving, but kudos to the releng team for 14.2! <3 22:05:40 mfisher: Thanksgiving is over, but no worries, you can still donate to FreeBSD Foundation