Re: bhyve in -current 4/14/13 can no longer support FreeBSD stable install
Hi Alfred, If you do this repeatedly, it may be possible to see some patterns e.g. counters incrementing, %RIP values being the same etc. Hmm, I keep seem to be getting this: /usr/home/alfred # bhyvectl --get-all --cpu=0 --vm=freebsd-stable lowmem 0x/536870912 highmem 0x0001/0 errno = 16 /usr/home/alfred # bhyvectl --get-all --cpu=1 --vm=freebsd-stable lowmem 0x/536870912 highmem 0x0001/0 errno = 16 Yeh, this is a problem :( Currently, the stats gathering does a trylock on the VM to avoid having the VM be perturbed by the bhyvectl process. We probably need to put something in there so it can eventually get the lock, and hence the stats, when the VM is busy rather than forcing the user to retry. The work around is to send a SIGSTOP to the bhyve process and then run the bhyvectl. A SIGSTART will then set the VM going again. later, Peter. ___ 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 in -current 4/14/13 can no longer support FreeBSD stable install
On 16.03.13 07:50, Neel Natu wrote: > Hi Alfred, > > On Fri, Mar 15, 2013 at 11:21 PM, Alfred Perlstein wrote: >> >> Yes, it is a bootonly image. Using the virtio-net seems to cause the >> machine to go sidewise relatively quickly. >> > > This should be fixed with r248368: > http://svnweb.freebsd.org/base?view=revision&revision=248368 > I was experiencing the same problem, and with the fix it's much better. Thank you. Florian signature.asc Description: OpenPGP digital signature
Re: bhyve in -current 4/14/13 can no longer support FreeBSD stable install
Hi Alfred, On Fri, Mar 15, 2013 at 11:21 PM, Alfred Perlstein wrote: > On 3/15/13 8:03 PM, Neel Natu wrote: >> >> Hi Alfred, >> >> On Fri, Mar 15, 2013 at 9:48 AM, Alfred Perlstein wrote: >>> >>> Hey guys, >>> >>> I've been trying to get bhyve to install FreeBSD-stable for the past day >>> on >>> a -current machine: >>> >>> FreeBSD dan 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248291: Fri Mar 15 >>> 00:58:03 PDT 2013 root@dan:/usr/obj/usr/trees/head/sys/GENERIC amd64 >>> >>> >>> The stable snapshot I'm using to install is from here: >>> >>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/9.1/FreeBSD-9.1-STABLE-amd64-20130216-r246877-bootonly.iso >>> >>> What will happen is during the extract process the install will hang. No >>> network IO happens and on the host I see bhyve's CPU hit 100% for each >>> core >>> assigned. >>> >> Are you installing over the virtio-net interface? > > > Yes, it is a bootonly image. Using the virtio-net seems to cause the > machine to go sidewise relatively quickly. > This should be fixed with r248368: http://svnweb.freebsd.org/base?view=revision&revision=248368 best Neel > thank you, > -Alfred ___ 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 in -current 4/14/13 can no longer support FreeBSD stable install
On 3/15/13 8:03 PM, Neel Natu wrote: Hi Alfred, On Fri, Mar 15, 2013 at 9:48 AM, Alfred Perlstein wrote: Hey guys, I've been trying to get bhyve to install FreeBSD-stable for the past day on a -current machine: FreeBSD dan 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248291: Fri Mar 15 00:58:03 PDT 2013 root@dan:/usr/obj/usr/trees/head/sys/GENERIC amd64 The stable snapshot I'm using to install is from here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/9.1/FreeBSD-9.1-STABLE-amd64-20130216-r246877-bootonly.iso What will happen is during the extract process the install will hang. No network IO happens and on the host I see bhyve's CPU hit 100% for each core assigned. Are you installing over the virtio-net interface? Yes, it is a bootonly image. Using the virtio-net seems to cause the machine to go sidewise relatively quickly. thank you, -Alfred ___ 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 in -current 4/14/13 can no longer support FreeBSD stable install
Hi Alfred, On Fri, Mar 15, 2013 at 9:48 AM, Alfred Perlstein wrote: > Hey guys, > > I've been trying to get bhyve to install FreeBSD-stable for the past day on > a -current machine: > > FreeBSD dan 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248291: Fri Mar 15 > 00:58:03 PDT 2013 root@dan:/usr/obj/usr/trees/head/sys/GENERIC amd64 > > > The stable snapshot I'm using to install is from here: > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/9.1/FreeBSD-9.1-STABLE-amd64-20130216-r246877-bootonly.iso > > What will happen is during the extract process the install will hang. No > network IO happens and on the host I see bhyve's CPU hit 100% for each core > assigned. > Are you installing over the virtio-net interface? best Neel > For reference this is the bhyve command invoked via Neel's "vmrun.sh". > > 0 3915 3908 0 103 0 2122208 103428 -R+2 1048:45.75 > /usr/sbin/bhyve -c 2 -m 2048 -M 0 -AI -H -P -g 0 -s 0:0,hostbridge -s > 1:0,virtio-net,tap0 -s 2:0,virtio-blk,../freebsd-stable.img -s > 3:0,virtio-blk,../FreeBSD-9.1-STABLE-amd64-20130216-r246877-bootonly.iso -S > 31,uart,stdio freebsd-stable > > I tried to gdb the bhyve process but that was bad news. Is there a set of > steps usually taken to help pinpoint what is going on when we this state? > > thank you, > -Alfred > ___ > 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"
Re: bhyve in -current 4/14/13 can no longer support FreeBSD stable install
On 3/15/13 2:27 PM, Peter Grehan wrote: Hi Alfred, What will happen is during the extract process the install will hang. No network IO happens and on the host I see bhyve's CPU hit 100% for each core assigned. For reference this is the bhyve command invoked via Neel's "vmrun.sh". 0 3915 3908 0 103 0 2122208 103428 - R+ 2 1048:45.75 /usr/sbin/bhyve -c 2 -m 2048 -M 0 -AI -H -P -g 0 -s 0:0,hostbridge -s 1:0,virtio-net,tap0 -s 2:0,virtio-blk,../freebsd-stable.img -s 3:0,virtio-blk,../FreeBSD-9.1-STABLE-amd64-20130216-r246877-bootonly.iso -S 31,uart,stdio freebsd-stable I tried to gdb the bhyve process but that was bad news. Is there a set of steps usually taken to help pinpoint what is going on when we this state? Does the previous snapshot (r247640) work better ? The relevant change there was the recent virtio guest MFC. Some things to try: - boot bhyve uniprocessor - is the bhyve process performing any disk i/o, or is it just spinning ? the bhyvectl program can dump a lot of vm state - you can try something like sudo bhyvectl --get-all --cpu=0 --vm= sudo bhyvectl --get-all --cpu=1 --vm= If you do this repeatedly, it may be possible to see some patterns e.g. counters incrementing, %RIP values being the same etc. Hmm, I keep seem to be getting this: /usr/home/alfred # bhyvectl --get-all --cpu=0 --vm=freebsd-stable lowmem0x/536870912 highmem0x0001/0 errno = 16 /usr/home/alfred # bhyvectl --get-all --cpu=1 --vm=freebsd-stable lowmem0x/536870912 highmem0x0001/0 errno = 16 Regarding gdb and bhyve, for debugging I usually start bhyve under gdb in the foreground and send output to another pty with the gdb "set tty" command (note the other pty should have a 'sleep 10' command run to avoid input being captured) - this way, a ctl-C in the gdb session will drop into gdb and allow breakpoints to be set etc. I will try this next. Thank you. later, Peter. ___ 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"
Re: bhyve in -current 4/14/13 can no longer support FreeBSD stable install
Hi Alfred, What will happen is during the extract process the install will hang. No network IO happens and on the host I see bhyve's CPU hit 100% for each core assigned. For reference this is the bhyve command invoked via Neel's "vmrun.sh". 0 3915 3908 0 103 0 2122208 103428 - R+ 2 1048:45.75 /usr/sbin/bhyve -c 2 -m 2048 -M 0 -AI -H -P -g 0 -s 0:0,hostbridge -s 1:0,virtio-net,tap0 -s 2:0,virtio-blk,../freebsd-stable.img -s 3:0,virtio-blk,../FreeBSD-9.1-STABLE-amd64-20130216-r246877-bootonly.iso -S 31,uart,stdio freebsd-stable I tried to gdb the bhyve process but that was bad news. Is there a set of steps usually taken to help pinpoint what is going on when we this state? Does the previous snapshot (r247640) work better ? The relevant change there was the recent virtio guest MFC. Some things to try: - boot bhyve uniprocessor - is the bhyve process performing any disk i/o, or is it just spinning ? the bhyvectl program can dump a lot of vm state - you can try something like sudo bhyvectl --get-all --cpu=0 --vm= sudo bhyvectl --get-all --cpu=1 --vm= If you do this repeatedly, it may be possible to see some patterns e.g. counters incrementing, %RIP values being the same etc. Regarding gdb and bhyve, for debugging I usually start bhyve under gdb in the foreground and send output to another pty with the gdb "set tty" command (note the other pty should have a 'sleep 10' command run to avoid input being captured) - this way, a ctl-C in the gdb session will drop into gdb and allow breakpoints to be set etc. later, Peter. ___ 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 in -current 4/14/13 can no longer support FreeBSD stable install
Hey guys, I've been trying to get bhyve to install FreeBSD-stable for the past day on a -current machine: FreeBSD dan 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248291: Fri Mar 15 00:58:03 PDT 2013 root@dan:/usr/obj/usr/trees/head/sys/GENERIC amd64 The stable snapshot I'm using to install is from here: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/9.1/FreeBSD-9.1-STABLE-amd64-20130216-r246877-bootonly.iso What will happen is during the extract process the install will hang. No network IO happens and on the host I see bhyve's CPU hit 100% for each core assigned. For reference this is the bhyve command invoked via Neel's "vmrun.sh". 0 3915 3908 0 103 0 2122208 103428 -R+2 1048:45.75 /usr/sbin/bhyve -c 2 -m 2048 -M 0 -AI -H -P -g 0 -s 0:0,hostbridge -s 1:0,virtio-net,tap0 -s 2:0,virtio-blk,../freebsd-stable.img -s 3:0,virtio-blk,../FreeBSD-9.1-STABLE-amd64-20130216-r246877-bootonly.iso -S 31,uart,stdio freebsd-stable I tried to gdb the bhyve process but that was bad news. Is there a set of steps usually taken to help pinpoint what is going on when we this state? thank you, -Alfred ___ 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"
