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

2014-06-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #2 from kpiel...@tdx.co.uk --- Having setup a test system with FreeBSD 9.2-STABLE, 10-STABLE, 11-CURRENT etc. this bug still exists on all of those, regardless of version. For a 'Client' (i.e. a guest VM trying to route

[Bug 191173] [xen] Poor file write performance on xen blockfront

2014-06-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191173 Mark Felder f...@freebsd.org changed: What|Removed |Added CC||f...@freebsd.org

[Bug 190919] [patch] [xenhvm] stable/9 buildworld is broken with MODULES_WITH_WORLD=yes (again)

2014-07-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190919 Roger Pau Monné roy...@freebsd.org changed: What|Removed |Added CC|

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

2014-07-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186375 Roger Pau Monné roy...@freebsd.org changed: What|Removed |Added CC|

[Bug 180788] [xen] [panic] XEN PV kernel 9.2-BETA1 panics on boot

2014-07-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=180788 Roger Pau Monné roy...@freebsd.org changed: What|Removed |Added Status|In Discussion |Issue Resolved

[Bug 180402] [xen] XEN kernel does not load in XenClient 4.5.5

2014-07-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=180402 Roger Pau Monné roy...@freebsd.org changed: What|Removed |Added Status|In Discussion |Issue Resolved

[Bug 161318] [xen] sysinstall crashes with floating point exception

2014-07-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161318 Roger Pau Monné roy...@freebsd.org changed: What|Removed |Added Status|In Discussion |Issue Resolved

[Bug 164630] [xen] XEN HVM kernel: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb

2014-07-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 Mark Felder f...@freebsd.org changed: What|Removed |Added CC||f...@freebsd.org

[Bug 164630] [xen] XEN HVM kernel: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb

2014-07-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 --- Comment #7 from commit-h...@freebsd.org --- A commit references this bug: Author: royger Date: Fri Jul 18 07:18:38 UTC 2014 New revision: 268832 URL: http://svnweb.freebsd.org/changeset/base/268832 Log: MFC r256423: Allow FreeBSD

[Bug 164630] [xen] XEN HVM kernel: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb

2014-07-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 Roger Pau Monné roy...@freebsd.org changed: What|Removed |Added Status|Needs MFC |Issue Resolved

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

2014-08-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183397 miguelmcl...@gmail.com changed: What|Removed |Added CC||miguelmcl...@gmail.com

[Bug 195537] New: [xen] vt console somehow causes failures to boot and disk errors

2014-11-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195537 Bug ID: 195537 Summary: [xen] vt console somehow causes failures to boot and disk errors Product: Base System Version: 11.0-CURRENT Hardware: amd64

[Bug 195537] [xen] vt console somehow causes failures to boot and disk errors

2014-12-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195537 Roger Pau Monné roy...@freebsd.org changed: What|Removed |Added Assignee|freebsd-xen@FreeBSD.org

[Bug 164630] [xen] XEN HVM kernel: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb

2014-12-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 --- Comment #10 from miguelmcl...@gmail.com --- Actually after a reboot I'm back to: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb % svn info Path: . Working Copy Root Path: /usr/src URL:

[Bug 164630] [xen] XEN HVM kernel: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb

2014-12-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 --- Comment #11 from miguelmcl...@gmail.com --- Reverting xenfront.c to Revision 251973 worked for me! -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 164630] [xen] XEN HVM kernel: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb

2014-12-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 --- Comment #13 from miguelmcl...@gmail.com --- Sorry my confusion I assumed from the last comment that the patch was applied: Roger Pau Monné freebsd_committer 2014-07-18 07:38:39 UTC I've MFCed the patch to stable-9, sorry for missing

[Bug 164630] [xen] XEN HVM kernel: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb

2014-12-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 --- Comment #14 from Roger Pau Monné roy...@freebsd.org --- (In reply to miguelmclara from comment #13) Sorry my confusion I assumed from the last comment that the patch was applied: Roger Pau Monné freebsd_committer 2014-07-18

[Bug 164630] [xen] XEN HVM kernel: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb

2014-12-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 --- Comment #15 from miguelmcl...@gmail.com --- I'm no home now but I'll revert the patch as soon as I get there. I should add though that the Dom0 is NetBSD, sorry should have mention that already. -- You are receiving this mail

[Bug 164630] [xen] XEN HVM kernel: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb

2014-12-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164630 --- Comment #16 from miguelmcl...@gmail.com --- Since you mention this should work with the latest revision I tested with a fresh svn checkout and rebuilt/reinstalled the kernel. It works fine. So this was most likely a mistake I made or

[Bug 135178] [xen] Xen domU outgoing data transfer stall when TSO is enabled

2015-01-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=135178 Roger Pau Monné roy...@freebsd.org changed: What|Removed |Added Status|In Progress |Closed

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

2015-02-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 Sean Bruno sbr...@freebsd.org changed: What|Removed |Added CC||sbr...@freebsd.org

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

2015-02-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #3 from kpiel...@tdx.co.uk --- I just re-tested this with: - XenServer 6.5 - FreeBSD 10.1 amd64 Installing FreeBSD in PVHVM mode (i.e. with 'xn0' NIC etc.) - and the problem still exists (incase anyone else runs into it) -

[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)

2015-01-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 --- Comment #9 from miguelmcl...@gmail.com --- One thing to note is that the panic is not related to the mbuf already on the free list anymore: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address

[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)

2015-02-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 --- Comment #10 from miguelmcl...@gmail.com --- As requested in freebsd-xen mailing list: this is from a core dumb after reboot (saved to /var/crash) KDB: stack backtrace: #0 0x8095b070 at kdb_backtrace+0x60 #1 0x8091f765

[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)

2015-02-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 --- Comment #12 from miguelmcl...@gmail.com --- UPDATE: I've been trying to bisect with git, so far I tried only to bisect the changes here: https://github.com/freebsd/freebsd/commits/stable/10/sys/xen/xen_intr.h As they seem to affect

[Bug 195824] [xen] xen console broke with 10.1

2015-03-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195824 Mark Linimon lini...@freebsd.org changed: What|Removed |Added Keywords||regression

[Bug 195978] Add vlan support to xen netback

2015-03-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195978 Mark Linimon lini...@freebsd.org changed: What|Removed |Added Keywords||patch

[Bug 197344] tx checksum broken on XEN

2015-03-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197344 Mark Linimon lini...@freebsd.org changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org

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

2015-03-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183337 Mark Linimon lini...@freebsd.org changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org

[Bug 195978] Add vlan support to xen netback

2015-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195978 --- Comment #2 from Grischa Zengel bugs.freebsd@zengel.info --- Hi Marcelo, the developers of pfsense won't use a NIC for tagging, unless it supports tagging in hardware. In release 2.2.2 they will get altq support in xn:

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

2015-05-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428 Bryan Drewery bdrew...@freebsd.org changed: What|Removed |Added CC|

[Bug 135178] [xen] Xen domU outgoing data transfer stall when TSO is enabled

2015-05-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=135178 --- Comment #5 from Roger Pau Monné roy...@freebsd.org --- This bug is not about TSO + PF, just about TSO, which seems to work fine now (when not used in conjunction with PF). -- You are receiving this mail because: You are the assignee

[Bug 135178] [xen] Xen domU outgoing data transfer stall when TSO is enabled

2015-05-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=135178 Colin Percival cperc...@freebsd.org changed: What|Removed |Added CC|

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

2015-05-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 rait...@gmail.com changed: What|Removed |Added CC||rait...@gmail.com --- Comment

[Bug 175822] [xen] FreeBSD 9.1 does not work with Xen 4.0

2015-04-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=175822 Jeroen free...@dckd.nl changed: What|Removed |Added CC||free...@dckd.nl ---

[Bug 195978] Add vlan support to xen netfront

2015-04-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195978 Grischa Zengel bugs.freebsd@zengel.info changed: What|Removed |Added Summary|Add vlan support to xen |Add

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

2015-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #7 from kpiel...@tdx.co.uk --- (In reply to raitech from comment #6) Hi, I've tested those options here - and they do work *for FreeBSD* boxes. However - if you set '-txcsum -tso4 -lro' on the FreeBSD box acting as a router -

[Bug 183139] [xen] [patch] ifconfig options on xn0 lost after xen vm migration to another server

2015-07-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183139 Glen Barber g...@freebsd.org changed: What|Removed |Added CC||r...@freebsd.org,

[Bug 183139] [xen] [patch] ifconfig options on xn0 lost after xen vm migration to another server

2015-07-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183139 --- Comment #10 from Roger Pau Monné roy...@freebsd.org --- Now I remember the problem with the current patch, if the set of available options is different between the hosts we will fall back to enabling everything. The attached patch

[Bug 183139] [xen] [patch] ifconfig options on xn0 lost after xen vm migration to another server

2015-07-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183139 --- Comment #11 from commit-h...@freebsd.org --- A commit references this bug: Author: royger Date: Fri Jul 3 12:09:06 UTC 2015 New revision: 285089 URL: https://svnweb.freebsd.org/changeset/base/285089 Log: netfront: preserve

[Bug 195978] Add vlan support to xen netfront

2015-07-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195978 Glen Barber g...@freebsd.org changed: What|Removed |Added CC||cperc...@freebsd.org

[Bug 195978] Add vlan support to xen netfront

2015-07-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195978 Colin Percival cperc...@freebsd.org changed: What|Removed |Added CC|

[Bug 202199] packet forwarding in xen becomes slow

2015-08-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202199 --- Comment #4 from Andrei and...@fazik.net.ua --- (In reply to Sydney Meyer from comment #2) I've checked and behavior looks very similar to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197344 After disabling tx perfomance increased

[Bug 202199] packet forwarding in xen becomes slow

2015-08-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202199 --- Comment #2 from Sydney Meyer meyer.syd...@gmail.com --- and/or: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197344 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 195978] Add vlan support to xen netfront

2015-07-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195978 matt.th...@gmail.com changed: What|Removed |Added CC||matt.th...@gmail.com ---

[Bug 195978] Add vlan support to xen netfront

2015-07-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195978 --- Comment #8 from Grischa Zengel bugs.freebsd@zengel.info --- (In reply to Roger Pau Monné from comment #6) Really missing is ALTQ to have throttling and VLAN tagging with MTU 1504 (called Baby Jumbo Frames). -- You are receiving

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

2015-10-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428 --- Comment #21 from commit-h...@freebsd.org --- A commit references this bug: Author: kp Date: Wed Oct 21 15:32:21 UTC 2015 New revision: 289703 URL: https://svnweb.freebsd.org/changeset/base/289703 Log: MFC r289316: pf: Fix TSO

[Bug 204424] When live migrating FreeBSD domU's under XenServer the domU moves it's clock several seconds into the future.

2015-11-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204424 Roger Pau Monné changed: What|Removed |Added Status|New |In Progress

[Bug 204424] When live migrating FreeBSD domU's under XenServer the domU moves it's clock several seconds into the future.

2015-11-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204424 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org

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

2015-10-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428 --- Comment #15 from commit-h...@freebsd.org --- A commit references this bug: Author: kp Date: Wed Oct 14 16:21:41 UTC 2015 New revision: 289316 URL: https://svnweb.freebsd.org/changeset/base/289316 Log: pf: Fix TSO issues In

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

2015-10-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428 --- Comment #20 from Jonas Liepuonius --- I probably have the routing issue mentioned above by Sydney. Anyways, we're moving in the right direction. -- You are receiving this mail because: You are the assignee for

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

2015-10-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428 --- Comment #19 from Alex --- @Jonas I think your issue is something else. The issue was never no tcp flow at all, it was excruciatingly slow tcp performance. -- You are receiving this mail because: You are the assignee

[Bug 195824] [xen] xen console broke with 10.1

2015-07-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195824 --- Comment #2 from Glen Barber g...@freebsd.org --- Can you please retry this against 10.2-PRERELEASE and report back whether or not this is still an issue? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 195824] [xen] xen console broke with 10.1

2015-07-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195824 Roger Pau Monné roy...@freebsd.org changed: What|Removed |Added CC|

[Bug 195824] [xen] xen console broke with 10.1

2015-09-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195824 Roger Pau Monné changed: What|Removed |Added Status|New |Closed

[Bug 153477] [xen] XEN pmap code abuses vm page queue lock

2015-09-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=153477 Roger Pau Monné changed: What|Removed |Added Status|In Progress |Closed

[Bug 195824] [xen] xen console broke with 10.1

2015-09-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195824 --- Comment #5 from Jeroen --- (In reply to Jeroen from comment #4) That should be bug #201787 -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 195824] [xen] xen console broke with 10.1

2015-09-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195824 Jeroen changed: What|Removed |Added Resolution|Feedback Timeout|Not A Bug --- Comment

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

2015-10-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428 --- Comment #14 from Bryan Drewery --- Possible patch in https://reviews.freebsd.org/D3779 -- You are receiving this mail because: You are the assignee for the bug. ___

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

2015-09-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428 Jonas Liepuonius changed: What|Removed |Added CC|

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

2015-09-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428 --- Comment #13 from Bryan Drewery --- (In reply to Bryan Drewery from comment #11) > I just hit this on 10.1-GENERIC on EC2. Empty pf.conf with pf enabled = > horrible performance. Disabling pf or TSO with pf fixes

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

2016-06-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #24 from Sydney Meyer --- FWIW, i have applied the three patches to r301515M and on a dom0 running Xen 4.4.1 with Linux 4.5.1, and a Xen 4.5.3 / NetBSD 7.0.1 host i was able to ping, connect via ssh, scp

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

2016-06-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #23 from Roger Pau Monné --- (In reply to kpielorz from comment #22) Thanks for the traces, I will try to prepare a debug patch for you either this afternoon or tomorrow morning. -- You are receiving this

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

2016-06-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #21 from Roger Pau Monné --- (In reply to kpielorz from comment #20) Yes, I think I know what the issue is. What OS are the other DomUs on the same host using? If you can provide me with complete tcpdump

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

2016-06-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #14 from Roger Pau Monné --- Hello, I've recently committed a bunch of netfront fixes that I think should help solve this issue. ATM, the only reliable way to do packet forwarding on a FreeBSD DomU is to

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

2016-06-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #15 from Sydney Meyer --- (In reply to Roger Pau Monné from comment #14) Hello Roger, https://reviews.freebsd.org/D6656 https://reviews.freebsd.org/D6612 https://reviews.freebsd.org/D6612 is this a

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

2016-06-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #27 from Roger Pau Monné --- (In reply to Sydney Meyer from comment #26) Thanks, since in your case the patches seem to solve the issue, I'm waiting for the feedback from Karl with the debug patch applied.

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

2016-06-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #26 from Sydney Meyer --- (In reply to Roger Pau Monné from comment #25) I have applied your patch on top of the others and there seems to be no output related to packet forwarding, when doing the

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

2016-06-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #30 from kpiel...@tdx.co.uk --- (In reply to Roger Pau Monné from comment #29) Hi, This machine is running natd [this was briefly mentioned in the original ticket way-back-when] - so in /etc/rc.conf I have:

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

2016-06-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #28 from kpiel...@tdx.co.uk --- (In reply to Roger Pau Monné from comment #27) Hi, I've applied the patch and rebuilt/re-installed the kernel. Sadly I too get no output to the console / dmesg or /var/log/messages while

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

2016-06-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #31 from Roger Pau Monné --- (In reply to kpielorz from comment #30) Oh right, this is kind of different from my test setup, it could explain why it works in my case but not in yours. Do you see any

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

2016-06-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #32 from kpiel...@tdx.co.uk --- (In reply to Roger Pau Monné from comment #31) Hi, I can't see any obvious checksum errors recorded, and like yourself - I don't know how to get similar information from dom0 -Karl -- You

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

2016-06-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #18 from Sydney Meyer --- I don't know if i missed something, but i see only two diffs on phabricator, D6656 and D6612, where the last one is linked two times. -- You are receiving this mail because:

[Bug 197344] tx checksum broken on XEN

2016-01-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197344 --- Comment #1 from Andreas Pflug --- Problem still present with FreeBSD 10.2 p11 (used in OPNsense 16.1) -- You are receiving this mail because: You are the assignee for the bug.

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

2016-01-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428 Andreas Pflug changed: What|Removed |Added CC|

[Bug 182884] [xen] FreeBSD HVMPV domU networking does not work

2016-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=182884 Mark Linimon changed: What|Removed |Added Assignee|emulat...@freebsd.org

[Bug 188369] [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING: response is -1)

2016-05-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369 Roger Pau Monné changed: What|Removed |Added CC|

[Bug 197344] tx checksum broken on XEN

2016-05-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197344 Roger Pau Monné changed: What|Removed |Added CC|

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

2016-05-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #8 from Roger Pau Monné --- Hello, I would really like to reproduce this, but sadly my FreeBSD network knowledge is very limited, so please bear with me. When you say: "Set this first machine up with (for

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

2016-05-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #9 from Sydney Meyer --- In its most basic form, without doing nat, without have pf loaded, the problem comes up e.g. in the following setup: (PC1) 10.0.1.2/24 on xn0 <--> 10.0.1.1/24 on xn0 (FreeBSD

[Bug 209327] Under XenServer 6.5 - Live Migration results in a Kernel Panic when the VM 'Lands' on the other Node

2016-05-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209327 Roger Pau Monné changed: What|Removed |Added CC|

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

2016-05-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #11 from Andreas Pflug --- It is a problem with DomUs, not Dom0. -- 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.

2016-05-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #12 from Roger Pau Monné --- (In reply to Andreas Pflug from comment #11) I know, I'm just pointing out that this doesn't happen with a FreeBSD Dom0 running FreeBSD DomUs. I guess you are always using a

[Bug 209327] Under XenServer 6.5 - Live Migration results in a Kernel Panic when the VM 'Lands' on the other Node

2016-05-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209327 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org

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

2016-05-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261 --- Comment #13 from Andreas Pflug --- Yes, only Linux Dom0. I've only seen one anomaly with offloading, which was fixed in Windows PVM drivers a long time ago, so I assume that there's something in FreeBSD Dom0

[Bug 209327] Under XenServer 6.5 - Live Migration results in a Kernel Panic when the VM 'Lands' on the other Node

2016-05-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209327 --- Comment #3 from kpiel...@tdx.co.uk --- Hi, In your test - did you use shared storage? Having looked at this yesterday, and this morning - I tried setting up a completely separate pool - and found: - Live migration with local

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

2017-02-07 Thread bugzilla-noreply
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

2017-02-07 Thread bugzilla-noreply
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

2017-02-07 Thread bugzilla-noreply
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

2017-02-07 Thread bugzilla-noreply
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

2017-02-07 Thread bugzilla-noreply
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

2017-02-07 Thread bugzilla-noreply
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

2017-02-08 Thread bugzilla-noreply
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

2017-02-08 Thread bugzilla-noreply
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

2017-02-07 Thread bugzilla-noreply
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

2017-02-06 Thread bugzilla-noreply
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

2017-02-03 Thread bugzilla-noreply
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 212681] I/O is slow for FreeBSD DOMu on XenServer

2017-02-10 Thread bugzilla-noreply
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

2017-02-10 Thread bugzilla-noreply
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

2017-02-10 Thread bugzilla-noreply
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

  1   2   3   >