From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id CE78D65A80 for ; Fri, 24 Jul 2020 07:10:53 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BFF562E79B for ; Fri, 24 Jul 2020 07:10:53 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id C91282E790 for ; Fri, 24 Jul 2020 07:10:52 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 8E97943152 for ; Fri, 24 Jul 2020 07:10:52 +0200 (CEST) Date: Fri, 24 Jul 2020 07:10:45 +0200 From: Fabian =?iso-8859-1?q?Gr=FCnbichler?= To: Proxmox VE development discussion References: <50825279-7f65-e255-6d83-350effd1fe91@samip.fi> In-Reply-To: <50825279-7f65-e255-6d83-350effd1fe91@samip.fi> MIME-Version: 1.0 User-Agent: astroid/0.15.0 (https://github.com/astroidmail/astroid) Message-Id: <1595567236.8argd652f8.astroid@nora.none> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.055 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Subject: Re: [pve-devel] Enabling mips/mipsel support in Hypervisor X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2020 05:10:53 -0000 On July 24, 2020 2:23 am, Skyler M=C3=A4ntysaari wrote: > Hi all, >=20 > I would like to ask how can I get mips/mipsel arch qemu working on Proxmo= x? quoting my own post in the forum thread you linked ;) > we only build the amd64 emulation, and install qemu-system-amd64 as=20 > "kvm" binary. so no, this does not work unless you manually re-build=20 > our pve-qemu-kvm packages with more architecture support and adapt the=20 > perl scripts to use the appropriate qemu-system-XXX binary. > This=20 > =20 > forum post, seems to indicate it should be rather simple, but why was it=20 > disabled to begin with? because for it to make sense we need to implement and maintain the full=20 machine model, which is quite a lot of work for x86 already. all the=20 other arches are rather niche, so the cost of implementation and=20 maintenance is rather high. > # apt install qemu-system-mipsel > Reading package lists... Done > Building dependency tree > Reading state information... Done > Note, selecting 'qemu-system-mips' instead of 'qemu-system-mipsel' > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: >=20 > The following packages have unmet dependencies: > =C2=A0qemu-system-mips : Depends: qemu-system-common (> 1:2.12~) but it = is=20 > not going to be installed > E: Unable to correct problems, you have held broken packages. >=20 > and >=20 > Get:1 http://security.debian.org buster/updates/main amd64=20 > qemu-system-common amd64 1:3.1+dfsg-8+deb10u6 [989 kB] > Fetched 989 kB in 0s (5,040 kB/s) > W: (pve-apt-hook) !! WARNING !! > W: (pve-apt-hook) You are attempting to remove the meta-package=20 > 'proxmox-ve'! > W: (pve-apt-hook) > W: (pve-apt-hook) If you really want to permanently remove 'proxmox-ve'=20 > from your system, run the following command > W: (pve-apt-hook)=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 touch '/please-remo= ve-proxmox-ve' > W: (pve-apt-hook) run apt purge proxmox-ve to remove the meta-package > W: (pve-apt-hook) and repeat your apt invocation. > W: (pve-apt-hook) > W: (pve-apt-hook) If you are unsure why 'proxmox-ve' would be removed,=20 > please verify > W: (pve-apt-hook)=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 - your APT reposito= ry settings > W: (pve-apt-hook)=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 - that you are usin= g 'apt full-upgrade' to=20 > upgrade your system > E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code = (1) > E: Failure running script /usr/share/proxmox-ve/pve-apt-hook the above attempts to install the stock qemu package from Debian Buster,=20 which is not compatible with our stack and Qemu packages.. =