https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236922
--- Comment #4 from Tommy P ---
(In reply to Kubilay Kocak from comment #2)
Thank you for the feedback. I'm hesitant to try QEMU 4.0 since it's not
officially supported on Ubuntu (even the current 18.10):
https://packages.ubuntu.com/sear
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236922
--- Comment #3 from Tommy P ---
Created attachment 203281
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203281&action=edit
/var/log/messages file as requested with verbose logging during boot
--
You are receiving this mail bec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236922
Kubilay Kocak changed:
What|Removed |Added
CC||bry...@freebsd.org
Keywo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236918
Kubilay Kocak changed:
What|Removed |Added
Status|New |Open
Summary|Crash and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236922
--- Comment #1 from Tommy P ---
PS: I forgot to mention that I did a diff of src/sys/dev/virtio of the original
src during install (presumably r341666) against the updated src (r345757) via
svnlite checkout of 12.0. diff reported no differ
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236922
Bug ID: 236922
Summary: Virtio fails as QEMU-KVM guest with Q35 chipset on
Ubuntu 18.04.2 LTS
Product: Base System
Version: 12.0-RELEASE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236918
Bug ID: 236918
Summary: Crash and Dump
Product: Base System
Version: 12.0-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
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 ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236870
--- Comment #3 from and...@tao11.riddles.org.uk ---
A version of this patch was accepted by upstream libarchive:
https://github.com/libarchive/libarchive/pull/1167
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236836
--- Comment #7 from Conrad Meyer ---
(In reply to Torbjørn Birch Moltu from comment #5)
> I'm a bit surprised that the approach in my patch is the proper solution.
> Wouldn't it be better to check the type of node before opening or unlinkin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236836
--- Comment #5 from Torbjørn Birch Moltu ---
My reasoning for choosing EACCES is that it's what unprivileged processes
already get, and Linux also returns this error. I agree that EINVAL is more
accurate though, and compatibility shouldn't
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236836
Torbjørn Birch Moltu changed:
What|Removed |Added
Attachment #203197|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=177008
Andriy Voskoboinyk changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167107
Andriy Voskoboinyk changed:
What|Removed |Added
CC||a...@freebsd.org
Reso
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236836
--- Comment #4 from Conrad Meyer ---
(In reply to Jilles Tjoelker from comment #3)
> The concept seems good but I disagree with the chosen error numbers.
+1
--
You are receiving this mail because:
You are the assignee for the bug.
__
Hi Mark,
FreeBSD didn't create an interface for it when it was plugged in before
rebooting. This box also has another USB NIC plugged in, an elderly 10/100
one, which is what is presenting as ue0. The box does see it when it's
plugged in prior to powering on (cold start), but not on a reboot (warm
16 matches
Mail list logo