Age | Commit message (Collapse) | Author | Files | Lines |
|
Now the binary format setup will not be overwritten if it matches with
the one needed for build.
This change will prevent build failures caused by race condition during
"Runscripts:" phase of the package for host setups with single Linux
kernel and multiple Tizen buildroots for single architecture.
Change-Id: I66a9b1319fc951d6b392533207373c69af12d2cb
Signed-off-by: Vyacheslav Barinov <v.barinov@samsung.com>
|
|
Change-Id: Iead1a06555abcd46e348a62213386e6b4b5ace44
|
|
These files were imported from OpenSUSE OBS with this package
and are no longer used.
Change-Id: Ifd063afa1cccc7145f798f68ffd95bda476ef9a4
|
|
Symlinks to qemu binaries placed in directories where they are searched by
common non-Tizen binfmt_misc configurations (eq. in Ubuntu).
Change-Id: I6b8602736926dba24a7ffbc70c91222ec3ba5cc8
|
|
1. Rename exported binary, now binaries with identical names are
installed in all builroots with acceleration
2. Set binfmt from postinstall script. This fixes wrong binfmt installed
in OBS environment and allows us to run build on systems with different
binfmt installed
Change-Id: I0fb82b261b61f2246447de4f6dd382e9996a3932
|
|
This allows removing hardcoded architecture-dependent paths
from qemu-accel package. Also allows using symlinks for qemu-*-binfmt
as path don't depend on binary name now.
Change-Id: I92b9bc6df477ef925c761045d5307aca8cc1b2d4
|
|
Change-Id: Ic74232f69e1f424628318e478eff83917b1a4e1d
|
|
Change-Id: I48a2236de35beb5d5f63c1d585aad8629cb9d93b
|
|
Change-Id: Id8c1a48311e6d3a4d5bc210154d00dad951379c4
|
|
Change-Id: I8f8a481a6bd0477875b1a29f580445e6eb815a4e
|
|
Change-Id: I56ca7e23968a8fc80fbf3390f9c730d0fdb31c9f
|
|
This reverts commit a82e4a19e88da9bccb1fb539f66298a7e3b8cac6.
This revert commit harms stability of GBS build and may cause hang in OBS build.
Change-Id: I017d6accb0bcc7b2b2df662590ed05b81b82f28c
|
|
This reverts commit 0bcc4adb9792b7a446494b6494e13a0d109eb45a.
Change-Id: I8e382f6eae453dbabb3be20df5568db31a013734
Signed-off-by: Jongwoo Chae <jongwoo.chae@samsung.com>
|
|
The second and fourth argument are in/out parameters, store them back
after the syscall. Also, the fourth argument was mishandled, and EFAULT
handling was missing.
Change-Id: I625ecd4dc3e53b8025585727439f1112c38d1758
Patch-Url: https://www.mail-archive.com/qemu-devel@nongnu.org/msg277687.html
Signed-off-by: Stephane Desneux <stephane.desneux@open.eurogiciel.org>
|
|
According to official standard POSIX.1-2001. pread64 and pwrite64
should return 0 for zero-length buffers as mentioned at
http://pubs.opengroup.org/onlinepubs/009695399/functions/read.html
http://pubs.opengroup.org/onlinepubs/009695399/functions/write.html
Change-Id: Icd66ea29658329fbd5e6461d1def0c78c81d2671
Signed-off-by: Ilya Palachev <i.palachev@samsung.com>
|
|
|
|
Change-Id: Iea5fef506730b3cb66de0d3317986e9a2986b723
Signed-off-by: Ilya Palachev <i.palachev@samsung.com>
|
|
Change-Id: Ia866ea808806ce4b49d64522c3d2f299d49a32be
Signed-off-by: Vyacheslav Barinov <v.barinov@samsung.com>
|
|
Change-Id: I75487486c632fb377032ab3f7167cd4c01bfc20c
Signed-off-by: Vyacheslav Barinov <v.barinov@samsung.com>
|
|
Otherwise the build fails at the execution of the %packagind section:
[ 662s] error: Installed (but unpackaged) file(s) found:
[ 662s] /usr/bin/qemu-ppc64le
Change-Id: Iae46712a3a94893e99516972d5163a83897bb41b
Signed-off-by: Ilya Palachev <i.palachev@samsung.com>
|
|
This patch adds packaging files to build with GBS and rpmbuild.
Change-Id: I1cb93997635a28b91a489dbe77d306e6ac684581
Signed-off-by: Chanho Park <chanho61.park@samsung.com>
|
|
Change-Id: I75ecb5ef6952d1083c030f5e48ba2a24e4d6f4a1
Signed-off-by: Junfeng Dong <junfeng.dong@intel.com>
|
|
This is caused by a linux/xattr.h and sys/xattr.h incompatibility:
In file included from /home/snoonan/Development/qemu/include/qemu/xattr.h:27:0,
from fsdev/virtfs-proxy-helper.c:25:
/usr/include/sys/xattr.h:31:3: error: expected identifier before numeric constant
XATTR_CREATE = 1, /* set value, fail if attr already exists. */
^
/home/snoonan/Development/qemu/qemu/rules.mak:25: recipe for target 'fsdev/virtfs-proxy-helper.o' failed
Moving the include around resolves it.
Change-Id: I8242070c18a511e62877d57564a7ad754a8f14c8
Signed-off-by: Steven Noonan <snoonan@amazon.com>
Cc: Anthony Liguori <aliguori@amazon.com>
|
|
Change from 5 to 15 seconds.
Signed-off-by: Andreas Färber <afaerber@suse.de>
|
|
Signed-off-by: Dinar Valeev <dvaleev@suse.com>
[AF: Rebased for v1.7]
Signed-off-by: Andreas Färber <afaerber@suse.de>
|
|
Fixes the build on SLE 11 SP2.
[AF: Extend to ppc64]
|
|
When doing lseek, SEEK_SET indicates that the offset is an unsigned variable.
Other seek types have parameters that can be negative.
When converting from 32bit to 64bit parameters, we need to take this into
account and enable SEEK_END and SEEK_CUR to be negative, while SEEK_SET stays
absolute positioned which we need to maintain as unsigned.
Signed-off-by: Alexander Graf <agraf@suse.de>
|
|
Virtio-Console can only process one character at a time. Using it on S390
gave me strage "lags" where I got the character I pressed before when
pressing one. So I typed in "abc" and only received "a", then pressed "d"
but the guest received "b" and so on.
While the stdio driver calls a poll function that just processes on its
queue in case virtio-console can't take multiple characters at once, the
muxer does not have such callbacks, so it can't empty its queue.
To work around that limitation, I introduced a new timer that only gets
active when the guest can not receive any more characters. In that case
it polls again after a while to check if the guest is now receiving input.
This patch fixes input when using -nographic on s390 for me.
|
|
Some termcaps (found using SLES11SP1) use [? sequences. According to man
console_codes (http://linux.die.net/man/4/console_codes) the question mark
is a nop and should simply be ignored.
This patch does exactly that, rendering screen output readable when
outputting guest serial consoles to the graphical console emulator.
Signed-off-by: Alexander Graf <agraf@suse.de>
|
|
|
|
|
|
Tar is a very widely used format to store data in. Sometimes people even put
virtual machine images in there.
So it makes sense for qemu to be able to read from tar files. I implemented a
written from scratch reader that also knows about the GNU sparse format, which
is what pigz creates.
This version checks for filenames that end on well-known extensions. The logic
could be changed to search for filenames given on the command line, but that
would require changes to more parts of qemu.
The tar reader in conjunctiuon with dzip gives us the chance to download
tar'ed up virtual machine images (even via http) and instantly make use of
them.
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Bruce Rogers <brogers@novell.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
[TH: Use bdrv_open options instead of filename]
Signed-off-by: Tim Hardeck <thardeck@suse.de>
[AF: bdrv_file_open got an Error **errp argument, bdrv_delete -> brd_unref]
[AF: qemu_opts_create_nofail() -> qemu_opts_create(),
bdrv_file_open() -> bdrv_open(), based on work by brogers]
[AF: error_is_set() dropped for v2.1.0-rc0]
Signed-off-by: Andreas Färber <afaerber@suse.de>
|
|
DictZip is an extension to the gzip format that allows random seeks in gzip
compressed files by cutting the file into pieces and storing the piece offsets
in the "extra" header of the gzip format.
Thanks to that extension, we can use gzip compressed files as block backend,
though only in read mode.
This makes a lot of sense when stacked with tar files that can then be shipped
to VM users. If a VM image is inside a tar file that is inside a DictZip
enabled gzip file, the user can run the tar.gz file as is without having to
extract the image first.
Tar patch follows.
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Bruce Rogers <brogers@novell.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
[TH: Use bdrv_open options instead of filename]
Signed-off-by: Tim Hardeck <thardeck@suse.de>
[AF: Error **errp added for bdrv_file_open, bdrv_delete -> bdrv_unref]
[AF: qemu_opts_create_nofail() -> qemu_opts_create(),
bdrv_file_open() -> bdrv_open(), based on work by brogers]
[AF: error_is_set() dropped for v2.1.0-rc0]
Signed-off-by: Andreas Färber <afaerber@suse.de>
|
|
Linux syscalls pass pointers or data length or other information of that sort
to the kernel. This is all stuff you don't want to have sign extended.
Otherwise a host 64bit variable parameter with a size parameter will extend
it to a negative number, breaking lseek for example.
Pass syscall arguments as ulong always.
Signed-off-by: Alexander Graf <agraf@suse.de>
|
|
Implement a few more ioctls that operate on block devices.
Signed-off-by: Alexander Graf <agraf@suse.de>
|
|
TBD (from SUSE Studio team)
|
|
TBD (from SUSE Studio team)
|
|
agraf: fiemap breaks in libarchive. Disable it for now.
|
|
Signed-off-by: Alexander Graf <agraf@suse.de>
|
|
Signed-off-by: Alexander Graf <agraf@suse.de>
|
|
Fedora 17 for ARM reads /proc/cpuinfo and fails if it doesn't contain
ARM related contents. This patch implements a quick hack to expose real
/proc/cpuinfo data taken from a real world machine.
The real fix would be to generate at least the flags automatically based
on the selected CPU. Please do not submit this patch upstream until this
has happened.
Signed-off-by: Alexander Graf <agraf@suse.de>
[AF: Rebased for v1.6 and v1.7]
Signed-off-by: Andreas Färber <afaerber@suse.de>
|
|
Signed-off-by: Alexander Graf <agraf@suse.de>
[AF: Rebased onto exec.c/translate-all.c split for 1.4]
Signed-off-by: Andreas Färber <afaerber@suse.de>
|
|
Running multi-threaded code can easily expose some of the fundamental
breakages in QEMU's design. It's just not a well supported scenario.
So if we pin the whole process to a single host CPU, we guarantee that
we will never have concurrent memory access actually happen. We can still
get scheduled away at any time, so it's no complete guarantee, but apparently
it reduces the odds well enough to get my test cases to pass.
This gets Java 1.7 working for me again on my test box.
Signed-off-by: Alexander Graf <agraf@suse.de>
|
|
The tcg code generator is not thread safe. Lock its generation between
different threads.
Signed-off-by: Alexander Graf <agraf@suse.de>
[AF: Rebased onto exec.c/translate-all.c split for 1.4]
[AF: Rebased for v2.1.0-rc0]
Signed-off-by: Andreas Färber <afaerber@suse.de>
|
|
During invocations of losetup, we run into an ioctl that doesn't
exist. However, because of that we output an error, which then
screws up the kiwi logic around that call.
So let's silently ignore that bogus ioctl.
Signed-off-by: Alexander Graf <agraf@suse.de>
[AF: Rebased for v2.1.0-rc0]
Signed-off-by: Andreas Färber <afaerber@suse.de>
|
|
When running automoc4 as linux-user guest program, it segfaults right after
it creates a thread. Bisecting pointed to commit a84fac1426 which introduces
tb_flush on reset.
So something in our thread creation is broken. But for now, let's revert the
change to at least get a working build again.
[AF: Rebased, fixed typo]
|
|
When we have a working host binary equivalent for the guest binary we're
trying to run, let's just use that instead as it will be a lot faster.
Signed-off-by: Alexander Graf <agraf@suse.de>
|
|
When entering the guest we take a lock to ensure that nobody else messes
with our TB chaining while we're doing it. If we get a segfault inside that
code, we manage to work on, but will not unlock the lock.
This patch forces unlocking of that lock in the segv handler. I'm not sure
this is the right approach though. Maybe we should rather make sure we don't
segfault in the code? I would greatly appreciate someone more intelligible
than me to look at this :).
Example code to trigger this is at: http://csgraf.de/tmp/conftest.c
Reported-by: Fabio Erculiani <lxnay@sabayon.org>
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Andreas Färber <afaerber@suse.de>
|
|
When using hugetlbfs (which is required for HV mode KVM on 970), we
check for MMU notifiers that on 970 can not be implemented properly.
So disable the check for mmu notifiers on PowerPC guests, making
KVM guests work there, even if possibly racy in some odd circumstances.
|
|
When using qemu's linux-user binaries through binfmt, argv[0] gets lost
along the execution because qemu only gets passed in the full file name
to the executable while argv[0] can be something completely different.
This breaks in some subtile situations, such as the grep and make test
suites.
This patch adds a wrapper binary called qemu-$TARGET-binfmt that can be
used with binfmt's P flag which passes the full path _and_ argv[0] to
the binfmt handler.
The binary would be smart enough to be versatile and only exist in the
system once, creating the qemu binary path names from its own argv[0].
However, this seemed like it didn't fit the make system too well, so
we're currently creating a new binary for each target archictecture.
CC: Reinhard Max <max@suse.de>
Signed-off-by: Alexander Graf <agraf@suse.de>
[AF: Rebased onto new Makefile infrastructure, twice]
[AF: Updated for aarch64 for v2.0.0-rc1]
[AF: Rebased onto Makefile changes for v2.1.0-rc0]
Signed-off-by: Andreas Färber <afaerber@suse.de>
|