https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249123
Roger Pau Monné changed:
What|Removed |Added
CC||roy...@freebsd.org
--- Comment #
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 receiv
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 I'
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?
C
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
https://www.freebsd
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:
[adm
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
su
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
Ricardo changed:
What|Removed |Added
CC||maveric...@outlook.pt
--- Comment #38 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243993
Mark Johnston changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243993
Mark Johnston changed:
What|Removed |Added
CC||kak...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243993
Roger Pau Monné changed:
What|Removed |Added
CC||roy...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243993
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|x...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845
Kubilay Kocak changed:
What|Removed |Added
CC||x...@freebsd.org
Keyword
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845
Roger Pau Monné changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845
Mark Linimon changed:
What|Removed |Added
Keywords||regression
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845
--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kp
Date: Thu Aug 23 16:52:53 UTC 2018
New revision: 338256
URL: https://svnweb.freebsd.org/changeset/base/338256
Log:
xen/netfront: Ensure curvnet is s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845
--- Comment #2 from Roger Pau Monné ---
(In reply to Kristof Provost from comment #1)
Thanks! That does indeed seems to solve the issue, it just has a minor typo:
s/vnet/if_vnet/. Would you like to commit it?
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845
Kristof Provost changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230845
Roger Pau Monné changed:
What|Removed |Added
Assignee|b...@freebsd.org|x...@freebsd.org
Keyw
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230570
Roger Pau Monné changed:
What|Removed |Added
CC||roy...@freebsd.org
--- Comment
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 receiv
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 it
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 beca
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.
___
f
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
fixe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183337
Roger Pau Monné changed:
What|Removed |Added
Resolution|--- |Overcome By Events
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183397
Roger Pau Monné changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428
Roger Pau Monné changed:
What|Removed |Added
CC||roy...@freebsd.org
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186375
Roger Pau Monné changed:
What|Removed |Added
Resolution|--- |Not Enough Information
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183397
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #8 from Eitan Adler
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=154428
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #26 from Eitan Adle
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186375
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #5 from Eitan Adler
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183337
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #1 from Eitan Adler
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #33 from Eitan Adle
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213439
trond.endres...@ximalas.info changed:
What|Removed |Added
Status|Open|Closed
Resol
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213439
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #10 from Eitan Adle
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 and the network group
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 assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=155353
Eitan Adler changed:
What|Removed |Added
Assignee|freebsd-xen@FreeBSD.org |freebsd-b...@freebsd.org
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 VT-d support.
--
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224003
Roger Pau Monné changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
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 VT-d features.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224003
Sydney Meyer changed:
What|Removed |Added
CC||meyer.syd...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224003
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-xen@FreeBSD.org
--
You are
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 conclusions because
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 have no idea how to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220
--- Comment #16 from Roger Pau Monné ---
Is there any news on the issue?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-xen@freebsd.org mailing list
https
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 enabled? You can pick t
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:
ftp://ftp.nl.freebsd.org/pub/FreeBSD/releases/VM-IMAGES/11.0-RELEASE/amd64/Latest/
--
You are rece
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 Debian 4.9.30-2+d
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 far I'm unable to re
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&action=edit
XenStore output
--
You are receiving this mail because:
You are the assignee for the bug.
___
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.
__
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 assignee for the bug.
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 serial console, so
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&action=edit
xen dmesg
--
You are receiving this mail because:
You are the assignee for the bug.
__
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 because:
You are the assi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220
Roger Pau Monné changed:
What|Removed |Added
CC||roy...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-xen@FreeBSD.org
--
You are
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.
___
freebsd-xen@freebsd
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220119
Roger Pau Monné changed:
What|Removed |Added
CC||roy...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220119
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-xen@FreeBSD.org
--
You are
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:
xen/netfront:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217751
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-xen@FreeBSD.org
K
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217740
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-xen@FreeBSD.org
K
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217744
Mark Linimon changed:
What|Removed |Added
Keywords||patch
Assignee|freebsd-b.
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 that patch. Let's giv
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
function states, it's better
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990
--- Comment #20 from Bhavesh Davda ---
(In reply to Roger Pau Monné from comment #18)
Roger, thanks a bunch for creating a review for the dhclient change!
I don't know the code review process in this community: do you have to wait for
a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990
Alexander Nusov changed:
What|Removed |Added
CC||alexander.nusov@nfvexpress.
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 based on your patch, a
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 "right" way to fix this,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990
--- Comment #17 from Bhavesh Davda ---
Created attachment 180347
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=180347&action=edit
dhclient: skip UDP checksum validation if Rx checksum offload in effect
--
You are receiving thi
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 validation without returning
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
'NETRXF_data_validated' r
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 checksum is offloaded).
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 [bpf(4)] to send and receive
p
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 that you only need to disab
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990
Roger Pau Monné changed:
What|Removed |Added
Attachment #180307|0 |1
is obsolete|
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).
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990
Roger Pau Monné changed:
What|Removed |Added
CC||roy...@freebsd.org
--- Comment
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 checksum offloaded packets arriv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188990
Bhavesh Davda changed:
What|Removed |Added
CC||bhavesh.da...@gmail.com
--- Commen
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, 0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681
--- Comment #58 from Roger Pau Monné ---
(In reply to rainer from comment #57)
You can also use plain dd to write to a block device, just like you do with
dc3dd. Can you actually also try if plain dd shows the same slowness with
writing to
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.
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 fine (and yielding resul
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681
--- Comment #55 from rai...@ultra-secure.de ---
I can't see these tunables in sysctl.
But:
hw.xen.disable_pv_disks=1
is responsible for the slight increases in disk-performance.
--
You are receiving this mail because:
You are the assign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681
--- Comment #54 from Roger Pau Monné ---
Created attachment 179940
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179940&action=edit
Selectively disable PV optimizations
--
You are receiving this mail because:
You are the assi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681
--- Comment #53 from Roger Pau Monné ---
I'm attaching another patch that will allow to selectively disable some PV
optimizations, you will have to play with the following tunables, and see if
you can find which one(s) causes the VM to go
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
https
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 this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681
--- Comment #50 from rai...@ultra-secure.de ---
Output from the xen-server:
xe vm-list name-label=i-129-1591-VM params=all
uuid ( RO) : 30f354c0-6a14-0dea-2be2-070a38ca2fc0
name-label ( RW): i-1
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) wi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681
--- Comment #48 from Roger Pau Monné ---
(In reply to Roger Pau Monné from comment #46)
OK, I've re-done the patch to disable the Xen enlightenments, could you please
try it again? Although the LAPIC timer issue is also concerning.
--
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681
Roger Pau Monné changed:
What|Removed |Added
Attachment #179844|0 |1
is obsolete|
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 -> hammer_time_xen and this path
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 see anything in the
c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681
--- Comment #44 from rai...@ultra-secure.de ---
Created attachment 179858
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179858&action=edit
Screenshot of panic
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212681
--- Comment #43 from rai...@ultra-secure.de ---
# sysctl -w kern.timecounter.hardware=ACPI-fast
Already had that.
IIRC, it's mentioned in the bug about moving a VM freezing it...
# sysctl -w kern.eventtimer.timer=LAPIC
and that freezes t
1 - 100 of 319 matches
Mail list logo
