https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470
Craig Rodrigues rodr...@freebsd.org changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183408
Craig Rodrigues rodr...@freebsd.org changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281
Craig Rodrigues rodr...@freebsd.org changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=147950
Damir Bikmukhametov b...@ufanet.ru changed:
What|Removed |Added
CC||b...@ufanet.ru
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470
--- Comment #2 from Nikolai Lifanov lifa...@mail.lifanov.com ---
Created attachment 146376
-- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146376action=edit
sysctl hw.vmm
output of sysctl hw.vmm
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470
--- Comment #4 from Nikolai Lifanov lifa...@mail.lifanov.com ---
Created attachment 146380
-- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146380action=edit
dmesg from CURRENT boot
The boot sometimes works. Trying to boot CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470
Peter Grehan gre...@freebsd.org changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470
--- Comment #7 from Nikolai Lifanov lifa...@mail.lifanov.com ---
Pinning vcpu 0 on hostcpu 1 does not allow boot.
It seems that all cpus other than 0 produce a similar diff.
I'm about to attach it.
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470
--- Comment #8 from Nikolai Lifanov lifa...@mail.lifanov.com ---
Created attachment 146425
-- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146425action=edit
cpuid difference
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470
--- Comment #9 from Peter Grehan gre...@freebsd.org ---
Comment on attachment 146425
-- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146425
cpuid difference
Thanks - I think this explains it.
-Vendor ID: GenuineIntel; CPUID level
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281
--- Comment #5 from Dave Smith dsm...@johncompanies.com ---
Hi Peter,
I had 3 VMs running with a slightly modified vmrc. The vms had names like
col02325.
When I tried to start a 4th VM it happened to have a name like col00345. I was
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281
--- Comment #6 from Peter Grehan gre...@freebsd.org ---
Thanks - yes, easy repro on 10. Doesn't crash on CURRENT, but the bug is
still there in that the leading zeros are stripped when the devfs entry
is created. This in turn means that it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281
--- Comment #7 from Craig Rodrigues rodr...@freebsd.org ---
+1
Being able to put the VM name in the nmdm device name is super useful.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470
Nikolai Lifanov lifa...@mail.lifanov.com changed:
What|Removed |Added
Status|Needs Triage|Issue
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281
Peter Grehan gre...@freebsd.org changed:
What|Removed |Added
Status|Open|Issue Resolved
Hi,
You have a bug in the Needs MFC state which has not been touched in 7 or more
days. This email serves as a reminder that you may want to MFC this bug or
marked it as completed.
In the event you have a longer MFC timeout you may update this bug with a
comment and I won't remind you again
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165252
Craig Rodrigues rodr...@freebsd.org changed:
What|Removed |Added
Status|In Progress |Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=160496
Craig Rodrigues rodr...@freebsd.org changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161094
Craig Rodrigues rodr...@freebsd.org changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=160496
Craig Rodrigues rodr...@freebsd.org changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148155
Craig Rodrigues rodr...@freebsd.org changed:
What|Removed |Added
Status|In Progress |Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195238
--- Comment #3 from Xin LI delp...@freebsd.org ---
(In reply to Wei Hu from comment #2)
Hi,
I have noticed that there is a different implementation in kern/196185, is that
a newer version of this patchset?
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195238
--- Comment #4 from Wei Hu w...@microsoft.com ---
(In reply to Xin LI from comment #3)
No. Fang Jun has just updated the Bug 196185, -- The hyperv_support.S will not
be used this time, we will delete it.
It turned out it is possible to add
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198344
Bryan Venteicher bry...@freebsd.org changed:
What|Removed |Added
Status|New |Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198344
Jan Henke jan.he...@taujhe.de changed:
What|Removed |Added
Status|Closed |Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183401
Allan Jude allanj...@freebsd.org changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195238
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196243
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195839
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198344
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183401
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195238
--- Comment #5 from commit-h...@freebsd.org ---
A commit references this bug:
Author: whu
Date: Wed Apr 29 10:12:36 UTC 2015
New revision: 282212
URL: https://svnweb.freebsd.org/changeset/base/282212
Log:
Microsoft vmbus, storage and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194838
John Baldwin j...@freebsd.org changed:
What|Removed |Added
Status|New |Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196243
Neel Natu n...@freebsd.org changed:
What|Removed |Added
CC||n...@freebsd.org
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195238
--- Comment #6 from commit-h...@freebsd.org ---
A commit references this bug:
Author: whu
Date: Fri May 22 09:03:58 UTC 2015
New revision: 283280
URL: https://svnweb.freebsd.org/changeset/base/283280
Log:
MFC r282212:
Microsoft
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202321
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Assignee|emulat...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195839
Peter Grehan gre...@freebsd.org changed:
What|Removed |Added
Resolution|--- |Works As Intended
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202321
Peter Grehan gre...@freebsd.org changed:
What|Removed |Added
Status|New |In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203994
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203884
--- Comment #6 from commit-h...@freebsd.org ---
A commit references this bug:
Author: ngie
Date: Thu Oct 22 08:37:11 UTC 2015
New revision: 289746
URL: https://svnweb.freebsd.org/changeset/base/289746
Log:
Exit with a user-friendly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203884
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
Status|New |In
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203884
--- Comment #5 from Peter Grehan ---
Looks fine to me.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virtualization@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196243
amvandem...@gmail.com changed:
What|Removed |Added
CC||amvandem...@gmail.com
---
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203884
--- Comment #4 from Garrett Cooper,425-314-3911 ---
(In reply to will from comment #2)
Much better :). grehan/neel: what do you think about the attached patch?
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203884
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200859
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203884
w...@worrbase.com changed:
What|Removed |Added
Attachment #162227|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203884
--- Comment #2 from w...@worrbase.com ---
Wow, that's the most embarrassing mistake I've made to date :)
I've updated the patch not to be braindead.
--
You are receiving this mail because:
You are the assignee for the bug.
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202687
Ed Maste changed:
What|Removed |Added
Keywords||uefi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202687
Ed Maste changed:
What|Removed |Added
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202687
Ed Maste changed:
What|Removed |Added
Status|New |In Progress
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202687
Ed Maste changed:
What|Removed |Added
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202687
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198344
Vick Khera changed:
What|Removed |Added
CC||vi...@khera.org
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202687
Marcel Moolenaar changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198344
Jan Henke changed:
What|Removed |Added
Version|10.1-RELEASE|10.2-RELEASE
---
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203820
--- Comment #6 from martin ilavsky ---
(In reply to John Baldwin from comment #5)
Yeah, it does make sense that only one monitor should be running. I went trough
it went I was trying to figure out where the
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198344
Roger Pau Monné changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198344
Brad Davis changed:
What|Removed |Added
CC||b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205445
Mark Linimon changed:
What|Removed |Added
Assignee|emulat...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205445
Peter Grehan changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205549
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202321
Peter Grehan changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210044
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210175
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209427
--- Comment #4 from Roman Bogorodskiy ---
(In reply to Bryan Venteicher from comment #3)
I'm using it with bhyve.
Looks like it does advertise the VIRTIO_NET_F_STATUS feature:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209427
--- Comment #3 from Bryan Venteicher ---
(In reply to Roman Bogorodskiy from comment #2)
I think is still a bit dirty: are you using a host that does not advertise the
VIRTIO_NET_F_STATUS feature?
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209427
Roman Bogorodskiy changed:
What|Removed |Added
Keywords||patch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202321
--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:
Author: bapt
Date: Fri May 27 11:46:54 UTC 2016
New revision: 300843
URL: https://svnweb.freebsd.org/changeset/base/300843
Log:
Improve error message when
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209443
--- Comment #1 from Hongjiang ---
Created attachment 171852
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=171852=edit
fix the inquiry issue on 10.3
This patch fixed the issue cause by SCSI inquiry
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206699
Hongjiang changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206699
--- Comment #1 from Roger Pau Monné ---
I've already told Wei that creating your own bounce buffer is a bad idea.
Instead you should use the BUSDMA API and let it take care of the bouncing when
necessary:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206699
--- Comment #2 from Hongjiang ---
Yes, the final fix should be using BUSDMA. Temporarily we still used the
customized bounce buffer.
The code review for this patch: https://reviews.freebsd.org/D5097
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206630
Mark Linimon changed:
What|Removed |Added
Keywords||patch
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206699
Mark Linimon changed:
What|Removed |Added
Keywords||patch
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205549
--- Comment #1 from Sergey Manucharian ---
Update:
The issue does not appear with MS Windows guest. I can start and halt Windows
2012 R2 many times, and bhyve always pass through that USB controller to the
guest.
The
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206630
Hongjiang changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206630
--- Comment #3 from Hongjiang ---
This issue was fixed on both 10 stable branch (r294890) and head (r294557).
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207297
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198344
--- Comment #7 from Brad Davis ---
It looks like this should be fixed in this MFC:
https://svnweb.freebsd.org/base/stable/10/sys/dev/virtio/balloon/virtio_balloon.c?view=log
Can someone test 10.3 and let us know?
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208238
--- Comment #2 from Dexuan Cui ---
The tsc-calibration fix was temporarily taken back last Friday because we found
an interesting thing: with some kind of config, Xen can pretend to be Hyper-V
by mimicking the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208238
--- Comment #3 from Dexuan Cui ---
The further patches on 11-CURRENT should fix the bug safely now:
https://github.com/freebsd/freebsd/commit/297e2d2f528a41d9a9614e9b34049801f6935b31
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
1 - 100 of 2494 matches
Mail list logo