n coreos system.
The linux header file says '2' is unused but it appears to be set, no? 10==8+2
dan
--
Dan Mack
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsu
On Fri, 5 Sep 2014, Peter Grehan wrote:
Hi Dan,
Is there a way to direct grub-bhyve to use the
centos:/boot/grub2/grub.cfg file ala some argument -- I scanned the
source and couldn't find a simple over-ride.
The Centos7 install I did put the grub2 config into /grub2/grub.cfg
grub-bhyve can
the suite if you can point me in the general
direction.
Thanks,
dan
--
Dan Mack
___
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"
keep all the bhyves running in it ...
# screen -S bhyve
# cd /vms/system1
# ./vmrun.sh system1
#
I would prefer a serial console based scheme obviously where they could
run completely headless. Screen is nice because at least I have
configurable scrollback and such.
dan
--
Dan
on, 24 Jun 2013, Neel Natu wrote:
Hi Dan,
On Sun, Jun 23, 2013 at 7:02 AM, Dan Mack wrote:
Is this just me? When I start a new bhyve instance, it hangs on /sbin/init.
top shows bhyve consuming about 1 host core of CPU. This is on a real recent
current.
I don't see it on my system wit
Is this just me? When I start a new bhyve instance, it hangs on /sbin/init.
top shows bhyve consuming about 1 host core of CPU. This is on a real recent
current.
root@darkstor:/vms/porter # ./vmrun.sh porter
Launching virtual machine "porter" ...
Consoles: userboot
FreeBSD/amd64 User
Just FYI/FWIW I am still seeing semi-regular messages like this on my
bhyve console on releases as late as head-251224:
calcru: runtime went backwards from 992 usec to 982 usec for pid 794 (sshd)
calcru: runtime went backwards from 702 usec to 695 usec for pid 800 (sendmail)
I am not seeing s
Ahh, cool. I wasn't paying attention I guess:
uart2: <16550 or compatible> port 0x3f8-0x3ff irq 4 at device 31.0 on pci0
uart2: console (9600,n,8,1)
which maps to the bhyve argument given: '-S 31,uart,stdio'
and subsequently the serial console getty on ttyu2. Nice. Thank you,
It would
Yes, the current bhyve-manual has that as a step in the configuration
(http://bhyve.org/bhyve-manual.txt) which I guess is the culprit. I
guess I just didn't expect that side effect but admit to not spending much
time thinking about it first :-)
Dan
On Sat, 27 Apr 2013, Peter Grehan wrote
For those of you tinkering with bhyve; quick question. I've noticed that
everything I type on the console ends up in /var/log/messages on the
guest. This includes all shell activity and login stuff.
Is this expected behaviour ?
When following the standard bhyve recipes on the interwebs, it
Here's the latest (note I didn't update my release.iso with the latest, at
this point I'm still running a slightly earlier (cd /usr/src/release ; make release) copy from 248935 below. Also,
the kernel that the VM is running I actually built while in uni-processor mode
which shows how well
beh
state changed to DOWN
tap0: link state changed to UP
tap0: link state changed to DOWN
tap0: link state changed to UP
Yep, no problem. I saw the checkin and started a rebuild a few minutes ago
:-)
Thanks,
Dan
On Sat, 30 Mar 2013, Neel Natu wrote:
Hi Dan,
On Fri, Mar 29, 2013 at 3:20 PM, Dan
Yep, no problem. I saw the checkin and started a rebuild a few minutes
ago :-)
Thanks,
Dan
On Sat, 30 Mar 2013, Neel Natu wrote:
Hi Dan,
On Fri, Mar 29, 2013 at 3:20 PM, Dan Mack wrote:
Here you go Neel:
root@olive:~ # bhyvectl --vm=coco --get-stats --cpu=0
vcpu0
vm exits due to
Dan
On Fri, 29 Mar 2013, Neel Natu wrote:
Hi Dan,
On Fri, Mar 29, 2013 at 12:38 PM, Dan Mack wrote:
I ran the procsystime dtrace script on bhyve when it was chewing up all
the CPU in vCPU=2 mode, and this is what I see for about 10s of runtime:
root@olive:/usr/share/dtrace/**toolkit
85.2%
Hope this helps, let me know if you have any ideas on what to try next.
Dan
On Fri, 29 Mar 2013, Dan Mack wrote:
On Thu, 28 Mar 2013, Peter Grehan wrote:
Hi Dan,
Any ideas?
Just to confirm: your host system is an i7 3930k, which looks like a 6 core
system. Should be plenty beefy
On Thu, 28 Mar 2013, Peter Grehan wrote:
Hi Dan,
Any ideas?
Just to confirm: your host system is an i7 3930k, which looks like a 6 core
system. Should be plenty beefy enough for a 2 vCPU guest.
That's what I thought, 6 cores, 12 threads, 64 GB RAM.
The issue you are seeing looks a bit li
(other than only using uni-processor guests).
Thanks,
Dan
On Thu, 28 Mar 2013, Dan Mack wrote:
I haven't spent too much time debugging this yet but I'd thought I'd ask just
in case someone else has seen this:
- fresh 10.x system (248804) , standard FreeBSD iso image I m
I haven't spent too much time debugging this yet but I'd thought I'd ask
just in case someone else has seen this:
- fresh 10.x system (248804) , standard FreeBSD iso image I made with
make release
- latest vmrun.sh release.iso ...
- install went okay, everything seemed normal
- boot s
On Thu, 21 Jun 2012, Maurizio Vairani wrote:
On 21/06/2012 0.39, Dan Mack wrote:
I think this patch is broken. I get :
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/src/VBox/Frontends/VBoxHeadless/FramebufferVNC.cpp:94:
error: 'struct _rfbScreenInfo' has no me
I think this patch is broken. I get :
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/src/VBox/Frontends/VBoxHeadless/FramebufferVNC.cpp:94:
error: 'struct _rfbScreenInfo' has no member named 'ipv6port'
kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/out/freebs
20 matches
Mail list logo