Please disregard the `# Test a coworkaround` stuff in comment #1, bad
copypasta, too late at night ;-)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1913012
Title:
Installed firmware descriptor fil
** Description changed:
After building and installing QEMU, the resulting installed firmware
descriptor files contain relative paths for their `mapping.filename`
- properties. These relative paths will not be accepted as valid by tools
- like `virt-install`, resulting in the inability to confi
** Description changed:
After building and installing QEMU, the resulting installed firmware
descriptor files contain relative paths for their `mapping.filename`
properties. These relative paths will not be accepted as valid by tools
like `virt-install`, resulting in the inability to confi
I think this needs to be fixed in QEMU source. The `configure_file()`
action needs both an absolute path for `configuration` (to substitute
into the descriptor files) _and_ a relative path for use with the
`install_dir` keyword argument.
--
You received this bug notification because you are a mem
There is an issue on Void Linux packages issue tracker about this bug[1]
# Steps to verify the issue on a fresh Git clone of QEMU source
$ git clone https://github.com/qemu/qemu
$ cd qemu
$ make DEBUG=1 docker-test-misc@alpine
[...]
COPYRUNNER
RUN test-misc in qemu/alpine
* Prepared to
Public bug reported:
Unless the Qemu build is configured using `./configure --datadir=
where is some absolute path which is a subdirectory of ,
the resulting installed firmware descriptor files contain relative paths
for their `mapping.filename` properties. These relative paths will not
be accept
If it is decided to retain the change, please do consider adding a
commandline option to enable debugging Real mode code after `set
architecture i8086`, even if this requires the GDB workaround previously
mentioned. Thanks in advance.
--
You received this bug notification because you are a member
Public bug reported:
OS: Void Linux x86_64 (glibc)
QEMU version: 2.9.0
GDB version: 7.12.1
Problem description:
After I updated QEMU from version 2.8.1 to 2.9.0, I found that when I try to
connect GDB to a running QEMU and try to debug Real mode machine code, I can no
longer set architecture t
On my system, `qemu` is an alias for `qemu-system-x86_64`.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1451067
Title:
-smb option requires full path for Samba sharing to work
Status in QEMU:
N
Public bug reported:
This issue has been reported on qemu-devel a looong time ago:
https://lists.gnu.org/archive/html/qemu-devel/2005-12/msg00141.html
QEMU version 2.2.1-4 on Arch Linux x86_64
Steps to reproduce:
host$ mkdir share
host$ chmod o+rwx share
host$ qemu -smb share
vm$ smbclient //
10 matches
Mail list logo
