How to include Xen as Host kernel (on FreeBSD) in my custom kernel

That's really a Windows support question. You can remove the device from the device manager. Right click on it and select 'uninstall device'.

How to Uninstall Drivers in Windows

If your computer is acting up, hardware drivers may be to blame. Learn how to roll back or even uninstall driver software with this handy guide.
www.pcworld.com www.pcworld.com
 
SirDice said:
Remove these two:
Code: 
disk1_type="ahci-cd"
disk1_name="Windows10x64ukr-1803.iso"

You don't need to add a CD device for the install, it's automatically added when you use vm install ... and then automatically removed after the fist boot.

github.com

Running Windows

Shell based, minimal dependency bhyve manager. Contribute to churchers/vm-bhyve development by creating an account on GitHub.
github.com github.com
Click to expand...
github.com

Running Windows

Shell based, minimal dependency bhyve manager. Contribute to churchers/vm-bhyve development by creating an account on GitHub.
github.com github.com
There it is written:
  • If the machine has Internet access via the e1000 device, you can download and install the virtio drivers directly in the guest. Once installed, shutdown the guest, change the device in guest configuration and restart.
  • The guest can be booted in install mode, but specifying the VirtIO ISO file.
    # vm install winguest virtio-installer.iso



  • A CD device can be added to the guest and pointed at the ISO file
    disk1_type="ahci-cd"
    disk1_dev="custom"
    disk1_name="/full/path/to/virtio-installer.iso"
 
This is the drive that I want to delete is present in the system because there is a configuration file:
Code: 
May 08 14:15:50: booting
May 08 14:15:50:  [bhyve options: -c 1,sockets=1,cores=1 -m 2G -Hwl bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -p 1:1 -U 3f4c7262-7165-11e9-8590-f4f26d026783]
May 08 14:15:50:  [bhyve devices: -s 0,amd_hostbridge -s 31,lpc -s 4:0,ahci,hd:/virtmachins/win10/win10.img,nocache,cd:/virtmachins/win10/Windows10x64ukr-1803.iso -s 5:0,virtio-net,tap0,mac=58:9c:fc:01:bf:03 -s 6:0,fbuf,tcp=10.144.40.6:5999,w=800,h=600,vga=io -s 7:0,xhci,tablet]
May 08 14:15:50:  [bhyve console: -l com1,/dev/nmdm-win10.1A]
*****
--->>> May 08 14:15:50:  [bhyve iso device: -s 3:0,ahci-cd,/virtmachins/.config/null.iso]
*****
May 08 14:15:50: starting bhyve (run 1)

but in config file have only line about "-s 4:0,ahci,hd:/virtmachins/win10/win10.img,nocache,cd:/virtmachins/win10/Windows10x64ukr-1803.iso"
...
ahci_device_limit="8"
disk0_type="ahci-hd" <<<<<< ( -s 4:0,ahci,hd: .....
disk0_dev="file"
disk0_name="win10.img"
disk0_opts="nocache"
disk1_type="ahci-cd" <<<<<< ( .... cd:
disk1_name="Windows10x64ukr-1803.iso"
network0_type="virtio-net"

...

Where is going from this "bhyve iso device: -s 3:0,ahci-cd,/virtmachins/.config/null.iso" i do not understand !!!!
 
SirDice said:
Remove these two:
Code: 
disk1_type="ahci-cd"
disk1_name="Windows10x64ukr-1803.iso"
Click to expand...
I made your recommendations, but they were so doomed.

6482
 
Make sure you stop the VM; vm stop ..., then modify the configuration file. Then start the VM. If I recall correctly you need to stop, then start the VM for the configuration changes to take hold. Restarting the VM does not re-read the config.
 
SirDice said:
Make sure you stop the VM; vm stop ..., then modify the configuration file. Then start the VM. If I recall correctly you need to stop, then start the VM for the configuration changes to take hold. Restarting the VM does not re-read the config.
Click to expand...

yes, i stop vm -> modify the configuration file and -> start vm again.
Code: 
May 08 15:15:49: stopped
May 08 15:16:44: initialising
May 08 15:16:44:  [loader: uefi]
May 08 15:16:44:  [cpu: 1,sockets=1,cores=1]
May 08 15:16:44:  [memory: 2G]
May 08 15:16:44:  [hostbridge: amd]
May 08 15:16:44:  [com ports: com1]
May 08 15:16:44:  [uuid: 3f4c7262-7165-11e9-8590-f4f26d026783]
May 08 15:16:44:  [utctime: no]
May 08 15:16:44:  [debug mode: no]
May 08 15:16:44:  [primary disk: win10.img]
May 08 15:16:44:  [primary disk dev: file]
May 08 15:16:44: initialising network device tap0
May 08 15:16:44: adding tap0 -> vm-ForVMS (ForVMS addm)
May 08 15:16:44: bring up tap0 -> vm-ForVMS (ForVMS addm)
May 08 15:16:44: booting
May 08 15:16:44:  [bhyve options: -c 1,sockets=1,cores=1 -m 2G -Hwl bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -U 3f4c7262-7165-11e9-8590-f4f26d026783]
****(see changed - not cd)
--->May 08 15:16:44:  [bhyve devices: -s 0,amd_hostbridge -s 31,lpc -s 4:0,ahci,hd:/virtmachins/win10/win10.img,nocache -s 5:0,virtio-net,tap0,mac=58:9c:fc:01:bf:03 -s 6:0,fbuf,tcp=10.144.40.6:5999,w=800,h=600,vga=io -s 7:0,xhci,tablet]
****
May 08 15:16:44:  [bhyve console: -l com1,/dev/nmdm-win10.1A]
May 08 15:16:44:  [bhyve iso device: -s 3:0,ahci-cd,/virtmachins/.config/null.iso]
May 08 15:16:44: starting bhyve (run 1)

Removed only not that drive, but you have to give out another, as in the photo!
 
Did you double click an ISO file in Windows? Windows 8 and higher will create a virtual CD drive and load the ISO automatically. Just right click on the drive and select "eject", the virtual CD drive will disappear if it's empty.
 
Clean up your config, there's a lot of cruft. "start_slot" and "install_slot" look suspicious, never needed this. My whole config for a windows server looks like this:
Code: 
uefi="yes"
cpu=4
memory=8G
graphics="yes"
xhci_mouse="yes"
network0_type="virtio-net"
network0_switch="internal"
disk0_type="virtio-blk"
disk0_name="disk0"
disk0_dev="sparse-zvol"

uuid="[.....]"
network0_mac="[.....]"
with the last two lines added by vm-bhyve on first run.

If you start in install mode, a dvd drive is added automatically, as told by sirdice.

Don't use virtio-blk for a windows guest unless you patched your bhyve as I already wrote here. ahci-hd is safe but slower.
 
You must log in or register to reply here.
Back
Top