Re: Curent Centos 7 and bhyve
The Doctor via freebsd-virtualization wrote: > Are there issues with Current CEntos and bhyve? Sure there are, please look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230453 > > I have tried 3 installation method. > > On 2nd phase, it looks like the xfs indoe are skewered. Duh! -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 230402] With buildworld, the system can not use swap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230402
--- Comment #7 from Mark Millard ---
Mark Johnston has indicated that after investigations
in small armv7 and aarch64 examples, such as rpi3's
and rpi2's (V1.1):
I do think the default [vm.pageout_oom_seq] value
is too low and will get that addressed in 12.0.
Mark J. had someone with rpi3 and rpi2 (V1.1)
usage experiment with:
sysctl vm.pageout_oom_seq=120
and things got much farther but it was not
a cure.
While not a cure but it was discovered that
when some other changes were made ("lowering the
pagedaemon sleep period") a fair time ago,
vm.pageout_oom_seq was not rescaled to roughly
match, making OOM kills happen easier.
There are some patches for reporting information
that Mark J. has indicated will likely have some
variant become standard FreeBSD code that could
be enabled without needing patches, targeting
12.0 having such.
The lists have a long history tied to the
investigations on arm. I'll reference the first
Mark Johnston message here:
https://lists.freebsd.org/pipermail/freebsd-arm/2018-August/018506.html
His messages have most of the technical content
tied to internal evidence his patches produced
and what might be done. (Other folks produced data
from there environments, mostly one person.)
The prior activity does not get much into internal
activity tied to the issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"
Re: Curent Centos 7 and bhyve
On Sat, Aug 11, 2018 at 7:46 AM, The Doctor via freebsd-virtualization < freebsd-virtualization@freebsd.org> wrote: > Are there issues with Current CEntos and bhyve? > > I have tried 3 installation method. > > On 2nd phase, it looks like the xfs indoe are skewered. > Maybe try to use CentOS-7-x86_64-Minimal-1511.iso. This is 7.2.1551. Later versions default to XFS which FreeBSD grub2 doesn't seem to support. There is no known way to switch this from anaconda so you have to use the old ISO and then update. Ganbold > -- > Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@ > nl2k.ab.ca > Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist > rising! > https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on > Atheism > We cannot direct the wind, but we can adjust the sails. -Bertha Calloway > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization- > unsubscr...@freebsd.org" > ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 230402] With buildworld, the system can not use swap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230402 Rodney W. Grimes changed: What|Removed |Added CC||rgri...@freebsd.org --- Comment #6 from Rodney W. Grimes --- I would suggest that make with -j3 on a 1024MB machine is not a reasonable expectation. It is very easy for a compile or linker process to get into the 500MB size region and suggest you either increase avaliable memory to the VM, or decrease the job count. Due to the fact that "runnable" processes are not swapped in FreeBSD, this leads to an OOM condition, and the kill you see. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Curent Centos 7 and bhyve
Are there issues with Current CEntos and bhyve? I have tried 3 installation method. On 2nd phase, it looks like the xfs indoe are skewered. -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism We cannot direct the wind, but we can adjust the sails. -Bertha Calloway ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 230402] With buildworld, the system can not use swap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230402 Mark Linimon changed: What|Removed |Added CC||virtualizat...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Bhyve Guest Network Troubles
Good afternoon, Both the host and guest are freebsd 11.2. The guest is actually a live CD boot to work out the configuration. The host does have connectivity to the Internet via its default route. Host —— root@FreeBSDHost:~ # uname -a FreeBSD FreeBSDHost.davehome.local 11.2-RELEASE-p1 FreeBSD 11.2-RELEASE-p1 #0: Sun Aug 5 12:04:13 UTC 2018 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 root@FreeBSDHost:~ # ifconfig -a igb0: flags=8943 metric 0 mtu 1500 options=6403bb ether 00:25:90:f4:74:56 hwaddr 00:25:90:f4:74:56 inet 192.168.1.75 netmask 0xff00 broadcast 192.168.1.255 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active igb1: flags=8943 metric 0 mtu 1500 options=6403bb ether 00:25:90:f4:74:57 hwaddr 00:25:90:f4:74:57 inet 192.168.10.200 netmask 0xff00 broadcast 192.168.10.255 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active igb2: flags=8c02 metric 0 mtu 1500 options=6403bb ether 00:25:90:f4:74:58 hwaddr 00:25:90:f4:74:58 nd6 options=29 media: Ethernet autoselect status: no carrier igb3: flags=8c02 metric 0 mtu 1500 options=6403bb ether 00:25:90:f4:74:59 hwaddr 00:25:90:f4:74:59 nd6 options=29 media: Ethernet autoselect status: no carrier lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet 127.0.0.1 netmask 0xff00 nd6 options=21 groups: lo vm-snet3: flags=8843 metric 0 mtu 1500 ether fa:59:16:f5:07:43 inet 192.168.3.1 netmask 0xff00 broadcast 192.168.3.255 nd6 options=1 groups: bridge vm-switch viid-04c92@ id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: igb1.3 flags=143 ifmaxaddr 0 port 7 priority 128 path cost 55 member: tap0 flags=143 ifmaxaddr 0 port 12 priority 128 path cost 200 vm-cnet2: flags=8843 metric 0 mtu 1500 ether 2e:19:74:e4:3e:dd inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255 nd6 options=1 groups: bridge vm-switch viid-1e291@ id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: igb1.2 flags=143 ifmaxaddr 0 port 9 priority 128 path cost 2 igb1.2: flags=8943 metric 0 mtu 1500 description: vm-vlan-cnet2-igb1.2 options=600303 ether 00:25:90:f4:74:57 inet6 fe80::225:90ff:fef4:7457%igb1.2 prefixlen 64 scopeid 0x9 nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 2 vlanpcp: 0 parent interface: igb1 groups: vlan vm-vlan viid-dd265@ vm-gnet5: flags=8843 metric 0 mtu 1500 ether 02:48:27:ed:e7:d2 inet 192.168.5.1 netmask 0xff00 broadcast 192.168.5.255 nd6 options=1 groups: bridge vm-switch viid-13459@ id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: igb1.5 flags=143 ifmaxaddr 0 port 11 priority 128 path cost 2 igb1.5: flags=8943 metric 0 mtu 1500 description: vm-vlan-gnet5-igb1.5 options=600303 ether 00:25:90:f4:74:57 inet6 fe80::225:90ff:fef4:7457%igb1.5 prefixlen 64 scopeid 0xb nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 5 vlanpcp: 0 parent interface: igb1 groups: vlan vm-vlan viid-2eab2@ tap0: flags=8943 metric 0 mtu 1500 description: vmnet-testvm-0-snet3 options=8 ether 00:bd:69:70:fb:00 hwaddr 00:bd:69:70:fb:00 inet6 fe80::2bd:69ff:fe70:fb00%tap0 prefixlen 64 tentative scopeid 0xc nd6 options=29 media: Ethernet autoselect status: active groups: tap vm-port Opened by PID 3343 igb1.3: flags=8943 metric 0 mtu 1500 description: vm-vlan-snet3-igb1.3 options=21 ether 00:25:90:f4:74:57 inet6 fe80::225:90ff:fef4:7457%igb1.3 prefixlen 64 scopeid 0x7 nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 3 vlanpcp: 0 parent interface: igb1 groups: vlan vm-vlan viid-20a6f@ vm-inet1: flags=8843 metric 0 mtu 1500 ether 86:21:60:0f:9c:f1 inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255
Re: Why can't I dtrace processes running in a jail from the host?
On Fri, Aug 10, 2018 at 09:15:22AM +0200, Patrick M. Hausen wrote: > Hi! > > > Am 09.08.2018 um 16:52 schrieb Mark Johnston : > > For userland static probes to be globally visible, the process needs to > > register them with the kernel when it starts. This is done > > automatically using a constructor which issues ioctls to > > /dev/dtrace/helper, hence the requirement for /dev/dtrace/* in the jail. > > I figured as much. Enabling /dev/dtrace/* in the jail and restarting > the jail made the probes visible in the host system > > I'm still somewhat stuck. What I'm trying to do is track down some > performance problems in a large complex PHP web application. > I have done this in the past on "regular" setups without jails > and with PHP 5.6 compiled with dtrace support using > /usr/local/share/dtrace-toolkit/Php/* ... > > This setup is jailed with PHP 7.2, dtrace support seems to be the > default for the port. > > I'm specifically after > > php-fpm dtrace_execute_ex function-entry > php-fpm dtrace_execute_ex function-return > > of course, to see where the application spends it's CPU cycles. > > But regardless if I'm doing this on the host or in the jail, I only get > these results: > > dtrace -m php\* > ZEND_CATCH_SPEC_CONST_CV_HANDLER:exception-caught > php_request_shutdown:request-shutdown > php_request_startup:request-startup > zend_error:error > zend_throw_exception_internal:exception-thrown > > Nothing else. Still `dtrace -m php\* -l` does show all the probes. Indeed, I can reproduce this. Peering at the zend source code, it seems that there's a difference in how the dtrace_execute_ex hook gets installed: with 5.6, it's unconditional so long as zend is compiled with HAVE_DTRACE. In 7.2, the php process needs to have USE_ZEND_DTRACE=1 set in its environment for the dtrace function execution hook to be installed. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 230082] bhyve doesn't set process title
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230082 --- Comment #15 from Nikita Olenets --- I'm confirming that it is working now. Thank you, Mariusz! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 230082] bhyve doesn't set process title
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230082 --- Comment #14 from Mariusz Zaborski --- Yes :) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 230082] bhyve doesn't set process title
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230082 --- Comment #13 from commit-h...@freebsd.org --- A commit references this bug: Author: oshogbo Date: Fri Aug 10 14:47:17 UTC 2018 New revision: 337575 URL: https://svnweb.freebsd.org/changeset/base/337575 Log: MFC r337189: bhyve: set title before entering capability mode PR: 230082 Submitted by: Yuichiro NAITO Changes: _U stable/11/ stable/11/usr.sbin/bhyve/bhyverun.c -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Bhyve Guest Network Troubles
... does your WAN (eg. internet) interface have any IP assigned...? I mean your bhyve hypervisor... -- regards / s pozdravem Jakub Chromy CGI Systems div. CGI CZ s.r.o. sa...@cgi.cz 775 144 257 234 697 102 www.cgi.cz On 10.8.2018 11:29, David Powers via freebsd-virtualization wrote: Good morning, I am sure this is a common issue, but I was unable to find a way to search the list archives in an attempt to find a potential answer. I have a test vm running in Bhyve that is able to reach all interfaces on its host via icmp. However, the guest is unable to reach the default route of the host, and thus no Internet. I was hoping that someone might be able to help take a look at my config and spot the potential issue(s), but not sure what information would be most helpful. When I run a tcpdump I can see the traffic on the tap and bridge that the guest is attached to. However, I never observe the traffic on any of the physical interfaces. Blessings, David Powers Ephesians 2 14-16 For he himself is our peace, who has made the two groups one and has destroyed the barrier, the dividing wall of hostility, by setting aside in his flesh the law with its commands and regulations. His purpose was to create in himself one new humanity out of the two, thus making peace, and in one body to reconcile both of them to God through the cross, by which he put to death their hostility. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Bhyve Guest Network Troubles
I had a similar problem. I had to turn off TCP offloading and other hardware offloading features on the NIC for it to work. On Fri, Aug 10, 2018, 12:31 David Powers via freebsd-virtualization < freebsd-virtualization@freebsd.org> wrote: > Good morning, > > I am sure this is a common issue, but I was unable to find a way to search > the list archives in an attempt to find a potential answer. > > I have a test vm running in Bhyve that is able to reach all interfaces on > its host via icmp. > However, the guest is unable to reach the default route of the host, and > thus no Internet. > I was hoping that someone might be able to help take a look at my config > and spot the potential issue(s), but not sure what information would be > most helpful. > When I run a tcpdump I can see the traffic on the tap and bridge that the > guest is attached to. > However, I never observe the traffic on any of the physical interfaces. > > Blessings, > > David Powers > > > Ephesians 2 14-16 > > For he himself is our peace, who has made the two groups one and has > destroyed the barrier, the dividing wall of hostility, by setting aside in > his flesh the law with its commands and regulations. His purpose was to > create in himself one new humanity out of the two, thus making peace, and > in one body to reconcile both of them to God through the cross, by which he > put to death their hostility. > > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscr...@freebsd.org" > ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Bhyve Guest Network Troubles
Hi, > Am 10.08.2018 um 11:29 schrieb David Powers via freebsd-virtualization > : > I have a test vm running in Bhyve that is able to reach all interfaces on its > host via icmp. > However, the guest is unable to reach the default route of the host, and thus > no Internet. > I was hoping that someone might be able to help take a look at my config and > spot the potential issue(s), but not sure what information would be most > helpful. What OS is the guest running? Please provide ifconfig -a netstat -rn of both host and guest. Kind regards, Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe i...@punkt.de http://punkt.de AG Mannheim 108285 Gf: Juergen Egeling ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Bhyve Guest Network Troubles
Good morning, I am sure this is a common issue, but I was unable to find a way to search the list archives in an attempt to find a potential answer. I have a test vm running in Bhyve that is able to reach all interfaces on its host via icmp. However, the guest is unable to reach the default route of the host, and thus no Internet. I was hoping that someone might be able to help take a look at my config and spot the potential issue(s), but not sure what information would be most helpful. When I run a tcpdump I can see the traffic on the tap and bridge that the guest is attached to. However, I never observe the traffic on any of the physical interfaces. Blessings, David Powers Ephesians 2 14-16 For he himself is our peace, who has made the two groups one and has destroyed the barrier, the dividing wall of hostility, by setting aside in his flesh the law with its commands and regulations. His purpose was to create in himself one new humanity out of the two, thus making peace, and in one body to reconcile both of them to God through the cross, by which he put to death their hostility. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 230082] bhyve doesn't set process title
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230082 --- Comment #12 from Nikita Olenets --- Hi Mariusz, Was this patch added to the 11? Thank you. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Why can't I dtrace processes running in a jail from the host?
Hi! > Am 09.08.2018 um 16:52 schrieb Mark Johnston : > For userland static probes to be globally visible, the process needs to > register them with the kernel when it starts. This is done > automatically using a constructor which issues ioctls to > /dev/dtrace/helper, hence the requirement for /dev/dtrace/* in the jail. I figured as much. Enabling /dev/dtrace/* in the jail and restarting the jail made the probes visible in the host system I'm still somewhat stuck. What I'm trying to do is track down some performance problems in a large complex PHP web application. I have done this in the past on "regular" setups without jails and with PHP 5.6 compiled with dtrace support using /usr/local/share/dtrace-toolkit/Php/* ... This setup is jailed with PHP 7.2, dtrace support seems to be the default for the port. I'm specifically after php-fpm dtrace_execute_ex function-entry php-fpm dtrace_execute_ex function-return of course, to see where the application spends it's CPU cycles. But regardless if I'm doing this on the host or in the jail, I only get these results: dtrace -m php\* ZEND_CATCH_SPEC_CONST_CV_HANDLER:exception-caught php_request_shutdown:request-shutdown php_request_startup:request-startup zend_error:error zend_throw_exception_internal:exception-thrown Nothing else. Still `dtrace -m php\* -l` does show all the probes. Any ideas? Thanks Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe i...@punkt.de http://punkt.de AG Mannheim 108285 Gf: Juergen Egeling ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
