00:58:26 hi, im trying to boot and imported win7 img in bhyve. it boots into uefi interactive shell. any ideas how to solve this ? 01:01:06 Was the Windows 7 installation already UEFI-ready? 01:06:23 michaeldexter: dont know.. its from a virtualbox vm 01:06:27 maybe not 01:06:46 virtualbox vdi* 01:07:14 is there an alternatie config from uefi that i could use in the vm.conf ? 01:14:07 michaeldexter: maybe its legacy 05:12:32 hernan: It would need to be converted to UEFI first. Reportedly this can be done with some versions of Windows 7. 09:02:23 this is a fascinating case of dunning kruegerism: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271403 09:02:25 Title: 271403 – System unusable at first boot after install of 13.2-RELEASE amd64 09:02:34 like, yeah, been there, done that 09:08:58 meena: Oh, it's Dennis 09:53:06 * RhodiumToad grumbles about the lack of a siginvertset 10:13:04 vkarlsen: who's Dennis? 11:44:15 grahamperrin: you maybe saw Mina here? 11:46:12 * RhodiumToad is not grahamperrin, but notes that Mina (meena) is often here but is currently marked afk 11:48:10 I set up a azure cloud native freebsd instance with 2 vcpus up and running. Trying to make a Orleans bootstrap script soon(tm). 11:48:37 RhodiumToad: a meena, I recall here. 11:50:25 for root on azure you can create a different user in azure console and then # sudo /bin/csh 11:51:10 password based ssh login works there have not tried ssh keys there. 12:02:55 I wonder if this was about cloud-init 12:21:04 meena: Dennis Clarke of Blastwave fame 12:22:46 * meena used to be an OpenCSW committer 13:07:48 what might cause zfs send dset@now | cat > /dev/null to only do about 100MB/sec ? 13:08:27 dd read/writes can do 600MB/sec, FTP/SCP transfers of files also net 500-700MB/sec 13:15:29 last 13:15:51 last1: what if you skip cat? 13:17:04 I don't think our cat is as optimised as GNU cat 13:38:41 even without cat, I get about the same speeds 13:38:48 zfs send dset@now | mbuffer -s 128k -m 1G | pv -rtab > /dev/null 13:38:52 110-120MB/sec 16:16:45 "gptzfsboot tries to find all ZFS pools that are composed of BIOS-visible hard disks or partitions on them." man GPTZFSBOOT(8) 16:17:13 does anyone know if a way to boot a ZFS pool form a non BIOS-visible disk? 16:20:00 <_xor> meena: Not sure if it's an issue on my end, but FreeBSD-clibs-dev had an issue installing due to not being able to rename some temp files (or dirs) in /usr/include/c++/v1. 16:21:00 <_xor> meena: Can't remember off the top of my head, but it looked like existing files in /usr/include/c++/v1 weren't being dealt with before installing the new ones. Though now that I think about, if it's using /usr/bin/install, then that should happened automatically. 16:23:06 Usecase: use USB to boot NVME on a motherboard that doesn't support booting from NVME. (I've done this on Linux, so I would assume freeBSD could also do this as well) 16:46:13 _xor: i usually blame whoever committed last 17:37:07 Any idea how to resolve this so that Arch Linux is satisfied: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=69 ? 17:37:09 Title: 69 – "Erase pencil mark!" does not leave enough clues 17:56:12 qtc`: depends what exactly you mean by "boot" 17:57:46 qtc`: on a non-UEFI system, neither boot nor loader can access anything that the bios can't access, so all of /boot would need to be on the USB. but from that point on, anything that the kernel can access is available 18:33:00 is 14.0 suppose to be stable ? if so - where is the download for it --- stable/14 branch --- 12 May 2023 -stable/14 branch created; release engineering continues on this branch 18:33:11 https://www.freebsd.org/releases/14.0R/schedule/ 18:33:13 Title: FreeBSD 14.0 Release Process | The FreeBSD Project 18:33:57 https://www.freebsd.org/where/ 18:33:58 Title: Get FreeBSD | The FreeBSD Project 18:34:15 https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/14.0/ 18:34:15 Title: Index of /snapshots/amd64/amd64/ISO-IMAGES/14.0/ 18:34:48 acu: No, the code freeze was delayed. The core team is still pushing things to that step first. 18:36:11 coreystephanphd, thanks - anyhow - once in stable, whatever it is built on that will end in 14 Release I assume 18:39:45 Yes. There will not be binary upgrades available until (at least) -ALPHA, otherwise -BETA or -RC. So for an ordinary end user not doing production testing etc., 13.2-RELEASE (which just came out a month or 2 ago) is the place to be. 19:11:04 if using synth, do i just use "make config" if i want to tweak a port's config options, or is there a way to do that in synth? i'm not seeing one in the docs. 19:12:37 * elgrande is anxious to see how azure likes -CURRENT (GitHub version) 19:52:32 RhodiumToad > anything that the kernel can access is available. 19:53:49 thats the method I used with Linux. but I don't know how to accomplish this with freeBSD 19:54:14 maybe I'm just looking at the wrong portion docs? 19:54:46 what you need to do is to split off /boot from the rest of the root filesystem, put it on a bootable USB, and put appropriate definitions into /boot/loader.conf (and in /etc/fstab to mount /boot) 19:55:04 I don't know if it's documented as such 19:55:37 is this a UEFI system or legacy boot? and does it support GPT? 19:57:05 No, right now I'm working on a MBR/BIOS system 19:57:29 But I plan to move one of the installs over toa GPT system when its setup/configured correctly 19:58:01 ok. so the USB needs to be partitioned for bootable MBR, and you need to install /boot/boot on it as bootcode 19:58:54 give it an "a" slice big enough to hold /boot with some spare space 20:00:21 then put vfs.root.mountfrom="zfs:zroot/ROOT/default" or whatever in the loader.conf on the usb 20:01:29 gpart bootcode -b /boot/pmbr -p /boot/boot -i 2 da0 20:01:35 look correct? 20:01:53 it's /boot/mbr for non-GPT 20:02:02 actually no 20:02:48 gpart bootcode -b /boot/mbr da0 and gpart bootcode -b /boot/boot da0s1 (or whatever the active partition is) 20:03:19 -p is only used for GPT where you have a freebsd-boot partition, which isn't what you're doing here 20:03:52 I think /boot/boot expects a BSD-style partition table, too 20:05:18 so gpart create -s MBR da0; gpart add -t freebsd da0; gpart create -s BSD da0s1; etc. 20:05:48 14 kernel boots fine waiting for buildworld if i may keep my iPhone such long. 20:06:48 but most important: azure uses tux as logo for a freebsd vm in the app. 20:11:35 qtc`: are you getting the idea or do I need to go into more detail? 20:12:47 I think I get the idea, will need to reformat the usb and copy data again before i know if i got it 20:47:05 <_xor> Is there a non-polling way to be notified when a jail stops/dies? Like is there a file descriptor or something created somewhere that I can select()? 20:50:51 <_xor> Also, what are prison_* functions? 20:51:06 <_xor> Oh, nevermind, just saw the comment. "Kernel support functions for jail()" 21:36:11 I'm definitely doing something wrong https://pad.bsd.to/p/usb-boot 21:36:13 Title: FreeBSD Etherpad 21:36:38 I'm getting "Boot error" 21:38:07 RhodiumToad> does what i'm doing look correct? 21:51:28 The "etherpad" -- which widget produces the raw text without any controls, formatting, etc? 21:54:53 "Print" produces the browser print dialog. 22:01:53 Etherpad is for group work on documents. Did you want the pastebin (https://bsd.to) instead? 22:01:54 Title: dpaste 22:03:31 qtc` posted on etherpad; so was trying to see if could get that in plainer text. V_PauAmma_V, thanks for the reminder about "bsd.to" 22:12:41 here is the pastebin https://bsd.to/HNpP 22:12:43 Title: dpaste/HNpP (Bash) 22:16:33 Does the order of "newfs" & "gpart bootcode" matter? Or, my question is would "newfs" not erase bootcode? 22:20:26 ahh.. I run bhyve guests with a stdio and just stuff them into the background with a tmux session. I accidentally killed the tmux window that a single bhyve guest was using. bhyve is still running in the background. Is there some way of re-attaching to what I'm assuming is now a dangling stdio handle? 22:20:41 I *could* just restart the bhyve in a fresh tmux window but.. ehh. 22:24:36 parv> Does the order of "newfs" & "gpart bootcode" matter? 22:25:22 I would think so, so when it didnt work I rebooted into the live installer and ran the gpart bootcode for da0 again 22:26:42 so it doesn't look like that is the issue 22:26:50 Ok 22:45:21 any good ios freebsd ssh client that can be recommended? 22:47:26 Don't know about "ios freebsd ssh client"; For iOS, ty mosh & La Terminal 22:48:04 I haven't used any much 22:48:57 ty, one of those works with screen off? 22:49:14 Can't say 22:49:32 trying la terminal when dropping out again 22:53:48 la terminal looks promising 23:17:39 woops, reptyr will instakill a bhyve session. restarting the bhyve guest it is then. 23:19:03 midnight: what? how? 23:22:57 meena: I was running bhyve using a stdio com1 in a tmux window. I wanted to kill that session, but not the whole server, so I c-b,: kill-window by accident. The bhyve guest was functioning fine in the background. I wanted to open a new shell in that tmux, then reptyr to recapture the stdio for that guest. I installed reptyr, then ran: reptyr [bhyve pid]. That failed with "Unable to attach to pid 61149: 23:23:03 Capabilities insufficient". I then observed that the bhyve process was gone, and the guest was not responding to network ping. I then completed the kill with bhyvectl --destroy, and restarted. It's possible I missed something obvious I guess. 23:25:10 if you can reproduce this, especially with another type of console attached to it, so you may be able to observe what's going on, it might very well be worth a bug report 23:25:54 it doesn't matter what reptyr is doing, bhyve should be more resilient than that 23:26:24 Doesn't reptyr do some process injection stuff with ptrace? 23:27:01 I don't care 23:27:14 00:25 it doesn't matter what reptyr is doing, bhyve should be more resilient than that 23:27:22 But, probably I agree with you. It's okay in my case, it was more a "ooh opportunity to try" 23:31:21 that's how i discover a lot of bugs 23:31:32 indeed :-D 23:33:21 "this is probably going to work out just fine!" followed by, "there's no reason why this shouldn't have worked out just fine! wtf?" 23:47:24 hah, heard that