<h2>Build instructions</h2>
@@ -24,7 +24,7 @@ make
{% endfor %}
<p>To download and build QEMU from git:</p>
-<pre>git clone https://git.qemu.org/git/qemu.git
+<pre>git clone https://gitlab.com/qemu-project/qemu.git
cd qemu
git submodule init
git submodule update --recursive
diff --git a/_posts/2017-02-04-the-new-qemu-website-is-up.md
b/_posts/2017-02-04-the-new-qemu-website-is-up.md
index b9455a0..e7ed349 100644
--- a/_posts/2017-02-04-the-new-qemu-website-is-up.md
+++ b/_posts/2017-02-04-the-new-qemu-website-is-up.md
@@ -15,7 +15,7 @@ developers to share information quickly with the rest of the
community.
We tried to test the website on most browsers and to make it lightweight
and responsive. It is built using [Jekyll](https://jekyllrb.com/)
and the source code for the website can be cloned from the
-[qemu-web.git](https://git.qemu.org/?p=qemu-web.git;a=summary)
+[qemu-web.git](https://gitlab.com/qemu-project/qemu-web.git)
repository. Just like for any other project hosted by QEMU, the best way
to propose or contribute a new change is by sending a patch through the
[qemu-devel@nongnu.org](https://lists.nongnu.org/mailman/listinfo/qemu-devel)
@@ -25,10 +25,10 @@ confuse it with a qemu.git patch (if you run `git config
format.subjectprefix
For example, if you would like to add a new screenshot to the homepage,
you can clone the `qemu-web.git` repository, add a PNG file to the
-[`screenshots/`](https://git.qemu.org/?p=qemu-web.git;a=tree;f=screenshots;hb=HEAD)
-directory, and edit the
[`_data/screenshots.yml`](https://git.qemu.org/?p=qemu-web.git;a=blob;f=_data/screenshots.yml;hb=HEAD)
+[`screenshots/`](https://gitlab.com/qemu-project/qemu-web/-/tree/master/screenshots)
+directory, and edit the
[`_data/screenshots.yml`](https://gitlab.com/qemu-project/qemu-web/-/tree/master/_data/screenshots.yml)
file to include the new screenshot.
Blog posts about QEMU are also welcome; they are simple HTML or Markdown
-files and are stored in the
[`_posts/`](https://git.qemu.org/?p=qemu-web.git;a=tree;f=_posts;hb=HEAD)
+files and are stored in the
[`_posts/`](https://gitlab.com/qemu-project/qemu-web/-/tree/master/_posts)
directory of the repository.
diff --git a/_posts/2017-10-04-qemu-2-10-1.md b/_posts/2017-10-04-qemu-2-10-1.md
index 6fa00fa..f20adce 100644
--- a/_posts/2017-10-04-qemu-2-10-1.md
+++ b/_posts/2017-10-04-qemu-2-10-1.md
@@ -9,9 +9,9 @@ is now available! You can grab the tarball from our
[download page](https://www.qemu.org/download/#source).
Version 2.10.1 is now tagged in the official
-[qemu.git repository](https://git.qemu.org/?p=qemu.git;a=shortlog;h=v2.10.1)
+[qemu.git repository](https://gitlab.com/qemu-project/qemu/-/commits/v2.10.1/)
(where you can also find the changelog with details), and the
-[stable-2.10
branch](https://git.qemu.org/?p=qemu.git;a=shortlog;h=refs/heads/stable-2.10)
+[stable-2.10
branch](https://gitlab.com/qemu-project/qemu/-/commits/stable-2.10)
has been updated accordingly.
Apart from the normal range of general fixes, this update contains security
diff --git a/_posts/2018-02-09-understanding-qemu-devices.md
b/_posts/2018-02-09-understanding-qemu-devices.md
index 25130b7..c201a9b 100644
--- a/_posts/2018-02-09-understanding-qemu-devices.md
+++ b/_posts/2018-02-09-understanding-qemu-devices.md
@@ -80,7 +80,7 @@ treating a file in the host filesystem as raw data (a 1:1
mapping of
offsets in the host file to disk offsets being accessed by the guest
driver), but QEMU actually has the ability to glue together a lot of
different host formats (raw,
-[qcow2](https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/qcow2.txt),
+[qcow2](https://gitlab.com/qemu-project/qemu/-/blob/master/docs/interop/qcow2.txt),
qed,
[vhdx](https://www.microsoft.com/en-us/download/details.aspx?id=34750),
...) and protocols (file system, block device,
diff --git a/_posts/2018-06-28-tcg-testing.md b/_posts/2018-06-28-tcg-testing.md
index ddaf18d..29ef602 100644
--- a/_posts/2018-06-28-tcg-testing.md
+++ b/_posts/2018-06-28-tcg-testing.md
@@ -69,7 +69,7 @@ tests it can support.
# `make check-tcg`
With the latest work [merged into
-master](https://git.qemu.org/?p=qemu.git;a=commit;h=de44c044420d1139480fa50c2d5be19223391218)
we can now
+master](https://gitlab.com/qemu-project/qemu/-/commit/de44c044420d1139480fa50c2d5be19223391218)
we can now
take advantage of either hand-configured and Docker-based cross
compilers to build test cases for TCG again. To run the TCG tests
after you have built QEMU:
@@ -133,5 +133,5 @@ results from a qemu-system emulation. Some architectures
have
semi-hosting support already for this while others report their test
status over a simple serial link which will need to be parsed and
handled in custom versions of the
-[`run-%:`](https://git.qemu.org/?p=qemu.git;a=blob;f=tests/tcg/Makefile;h=bf064153900a438e4ad8e2d79eaaac8a27d66062;hb=HEAD#l95)
+[`run-%:`](https://gitlab.com/qemu-project/qemu/-/blob/de44c044420d1139480fa50c2d5be19223391218/tests/tcg/Makefile#L95)
rule.
diff --git a/contribute.md b/contribute.md
index 96901b5..307f1be 100644
--- a/contribute.md
+++ b/contribute.md
@@ -6,7 +6,7 @@ permalink: /contribute/
* Report a bug in our bugtracker:
[https://bugs.launchpad.net/qemu/](https://bugs.launchpad.net/qemu/)<br>
See also [How to report a bug](report-a-bug/) or [How to report a security
bug](security-process/)
-* Clone ([or browse](https://git.qemu.org/?p=qemu.git)) the git repository: <br>`git clone https://git.qemu.org/git/qemu.git`
+* Clone ([or browse](https://gitlab.com/qemu-project/qemu.git)) the git repository:
<br>`git clone https://gitlab.com/qemu-project/qemu.git`
* Join the mailing list: [qemu-devel@nongnu.org](https://lists.nongnu.org/mailman/listinfo/qemu-devel)<br>[See the list of QEMU mailing lists](https://wiki.qemu.org/MailingLists)
diff --git a/contribute/security-process.md b/contribute/security-process.md
index 13b6b97..94eef35 100644
--- a/contribute/security-process.md
+++ b/contribute/security-process.md
@@ -140,7 +140,7 @@ only be exercised in use cases where QEMU and everything
interacting with it is
trusted.
For example, consider upstream commit [9201bb9 "sdhci.c: Limit the maximum
-block size"](http://git.qemu.org/?p=qemu.git;a=commit;h=9201bb9), an of out of
+block size"](https://gitlab.com/qemu-project/qemu/-/commit/9201bb9), an of out
of
bounds (OOB) memory access (ie. buffer overflow) issue that was found and
fixed
in the SD Host Controller emulation (hw/sd/sdhci.c).
@@ -151,7 +151,7 @@ is via 'generic-sdhci' interface.
Of these two, the 'sdhci-pci' interface had actually been disabled by default
in the upstream QEMU releases (commit [1910913 "sdhci: Make device "sdhci-pci"
-unavailable with -device"](http://git.qemu.org/?p=qemu.git;a=commit;h=1910913)
+unavailable with
-device"](https://gitlab.com/qemu-project/qemu/-/commit/1910913)
at the time the flaw was reported; therefore, guests could not possibly use
'sdhci-pci' for any purpose.
diff --git a/documentation.md b/documentation.md
index 41d9b3a..be4e637 100644
--- a/documentation.md
+++ b/documentation.md
@@ -9,7 +9,7 @@ is the first place to go in case you have questions about using
QEMU.
Most of the documentation is generated automatically from the QEMU git source
tree, however some text files have not been converted to the new format yet.
These documentation files can be browsed via the
-[git web interface](https://git.qemu.org/?p=qemu.git;a=tree;f=docs;hb=master)
+[git web interface](https://gitlab.com/qemu-project/qemu/-/tree/master/docs)
instead.
The [QEMU wiki](https://wiki.qemu.org) contains more
diff --git a/support.md b/support.md
index 031f045..49cbb0f 100644
--- a/support.md
+++ b/support.md
@@ -12,7 +12,7 @@ rest of your Linux distribution you may be better served by
asking
through your distribution's support channels. This includes questions
about a specifically packaged version of QEMU. The QEMU developers are
generally concerned with the latest release and the current state of
-the [master branch](https://git.qemu.org/?p=qemu.git) and do not
+the [master branch](https://gitlab.com/qemu-project/qemu.git) and do not
provide support for QEMU binaries shipped by Linux distributions.
Questions about complex configurations of networking and storage are