This is just an FYI about my attempt to use
FreeBSD-11.0-RELEASE-arm64-aarch64.raw under Ubuntu's qemu on an odroid-c2.
(This is my first ever use of qemu. I've no clue about how well the qemu for
this context works --or how well for any other context.)
Context of use of FreeBSD 11
My first try at building qemu (really emulators/qemu-devel ) and trying to use
it. What I tried turns out to not work:
CAM status: Command timeout
and related material result.
Context for the below amd64 FreeBSD 11.0-BETA3 -r303469 running under
VirtualBox 5.0.26 r108824 on Mac OS X 10.11.6
Hello,
When i try to run FreeBSD-9.0-RELEASE-amd on more than 1 vcpu in
quemu-kvm (Fedora Core 17) eg. with:
qemu-kvm -m 1024m -cpu host -smp 2 -cdrom
/storage/iso/FreeBSD-9.0-RELEASE-amd64-dvd1.iso
it freezes KVM with:
KVM internal error. Suberror: 1
emulation failure
RAX
Hello,
When i try to run FreeBSD-9.0-RELEASE-amd on more than 1 vcpu in
quemu-kvm (Fedora Core 17) eg. with:
qemu-kvm -m 1024m -cpu host -smp 2 -cdrom
/storage/iso/FreeBSD-9.0-RELEASE-amd64-dvd1.iso
it freezes KVM with:
KVM internal error. Suberror: 1
emulation failure
RAX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/07/2012 03:37, Richard Yao wrote:
>> Can you boot FreeBSD kernel on this machine bare ?
> This machine is headless. It would be difficult for me to boot FreeBSD
> on it.
>
Not necessarily useful now, but for future reference I've found
pxebootin
t;>>
> >>> Trying to install FreeBSD 9.1 Beta 1 in qemu-kvm on Gentoo Linux fails
> >>> before the kernel dmesg with 'kernel trap 9 with interrupts disabled'. I
> >>> am running the following command:
> >>>
> >>> qemu-system-x
On 07/20/2012 08:56 PM, Konstantin Belousov wrote:
> On Fri, Jul 20, 2012 at 08:40:30PM -0400, Richard Yao wrote:
>> On 07/20/2012 06:23 PM, Richard Yao wrote:
>>> Dear FreeBSD Developers,
>>>
>>> Trying to install FreeBSD 9.1 Beta 1 in qemu-kvm on Gentoo Lin
On Fri, Jul 20, 2012 at 08:40:30PM -0400, Richard Yao wrote:
> On 07/20/2012 06:23 PM, Richard Yao wrote:
> > Dear FreeBSD Developers,
> >
> > Trying to install FreeBSD 9.1 Beta 1 in qemu-kvm on Gentoo Linux fails
> > before the kernel dmesg with 'kernel trap 9 wit
On 07/20/2012 06:23 PM, Richard Yao wrote:
> Dear FreeBSD Developers,
>
> Trying to install FreeBSD 9.1 Beta 1 in qemu-kvm on Gentoo Linux fails
> before the kernel dmesg with 'kernel trap 9 with interrupts disabled'. I
> am running the following command:
>
> q
Dear FreeBSD Developers,
Trying to install FreeBSD 9.1 Beta 1 in qemu-kvm on Gentoo Linux fails
before the kernel dmesg with 'kernel trap 9 with interrupts disabled'. I
am running the following command:
qemu-system-x86_64 -drive
file=/dev/zvol/rpool/KVM/freebsd,if=scsi-bootorder=c
> I see something unusual and surprising for me: if I kldload aio for
> qemu's sake
> and then actually start qemu, I see that share of C2 in cx_usage is
> constantly
> dropping and then finally there is "too many short sleeps, backing off
> to C1".
>
> This
on 26/02/2009 18:27 Paul B. Mahol said the following:
> On 2/26/09, Andriy Gapon wrote:
>> I see something unusual and surprising for me: if I kldload aio for qemu's
>> sake
>> and then actually start qemu, I see that share of C2 in cx_usage is
>> constantly
>&
On 2/26/09, Andriy Gapon wrote:
>
> I see something unusual and surprising for me: if I kldload aio for qemu's
> sake
> and then actually start qemu, I see that share of C2 in cx_usage is
> constantly
> dropping and then finally there is "too many short sleeps, backi
I see something unusual and surprising for me: if I kldload aio for qemu's sake
and then actually start qemu, I see that share of C2 in cx_usage is constantly
dropping and then finally there is "too many short sleeps, backing off to C1".
This is on i386 with stable/7 as of r18811
From: bazzoola <[EMAIL PROTECTED]>
Subject: Auto bridge for qemu network [was: kqemu support: not compiled]
Date: Thu, 15 May 2008 03:06:25 -0400
> Thanks for updating the port!
>
> I have few suggestions:
>
> #cat /etc/rc.conf
> [...]
> #KQEMU for qemu
> kqemu
From: bazzoola <[EMAIL PROTECTED]>
Subject: Auto bridge for qemu network [was: kqemu support: not compiled]
Date: Thu, 15 May 2008 03:06:25 -0400
> Also, is it possible to update this page, it has some outdated info:
> http://people.freebsd.org/~maho/qemu/qemu.html
> *It is the
Thanks for updating the port!
I have few suggestions:
#cat /etc/rc.conf
[...]
#KQEMU for qemu
kqemu_enable="YES"
#Bridge for qemu
cloned_interfaces="bridge0"
ifconfig_bridge0="up addm sk0"
autobridge_interfaces="bridge0"
autobridge_bridge0=&quo
The amd64 version of -BETA4 doesn't completely boot under
qemu-system-x86_64 -- it hangs while trying to mound md0 as
root. The i386 version of -BETA4 does work under
qemu-system-x86_64.
Note that if you want to try this, use the -no-kqemu switch
as kqemu with the 64 bit qemu crashes the s
___
Windows as a desktop?
Feliks Dzerzhinsky is no doubt smirking from some place with uncommonly hot
weather.
;-)
Better to put it in a Qemu instance. Without networking.
Bill
___
freebsd-stable
On Sat, Dec 08, 2007 at 07:41:04PM +, ? Bill Hacker wrote:
> The ability to build from source and have access to source, is prized among
> the experienced not so much because we fear hidden 'gotcha's from the
> malicious or even proprietary vendor lock-in - but more for the ability t
Eugene Grosbein wrote:
David Wood <[EMAIL PROTECTED]> wrote:
It's your choice, but from a security perspective, this worries me.
You will have applications you are using linked against FreeBSD
libraries that no longer have any FreeBSD security team support.
[skip]
The definite need to keep
On Sat, Dec 08, 2007 at 05:38:14PM +, ? Bill Hacker wrote:
> Agree the need to keep ports (and everything) as current as is practical.
> Rebuilding frequently is unavoidable.
There is no such need for me; I do not rebuild what ain't broken
within the environment and tasks it was insta
David Wood <[EMAIL PROTECTED]> wrote:
> It's your choice, but from a security perspective, this worries me.
>
> You will have applications you are using linked against FreeBSD
> libraries that no longer have any FreeBSD security team support.
[skip]
The definite need to keep the system secure i
[ Library incompatiblity problems between major FreeBSD releases ]
One of the things that should make life a little easier in
FreeBSD 7.0 and subsequent (-current, 8.x, etc) is that we
now have symbol versioning in some of our libraries. The
libraries that have caused the most problems in the pa
David Wood wrote:
[cc line trimmed]
*useful but already posted details trimmed*
Agree the need to keep ports (and everything) as current as is practical.
Rebuilding frequently is unavoidable.
portupgrade -af can be somewhat painful on systems with plenty of ports
installed.
But portupgra
[cc line trimmed]
In message <[EMAIL PROTECTED]>, Eugene Grosbein
<[EMAIL PROTECTED]> writes
I know. I will never 'rebuild all ports', I don't think that's Right Thing.
I've upgraded once from 4.11-STABLE to 6.0-RELEASE (binary upgrade
over existing system) and all ports worked nice, including
On Sat, Dec 08, 2007 at 10:43:41PM +0700, Eugene Grosbein wrote:
> On Sat, Dec 08, 2007 at 09:37:12AM -0500, Daniel Eischen wrote:
> > Please reread my original reply to you. If you are going to be
> > rebuilding or installing new ports, then you really need to do
> > a portupgrade -af. The same
On Sat, Dec 08, 2007 at 09:37:12AM -0500, Daniel Eischen wrote:
> Please reread my original reply to you. If you are going to be
> rebuilding or installing new ports, then you really need to do
> a portupgrade -af. The same thing may happen again for some
> other library.
I know. I will never '
On Sat, 8 Dec 2007, Eugene Grosbein wrote:
On Sat, Dec 08, 2007 at 01:09:47PM +0700, Eugene Grosbein wrote:
Thank you. Now I wonder, how such thing may happen
if qemu was built under 6.2 where there were no
libthr.so.3 and libc.so.7?
Most likely, you have rebuilt some library that brough in
On Sat, Dec 08, 2007 at 01:09:47PM +0700, Eugene Grosbein wrote:
> > > Thank you. Now I wonder, how such thing may happen
> > > if qemu was built under 6.2 where there were no
> > > libthr.so.3 and libc.so.7?
> > Most likely, you have rebuilt some librar
ibraries that are linked to multiple FreeBSD library versions
> > (e.g., libc.so.6 and libc.so.7, libthr.so.2 and libthr.so.3,
> > etc) and that doesn't work and is not supported.
>
> But I do not see this:
>
> # ldd `which qemu`
> /usr/local/bin/qemu:
>
;
> > [skip]
> >
> > > > libthr.so.3 => /lib/libthr.so.3 (0x48546000)
> > > RELENG_7 libpthread
> > > > libc.so.7 => /lib/libc.so.7 (0x48558000)
> > > RELENG_7 libc
> >
> > Thank you. Now I wonder, how such thing
On Sat, Dec 08, 2007 at 12:55:37PM +0700, Eugene Grosbein wrote:
> On Sat, Dec 08, 2007 at 07:45:52AM +0200, Kostik Belousov wrote:
>
> > > But I do not see this:
> > >
> > > # ldd `which qemu`
> > > /usr/local/bin/qemu:
>
> [skip]
>
> >
On Sat, Dec 08, 2007 at 07:45:52AM +0200, Kostik Belousov wrote:
> > But I do not see this:
> >
> > # ldd `which qemu`
> > /usr/local/bin/qemu:
[skip]
> > libpthread.so.2 => /lib/libpthread.so.2 (0x481f5000)
> RELENG_6 libpthread
> > libc.so.6
d now: install compat-6x port and ran "make delete-old-libs",
no change - the same error (ldd shows, that qemu uses libs
from /usr/local/lib/compat now).
Eugene Grosbein
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
nd libc.so.7, libthr.so.2 and libthr.so.3,
> etc) and that doesn't work and is not supported.
But I do not see this:
# ldd `which qemu`
/usr/local/bin/qemu:
libm.so.4 => /lib/libm.so.4 (0x4815c000)
libz.so.3 => /lib/libz.so.3 (0x48172000)
libSDL.so.11 =>
make delete-old-libs"?
Did you install compat-6x?
compiled in. However, qemu-0.8.2s.20061225_1 stopped to work,
Seems to be a rather old qemu version...
it dumps core when started with an error:
Fatal error 'Cannot allocate red zone for initial thread' at line 384 in
file
Did you install compat-6x?
> compiled in. However, qemu-0.8.2s.20061225_1 stopped to work,
Seems to be a rather old qemu version...
> it dumps core when started with an error:
> Fatal error 'Cannot allocate red zone for initial thread' at line 384 in
> file /usr/local/obj/src/lib
Hi!
There is FreeBSD box that was 6.2-STABLE before, now it became
7.0-BETA3 via source upgrade. The kernel has 'options COMPAT_FREEBSD6'
compiled in. However, qemu-0.8.2s.20061225_1 stopped to work,
it dumps core when started with an error:
Fatal error 'Cannot allocate red z
Gergely CZUCZY wrote:
Hello,
I'm trying to set up a qemu with 4G memory to the host system
on a 7-BETA2, and I've hit some kind of limit in freebsd.
When i give more then ~2000MB of memory to qemu, it returns
an after trying to mmap() it, saying "Could not map physical memory&q
Guy Helmer wrote:
Gergely CZUCZY wrote:
Hello,
I'm trying to set up a qemu with 4G memory to the host system
on a 7-BETA2, and I've hit some kind of limit in freebsd.
When i give more then ~2000MB of memory to qemu, it returns
an after trying to mmap() it, saying "Could n
On Mon, Nov 26, 2007 at 08:59:12AM -0600, Guy Helmer wrote:
> Gergely CZUCZY wrote:
> >Hello,
> >
> >I'm trying to set up a qemu with 4G memory to the host system
> >on a 7-BETA2, and I've hit some kind of limit in freebsd.
> >
> >When i give more
Hello,
I'm trying to set up a qemu with 4G memory to the host system
on a 7-BETA2, and I've hit some kind of limit in freebsd.
When i give more then ~2000MB of memory to qemu, it returns
an after trying to mmap() it, saying "Could not map physical memory".
At the end of mm
inclusion on machines with untrusted local users.
options VFS_AIO
Does that warning about stability and security issues still
apply on RELENG_6? If it does, is somebody working on a
fix for that?
The problem is that recent versions of qemu seem to require
AIO (for IDE DMA). Given the above
Hi
I updated qemu to 0.8.2s.20070111, it is not stable with WinXP guest.
Qemu always quit after windox xp login'ed.
It is OK in 0.8.2s.20061225_1.
/Eric
signature.asc
Description: This is a digitally signed message part
On Fri, 2007-01-12 at 19:11 +0800, Eric L. Chen wrote:
> Hi
> I updated qemu to 0.8.2s.20070111, it is not stable with WinXP guest.
> Qemu always quit after windox xp login'ed.
> It is OK in 0.8.2s.20061225_1.
>
> /Eric
Never mind!
That's my mistake, some apps u
Has anyone gotten QEmu floppies working in FreeBSD?
I've tried booting both amd64 and i386 ISOs in qemu but the kernel does not
see the drive.
In the loader I can read files that are on the floppy image though..
Booting -v only shows..
fdc0 failed to probe at port 0xf0-0x3f5,0x3f7 irq 6
Hello,
i observe a regression running 6.0-RC1 under qemu, compared to 6.0-BETA5.
Now the ethernet card driver doesn't attach, i get
ed0: port 0xc100-0xc1FF irq 11 at device 3.0 on pci0
ed0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xc100
device_attach: ed0 attach returned 6
Under BETA
Roland Smith wrote:
> On Mon, Dec 13, 2004 at 08:03:00PM +0100, Ivan Voras wrote:
>> Is anybody running qemu successfully on 5-stable? I'm trying to boot a
>> knoppix live-cd from iso-image with:
>
> I tried to build it from ports on amd64 but the compiler segfau
On Mon, Dec 13, 2004 at 08:03:00PM +0100, Ivan Voras wrote:
> Is anybody running qemu successfully on 5-stable? I'm trying to boot a
> knoppix live-cd from iso-image with:
I tried to build it from ports on amd64 but the compiler segfaulted. :-(
So it might be interesting to know wh
Jon Noack wrote:
Roland Smith wrote:
On Mon, Dec 13, 2004 at 08:03:00PM +0100, Ivan Voras wrote:
Is anybody running qemu successfully on 5-stable? I'm trying to boot a
knoppix live-cd from iso-image with:
I tried to build it from ports on amd64 but the compiler segfaulted. :-(
So it mig
Ivan Voras wrote:
> Is anybody running qemu successfully on 5-stable? I'm trying to boot a
> knoppix live-cd from iso-image with:
>
> qemu -cdrom knoppix.iso -boot d
>
> It always reboots the computer (no core-dump, no panic, just reboot -
> and that's as user-
Is anybody running qemu successfully on 5-stable? I'm trying to boot a
knoppix live-cd from iso-image with:
qemu -cdrom knoppix.iso -boot d
It always reboots the computer (no core-dump, no panic, just reboot -
and that's as user-started process, not under root). Same thing under
X11
53 matches
Mail list logo
