Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 03 Apr 2019 08:24:15 +0000
From:      Michael Reifenberger <Michael@reifenberger.com>
To:        Nick Wolff <darkfiberiru@gmail.com>
Cc:        Jason Barbier <jason@corrupted.io>, freebsd-virtualization@freebsd.org
Subject:   Re: Windows 2019 server
Message-ID:  <20190403082415.Horde.2jD2Fjwd-E1Bk1_ZUlCRJwn@app.eeeit.de>
In-Reply-To: <CACxAneAkmQPui9jPd1MimJ8oO4ee2_pYWGsoKfrsJTXr2=XEJQ@mail.gmail.com>
References:  <20190216123859.GA24315@doctor.nl2k.ab.ca> <40ddfdd6-a1c4-ac00-f088-2880a7d372ce@smeets.xyz> <20190302094829.GA48523@admin.sibptus.ru> <CACLnyCL5V5j3ykq=VZdwfM8LsKOCfw7rQZH1UnbERq4NTwVGTA@mail.gmail.com> <20190303032918.GA60561@admin.sibptus.ru> <CACxAneBRy4=5mSz=9eAqs53wSG9=fv41f_UUVYpSDFb_rkCB-A@mail.gmail.com> <AE77DDF7-8420-45F6-A165-1C347F00F53E@reifenberger.com> <1c80a14e-eb1e-4d95-b74a-337f20573189@www.fastmail.com> <CACxAneAkmQPui9jPd1MimJ8oO4ee2_pYWGsoKfrsJTXr2=XEJQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

Zitat von Nick Wolff <darkfiberiru@gmail.com>:

> Micheal,
>
> Would you mind trying with
> https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.118-1/
>
>
> That is the iso I've used in the past with newer drivers failing(I don't
> think it caused a panic though when I dealt with it)
>

Trying to use this ISO for loading the driver during the installation  
doesn't lead to a panic
but aborts the guest while the driver gets loaded:

Apr. 03 10:11:11: initialising
Apr. 03 10:11:11:  [loader: uefi]
Apr. 03 10:11:11:  [cpu: 2]
Apr. 03 10:11:11:  [memory: 6G]
Apr. 03 10:11:11:  [hostbridge: standard]
Apr. 03 10:11:11:  [com ports: com1]
Apr. 03 10:11:11:  [uuid: a9656f03-7f7a-11e7-983e-98e7f4868540]
Apr. 03 10:11:11:  [utctime: yes]
Apr. 03 10:11:11:  [debug mode: no]
Apr. 03 10:11:11:  [primary disk: disk0]
Apr. 03 10:11:11:  [primary disk dev: zvol]
Apr. 03 10:11:11: initialising network device tap0
Apr. 03 10:11:11: adding tap0 -> bridge1 (private addm)
Apr. 03 10:11:11: bring up tap0 -> bridge1 (private addm)
Apr. 03 10:11:11: booting
Apr. 03 10:11:11:  [bhyve options: -c 2 -m 6G -Hwl  
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U  
a9656f03-7f7a-11e7-983e-98e7f4868540 -u]
Apr. 03 10:11:11:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s  
4:0,virtio-blk,/dev/zvol/zdata/VM/w10e-ltsb-2/disk0 -s  
5:0,nvme,/dev/zvol/zdata/VM/w10e-ltsb-2/disk1 -s  
6:0,ahci-cd,/VM2/w10e-ltsb-2/disk2.img -s  
7:0,virtio-net,tap0,mac=58:9c:fc:04:eb:ed -s  
8:0,fbuf,tcp=0.0.0.0:5900,w=1600,h=900 -s 9:0,xhci,tablet]
Apr. 03 10:11:11:  [bhyve console: -l com1,/dev/nmdm-w10e-ltsb-2.1A]
Apr. 03 10:11:11:  [bhyve iso device: -s  
3:0,ahci-cd,/VM/.iso/en_windows_10_enterprise_ltsc_2019_x64_dvd_be3c8ffb.iso,ro]
Apr. 03 10:11:11: starting bhyve (run 1)
Apr. 03 10:13:10: bhyve exited with status 134
Apr. 03 10:13:10: destroying network device tap0
Apr. 03 10:13:10: stopped

The relevant entries of the config file are:

...
cpu=2
memory=6G
network0_type="virtio-net"
network0_switch="private"
disk0_type="virtio-blk"
disk0_dev="zvol"
disk0_name="disk0"
disk1_type="nvme"
disk1_dev="zvol"
disk1_name="disk1"
disk2_type="ahci-cd"
disk2_name="disk2.img"
...

(disk0 is the one I'm trying to use here, disk2 is the ISO)

Greetings
---
mike

Gruß
---
Michael Reifenberger




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190403082415.Horde.2jD2Fjwd-E1Bk1_ZUlCRJwn>