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 seems to support it.
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, Strahil Nikolov
On 2019-04-29, Strahil Nikolov wrote:
> Yes , but not only.
> I'm using oVirt - a KVM management tool and I can currently make a snapshot
> only by pausing the VM or by completely stopping it first.
> For now, it's not a big deal - as I'm still exploring openBSD , but who knows.
> Also the manage
QGA depends on specific device name in /dev. Ideally the best would be
kernel-based support like vmt.
Dne po 29. 4. 2019 10:03 uživatel Solene Rapenne napsal:
> 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 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:14AM +
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.
> Anything I dig up (v
Yes , but not only.
I'm using oVirt - a KVM management tool and I can currently make a snapshot
only by pausing the VM or by completely stopping it first.
For now, it's not a big deal - as I'm still exploring openBSD , but who knows.
Also the management interface cannot provide details about CPU a
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 really like the idea. S
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.
> Anything I dig up (via goog
On 12/3/18 5:00 AM, Reyk Floeter wrote:
> 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?
I mistakenly sent the following to bugs@ and it appears to be gre
Thanks Reyk,
dmesg from bsd.rd attached, apologies again for the pictures.
[image: 1543831744.png]
[image: 1543831753.png]
[image: 1543831765.png]
[image: 1543831775.png]
[image: 1543831786.png]
Thanks,
Zach
On Mon, Dec 3, 2018 at 8:01 PM Reyk Floeter wrote:
> Hi,
>
> thanks for the report.
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 OpenBSD snapshots on QEMU (a
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 newimg
>$ nbsvm foo sta
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
Quoting Warner Losh :
Greetings,
I was wondering if anybody is using the current stock qemu user-mode code
to run OpenBSD code. The code looks woefully incomplete to my eye, so
incomplete I can't see how it would work for anything useful. I'm not even
sure it would work for anything trivial.
On 2017-05-15, Mike Hammett wrote:
> Offlist someone recommended I install the QEMU pckage. I'm trying to, but I'm
> getting dependency errors that I can't seem to resolve.
qemu-ga is part of the qemu package, though I haven't heard of it
actually being used on OpenBSD. If it works at all I thi
Offlist someone recommended I install the QEMU pckage. I'm trying to, but I'm
getting dependency errors that I can't seem to resolve.
Can't install cairo-1.14.6p1 because of libraries
|library fontconfig.10.0 not found
| not found anywhere
|library freetype.25.0 not found
| not found anywhe
Hi,
I modified the value of :
default:\
:datasize-max=4G:\
:datasize-cur=4G:\
:maxproc-max=512:\
:maxproc-cur=256:\
:openfiles-cur=1024:\
staff:\
:datasize-cur=4G:\
:datasize-max=infinity:\
:maxproc-max=512:\
:maxproc-cur=25
Le 10/26/15 10:34, Jan Lambertz a écrit :
When you do:
open xterm
ulimit -d 2000
start vm from this xterm
same error ?
Yes, Qemu work now without any problem.
On Sun, Oct 25, 2015 at 10:20:13PM +0100, ilyes aiouaz wrote:
> Le 10/25/15 22:08, Stuart Henderson a écrit :
>>On 2015-10-25, ilyes aiouaz wrote:
>>>Hi every body,
>>>Qemu-i386 present this error :
>>>
>>>(qemu-system-i386:18034): GLib-ERROR **: gmem.c:103: failed to allocate
>>>592 byte
>>>
>>>w
Le 10/25/15 22:08, Stuart Henderson a écrit :
On 2015-10-25, ilyes aiouaz wrote:
Hi every body,
Qemu-i386 present this error :
(qemu-system-i386:18034): GLib-ERROR **: gmem.c:103: failed to allocate
592 byte
when I run it on OpenBSD 5.8 amd64 stable + patchs. Can you help me ?
Is it a bug on
On 10/25/15 3:37 PM, ilyes aiouaz wrote:
Hi every body,
qemu-i368 prensent this error when I run it on OpenBSD 5.8 amd64 stable
and patched :
*(qemu-system-i386:18034): GLib-ERROR **: gmem.c:103: failed to allocate
592 byte*
Can you help me, I have no problem on OpenBSD 5.7 amd64 stable and pat
Sorry, I joined now my dmesg.
Le 10/25/15 21:49, ilyes aiouaz a écrit :
> Hi every body,
> Qemu-i386 present this error :
>
> (qemu-system-i386:18034): GLib-ERROR **: gmem.c:103: failed to
> allocate 592 byte
>
> when I run it on OpenBSD 5.8 amd64 stable + patchs. Can you help me ?
>
> Is it a
On 2015-10-25, ilyes aiouaz wrote:
> Hi every body,
> Qemu-i386 present this error :
>
> (qemu-system-i386:18034): GLib-ERROR **: gmem.c:103: failed to allocate
> 592 byte
>
> when I run it on OpenBSD 5.8 amd64 stable + patchs. Can you help me ?
>
> Is it a bug on the new version of qemu packaged
Le 10/25/15 21:44, Michael S. Keller a écrit :
On 10/25/15 3:37 PM, ilyes aiouaz wrote:
Hi every body,
qemu-i368 prensent this error when I run it on OpenBSD 5.8 amd64 stable
and patched :
*(qemu-system-i386:18034): GLib-ERROR **: gmem.c:103: failed to allocate
592 byte*
Can you help me, I hav
Em 15-11-2013 06:20, InterNetX - Robert Garrett escreveu:
> Then as Stated you are already vulnerable to much more than interrupt
> remapping will fix. So dont worry about it.
Well, I said I have it enabled on my BIOS. Me having a sriov enabled
kernel and a sriov capable NIC is another history. I'
On Thu, 14 Nov 2013 09:51:04 -0700
Theo de Raadt wrote:
> Then we'll be not be hearing from you again, I assume.
>
> > I am not putting up with this bulling shit. :)
> >
> > --
> > Bruno Delbono
> > | Cognitive Researcher
Doubtless.
Dhu
> > - Human Behavioural Project
> > | Real Sociedad E
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Then as Stated you are already vulnerable to much more than interrupt
remapping will fix. So dont worry about it.
On 11/14/2013 06:00 PM, Giancarlo Razzolini wrote:
> Em 14-11-2013 14:18, InterNetX - Robert Garrett escreveu:
>> The issue you outlined
| -Original Message-
| From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On
| Behalf Of Bruno Delbono
| Sent: Thursday, November 14, 2013 10:48 AM
| To: Theo de Raadt
| Cc: misc@openbsd.org; mlar...@azathoth.net
| Subject: Re: QEMU CPU cores not showing up
|
Useless crying
Em 14-11-2013 14:18, InterNetX - Robert Garrett escreveu:
> The issue you outlined below is not an openbsd issue, this is a kvm
> issue. and depends greatly on the version of linux/whatever you are
> using. The interrupt remapping you are talking about is either a bios
> issue (likely) or an issue
Then we'll be not be hearing from you again, I assume.
> I am not putting up with this bulling shit. :)
>
> --
> Bruno Delbono
> | Cognitive Researcher - Human Behavioural Project
> | Real Sociedad Española De AntropologÃa
> | â: +1 855 253 5436 â: +1 424 354 4700
aadt
Sent: Wednesday, November 13, 2013 5:29 PM
To: Bruno Delbono
Cc: misc@openbsd.org; mlar...@azathoth.net
Subject: Re: QEMU CPU cores not showing up
> Sigh, Theo. Seriously I am asking for your help to find out the
> issue as its unique to OpenBSD.
> Stop ranting away on the demerits of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The issue you outlined below is not an openbsd issue, this is a kvm
issue. and depends greatly on the version of linux/whatever you are
using. The interrupt remapping you are talking about is either a bios
issue (likely) or an issue with the hypervisor
Em 14-11-2013 11:43, David Coppa escreveu:
> On Thu, Nov 14, 2013 at 2:33 PM, Giancarlo Razzolini
> wrote:
>> Em 13-11-2013 22:40, Jeff Fuhrman escreveu:
>>> I'm the tech Bruno has been working with regarding this. QEMU version is
>>> 1.5 and the relevant section of the KVM Config file is "
>>>
On Thu, Nov 14, 2013 at 2:33 PM, Giancarlo Razzolini
wrote:
> Em 13-11-2013 22:40, Jeff Fuhrman escreveu:
>> I'm the tech Bruno has been working with regarding this. QEMU version is 1.5
>> and the relevant section of the KVM Config file is "
>> 4".
>> We've tried it with 2 sockets, with 4 socke
Em 13-11-2013 22:40, Jeff Fuhrman escreveu:
> I'm the tech Bruno has been working with regarding this. QEMU version is 1.5
> and the relevant section of the KVM Config file is "
> 4".
> We've tried it with 2 sockets, with 4 sockets, with 2 threads, 4 threads, and
> so on. ACPI and APIC are enab
2013/11/13 Bruno Delbono
> Stop ranting away on the demerits of disabling apm (and now pci - right!
> wtf?!).
>
He's not. He's rambling about you twisting knobs without having any kind of
clue as to why or how it would have helped, probably based on an outdated
guide which now also don't know w
Jeff Fuhrman
Level 2 Technician - BlueVM
-Original Message-
From: Bruno Delbono [mailto:b...@t.gt]
Sent: Wednesday, November 13, 2013 2:25 PM
To: Theo de Raadt; Theo de Raadt
Cc: misc@openbsd.org; mlar...@azathoth.net; misc@openbsd.org;
mlar...@azathoth.net
Subject: Re: QEMU CPU cores not sh
4700
From: Theo de Raadt
Sent: Wednesday, November 13, 2013 5:13 PM
To: Bruno Delbono
Cc: misc@openbsd.org; mlar...@azathoth.net
Subject: Re: QEMU CPU cores not showing up
> As for why completely random disabling apm and acpi...rant by you and Theo...
Bullshit.
Perhaps the solu
: Wednesday, November 13, 2013 5:29 PM
To: Bruno Delbono
Cc: misc@openbsd.org; mlar...@azathoth.net
Subject: Re: QEMU CPU cores not showing up
> Sigh, Theo. Seriously I am asking for your help to find out the
> issue as its unique to OpenBSD.
> Stop ranting away on the demerits of disabling
> Sigh, Theo. Seriously I am asking for your help to find out the
> issue as its unique to OpenBSD.
> Stop ranting away on the demerits of disabling apm (and now pci - right!
> wtf?!).
Then stop justifying your blind following of what you read on the web.
It looks too much like incompetence.
> As for why completely random disabling apm and acpi...rant by you and Theo...
Bullshit.
Perhaps the solution you are looking for is:
boot -c
> disable pci*
You never know, it just might work.
We are not ranting. We're telling you that you don't know what the
hell you are doing, an
fine...
Bruno Delbono
| Cognitive Researcher - Human Behavioural Project
| Real Sociedad Española De Antropología
| ☎: +1 855 253 5436 ☎: +1 424 354 4700
From: Mike Larkin
Sent: Wednesday, November 13, 2013 4:13 PM
To: Bruno Delbono; misc@openbsd.org
Subjec
On Wed, Nov 13, 2013 at 10:29:34PM +0100, Peter J. Philipp wrote:
> He took the advice from me on IRC. I had googled and found a similar
> mail from someone who could not see 2 cpu's but only 1, people told that
> person to disable apm, but granted the mails were a little dated.
>
> So I was givi
ral Project
>>> | Real Sociedad Espa??ola De Antropolog??a
>>> | ???: +1 855 253 5436 ???: +1 424 354 4700
>>>
>>>
>>> From: Otto Moerbeek
>>> Sent: Wednesday, November 13, 2013 3:11 PM
>>> To:
> On Wed, Nov 13, 2013 at 09:44:11PM +0100, Otto Moerbeek wrote:
> > On Wed, Nov 13, 2013 at 08:26:57PM +, Bruno Delbono wrote:
> >
> > > Hi Otto,
> > >
> > > http://pastebin.com/zfkEUxX8
> > >
> > > This is generic.mp with flags of apm and acpi disable
> > >
>
> Why would you start tryin
> >
> >
> > --
> >
> > Bruno Delbono
> > | Cognitive Researcher - Human Behavioural Project
> > | Real Sociedad Espa??ola De Antropolog??a
> > | ???: +1 855 253 5436 ???: +1 424 354 4700
> >
> > ________
> &g
354 4700
>
>
> From: Otto Moerbeek
> Sent: Wednesday, November 13, 2013 3:11 PM
> To: Bruno Delbono
> Cc: misc@openbsd.org
> Subject: Re: QEMU CPU cores not showing up
>
> On Wed, Nov 13, 2013 at 07:36:58PM +, Bruno Del
Real Sociedad Española De Antropología
| ☎: +1 855 253 5436 ☎: +1 424 354 4700
From: Otto Moerbeek
Sent: Wednesday, November 13, 2013 3:11 PM
To: Bruno Delbono
Cc: misc@openbsd.org
Subject: Re: QEMU CPU cores not showing up
On Wed, Nov 13, 2013 at 07:36
On Wed, Nov 13, 2013 at 07:36:58PM +, Bruno Delbono wrote:
> Hello,
>
>
> I have a QEMU instance that works perfectly fine at detecting cpu cores on
> NetBSD/FreeBSD/Linux. All except OpenBSD 5.4
>
>
> - I have tried the GENERIC amd64 and i386 bsd.mp kernel and the bsd.mp
> snapshot kernel
On Fri, Dec 07, 2012 at 02:58:59PM -0800, Constantine A. Murenin wrote:
> On 11 January 2011 11:18, wrote:
> > The trick with /etc/boot.conf does work; this should transform the
> > cd48.iso install cd into a 'serial' one:
> >
> > $ echo 'set tty com0' > /tmp/boot.conf
> > $ growisofs -M cd48.iso
On 11 January 2011 11:18, wrote:
> The trick with /etc/boot.conf does work; this should transform the
> cd48.iso install cd into a 'serial' one:
>
> $ echo 'set tty com0' > /tmp/boot.conf
> $ growisofs -M cd48.iso -l -graft-points /etc/boot.conf=/tmp/boot.conf
>
> Then:
> $ qemu -nographic -cdrom
Hello again,
after several hours of testing i found a solution for my problem. Here the
command i run as root (so no ulimit problems):
qemu-system-i386 -smp 1 -drive
file=harddisk.qcow2,if=sd,media=disk,cache=writeback,aio=native -cdrom
/mnt/usb/debian-6.0.6-i386-CD-1.iso -m 512 -k de -localtime -
On Mon, 3 Dec 2012 07:15:13 +0100
Jan Lambertz wrote:
> Hello,
> I try to run a qemu linux guest ontop of my openbsd 5.1 i386. I've tried
> nearly any possible qemu command. I've tested archlinux,debian,sled and
> ubuntu. In every case,qemu core dumps when loading the linux kernel. When i
> run
On Mon, Jun 18, 2012 at 08:23:05AM +0200, Tomas Bodzar wrote:
>
> If audio input/output will be working then it's possible to use
> Microsoft Office Communicator and/or Lync for Live meetings. Just idea
> for now as it can end quite complicated. But in same time it probably
> means that support fo
On Sun, Jun 17, 2012 at 9:43 PM, Alexandre Ratchov wrote:
> On Thu, Jun 14, 2012 at 12:54:49PM +0200, Tomas Bodzar wrote:
>> Hi all,
>>
>> have someone working audio input with Qemu on OpenBSD?
>
> IIRC, sdl is play-only. Adding a sndio backend could add
> record-only support (and possibly better
On Thu, Jun 14, 2012 at 12:54:49PM +0200, Tomas Bodzar wrote:
> Hi all,
>
> have someone working audio input with Qemu on OpenBSD?
IIRC, sdl is play-only. Adding a sndio backend could add
record-only support (and possibly better play-only support as
well). Qemu is not weired so writing one wouldn
Quoting Stuart Henderson :
On 2012-01-28, Vijay Sankar wrote:
Hi,
Sorry for the long message. I am not able to figure out a good
solution for the following:
Right now, what I do to test ports etc., is download install51.iso,
run it within qemu, and then do the work. To test the port on a
dif
On 2012-01-28, Vijay Sankar wrote:
> Hi,
>
> Sorry for the long message. I am not able to figure out a good
> solution for the following:
>
> Right now, what I do to test ports etc., is download install51.iso,
> run it within qemu, and then do the work. To test the port on a
> different serv
On Sat, Jan 28, 2012 at 10:49 AM, Vijay Sankar wrote:
> Hi,
>
> Sorry for the long message. I am not able to figure out a good solution for
> the following:
>
> Right now, what I do to test ports etc., is download install51.iso, run it
> within qemu, and then do the work. To test the port on a dif
On Tue, 11 Jan 2011 21:18:49 +0200, a.velichin...@gmail.com wrote:
On Sat, Jan 08, 2011 at 11:43:17PM +0100, Pieter Verberne wrote:
Actually, obsd.img is empty. I'm trying to start a fresh
installation.
And, I should be able to see BIOS messages like "Starting SeaBIOS"
and "Booting from" anyway
On Sat, Jan 08, 2011 at 11:43:17PM +0100, Pieter Verberne wrote:
> Actually, obsd.img is empty. I'm trying to start a fresh installation.
> And, I should be able to see BIOS messages like "Starting SeaBIOS"
> and "Booting from" anyway, right?
Wrong. The BIOS doesn't print those messages to the ser
On Sat, Jan 08, 2011 at 09:50:36PM +0100, Pieter Verberne wrote:
> On Sat, 8 Jan 2011 21:03:56 +0100, Henning Brauer wrote:
> >* Pieter Verberne [2011-01-08 17:23]:
> >>I'm not sure if it is a good idea (or even possible) but I'm
> >>trying to
> >>run OpenBSD as guest in qmemu on a Soerkis and Ope
On Sat, Jan 08, 2011 at 09:50:36PM +0100, Pieter Verberne wrote:
>lilium$ qemu -no-kqemu -nographic -serial stdio obsd.img
>[this time no "could not open serial device 'stdio'" error, but no
>further output. Is there any way to catch the output?]
>
>lilium$ qemu -no-kqemu -nographic -serial
>telnet
* Pieter Verberne [2011-01-08 21:53]:
> On Sat, 8 Jan 2011 21:03:56 +0100, Henning Brauer wrote:
> >* Pieter Verberne [2011-01-08 17:23]:
> >>Hello,
> >>
> >>I'm not sure if it is a good idea (or even possible) but I'm
> >>trying to
> >>run OpenBSD as guest in qmemu on a Soerkis and OpenBSD as ho
On Sat, 8 Jan 2011 21:03:56 +0100, Henning Brauer wrote:
* Pieter Verberne [2011-01-08 17:23]:
Hello,
I'm not sure if it is a good idea (or even possible) but I'm trying
to
run OpenBSD as guest in qmemu on a Soerkis and OpenBSD as host. A
Soekris has no graphic capabilities so I need to run
* Pieter Verberne [2011-01-08 17:23]:
> Hello,
>
> I'm not sure if it is a good idea (or even possible) but I'm trying to
> run OpenBSD as guest in qmemu on a Soerkis and OpenBSD as host. A
> Soekris has no graphic capabilities so I need to run qemu in nographic
> mode. I'm not able to do that un
On 12/06/10 10:40, Stuart Henderson wrote:
On 2010-12-05, Frank Bax wrote:
After my cdrom arrived; I upgraded to 4.8 -release soon after packages
became available online. I don't use qemu often; but when I tried to
run it after upgrade; I get core dump. I don't use kqemu.
I invoke qemu using
On 2010-12-05, Frank Bax wrote:
> After my cdrom arrived; I upgraded to 4.8 -release soon after packages
> became available online. I don't use qemu often; but when I tried to
> run it after upgrade; I get core dump. I don't use kqemu.
> I invoke qemu using same options (saved in file) as work
On 12/05/10 15:58, Frank Bax wrote:
After my cdrom arrived; I upgraded to 4.8 -release soon after packages
became available online. I don't use qemu often; but when I tried to run
it after upgrade; I get core dump. I don't use kqemu.
I invoke qemu using same options (saved in file) as worked in 4
On Sun, Sep 12, 2010 at 04:28:25PM +0200, Elmar Bschorer wrote:
> hi list,
>
> I tried to install ubuntu with qemu as neither jconsole nor skype
> with emulation do work on openbsd 4.7 :-(
You are using the wrong operating system for the job. Don't.
There are plenty of Linux distros out there.
> There is nothing (..noticeable) wrong with 0.9.x of QEMU, you just
> won't be getting any fancy features.
The os i had to test was not able to run with 0.9 but does with 10.6 .
This more than a fancy feature for me :))
> Compiling a semi-usable version of QEMU is easy, but that's not the
> poi
The later versions of QEMU no longer support kqemu at all, was removed.
I've had chats with the maintainer (Todd Fries), but so far it seems
that newer versions of QEMU are just not stable enough yet.. exposing
compiler/optimization bugs and generally just sucking badly.
There is nothing (..notic
No it didn't work. It had the illusion of working in i386 UP but that
could also be made to crash.
On Thu, Apr 01, 2010 at 05:48:34AM +0200, Johan SANCHEZ wrote:
> On Wed, 31 Mar 2010 17:40:42 -0500
> Marco Peereboom wrote:
>
> > kqemu is shite; i would like a new qemu version though...
>
> Ho
On Wed, 31 Mar 2010 17:40:42 -0500
Marco Peereboom wrote:
> kqemu is shite; i would like a new qemu version though...
Honnestly kqemu worked really fine with 4.6 and qemu 0.9.
But i had the need for some recent features from 10.6.
Actually i can t use the kqemu module but i should be able to run
kqemu is shite; i would like a new qemu version though...
On Wed, Mar 31, 2010 at 10:25:35PM +0200, Johan SANCHEZ wrote:
> Hi list,
>
> I did have succesfully built QEMU 0.10.6
> with no particular tweaking once gcc 4.3
> is installed.
>
> QEMU PC emulator version 0.10.6, Copyright (c) 2003-2008
On Wed, Mar 31, 2010 at 15:25, Johan SANCHEZ wrote:
> Hi list,
>
> I did have succesfully built QEMU 0.10.6
> with no particular tweaking once gcc 4.3
> is installed.
>
> QEMU PC emulator version 0.10.6, Copyright (c) 2003-2008 Fabrice Bellard
>
> However yet i was not able to compile the accelera
On Mon, Jun 08, 2009 at 04:20:43PM +0300, What you get is Not what you see
wrote:
> Hi
> I have an old P2 box with Openbsd 4.1 on it. I compiled qemu from
> ports and want to use freenas on it.
> I installed freenas and made it work. To make freenas available on
> network I needed to open some por
2009/5/27 Christopher J. Gibbons :
>
> I found this in the README.OpenBSD for QEMU to be most helpful when doing a
> similar sort of thing (plus you get the bonus of not having to run QEMU
> as root):
>
> $ sudo sh -c "sudo -u $USER qemu -nographic -net nic -net tap,fd=3 \
> B B B B B B -no-f
On 05/26/2009 at 11:05PM, Sunnz wrote:
> And I have pass quick on {tun0 tun1 tun2} in pf.conf, so it is not the
> firewall blocking it.
>
I found this in the README.OpenBSD for QEMU to be most helpful when doing a
similar sort of thing (plus you get the bonus of not having to run QEMU
as root):
And I have pass quick on {tun0 tun1 tun2} in pf.conf, so it is not the
firewall blocking it.
Ok, based on some other feedback from Stuart, here is a new diff to test
that should work better ;-)
--- emulators/qemu/files/qemu-ifup
+++ emulators/qemu/files/qemu-ifup
@@ -16,16 +16,19 @@ echo -n " {$1 ($BRIDGE <-> $ETHER)"
# Set the tun device into layer2 mode
$SUDO ifconfig $1 link0 up
+#
See if this works any better.
--- emulators/qemu/files/qemu-ifup
+++ emulators/qemu/files/qemu-ifup
@@ -16,6 +16,15 @@ echo -n " {$1 ($BRIDGE <-> $ETHER)"
# Set the tun device into layer2 mode
$SUDO ifconfig $1 link0 up
+# setup up $ETHER incase it wasn't created before
+if ! ifconfig $ETHER >
And you are smart enough to fix it ;-)
It is ugly to see it fly by.
On Thu, Dec 04, 2008 at 06:39:50AM -0600, [EMAIL PROTECTED] wrote:
> Yes, the error is the 1st time said bridge is created. Call it a wart. ;-)
> --
> Todd Fries .. [EMAIL PROTECTED]
>
> __
Yes, the error is the 1st time said bridge is created. Call it a wart. ;-)
--
Todd Fries .. [EMAIL PROTECTED]
_
| \ 1.636.410.0632 (voice)
| Free Daemon Consulting, LLC \ 1.405.227.9094 (vo
Hi Todd:
You asked for feedback. Most of the time; qemu produces:
{tun0 (bridge0 <-> em0)}
But sometimes it produces:
{tun0 (bridge0 <-> em0)brconfig: bridge0: No such process
brconfig: bridge0: No such process
}
Network access still works, despite the error message.
Frank
On 2008-Nov-0
Todd T. Fries wrote:
Just out of curiosity, humor me, run qemu as root with the following added
options:
-net nic,vlan=0 -net tap,vlan=0
I've observed that at some point user mode networking has started segv'ed on
amd64 when running any qemu guest, and am sorry to report I have not yet
Just out of curiosity, humor me, run qemu as root with the following added
options:
-net nic,vlan=0 -net tap,vlan=0
I've observed that at some point user mode networking has started segv'ed on
amd64 when running any qemu guest, and am sorry to report I have not yet
tracked down the source
On Mon, Nov 3, 2008 at 9:07 PM, Frank Bax <[EMAIL PROTECTED]> wrote:
> I've been using qemu to run a Win98 guest on i386 host for about a year. On
> Aug.2, I installed an i386 snapshot that was a few days old. Since then,
> I've been running a Win98 guest on qemu-0.9.1p3 with no issues.
>
> Somet
On Thu, Oct 25, 2007 at 11:03:56AM -0200, Marcus Andree wrote:
> comments inline.
>
> On 10/25/07, Michael <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > thanks for your fast answer.
> >
> > Marcus Andree schrieb:
> > > Maybe you'll have to compile a new kernel. There's an options(4) option
> > > call
On Thu, Oct 25, 2007 at 10:37:32AM -0200, Marcus Andree wrote:
> On 10/25/07, Michael <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I've tried to run 5 QEMU guests simultanously but when trying to start
> > the 5th I'll get the following error message:
> >
> > warning: could not open /dev/tun7 (No suc
comments inline.
On 10/25/07, Michael <[EMAIL PROTECTED]> wrote:
> Hi,
>
> thanks for your fast answer.
>
> Marcus Andree schrieb:
> > Maybe you'll have to compile a new kernel. There's an options(4) option
> > called tun. I had to add something like
> >
> > pseudo-device tun 16
>
> I read som
On 10/25/07, Michael <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've tried to run 5 QEMU guests simultanously but when trying to start
> the 5th I'll get the following error message:
>
> warning: could not open /dev/tun7 (No such file or directory): no
> virtual network emulation
> Could not initialize d
Hi,
thanks for your fast answer.
Marcus Andree schrieb:
> Maybe you'll have to compile a new kernel. There's an options(4) option
> called tun. I had to add something like
>
> pseudo-device tun 16
I read something while googling for this issue that you had to add
something like that for old
On 10/5/07, Nick Guenther <[EMAIL PROTECTED]> wrote:
> I'm curious: in principle, would it be possible to use lkm(4) in
> OpenBSD to get the same effect? Presumably it would mean a lot of
> porting, but is there something fundamentally different about BSD from
> Linux here?
it's possible.
You can't run java on what?
I use java every day for citrix so that I don't have to run a windows
machine at work at all. Works fine for me.
On Thu, Oct 04, 2007 at 03:50:13PM -0700, Allie D. wrote:
> I'm bitter because I can't run java on it. I have to use ubuntu with
> VirtualBox to run some c
On 10/5/07, Gerald Thornberry <[EMAIL PROTECTED]> wrote:
> On 10/4/07, Jacob Yocom-Piatt <[EMAIL PROTECTED]> wrote:
> > Gerald Thornberry wrote:
> > > I've never used QEMU so I may be talking out my hat. Looking at the
> > > docs for it yesterday I remember seeing something about the QEMU
> > > ac
On 10/5/07, Gerald Thornberry <[EMAIL PROTECTED]> wrote:
> I've been informed that I was talking out of my hat, as I suspected.
> KQEMU (QEMU accelerator) is a Linux kernel module and, therefore, not
> an option for the OpenBSD. I'll put my hat back on my head now.
For whatever it's worth, I had
I've been informed that I was talking out of my hat, as I suspected.
KQEMU (QEMU accelerator) is a Linux kernel module and, therefore, not
an option for the OpenBSD. I'll put my hat back on my head now.
On 10/4/07, Jacob Yocom-Piatt <[EMAIL PROTECTED]> wrote:
> Gerald Thornberry wrote:
> > I've n
I'm bitter because I can't run java on it. I have to use ubuntu with
VirtualBox to run some critical work apps that use java :(
--
~Allie D.
On Thu, October 4, 2007 15:41, Jacob Yocom-Piatt wrote:
> Gerald Thornberry wrote:
>> I've never used QEMU so I may be talking out my hat. Looking at the
1 - 100 of 125 matches
Mail list logo
