On 24/07/2013 14:16, Neil Bothwick wrote:
On Wed, 24 Jul 2013 11:57:41 +0100, Kerin Millar wrote:
WARN: pretend
You have decided to compile your own SeaBIOS. This is not supported
by upstream unless you use their recommended toolchain (which you are
not). If you are intending to use
Thanks, problem solved. qemu 2.9.0-r55 did not boot, but 2.9.0-r2
did. I've got my time-sink back.
BTW, qemu 2.9.0-r55 wanted to pull in sys-firmware/edk2-ovmf and
sys-firmware/seabios. 2.9.0-r2 pulls in sys-firmware/seabios,
sys-devel/dev86, and sys-firmware/vgabios.
--
Walter Dnes
Hi,
After updating qemu-kvm to 0.13.0-r2 I get an infinite loop when running
qemu.
You can spot the loop with strace.
This problem shows on Redhat
https://bugzilla.redhat.com/show_bug.cgi?id=553689#c5
and they say that it is related to the seabios.
Does anyone have this problem too?
I'm compiling
On 24/07/13 17:50, Walter Dnes wrote:
So I emerged QEMU, which pulled in some dependancies. Things are not
going well...
1) The following warning shows up in elog...
WARN: pretend
You have decided to compile your own SeaBIOS. This is not supported
by upstream unless you use
On Wed, 24 Jul 2013 11:57:41 +0100, Kerin Millar wrote:
WARN: pretend
You have decided to compile your own SeaBIOS. This is not supported
by upstream unless you use their recommended toolchain (which you are
not). If you are intending to use this build with QEMU, realize you
So I emerged QEMU, which pulled in some dependancies. Things are not
going well...
1) The following warning shows up in elog...
WARN: pretend
You have decided to compile your own SeaBIOS. This is not supported
by upstream unless you use their recommended toolchain (which you
to the seabios.
Does anyone have this problem too?
I'm compiling qemu-kvm with hardend flag.
I've been using app-emulation/qemu-kvm-0.13.0-r2 since early March. I
have not had that problem, but I do not use the hardened flag.
://bugzilla.redhat.com/show_bug.cgi?id=553689#c5
and they say that it is related to the seabios.
Does anyone have this problem too?
I'm compiling qemu-kvm with hardend flag.
I've been using app-emulation/qemu-kvm-0.13.0-r2 since early March. I
have not had that problem, but I do not use
that it is related to the seabios.
Does anyone have this problem too?
I'm compiling qemu-kvm with hardend flag.
Regards,
Kfir
When I run qemu -no-kvm things work as expected under hardened kernel.
Using regular kernel (none hardened) qemu works ok.
So, the problem is running qemu under hardened
- - screen : Enable support for running domain U
console in an app-misc/screen session
- - static-libs : Build static versions of dynamic
libraries as well
- - system-qemu : Using app-emulation/qemu instead of the
bundled one
- - system-seabios
in an app-misc/screen session
- - static-libs : Build static versions of dynamic
libraries as well
- - system-qemu : Using app-emulation/qemu instead of the
bundled one
- - system-seabios : Using sys-firmware/seabios instead of
the bundled one
moonflo ~ #
So
for running domain U
console in an app-misc/screen
session
- - static-libs : Build static versions of dynamic
libraries as well
- - system-qemu : Using app-emulation/qemu instead of
the bundled one
- - system-seabios : Using sys
On 24/07/2013 10:50, Walter Dnes wrote:
So I emerged QEMU, which pulled in some dependancies. Things are not
going well...
1) The following warning shows up in elog...
WARN: pretend
You have decided to compile your own SeaBIOS. This is not supported
by upstream unless you use
of the
bundled one
- - system-seabios : Using sys-firmware/seabios instead of
the bundled one
moonflo ~ #
So there is no such flag. Apparently my installation is missing
'hvmloader', and I'm guessing that I would have that if I could enable
the 'hmv' USE flag.
How do I enable a USE flag
://bugzilla.redhat.com/show_bug.cgi?id=553689#c5
and they say that it is related to the seabios.
Does anyone have this problem too?
I'm compiling qemu-kvm with hardend flag.
I've been using app-emulation/qemu-kvm-0.13.0-r2 since early March. I
have not had that problem, but I do not use
qemu.
You can spot the loop with strace.
This problem shows on Redhat
https://bugzilla.redhat.com/show_bug.cgi?id=553689#c5
and they say that it is related to the seabios.
Does anyone have this problem too?
I'm compiling qemu-kvm with hardend flag.
Regards,
Kfir
When I run qemu -no-kvm
toying with the idea of replacing BIOS/UEFI with coreboot/seabios
but time is lacking... :-(
For the record, I've always felt BIOS have been slow...
(OTOH, going from grub to login in 5 seconds - that suggests to me that
you're using an SSD and not a hard-drive).
I recently bought 4 SSDs
- - system-seabios : Using sys-firmware/seabios instead of
the bundled one
moonflo ~ #
So there is no such flag. Apparently my installation is missing
'hvmloader', and I'm guessing that I would have that if I could enable
the 'hmv' USE flag.
How do I enable a USE flag that doesn't
: Enable support for running domain U
console in an app-misc/screen session
- - static-libs : Build static versions of dynamic
libraries as well
- - system-qemu : Using app-emulation/qemu instead of the
bundled one
- - system-seabios : Using sys-firmware
that it is related to the seabios.
Does anyone have this problem too?
I'm compiling qemu-kvm with hardend flag.
Regards,
Kfir
when running 'strace qemu' I get this line:
read(11, 0xbf10ae5c, 128) = -1 EAGAIN (Resource temporarily
unavailable)
This seems related to hardened.
paxctl
Thanks to all who replied. sys-firmware/seabios needed the binary
flag and sys-firmware/ipxe needed the qemu and vmware flags. It's
starting now, and most of my problems are solved.
I still have permission problems as a regular user with qemu-kvm, but
qemu-system-i386 works. Root can start
On 25/07/2013 04:24, Walter Dnes wrote:
Thanks to all who replied. sys-firmware/seabios needed the binary
flag and sys-firmware/ipxe needed the qemu and vmware flags. It's
starting now, and most of my problems are solved.
I still have permission problems as a regular user with qemu-kvm
=
app-emulation/xen-tools-4.5.1-r1::gentoo was built with the following:
USE=pam -api -custom-cflags -debug -doc -flask (-hvm) (-ocaml) -ovmf
-pygrub -python -qemu -screen -static-libs -system-qemu -system-seabios
PYTHON_TARGETS=python2_7
CFLAGS=
CXXFLAGS=-O2 -pipe -march=native -fomit-frame
-flask (-hvm) (-ocaml) -ovmf
-pygrub -python -qemu -screen -static-libs -system-qemu -system-seabios
PYTHON_TARGETS=python2_7
CFLAGS=
CXXFLAGS=-O2 -pipe -march=native -fomit-frame-pointer
-fno-strict-overflow
LDFLAGS=
Were you able to start any virtual machine in your Xen environment yet
24 matches
Mail list logo
