[Bug 249123] PVH domU not migrating from one XEN host to another

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249123 Roger Pau Monné changed: What|Removed |Added CC||roy...@freebsd.org --- Comment

[Bug 249123] PVH domU not migrating from one XEN host to another

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249123 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|x...@freebsd.org -- You are

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #43 from Roger Pau Monné --- (In reply to Ricardo from comment #42) No, those patches have not been committed to FreeBSD upstream, partly to my lack of nagging, partly because I wasn't sure this was the best way to fix it (as

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #42 from Ricardo --- Thank you very much for your replies Roger. I will try to take it to the Netgate/pfSense community and see if they can help me from there! So from what I understand this issue was never officially fixed?

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #41 from Roger Pau Monné --- (In reply to Ricardo from comment #40) Oh, I'm afraid I don't know how to apply those against a pfesne build. With plain FreeBSD you would checkout the source from svn or git (see

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #40 from Ricardo --- Hi Roger thank you so much for the quick reply!! So looking for where to apply the patch I don't have the directory /sys and /usr/src/sys is empty/doesn't exist. Tried to find it but without success:

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #39 from Roger Pau Monné --- (In reply to Ricardo from comment #38) Hello, I've looked into it in the past, but I'm not a networking expert, and properly solving those issues requires a very good understanding of the network

[Bug 243993] FreeBSD as Guest with 5+ with xnb(4) devices panic on call to sysctl -a in strlen

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243993 Mark Johnston changed: What|Removed |Added CC||kak...@freebsd.org,

[Bug 243993] FreeBSD as Guest with 5+ with xnb(4) devices panic on call to sysctl -a in strlen

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243993 Roger Pau Monné changed: What|Removed |Added CC||roy...@freebsd.org --- Comment

[Bug 243993] FreeBSD as Guest with 5+ with xnb(4) devices panic on call to sysctl -a in strlen

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243993 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|x...@freebsd.org

[Bug 230845] VIMAGE regression: breaks netfront suspend/resume

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845 Kubilay Kocak changed: What|Removed |Added CC||x...@freebsd.org

[Bug 230845] VIMAGE regression: breaks netfront suspend/resume

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845 Roger Pau Monné changed: What|Removed |Added Resolution|--- |FIXED Status|New

[Bug 230570] src/sys/dev/xen/netback/netback_unit_tests.c:1408: pointless assert ?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230570 Roger Pau Monné changed: What|Removed |Added CC||roy...@freebsd.org --- Comment

[Bug 230570] src/sys/dev/xen/netback/netback_unit_tests.c:1408: pointless assert ?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230570 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|x...@freebsd.org -- You are

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #37 from Roger Pau Monné --- (In reply to karl from comment #36) Yes, I assumed so. I'm currently quite busy, so I don't think I will have time to look into this ATM. One thing I remember about reproducing this issue is that

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #36 from k...@pielorz.com --- (In reply to Roger Pau Monné from comment #35) Hi, Disabling LRO/TSO doesn't make any difference - I think we'd tried that previously as a possible fix. -Karl -- You are receiving this mail

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #35 from Roger Pau Monné --- Does this still happen if you disable LRO/TSO? (packets with size > 1500) -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #34 from k...@pielorz.com --- (In reply to Eitan Adler from comment #33) Hi - this issue still exists, I've just re-tested in 10.4 and 11.1. I'm not able to test 12.x at the moment, but I have no reason to believe it's been

[Bug 183337] run_interrupt_driven_hooks: still waiting after second for xenbusb_nop_confighook_cb

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183337 Roger Pau Monné changed: What|Removed |Added Resolution|--- |Overcome By Events

[Bug 183397] [xen] [panic] Kernel panic at first incoming ssh under Xen 4.2 with NetBSD Dom0

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183397 Roger Pau Monné changed: What|Removed |Added Status|Open|Closed Resolution|---

[Bug 154428] [xen] xn0 network interface and PF - Massive performance drop

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428 Roger Pau Monné changed: What|Removed |Added CC||roy...@freebsd.org

[Bug 186375] [xen] FreeBSD 10 is very unstable on Xen 4.1(XCP 1.6)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186375 Roger Pau Monné changed: What|Removed |Added Resolution|--- |Not Enough Information

[Bug 183397] [xen] [panic] Kernel panic at first incoming ssh under Xen 4.2 with NetBSD Dom0

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183397 Eitan Adler changed: What|Removed |Added Status|In Progress |Open --- Comment #8 from Eitan

[Bug 154428] [xen] xn0 network interface and PF - Massive performance drop

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428 Eitan Adler changed: What|Removed |Added Status|In Progress |Open --- Comment #26 from Eitan

[Bug 186375] [xen] FreeBSD 10 is very unstable on Xen 4.1(XCP 1.6)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186375 Eitan Adler changed: What|Removed |Added Status|In Progress |Open --- Comment #5 from Eitan

[Bug 183337] run_interrupt_driven_hooks: still waiting after second for xenbusb_nop_confighook_cb

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183337 Eitan Adler changed: What|Removed |Added Status|In Progress |Open --- Comment #1 from Eitan

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 Eitan Adler changed: What|Removed |Added Status|In Progress |Open --- Comment #33 from Eitan

[Bug 213439] ifOutOctets are always zero for Xen xn interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213439 Eitan Adler changed: What|Removed |Added Status|In Progress |Open ---

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 --- Comment #24 from Roger Pau Monné --- Hello, Maybe the dhclient fix is more appropriate? I'm quite lost, so I would recommend that you create a differential review with what you consider better and add hrs, adrian

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 --- Comment #23 from Bhavesh Davda --- Hi Roger, it's been quite some time since that last update and am wondering if this slipped through the cracks. Thanks. -- You are receiving this mail because: You are the

[Bug 155353] [xen] [patch] put "nudging TOD" message under boot_verbose

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=155353 Eitan Adler changed: What|Removed |Added Assignee|freebsd-xen@FreeBSD.org

[Bug 224003] xen kernel panics

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224003 --- Comment #4 from Roger Pau Monné --- FWIW, if you are searching for a compact virtualization server I would recommend the Intel NUC boxes, they are cheap and most of them (the ones based on the Core i CPUs) have

[Bug 224003] xen kernel panics

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224003 Roger Pau Monné changed: What|Removed |Added Resolution|--- |FIXED

[Bug 224003] xen kernel panics

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224003 --- Comment #2 from Bob Nestor --- I suspect Sydney Meyer's analysis is correct. From what I can find out about the SOC implementation used on the Antsle it only supports VT-x and doesn't appear to have implemented the

[Bug 224003] xen kernel panics

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224003 Sydney Meyer changed: What|Removed |Added CC|

[Bug 224003] xen kernel panics

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224003 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org

[Bug 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220 --- Comment #18 from John --- Oh no, strike that. I booted that one without OVMF and the problem was a different one (it as the Xen-pf bug where all network access is dropped when checksum offloading is on). I jumped to

[Bug 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220 --- Comment #17 from John --- Sorry for the delay, the issue still exists. I reproduced it with https://download.freebsd.org/ftp/releases/VM-IMAGES/11.1-RELEASE/amd64/Latest/FreeBSD-11.1-RELEASE-amd64.raw.xz but I still

[Bug 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220 --- Comment #15 from Roger Pau Monné --- I've installed pfSense-CE-2.4.0-BETA-amd64 on an OVMF VM with 2GB of RAM, 4vpcus and 5 network interfaces, and still unable to reproduce. Can you get a hypervisor with debug

[Bug 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220 --- Comment #14 from Roger Pau Monné --- Can you try of the same happens with a plain vanilla FreeBSD 11.0 image? You can get them from:

[Bug 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220 --- Comment #13 from John --- I can't boot pfSense 2.3 in UEFI mode, that's why I'm using their 2.4 beta. XL Info: host : xen-1-prod release: 4.9.0-3-amd64 version: #1 SMP

[Bug 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220 --- Comment #12 from Roger Pau Monné --- Can you reproduce the same issue using one of the vanilla FreeBSD images? I've tried to reproduce this with both the upstream FreeBSD images and the pfSense install iso, and so

[Bug 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220 --- Comment #11 from John --- Created attachment 185128 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185128=edit XenStore output -- You are receiving this mail because: You are the assignee for the bug.

[Bug 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220 --- Comment #10 from John --- (In reply to Roger Pau Monné from comment #9) It is a Linux Dom0 (Debian 9). I'll have it panic and get the xenstore. -- You are receiving this mail because: You are the assignee for the

[Bug 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220 --- Comment #9 from Roger Pau Monné --- Is it a FreeBSD Dom0 or a Linux Dom0? Can you paste the output of `xenstore-ls -fp` when the DomU panics? Thanks, Roger. -- You are receiving this mail because: You are the

[Bug 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220 --- Comment #7 from John --- The VM is booting in EFI mode so removing ovmf wouldn't work. I haven't tried this issue in BIOS mode, so it may be EFI-only. I can access the dom0, but it's not built with debug=y. I do have

[Bug 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220 --- Comment #8 from John --- Created attachment 185126 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185126=edit xen dmesg -- You are receiving this mail because: You are the assignee for the bug.

[Bug 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220 --- Comment #6 from Roger Pau Monné --- Also, if you have access to Dom0 can you paste the output of `xl dmesg`? (would be good if this was done on a hypervisor built with debug=y) -- You are receiving this mail

[Bug 220119] Problem with rpcapd support in xenserver environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220119 --- Comment #3 from ktcall...@gmail.com --- Thank you for answer. No error messages can be found. -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 220119] Problem with rpcapd support in xenserver environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220119 Roger Pau Monné changed: What|Removed |Added CC|

[Bug 220119] Problem with rpcapd support in xenserver environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220119 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org

[Bug 213439] ifOutOctets are always zero for Xen xn interfaces

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213439 --- Comment #9 from commit-h...@freebsd.org --- A commit references this bug: Author: royger Date: Thu Mar 16 09:40:54 UTC 2017 New revision: 315403 URL: https://svnweb.freebsd.org/changeset/base/315403 Log: MFC r308126:

[Bug 217740] netfront: cannot release all resources after adding and removing NICs time and again

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217740 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org

[Bug 217744] XEN:kernel does not support for canceled suspend

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217744 Mark Linimon changed: What|Removed |Added Keywords||patch

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 --- Comment #22 from Roger Pau Monné --- (In reply to Bhavesh Davda from comment #20) In this case I would prefer so. I don't know much about net, much less about dhclient, so I would like someone that knows to review

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 --- Comment #21 from Bhavesh Davda --- (In reply to Alexander Nusov from comment #19) Hi Alexander, IMHO just like the referenced bug https://bugzilla.redhat.com/show_bug.cgi?id=910619#c6 in that openstack nova

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 Alexander Nusov changed: What|Removed |Added CC|

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 --- Comment #18 from Roger Pau Monné --- (In reply to Bhavesh Davda from comment #16) Sadly dhclient is not my area of expertise, so we will have to wait for someone to review it. I've created a differential revision

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 --- Comment #16 from Bhavesh Davda --- (In reply to Roger Pau Monné from comment #15) Yes, your comment #15 convinces me that returning only CSUM_DATA_VALID and CSUM_PSEUDO_HDR with csum_data set to 0x is the

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 --- Comment #15 from Roger Pau Monné --- (In reply to Bhavesh Davda from comment #14) And the mbuf(9) man page says: "If a particular network interface just indicates success or failure of TCP or UDP checksum

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 --- Comment #14 from Bhavesh Davda --- (In reply to Roger Pau Monné from comment #8) I looked at the proposed patch to the netfront driver, and think this introduces a semantic mismatch between the meaning of the

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 --- Comment #13 from Roger Pau Monné --- (In reply to Bhavesh Davda from comment #12) IMHO, then the correct fix is to accept 0x as a valid checksum (which is the value set by netfront and other drivers when the

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 --- Comment #12 from Bhavesh Davda --- (In reply to Roger Pau Monné from comment #8) Yes, I know this change to dhclient seems unfortunately 'hackish' but is necessary because dhcilent relies on an interface

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 --- Comment #11 from Bhavesh Davda --- (In reply to Roger Pau Monné from comment #9) Yes, in a FreeBSD 11.0 VM, I had already verified this workaround works: in /etc/rc.conf: ifconfig_XN0="DHCP -rxcsum" Note

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 Roger Pau Monné changed: What|Removed |Added Attachment #180307|0 |1

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 --- Comment #9 from Roger Pau Monné --- (In reply to Bhavesh Davda from comment #7) Can you try to disable txcsum and rxcsum inside of the guest and see if that solves the issue? (this will only work on FreeBSD 11.0).

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 Roger Pau Monné changed: What|Removed |Added CC|

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 --- Comment #7 from Bhavesh Davda --- I'm hitting the same issue, as are other colleagues who have tried various versions of FreeBSD from 8.4 to 10.0 to 11.0 as a domU guest on Xen. The issue has to do with

[Bug 188990] [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990 Bhavesh Davda changed: What|Removed |Added CC|

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #59 from rai...@ultra-secure.de --- BYTE UNIX Benchmarks (Version 4.1.0) System -- freebsd11 Start Benchmark Run: Mon Feb 13 17:28:56 CET 2017 3 interactive users. 5:28PM up 3:06, 3 users, load averages: 0.62, 0.69,

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #57 from rai...@ultra-secure.de --- Well, I did do dd test, but they only write on a filesystem. It was (back then) most likely on ZFS, with compression etc. that changed the results. Esp. if I just write zeros from /dev/null.

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #56 from Roger Pau Monné --- (In reply to rainer from comment #55) Yes, you won't see those tunables in sysctl. Then again I'm quite lost, because you did test a plain dd, and that was actually working

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #52 from rai...@ultra-secure.de --- Yes. So, 60%-70% increase. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-xen@freebsd.org mailing list

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #51 from Roger Pau Monné --- (In reply to rainer from comment #49) So performance is slightly better with this patch? (IIRC you where getting 17M/s and with the patch you get 26M/s) -- You are receiving

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #49 from rai...@ultra-secure.de --- I switched back the OS-type to FreeBSD 10 64bit. I also booted back into a stock kernel and then the XENTIMER-LAPIC change went through without a freeze. I recompiled (a clean source-tree)

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 Roger Pau Monné changed: What|Removed |Added Attachment #179844|0 |1

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #46 from Roger Pau Monné --- (In reply to rainer from comment #44) This panic trace is very disturbing, I'm a little bit confused. Which kind of guest are you running? The trace shows xen_start ->

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #45 from Roger Pau Monné --- (In reply to rainer from comment #43) Hm, that's certainly not good, switching to the LAPIC timer shouldn't cause the VM to freeze, I've tried it and it works just fine. Do you

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #41 from Roger Pau Monné --- Can you try to change the event timer and the time counter to a different one than the Xen one: # sysctl -w kern.timecounter.hardware=ACPI-fast # sysctl -w

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #40 from rai...@ultra-secure.de --- Here: (freebsd11 ) 1 # sysctl -a |grep xbd hw.xbd.xbd_enable_indirect: 0 dev.xbd.2.xenstore_peer_path: /local/domain/0/backend/vbd3/13/768 dev.xbd.2.xenbus_peer_domid: 0

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #39 from Roger Pau Monné --- (In reply to rainer from comment #36) There's clearly something wrong there, you are not receiving as many interrupts as you should be, this is what I usually see when running

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #38 from rai...@ultra-secure.de --- Well, for some it works, for some it doesn't. The 10% I also see when writing to a RAM-disk. I'd just like to know how I can determine where all the performance is lost. -- You are

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #36 from rai...@ultra-secure.de --- Hi, I added the output. As I said, I could give ssh access to the box, if you want. I would need your ssh key. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #35 from rai...@ultra-secure.de --- Created attachment 179838 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179838=edit vmstat -ai while running dc3dd -- You are receiving this mail because: You are the assignee

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #31 from Roger Pau Monné --- You should see the messages in dmesg (if any), just execute: # dmesg As root from the console after having run your workload. -- You are receiving this mail because: You are

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #30 from rai...@ultra-secure.de --- Hi, I compiled a new kernel with this. Where would the messages show up? Anything special I need to add to GENERIC? Or a flag at booting? Sorry to sound so dumb. I stopped paying attention

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #28 from Roger Pau Monné --- (In reply to rainer from comment #26) Thanks! This shows that the guest is mostly inactive (low CPU load), is this correct? I'm attaching a patch to add some debug to

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #27 from rai...@ultra-secure.de --- (In reply to Roger Pau Monné from comment #25) (freebsd11 ) 0 # kldload pmc kldload: can't load pmc: module already loaded or in kernel (freebsd11 ) 1 # kldstat Id Refs Address

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #26 from rai...@ultra-secure.de --- Created attachment 179716 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179716=edit flamegraph dtrace This is running the example on Brendan's page with dtrace. While the VM was

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #24 from rai...@ultra-secure.de --- ok, (freebsd11 ) 64 # pmccontrol -L SOFT CLOCK.PROF CLOCK.HARD CLOCK.STAT LOCK.FAILED PAGE_FAULT.ALL PAGE_FAULT.READ PAGE_FAULT.WRITE

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #25 from Roger Pau Monné --- IIRC this was working fine last time I've tried. Have you loaded the pmc module (kldload pmc), and which CPU are you using? Note that you also need to enable the PMU support in

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #23 from rai...@ultra-secure.de --- Which event specifier should I use? I can't even run the sample: (freebsd11 ) 0 # pmcstat –S RESOURCE_STALLS.ANY -O out.pmcstat sleep 10 pmcstat: [options] [commandline] Measure

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #22 from Roger Pau Monné --- Hello, I don't have much time to look into this right now, could you try to create a flamegraph [0] of this workload, this way we might be able to identify the bottleneck(s).

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #21 from rai...@ultra-secure.de --- Still a problem on FreeBSD 12: root@f12test:~ # dc3dd wipe=/dev/ada1 dc3dd 7.2.641 started at 2017-02-06 10:12:31 +0100 compiled options: command line: dc3dd wipe=/dev/ada1 device size:

[Bug 212681] I/O is slow for FreeBSD DOMu on XenServer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681 --- Comment #20 from rai...@ultra-secure.de --- Interestingly enough, even when the backend storage is an SSD-backed ScaleIO volume (PCIe NVMe), it's not faster. Linux is faster on SSDs. -- You are receiving this mail because: You are

[Bug 215209] Kernel panic at boot under XEN: integer divide fault while in kernel mode

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215209 --- Comment #10 from commit-h...@freebsd.org --- A commit references this bug: Author: dim Date: Sun Dec 18 14:31:12 UTC 2016 New revision: 310228 URL: https://svnweb.freebsd.org/changeset/base/310228 Log: MFC r310013 (by cperciva):

[Bug 215209] Kernel panic at boot under XEN: integer divide fault while in kernel mode

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215209 --- Comment #9 from commit-h...@freebsd.org --- A commit references this bug: Author: dim Date: Sun Dec 18 14:31:12 UTC 2016 New revision: 310228 URL: https://svnweb.freebsd.org/changeset/base/310228 Log: MFC r310013 (by cperciva):

[Bug 215209] Kernel panic at boot under XEN: integer divide fault while in kernel mode

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215209 --- Comment #7 from commit-h...@freebsd.org --- A commit references this bug: Author: cperciva Date: Tue Dec 13 06:54:14 UTC 2016 New revision: 310013 URL: https://svnweb.freebsd.org/changeset/base/310013 Log: Check that blkfront

[Bug 215209] Kernel panic at boot under XEN: integer divide fault while in kernel mode

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215209 --- Comment #6 from Sylvain Garrigues --- (In reply to Colin Percival from comment #5) I had a system running CURRENT as of Nov. 3 so it was pre-r309124 and I upgraded to CURRENT as of Dec. 10. At first

[Bug 215209] Kernel panic at boot under XEN: integer divide fault while in kernel mode

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215209 --- Comment #4 from Roger Pau Monné --- I don't seem to be able to reproduce this with r309875, can you check if you still get the panic with that or any later revision? Thanks, Roger. -- You are receiving this mail

  1   2   3   >