I don't see this issue on my Debian system, but please try two things:
* disable kvm_intel.preemption_timer on the host
(see /sys/module/kvm_intel/parameters/preemption_timer )
This seems to be buggy in linux 4.10 and newer
* enable hpet in the vm config:
Make sure there is no in your
e time but not always. So you will have
to try it several times (10 ... 20) to be sure that it's reliable.
I have only tested the patch with older openbsd releases, but I expect
it works on current, too.
Author: Stefan Fritsch <s...@s
On Friday, 1 December 2017 02:27:53 CET Tom Smyth wrote:
> Hello All
> I havent seen much by way of advice about multiqueue virtio
> support on OpenBSD and I was wondering do other users use it ?
> does anyone have experience with setting the number of virtio
> queues in Proxmox for an OpenBSD
On Wednesday, 6 September 2017 19:18:49 CEST Rui Ribeiro wrote:
> I once booted netbsd in my Banana Pi/Lamobo R1, which is a similar machine
> from "the same manufacturer"; the bigger problem is that outside Linux,
> there is no support for the Broadcom switching chipset.
The R2 is a completely
On Thursday, 7 September 2017 19:15:31 CEST Arfnokill wrote:
> Using snapshots on amd64. Since two days ago the kernel prints this fd0 at
> fdc0 drive 0: density unknown very late during boot.
> It starts reordering libraries, and BAM... fd0 at fdc0 drive 0: density
> unknown in blue
On Tue, 15 Aug 2017, Stefan Fritsch wrote:
> On Mon, 14 Aug 2017, msheremet wrote:
> > I get kernel panic trying to boot snapshot image install61.iso on the
> > amd64 QEMU virtual machine. the problem started to happen with late
> > July snapshots. And it still happens with
On Mon, 14 Aug 2017, msheremet wrote:
> I get kernel panic trying to boot snapshot image install61.iso on the
> amd64 QEMU virtual machine. the problem started to happen with late
> July snapshots. And it still happens with the latest snapshot I can
> obtain (Aug 11). Here is the output of the
On Tuesday, 25 July 2017 21:30:08 CEST Mxher wrote:
> I'm renting a dedicated server from a web host that unfortunately does
> not propose OpenBSD installation.
> So I'm installing OpenBSD using qemu from my host rescue mode (which use
> Usually it works like a charm but this
On Saturday, 8 July 2017 14:58:59 CEST Stefan Fritsch wrote:
> A difference between i386 and amd64 is that on amd64, openbsd uses MSI-X for
> virtio. Maybe legacy interrupts are broken with vhost-net. This needs some
> more debugging. But its either a bug in qemu or in the lin
On Wednesday, 5 July 2017 12:51:26 CEST Karsten Horsmann wrote:
> found an very strange problem, which seems more to be an
> qemu/kvm issue. Maybe one of you knows what happens and
> give me an hint to solved this (with vio).
> I use an debian 9.0 kvm/qemu setup with
On Tuesday, 14 March 2017 20:16:17 CET Jiri B wrote:
> Recent dmesg, and VM exits because of virtio-scsi issue when it is
> installing 'bsd.mp'.
I think I have fixed all the bugs, at least I could not get any corruption any
more. The changes are in -current, in r1.5 of sys/dev/pv/vioscsi.c .
On Mon, 13 Mar 2017, Jiri B wrote:
> it seems virtio-scsi is not working correctly in OpenBSD, I gave it
> a try today and OpenBSD VM was killed with:
> 2017-03-13T15:29:00.814657Z qemu-kvm: wrong size for virtio-scsi headers
> on EL7 with qemu-kvm-rhev-2.6.0-28.el7_3.6.x86_64.
On Tue, 20 Sep 2016, Darren Tucker wrote:
> On Tue, Sep 20, 2016 at 1:43 AM, Jan Stary wrote:
> > This is current/i386 on an ALIX.1E (demsg below).
> > I have an USB disk connected for /backup.
> > Upon every reboot, the filesystem on that disk is dirty:
> > WARNING: R/W
I am rather late to this thread...
On Thursday 15 October 2015 15:46:47, Raimo Niskanen wrote:
> > > Are there more password ciphers planned for the future e.g
> > > sha256 and sha512?>
> > No, we will not be adding those.
> > Those simple hashes do not provide the
On Tuesday 08 September 2015 07:24:56, Joe Gidi wrote:
> > It is worth pointing out that amtterm is only useable with AMT
> > versions <= 8
> > as AMT version 9 removed the SOAP interface that amtterm uses. If
> > anyone knows of anything that can talk the ws-man protocol
> > variant AMT version
Thanks to everyone for the testing. The patch is now committed.
someone mentioned to me the i217-LM problems that were reported on misc
end of May. It is possible that the patch below helps.
For us, it fixed a problem on a laptop with i217-LM (pci id 8086:153a)
where the receiving of packets would stop until the battery of the laptop
was removed (or
Mail list logo