Date: Sat, 17 Oct 2020 18:49:35 +0000 (UTC) From: Kostya Berger <bergerkos@yahoo.co.uk> To: FreeBSD Current <freebsd-current@freebsd.org> Subject: bhyve win 10 guest: destroy to restart Message-ID: <1896911060.833428.1602960575313@mail.yahoo.com> References: <1896911060.833428.1602960575313.ref@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello!It's been like that ever since I started using win 10 guest in bhyve:= If I need to restart win 10 guest I have to destroy the VM after guest shu= tdown. Because the bhyve startup script aborts, but the VM remains and won'= t be started again unless destroyed. I'm using bhyve binary with starting command line, nothing else. Is that a = normal behaviour? Or am I supposed to use vm-bhyve? If so, how can I conver= t the existing script to vm-bhyve config without Windows requiring new regi= stration because of new hardware?Hope these aren't too many questions.... =D0=9E=D1=82=D0=BF=D1=80=D0=B0=D0=B2=D0=BB=D0=B5=D0=BD=D0=BE =D0=B8=D0=B7 Y= ahoo =D0=9F=D0=BE=D1=87=D1=82=D1=8B =D0=B4=D0=BB=D1=8F Android From owner-freebsd-current@freebsd.org Sat Oct 17 18:59:02 2020 Return-Path: <owner-freebsd-current@freebsd.org> Delivered-To: freebsd-current@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 A439443F6B7 for <freebsd-current@mailman.nyi.freebsd.org>; Sat, 17 Oct 2020 18:59:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qv1-xf42.google.com (mail-qv1-xf42.google.com [IPv6:2607:f8b0:4864:20::f42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CDC3n4WBZz4VrD for <freebsd-current@freebsd.org>; Sat, 17 Oct 2020 18:59:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qv1-xf42.google.com with SMTP id de3so2568009qvb.5 for <freebsd-current@freebsd.org>; Sat, 17 Oct 2020 11:59:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=m7B2TByXqwvSGY8PVg7cAyr7XtFq9EKavxXwdk8tQqo=; b=kYKOLEQ0OPw+kG195hGnsltrYvyTXnItiFnsweF/q0EcUSdiCaAhmHzJxe4OBsB+ih Y9sez+DA6ZLRjpS2hPv1U1E7rauEbwcVF12u79iQ8PuXKdhP/FMFNm3Qg2Fkys0aII3H G6PI0s3cKOfB9Gyc5kIc7fvHaihiVXerGgPZ6OGiqGOEmAaGf87i2jQME/cMF9ONDBmR aNoEAWfBMxNiOA/7chaiegBjgsp7wZQHIgqBgio7Kfnnj3mDV+yKQ3xB8xi8fH4fUl82 ACMfI0XXfN4TL9R3BK6/iopH07tj/HJouZwWcenkhQSf+d4dv03ZsC9kb6rNUN179gHu 4H+A== X-Gm-Message-State: AOAM532fesyIh18hOJuJltUogPJtlULXspsI/G4l7LzEkRtEcKxyjtw4 UUOn/1he5kzc1F41XCkW3QJqokuXLmgfyiplaAVPthBgogs= X-Google-Smtp-Source: ABdhPJzfd9AgA2/ZaDEZL8rOu25RZHJBSg/NV3hyaMEFzCu6VJayE0WprC3N1vtYgJaSYJNq0wIHlJalS/4RdQEQ7f8= X-Received: by 2002:a05:6214:10c4:: with SMTP id r4mr9583190qvs.62.1602961140431; Sat, 17 Oct 2020 11:59:00 -0700 (PDT) MIME-Version: 1.0 References: <20201015065632.GA72261@troutmask.apl.washington.edu> <3fdb18c1-5dc3-2e06-8825-db1daa425afb@yandex.ru> In-Reply-To: <3fdb18c1-5dc3-2e06-8825-db1daa425afb@yandex.ru> From: Warner Losh <imp@bsdimp.com> Date: Sat, 17 Oct 2020 12:58:48 -0600 Message-ID: <CANCZdfr+8MOwbZ4YACpLx5ZoFt3BSV3N9JQ=oZcKFEdFHRXRBg@mail.gmail.com> Subject: Re: kernel panic and fun debugging To: "Andrey V. Elsukov" <bu7cher@yandex.ru> Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>, FreeBSD Current <freebsd-current@freebsd.org> X-Rspamd-Queue-Id: 4CDC3n4WBZz4VrD X-Spamd-Bar: - X-Spamd-Result: default: False [-1.64 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-0.93)[-0.927]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.24)[0.237]; NEURAL_HAM_LONG(-0.95)[-0.951]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::f42:from]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[yandex.ru]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 17 Oct 2020 18:59:02 -0000 On Sat, Oct 17, 2020, 12:00 PM Andrey V. Elsukov <bu7cher@yandex.ru> wrote: > On 15.10.2020 09:56, Steve Kargl wrote: > > Just had a kernel panic. Best info I give you is > > > > % uname -a > > FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r366176M: Sat Sep 26 > 10:35:23 PDT 2020 kargl@mobile:/usr/obj/usr/src/i386.i386/sys/MOBILE > i386 > > > > % kgdb gdb /usr/lib/debug/boot/kernel/kernel.debug vmcore.1 > > ... > > Reading symbols from /usr/lib/debug/boot/kernel/kernel.debug... > > /usr/ports/devel/gdb/work-py37/gdb-9.2/gdb/inferior.c:283: > internal-error: struct inferior *find_inferior_pid(int): Assertion `pid != > 0' failed. > > A problem internal to GDB has been detected, > > further debugging may prove unreliable. > > Hi, > > do you have /var/crash/core.txt.1 file? > It may have some useful info. Also did you try an old version > /usr/libexec/kgdb ? > I got this same error, btw, when I pointed kgdb at the wrong kernel for the core file. But you can 'more' the uncompressed vmcore to get at least a traceback if the proper kernel is gone... Warner -- > WBR, Andrey V. Elsukov > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1896911060.833428.1602960575313>