From owner-freebsd-virtualization@freebsd.org Thu Nov 5 20:52:11 2020 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8B6142D0C8D for ; Thu, 5 Nov 2020 20:52:11 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4CRwgb2W1Wz3NmD for ; Thu, 5 Nov 2020 20:52:11 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: by mailman.nyi.freebsd.org (Postfix) id 55FF62D0C8C; Thu, 5 Nov 2020 20:52:11 +0000 (UTC) Delivered-To: virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5488D2D0E01; Thu, 5 Nov 2020 20:52:11 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [128.127.146.8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.norma.perm.ru", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CRwgW5LBhz3Ndh; Thu, 5 Nov 2020 20:52:07 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from [192.168.243.9] ([192.168.243.9]) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTP id 0A5Kqq2k065035; Fri, 6 Nov 2020 01:52:52 +0500 (+05) (envelope-from emz@norma.perm.ru) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=norma.perm.ru; s=key; t=1604609572; bh=WDieaXhnqVWLBfCNHhRuk2MQ5+/8Krt7CQejpvD2e+Y=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=UgF/e4R8vFmcKW4v7+zzsCAY6A2RcD/70erwCMEsOCpFat0uSBVb43j8GbFfPq2lv qzUxjbWTqKZuzgYY5vLdIN3zrfBXKEia/FYrB9lq6h9Bhrr5m+6g8h4XFiK1N+unZ/ s4VDOf5aBvr0WwnqF9sNOcHgtoaTaZIKeFxHhwR4= Subject: Re: FreeBSD 12.x, virtio and alicloud (aliyun.com) To: freebsd-stable@freebsd.org References: Cc: virtualization@freebsd.org From: "Eugene M. Zheganin" Message-ID: <98cd7866-7d05-6e49-e53b-e8dedf2a1531@norma.perm.ru> Date: Fri, 6 Nov 2020 01:52:03 +0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: ru X-Rspamd-Queue-Id: 4CRwgW5LBhz3Ndh X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=norma.perm.ru header.s=key header.b=UgF/e4R8; dmarc=pass (policy=none) header.from=perm.ru; spf=pass (mx1.freebsd.org: domain of emz@norma.perm.ru designates 128.127.146.8 as permitted sender) smtp.mailfrom=emz@norma.perm.ru X-Spamd-Result: default: False [4.28 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[128.127.146.8:from]; R_DKIM_ALLOW(0.00)[norma.perm.ru:s=key]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(0.00)[+a]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; HFILTER_HELO_IP_A(1.00)[elf.hq.norma.perm.ru]; HFILTER_HELO_NORES_A_OR_MX(0.30)[elf.hq.norma.perm.ru]; SPAMHAUS_ZRD(0.00)[128.127.146.8:from:127.0.2.255]; RBL_VIRUSFREE_BOTNET(2.00)[128.127.146.8:from]; NEURAL_SPAM_SHORT(0.98)[0.984]; DKIM_TRACE(0.00)[norma.perm.ru:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(0.00)[perm.ru,none]; BAD_REP_POLICIES(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:212494, ipnet:128.127.146.0/24, country:RU]; MID_RHS_MATCH_FROM(0.00)[]; MAILMAN_DEST(0.00)[freebsd-stable,virtualization]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2020 20:52:11 -0000 Hello. Well, with this patch I'm getting trap immediately on the kernel booting phase: ===Cut=== virtio_pci2:virtqueue 0 (vtnet0-0 rx) does not exists (size is zero) virtio_pci2: cannot allocate virtqueue 0: 19 vtnet0: cannot allocate virtqueues ===Cut=== see the screenshot below: https://enazadev.ru/stub-data/freebsd12-patched-trap.png 05.11.2020 11:06, Cevin пишет: > The problem seems to have been fixed, but the code is still in the review. > For more details, see https://reviews.freebsd.org/D26915#601420 > > Eugene M. Zheganin 于2020年11月5日周四 下午12:35写道： > >> Hello, >> >> >> Guys, does anyone have VM running in AliCloud Chinese provider (one of >> the biggest, if not the biggest one) ? They seem to provide stock >> FreeBSD 11.x images on some Redhat-based Linux with VirtIO which run >> just fine (at least I take a look at their kernel and it seem to be a >> stock GENERIC), but after source uprgading to 12.2 it cannot mountroot, >> because literally no disks are found after thee kernel booting stage. >> This, in turn, is cause by a bunch of repeatable virtio errors, which >> looks like (screenshot provided in the link): >> >> >> virtio_pci1: cannot map I/O space >> >> device_attach: virtio_pci1 attach returned 6 >> >> >> (https://enazadev.ru/stub-data/freebsd12-alicloud-cannot-map-io.png) >> >> So not only vtbd0 cannot be attached to, but also a network adater. >> Surprisingly, virtio_console and memory baloon device seems to be working. >> >> I've took a look at various VirtIO cases in the bug tracker and compiled >> a kernel without netmap (yeah, after some consideration this could help >> only with virtio_net part), but this doesn't help. >> >> Is this some sort of regression that needs to be reported ? Is there >> some kind of known workaround ? >> >> I also have a running 11.3 on a second VM, so I can provide any >> necessary details if needed. >> >> >> Thanks. >> >> Eugene. >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"