> Em 4 de out. de 2024, à(s) 05:54, Stuart Henderson
> escreveu:
>
> On 2024-10-03, Adriano Barbosa wrote:
>> I don=E2=80=99t have any real hardware available right now, and I would =
>> like to test nextcloudclient before submitting updates to ports@ as it =
>> recently moved from qt5 to qt6
On 2024-10-03, Adriano Barbosa wrote:
> I don=E2=80=99t have any real hardware available right now, and I would =
> like to test nextcloudclient before submitting updates to ports@ as it =
> recently moved from qt5 to qt6.
Maybe worth a try with ssh x-forwarding, or tigervnc (try e.g.
Xvnc :0, DI
Hi!
Is anyone able to start xenodm under a qemu vm, specifically in Proxmox?
I don’t have any real hardware available right now, and I would like to test
nextcloudclient before submitting updates to ports@ as it recently moved from
qt5 to qt6.
In Xorg.0.log, I have the following error. I can
eed possible you
drifted too far for ntpd to handle through this method.
You might want to look into installing the Qemu guest agent in OpenBSD
vms:
https://marc.info/?l=openbsd-ports&m=158936392710472&w=2
Usually these agents handle properly setting the rtc after a
suspend/resume cycle
Turns out the clock stopped every night at the time when backups were running
and thus the VM was paused (saved, or 'managedsaved' if someone uses libvirt)
for a minute.
Not sure why, though; while I was testing pause/resume the clock didn't stop,
it just failed to get synced by ntpd(8). Maybe o
On Friday, January 26th, 2024 at 13:40, Dave Voutila wrote:
>
> Lévai, Dániel l...@ecentrum.hu writes:
>
> > Hi all!
> >
> > I have this OpenBSD 7.4 qemu/kvm VM managed by libvirt on an Ubuntu 22.04
> > host.
[...]
> > Anyway, the symptoms are funny, it
Lévai, Dániel writes:
> Hi all!
>
> I have this OpenBSD 7.4 qemu/kvm VM managed by libvirt on an Ubuntu 22.04
> host.
>
> I started to notice this month that it started to act weird, it seems
> like the clock stops every night. I couldn't pinpoint exactly what
>
Hi all!
I have this OpenBSD 7.4 qemu/kvm VM managed by libvirt on an Ubuntu 22.04 host.
I started to notice this month that it started to act weird, it seems like the
clock stops every night. I couldn't pinpoint exactly what caused the change in
behavior, the host had two package updates
ello,
> I see 7.4 has been released and has the new viogpu(4) driver by joshua stein.
> I am trying to use it in a VM created with UTM, a wrapper for QEMU that works
> on M1 Macs. The virtual machine installs and starts up fine from the
> install74.img mounted as a disk, but running
I have a virtual machine in UTM (which is a MacOS app that provides a
GUI to manage QEMU virtual machines) on my M1 Mac. This VM was running
7.3 and X11 was working fine with the "virtio-ramfb" video card, but
after using `sysupgrade` to upgrade to 7.4, it stopped working
(`startx` just
Hello John,
I'm a veteran (a passed user) of Qemu.
I go by memory: it seems to me that viogpu must be specified in the
configuration
of the virtual machine...
Hope it is somewhat helpful.
-- Daniele Bonini
Oct 18, 2023 15:44:55 John Holland :
> Hello,
> I see 7.4 has been relea
Hello,
I see 7.4 has been released and has the new viogpu(4) driver by joshua stein. I
am trying to use it in a VM created with UTM, a wrapper for QEMU that works on
M1 Macs. The virtual machine installs and starts up fine from the install74.img
mounted as a disk, but running startx/X/xenodm
Stuart Henderson wrote in
:
|On 2022/04/15 22:02, Tom Smyth wrote:
...
|Thanks for the suggestions - since the change I made in the last mail
|("I've changed mine to acpihpet0 and it seems much happier", i.e. setting
|the kern.timecounter.hardware sysctl to acpihpet0, based on Stefan's
|poin
I'd like to keep it like that
if possible :)
> On Fri, 15 Apr 2022 at 11:12, Stuart Henderson
> wrote:
> >
> > On 2022-04-14, Stefan Sperling wrote:
> > > On Thu, Apr 14, 2022 at 09:26:41PM -, Stuart Henderson wrote:
> > >> I have some OpenBSD guest
derson wrote:
> >> I have some OpenBSD guests in Proxmox VE 7.1-7 (pve-qemu-kvm_6.1.0) and
> >> seeing pretty bad clock drift (50 seconds in ~7h uptime). ntpd can't cope
> >> with it. From boot:
> >>
> >> 2022-04-14T13:58:19.844Z ntpd[26996]: ad
On 2022-04-14, Stefan Sperling wrote:
> On Thu, Apr 14, 2022 at 09:26:41PM -, Stuart Henderson wrote:
>> I have some OpenBSD guests in Proxmox VE 7.1-7 (pve-qemu-kvm_6.1.0) and
>> seeing pretty bad clock drift (50 seconds in ~7h uptime). ntpd can't cope
>> with it.
using
$ sysctl kern.timecounter
kern.timecounter.tick=1
kern.timecounter.timestepwarnings=0
kern.timecounter.hardware=pvclock0
kern.timecounter.choice=i8254(0) pvclock0(1500) acpitimer0(1000)
for two months on this particular host and no issue. That said I'm
using an Intel CPU and I force kvm to virtual
cessor that is common to all your hosts in the cluster
> > Better acceleration with modern processeor
> >
> > Hope this helps
> >
> >
> > On Thu, 14 Apr 2022 at 22:37, Stuart Henderson
> > wrote:
> > >
> > > I have some OpenBSD guests in P
west generation
> > Processor that is common to all your hosts in the cluster
> > Better acceleration with modern processeor
> >
> > Hope this helps
> >
> >
> > On Thu, 14 Apr 2022 at 22:37, Stuart Henderson
> > wrote:
> > >
> > >
r acceleration with modern processeor
>
> Hope this helps
>
>
> On Thu, 14 Apr 2022 at 22:37, Stuart Henderson
> wrote:
> >
> > I have some OpenBSD guests in Proxmox VE 7.1-7 (pve-qemu-kvm_6.1.0) and
> > seeing pretty bad clock drift (50 seconds in ~7h
On Thu, Apr 14, 2022 at 09:26:41PM -, Stuart Henderson wrote:
> I have some OpenBSD guests in Proxmox VE 7.1-7 (pve-qemu-kvm_6.1.0) and
> seeing pretty bad clock drift (50 seconds in ~7h uptime). ntpd can't cope
> with it. From boot:
>
> 2022-04-14T13:58:19.844Z ntpd[269
roxmox VE 7.1-7 (pve-qemu-kvm_6.1.0) and
> seeing pretty bad clock drift (50 seconds in ~7h uptime). ntpd can't cope
> with it. From boot:
>
> 2022-04-14T13:58:19.844Z ntpd[26996]: adjusting local clock by 1.745061s
> 2022-04-14T13:59:24.070Z ntpd[26996]: adjusting local cl
I have some OpenBSD guests in Proxmox VE 7.1-7 (pve-qemu-kvm_6.1.0) and
seeing pretty bad clock drift (50 seconds in ~7h uptime). ntpd can't cope
with it. From boot:
2022-04-14T13:58:19.844Z ntpd[26996]: adjusting local clock by 1.745061s
2022-04-14T13:59:24.070Z ntpd[26996]: adjusting
Hi all,
I have recently attempted to install OpenBSD on QEMU, using UEFI boot
and OVMF/TianoCore. I configured OVMF to have a resolution of 1440x900,
which mapped to GOP mode 18.
boot(8) kept this resolution. When booting, efifb then uses the largest
possible resolution that is exposed by the
On 16/11/2020 23:03, Juan Francisco Cantero Hurtado wrote:
Try -cpu kvm64.
Thanks, Juan - yup, works similar to the Opteron, but lacks one of the
flags - not much difference.
I believe Philip is right in the assessment that a) the CPU isn't
patched with AMD errata in the first place; b)
note that on an Intel host, OpenBSD
> appears to work successfully on the same Linux base.
>
> qemu invocation that yields a trap:
> qemu-system-x86_64 -enable-kvm -machine q35 -cpu
> host,-nodeid-msr,-vmx-msr-bitmap,-popcnt,-tsc-deadline,-mmxext,-fxsr-opt,-pdpe1gb,-rdtscp,-3dnow
On 16/11/2020 20:40, Philip Guenther wrote:
Looks like qemu fails to behave like a real AMD CPU by failing to handle
the wrmsr() for that errata. Also the kernel you're running it on is
failing to apply the errata itself (because otherwise OpenBSD won't be
trying to flip the bit it
st, OpenBSD
> appears to work successfully on the same Linux base.
>
> qemu invocation that yields a trap:
>
...
Lots of looking everywhere but the error going on here. Let's look at the
trap/ddb output:
> kernel: protection fault trap, code=0
> Stopped at amd64
more, as I didn't want to attach a
massive file (Linux knows how to pollute dmesg).
Any chance to try live OpenBSD there to get dmesg too?
Harder to get dmesg from installcd than anticipated, but attached as
dmesg.baremetal :-)
What is the OS version and Qemu/KVM version on that Linux h
to work successfully on the same Linux base.
Can you show what is in /proc/cpuinfo in Linux host and possibly even
its dmesg?
Any chance to try live OpenBSD there to get dmesg too?
What is the OS version and Qemu/KVM version on that Linux host?
qemu invocation that yields a trap:
qemu-syste
note that on an Intel host, OpenBSD
> appears to work successfully on the same Linux base.
>
> qemu invocation that yields a trap:
> qemu-system-x86_64 -enable-kvm -machine q35 -cpu
> host,-nodeid-msr,-vmx-msr-bitmap,-popcnt,-tsc-deadline,-mmxext,-fxsr-opt,-pdpe1gb,-rdtscp,-3dnow
to work successfully on the same Linux base.
Not sure if this answers your question, but this is how I boot OpenBSD
6.6 (...yes!) on kvm/qemu:
#!/bin/sh
qemu-system-x86_64 \
-drive if=virtio,file=/home/oc/VM/img/openbsd.image,index=0,media=disk \
-M q35,accel=kvm -m 250M -cpu host,-kvmc
On 15/11/2020 20:14, Ottavio Caruso wrote:
(pay attention to "-kvmclock-stable-bit" otherwise it will crash into a
ddb debug shell)
Thank you very much for the idea; sadly, it didn't work, must be
something else!
Hi,
I would like to run OpenBSD as stated on the subject - I have been able,
however, to run it successfully with "-cpu Opteron_G2-v1", but I would
rather use "-cpu host" instead. Also note that on an Intel host, OpenBSD
appears to work successfully on the same Linux bas
Kevin Shell wrote:
> On Mon, Oct 26, 2020 at 08:46:55AM -0600, Theo de Raadt wrote:
> >
> > There are two versions of this code, for the small and large install media.
> >
> > /usr/src/distrib/amd64/ramdisk_cd
> >
> > /usr/src/distrib/amd64/iso
> >
> > Someone who wants this should do it.
> >
> I
On Mon, Oct 26, 2020 at 08:46:55AM -0600, Theo de Raadt wrote:
>
> There are two versions of this code, for the small and large install media.
>
> /usr/src/distrib/amd64/ramdisk_cd
>
> /usr/src/distrib/amd64/iso
>
> Someone who wants this should do it.
>
I see the Makefile uses the GNU tool mkhybri
Stuart Henderson wrote:
> On 2020-10-24, Kevin Shell wrote:
> > The OpenBSD .iso image file is not
> > hybrid image(both BIOS/UEFI iso9660 and USB boot drive support),
> > Linux, FreeBSD, NetBSD all produce hybrid iso images,
>
> OpenBSD produces a separate .img file, just choose the iso if you
On 2020-10-24, Kevin Shell wrote:
> The OpenBSD .iso image file is not
> hybrid image(both BIOS/UEFI iso9660 and USB boot drive support),
> Linux, FreeBSD, NetBSD all produce hybrid iso images,
OpenBSD produces a separate .img file, just choose the iso if you want an
iso, choose img if you want a
On 24/10/2020 11:33, Kevin Shell wrote:
On Sat, Oct 24, 2020 at 08:55:34AM +0100, Ottavio Caruso wrote:
On 24/10/2020 02:27, Kevin Shell wrote:
Why I keep received 2 copies email again?
Please don't To or Cc me.:-)
Because this is how old school mailing lists work. To: the OP and cc: the
list
On 24/10/2020 02:27, Kevin Shell wrote:
Why I keep received 2 copies email again?
Please don't To or Cc me. :-)
Because this is how old school mailing lists work. To: the OP and cc:
the list, unless you use a 3rd party service like, for example, gmane.io.
Any decent mail client can be conf
On Sat, Oct 24, 2020 at 08:55:34AM +0100, Ottavio Caruso wrote:
> On 24/10/2020 02:27, Kevin Shell wrote:
> > Why I keep received 2 copies email again?
> > Please don't To or Cc me. :-)
> >
>
> Because this is how old school mailing lists work. To: the OP and cc: the
> list, unless you use a 3rd pa
On 10/22/2020 11:22 PM, Jonathan Gray wrote:
On Thu, Oct 22, 2020 at 10:37:31PM -0400, Brad Smith wrote:
On 10/22/2020 9:59 PM, Kevin Shell wrote:
Hello misc@.
I want to try out OpenBSD UEFI.
How to install OpenBSD with UEFI boot on qemu?
The installer does prompt you during disk setup.
The
gt;
> > > > I want to try out OpenBSD UEFI.
> > > > How to install OpenBSD with UEFI boot on qemu?
> > > The installer does prompt you during disk setup.
> > > > The install68.iso has no UEFI support.
> > > This is not true.
> > It does not include a
Why I keep received 2 copies email again?
Please don't To or Cc me. :-)
On Fri, Oct 23, 2020 at 07:58:27AM -0600, jpegb...@dismail.de wrote:
> I would also like to point out that kevin doesn't have a virtual disk
> to install openbsd to, just the openbsd iso. You can create one wi
Please don't To or Cc me, I'm on the list.
On Fri, Oct 23, 2020 at 12:49:13PM +0900, YASUOKA Masahiko wrote:
> On Fri, 23 Oct 2020 09:59:24 +0800
> Kevin Shell wrote:
> > I want to try out OpenBSD UEFI.
> > How to install OpenBSD with UEFI boot on qemu?
> > The
I would also like to point out that kevin doesn't have a virtual disk
to install openbsd to, just the openbsd iso. You can create one with
qemu-create I think, and then you should add that file to the drive
parameter aswell.
YASUOKA Masahiko wrote:
> On Fri, 23 Oct 2020 09:59:24 +0800
On 10/22/2020 9:59 PM, Kevin Shell wrote:
Hello misc@.
I want to try out OpenBSD UEFI.
How to install OpenBSD with UEFI boot on qemu?
The installer does prompt you during disk setup.
The install68.iso has no UEFI support.
This is not true.
My following command on Linux can't boot Op
On Fri, 23 Oct 2020 09:59:24 +0800
Kevin Shell wrote:
> I want to try out OpenBSD UEFI.
> How to install OpenBSD with UEFI boot on qemu?
> The install68.iso has no UEFI support.
> My following command on Linux can't boot OpenBSD UEFI.
>
> qemu-sy
On Thu, Oct 22, 2020 at 10:37:31PM -0400, Brad Smith wrote:
> On 10/22/2020 9:59 PM, Kevin Shell wrote:
> > Hello misc@.
> >
> > I want to try out OpenBSD UEFI.
> > How to install OpenBSD with UEFI boot on qemu?
> The installer does prompt you during disk setup.
>
Hello misc@.
I want to try out OpenBSD UEFI.
How to install OpenBSD with UEFI boot on qemu?
The install68.iso has no UEFI support.
My following command on Linux can't boot OpenBSD UEFI.
qemu-system-x86_64 -enable-kvm \
-machine q35 \
-cpu
Hello once again.
Steffen Nurpmeso wrote in
<20200525221543.zdgwt%stef...@sdaoden.eu>:
|Ya, thanks!, i am doing my OpenBSD 6.7 today!
|
|I have switched to use "-device virtio-rng-pci" in qemu not too
|long ago after figuring out it works quite nice and almost
|everybody see
Hello!
Ya, thanks!, i am doing my OpenBSD 6.7 today!
I have switched to use "-device virtio-rng-pci" in qemu not too
long ago after figuring out it works quite nice and almost
everybody seems to support it. It is detected just fine for
OpenBSD 6.4 .. 6.6, but OpenBSD 6.7 causes q
On 25/5/20 8:34 am, abed wrote:
> Sorry what kind of details you guess we need?
>
> Host OS: FreeBSD 12.1
>
> VMM: Qemu 5.0.0 (compiled from source)
>
> Guest OS: OpenBSD 6.7
>
> qemu-system-x86_64 -m 2048 \ -cdrom cd67.iso \ -drive
> if=virtio,file=disk.qc
Sorry what kind of details you guess we need?
Host OS: FreeBSD 12.1
VMM: Qemu 5.0.0 (compiled from source)
Guest OS: OpenBSD 6.7
qemu-system-x86_64 -m 2048 \ -cdrom cd67.iso \ -drive
if=virtio,file=disk.qcow2,format=qcow2 \ -enable-kvm \ -netdev
user,id=mynet0,hostfwd=tcp:127.0.0.1:7922-:22
Even better. no hopefully I was able to press some keys but it crashing
randomly.
On 5/24/20 9:27 PM, Francois Pussault wrote:
> I failed to install it with Qemu because keyboard was "mad"
> ;)
>
>
>
>>
>> From: ab
I failed to install it with Qemu because keyboard was "mad"
;)
>
> From: abed
> Sent: Sun May 24 23:19:16 CEST 2020
> To:
> Cc:
> Subject: OpenBSD Qemu
>
>
> OpenBSD 6.7 version crashed on Qemu5.0.0. an
OpenBSD 6.7 version crashed on Qemu5.0.0. any idea?
Crap works as expected. Should be run from unprivileged user only.
On 1/25/2020 2:34 PM, Stuart Henderson wrote:
> On 2020-01-24, Denis wrote:
>> Trying to connect to QEMU 4.1.0 with VNC server enabled by
>> $ doas vncviewer -rawlocal 127.0.0.1:0
>
> For the love of cthulh
On 2020-01-24, Denis wrote:
> Trying to connect to QEMU 4.1.0 with VNC server enabled by
> $ doas vncviewer -rawlocal 127.0.0.1:0
For the love of cthulhu don't run that crap as root.
> All the time receive 'Error: Can't open display' by vncviewer
> (ssvnc-viewer
Trying to connect to QEMU 4.1.0 with VNC server enabled by
$ doas vncviewer -rawlocal 127.0.0.1:0
All the time receive 'Error: Can't open display' by vncviewer
(ssvnc-viewer package installed on OpenBSD 6.6) when connect to QEMU
machine which run on the same localhost and QEMU VNC
(3946MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5900 (10 entries)
bios0: vendor SeaBIOS version
"rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org" date 04/01/2014
bios0: QEMU Standard PC (Q35 + ICH9, 2009)
acpi0 at bios0: ACPI
Hi,
I installed OBSD 6.5 (or upgraded from 6.4, I'm not sure...) in a
qcow2 image in QEmu 3.1.0 (Xubuntu 19.04 host). I selected to run ssh
& start X with xenodm.
Everything went fine with the basic install.
Then I installed a few packages (emacs, python, spyder3, etc) and
updated e
On Sat, Jun 01, 2019 at 10:29:09PM +0200, Patrick Wildt wrote:
> As you can see in dmesg, it actually sees sd0, and it does not detach.
> Instead, the device node just isn't in /dev, because the insaller does
> create that on the fly. Since you are not using the installer, you
> have to manually t
On Sun, Jun 02, 2019 at 08:27:04AM -0600, Theo de Raadt wrote:
> Maksym Sheremet wrote:
>
> > The VM is installed on a dedicated drive with FDE. It is detected as sd0
> > by bsd.rd booted from install65.iso. But once installer is started the
> > drive disappears. Here is full output:
> ...
> > (I
Roderick wrote:
> > The Install script creates device nodes as required, because pre-creating
> > 32 inodes per potential drive overflows the limited space inside the
> > ramdisk.
>
> Well, a very good reason not to put vi in bsd.rd
>
> But ed is perhaps not the most comfortable in difficult s
On Sun, 2 Jun 2019, Theo de Raadt wrote:
The Install script creates device nodes as required, because pre-creating
32 inodes per potential drive overflows the limited space inside the ramdisk.
Well, a very good reason not to put vi in bsd.rd
But ed is perhaps not the most comfortable in dif
Maksym Sheremet wrote:
> The VM is installed on a dedicated drive with FDE. It is detected as sd0
> by bsd.rd booted from install65.iso. But once installer is started the
> drive disappears. Here is full output:
...
> (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s
> # bioctl -c C -l /dev/sd0a
at 09:08:58PM +0300, Maksym Sheremet wrote:
> There is a 6.5-current VM running with QEMU on linux host. Usually the
> VM is being updated to the latest snapshot once per 10 days. Everything
> was OK with with 2019-04-21 snapshot. The problem has been appeared
> since 2019-05-01 snapshot.
&g
There is a 6.5-current VM running with QEMU on linux host. Usually the
VM is being updated to the latest snapshot once per 10 days. Everything
was OK with with 2019-04-21 snapshot. The problem has been appeared
since 2019-05-01 snapshot.
The VM is installed on a dedicated drive with FDE. It is
Great.
What about CPU/RAM usage. Do you believe it will be possible to report it to
the management layer ?
If not - there will be no use of qemu-ga at all on openBSD.
Best Regards,
Strahil Nikolov
On April 29, 2019 2:49:43 PM GMT+03:00, Stuart Henderson
wrote:
>On 2019-04-29, Stra
(for a lab overcommitting is
> normal).
>
> I'm just looking to enable those fancy things that make our life easier.
qemu-ga needs a way to communicate with the kernel to tell it to stop
filesystem activity etc. OpenBSD doesn't support this.
the idea. Sadly I do not have
> > suitable hardware to run on , thus I use KVM and I would be happy if
> > anyone hint me of a working solution for Qemu Guest Agent.
> > Anything I dig up (via google searches) show up only suggestions , but
> > nothing more.In openBSD 6.4
I have installed qemu, as qemu-ga cannot be installed standalone.
I qm trying to have snapshots without pausing the VM and to provide basic
functionality from host.
Best Regards,
Strahil Niolov
On April 29, 2019 11:00:42 AM GMT+03:00, Solene Rapenne wrote:
>On Sun, Apr 28, 2019 at 11:10:1
On Sun, Apr 28, 2019 at 11:10:14AM +, Strahil Nikolov wrote:
> Hi All,
> I am new to openBSD and I really like the idea. Sadly I do not have
> suitable hardware to run on , thus I use KVM and I would be happy if
> anyone hint me of a working solution for Qemu Guest Agent.
> An
ncy things that make our life easier.
Best Regards,
Strahil Nikolov
On April 29, 2019 12:07:32 AM GMT+03:00, Tom Smyth
wrote:
>Hello Strahil,
>what are you trying to achieve with the Qemu Guest Agent ?
>
>is it quiescing during backups .>?
>
>
>
>
>
>
&g
Hello Strahil,
what are you trying to achieve with the Qemu Guest Agent ?
is it quiescing during backups .>?
On Sun, 28 Apr 2019 at 20:59, Kristjan Komloši
wrote:
>
> On Sun, 2019-04-28 at 11:10 +, Strahil Nikolov wrote:
> > Hi All,
> > I am new to openBSD and I
On Sun, 2019-04-28 at 11:10 +, Strahil Nikolov wrote:
> Hi All,
> I am new to openBSD and I really like the idea. Sadly I do not have
> suitable hardware to run on , thus I use KVM and I would be happy if
> anyone hint me of a working solution for Qemu Guest Agent.
> Anythin
Hi All,
I am new to openBSD and I really like the idea. Sadly I do not have suitable
hardware to run on , thus I use KVM and I would be happy if anyone hint me of a
working solution for Qemu Guest Agent.
Anything I dig up (via google searches) show up only suggestions , but nothing
more.In
s0: date 06/23/99, BIOS32 rev. 0 @ 0xfd4be, SMBIOS rev. 2.8 @
0xf0cd0 (9 entries)
bios0: vendor SeaBIOS version
"rel-1.7.5.1-0-g8936dbb-20141113_115728-nilsson.home.kraxel.org" date 04/01/2014
bios0: QEMU Standard PC (i440FX + PIIX, 1996)
acpi0 at bios0: rev 0
acpi0: sleep states S3 S4 S5
he report.
>
> We’re going to disable pvclock until I found a solution. It seems that old
> KVMs or KVM on old CPUs report stable support incorrectly.
>
> Do you have a dmesg?
>
> Reyk
>
> > Am 03.12.2018 um 09:26 schrieb Zach Nedwich :
> >
> > Hi all,
> &
Hi,
thanks for the report.
We’re going to disable pvclock until I found a solution. It seems that old KVMs
or KVM on old CPUs report stable support incorrectly.
Do you have a dmesg?
Reyk
> Am 03.12.2018 um 09:26 schrieb Zach Nedwich :
>
> Hi all,
>
> I'm running OpenB
Hi all,
I'm running OpenBSD snapshots on QEMU (amd64) via a VPS provider, I
upgraded yesterday and now I'm unable to boot.
The panic is: pvclock0: unstable result on stable clock
Excuse the images as a NoVNC console is the only out-of-band access I have:
[image: 1543825179.p
Hi Matthew,
Thanks a lot! Your script wasn't straight fit for my use case, but reading the
source I was able to put together a working flag for the Qemu.
BR, Justus
> On 17 Oct 2018, at 1.07, Matthew King wrote:
>
> I use the following commands:
>
>$ nbsvm foo new
I use the following commands:
$ nbsvm foo newimg
$ nbsvm foo start -cdrom cd63.iso --no-reboot -- serial # Installer
$ nbsvm foo start
$ nbsvm foo serial
or
$ nbsvm foo start -- serial
And in the final openbsd installation:
$ cat /etc/boot.conf
set tty com0
Si
Hi,
I have hard to of getting serial port working with qemu in Linux host and
OpenBSD quest. I am using following command:
# qemu-system-x86_64 -curses -boot d -smp 2 -m 1G -nographic \
-cdrom install63.iso -drive file=/dev/sda,format=raw \
-drive file=/dev/sdb,format=raw -net nic,model
). The
install.conf is described in the man page for autoinstall 2). I use Packer to
create Vagrant boxes, currently only for VirtualBox, VMware, and Parallels
Desktop, but Packer also support building on QEMU 3). The latest version, 1.2.5
also has a googlecompute-import post-processor 4) which can
, and Parallels Desktop, but Packer also support building on QEMU 3).
The latest version, 1.2.5 also has a googlecompute-import post-processor 4)
which can take the raw disk image create by QEMU and import it into a GCE
image (unfortunately the link to this is lost from the documentation so you
need to
> 5. Your customization step at the end should probably fixup /etc/ttys
or
> you won't be able to log in to the machine via serial (since no getty
will
> be spawned there). I sat there waiting for a while in qemu only to
realize
> the getty was waiting o
hung. I had to change the default
> location
> in the script to be cd.
>
> That does not happen for me, perhaps because of the install image I use
> (install63.iso).
>
> 5. Your customization step at the end should probably fixup /etc/ttys or
> you won
u won't be able to log in to the machine via serial (since no getty will
be spawned there). I sat there waiting for a while in qemu only to realize
the getty was waiting on the vga console, not serial. YMMV.
You are right. I have not managed to fix serial access for OpenBSD yet, becaus
l to boot
> cleanly with a long stream of "Process (pid 1) got signal 11".
>
> To reproduce try the following (please note that all my tests are on a macOS
> host with QEMU installed):
>
> - Clone the GitHub project at [2]
> - Assuming you have QEMU installed and ins
reproduce try the following (please note that all my tests are on a macOS
host with QEMU installed):
- Clone the GitHub project at [2]
- Assuming you have QEMU installed and install63.iso downloaded try the command:
./imgtool PATH/TO/install63.iso openbsd/base
- The openbsd/base expect script
On 20/06/18 17:03, Leo Unglaub wrote:
Hey,
thank you very much for the link. I have forwarded it to the support
staff at the datacenter. I hope they apply it very quickly. I let you
know if this fixes the problem.
Thanks and greetings
Leo
On 06/19/18 21:21, Kapetanakis Giannis wrote:
They s
Hey,
thank you very much for the link. I have forwarded it to the support
staff at the datacenter. I hope they apply it very quickly. I let you
know if this fixes the problem.
Thanks and greetings
Leo
On 06/19/18 21:21, Kapetanakis Giannis wrote:
They should try setting this on the host:
kv
;> of them found a solution for the problem. (at least not the threads i
>> have found)
>>
>> I run some OpenBSD 6.3 instances in a virtual environment. The host is
>> some unknown Linux distribution with qemu on it. After the data center
>> updated there kernels and a
is
> some unknown Linux distribution with qemu on it. After the data center
> updated there kernels and also qemu my virtual OpenBSD instances startet
> to freeze randomly but almost always during login. They freeze up so
> hard that i cannot drop into a debugger or get any output whatsoev
. The host is
some unknown Linux distribution with qemu on it. After the data center
updated there kernels and also qemu my virtual OpenBSD instances startet
to freeze randomly but almost always during login. They freeze up so
hard that i cannot drop into a debugger or get any output whatsoever.
There
some unknown Linux distribution with qemu on it. After the data center
> updated there kernels and also qemu my virtual OpenBSD instances startet
> to freeze randomly but almost always during login. They freeze up so
> hard that i cannot drop into a debugger or get any output whatsoever.
Hi,
i have searched the list archive and found some similar reports but none
of them found a solution for the problem. (at least not the threads i
have found)
I run some OpenBSD 6.3 instances in a virtual environment. The host is
some unknown Linux distribution with qemu on it. After the
On Sat, Jun 09, 2018 at 12:01:43PM +0300, Denis wrote:
> Does QEMU support vmm on OpenBSD without windows setup on HDD directly?
>
> Thanks
>
no
1 - 100 of 482 matches
Mail list logo
