Re: Windows support in bhyve
Excerpts from Peter Grehan's message from Sun 04-Oct-15 13:11: > As of r288524, bhyve has preliminary support to run Windows in headless > mode using UEFI firmware. > > Since it's headless, the install process consists of modifying the > Windows install ISO to include an 'unattend' XML script that automates > the install, and also inserting the virtio network driver currently > required by bhyve. > > This has been tested with 64-bit Windows Server 2k12r2 and 2k16 tp3, and > Windows 10. The server versions are recommended since they have serial > console support, whereas the desktop install is a black-screen experience. > > ISO repack instructions at: > http://people.freebsd.org/~grehan/bhyve_uefi/windows_iso_repack.txt > > Install/run instructions at: > http://people.freebsd.org/~grehan/bhyve_uefi/windows_install.txt > > Please give this a try and report back on how it goes. > That's really cool! Thanks for the instructions! I've installed Windows Server 2016 with no issues on a ZFS volume. Works fine. I can get the command prompt, set up IP address and so on. However I cannot get Remote Desktop connection working. I tried to (re)enable it from the command line: C:\Windows\system32>reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f The operation completed successfully. C:\Windows\system32>reg add "hklm\system\currentControlSet\Control\Terminal Server" /v "AllowTSConnections" /t REG_DWORD /d 1 /f The operation completed successfully. C:\Windows\system32>net start Termservice The Remote Desktop Services service is starting. The Remote Desktop Services service was started successfully. C:\Windows\system32>ipconfig Windows IP Configuration Ethernet adapter Ethernet: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::2cb4:3a4d:dff5:9f0c%3 IPv4 Address. . . . . . . . . . . : 192.168.4.5 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.4.1 But rdesktop cannot connect: $ ping 192.168.4.5 PING 192.168.4.5 (192.168.4.5): 56 data bytes 64 bytes from 192.168.4.5: icmp_seq=0 ttl=128 time=0.314 ms $ rdesktop 192.168.4.5 ERROR: 192.168.4.5: unable to connect Any ideas? Thanks, Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Windows support in bhyve
Excerpts from Allan Jude's message from Mon 14-Dec-15 14:26: > On 2015-12-14 11:43, Sergey Manucharian wrote: > > > > But rdesktop cannot connect: > > > > $ ping 192.168.4.5 > > PING 192.168.4.5 (192.168.4.5): 56 data bytes > > 64 bytes from 192.168.4.5: icmp_seq=0 ttl=128 time=0.314 ms > > > > $ rdesktop 192.168.4.5 > > ERROR: 192.168.4.5: unable to connect > > You likely have to allow it through the windows firewall. > > Last time I had to do this from a command prompt, i used netcmd or > something, I don't recall now, it was 7 or 8 years ago. I hope I've disabled it through the command line. The ping didn't go through before, then it does. I thought it could be also RDP protocol version (it's 8.0) problem, tried xfreerdp and a connection from another Win7 Windows computer - no luck... I've also disabled Network Layer autentication in Widnows Server. Don't know what else can cause that. Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Windows support in bhyve
Excerpts from Trent Thompson's message from Mon 14-Dec-15 13:26: > Can you confirm Remote Desktop Services is running? > You can try something like `net start | more` to see services that are > running via CMD. It does: C:\Windows\system32>net start | more These Windows services are started: . Print Spooler Program Compatibility Assistant Service Remote Desktop Services Remote Procedure Call (RPC) RPC Endpoint Mapper Security Accounts Manager . The command completed successfully. C:\Windows\system32>sc query termservice SERVICE_NAME: termservice TYPE : 20 WIN32_SHARE_PROCESS STATE : 4 RUNNING (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN) WIN32_EXIT_CODE: 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 Thanks, Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Windows support in bhyve
Excerpts from Peter Grehan's message from Sun 04-Oct-15 13:11: > As of r288524, bhyve has preliminary support to run Windows in headless > mode using UEFI firmware. > > Since it's headless, the install process consists of modifying the > Windows install ISO to include an 'unattend' XML script that automates > the install, and also inserting the virtio network driver currently > required by bhyve. > > This has been tested with 64-bit Windows Server 2k12r2 and 2k16 tp3, and > Windows 10. The server versions are recommended since they have serial > console support, whereas the desktop install is a black-screen experience. > > ISO repack instructions at: > http://people.freebsd.org/~grehan/bhyve_uefi/windows_iso_repack.txt > > Install/run instructions at: > http://people.freebsd.org/~grehan/bhyve_uefi/windows_install.txt > > Please give this a try and report back on how it goes. > Another report: Windows 2012 works perfectly. FreeBSD 11-CURRENT on Thinkpad T430. Also I was able to pass through USB3 controller to Windows. Thinkpad has another USB2 controller which I kept with FreeBSD. Thanks! Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
CDROM options in bhyve
Hello, Currently bhyve supports attaching a cd image when started. Is there any way to "change" it when the guest is already running? Is there a way to attach the host's CD/DVD drive? E.g. it would be useful to be able creating symlink to an image file, and then re-point it to another one (currently does not work). Thanks, Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: CDROM options in bhyve
Excerpts from Anish's message from Wed 16-Dec-15 11:08:
> >Is there any way to "change" it when the guest is already running?
> You can specify at boot time, for example in vmrun.sh
>
> -s $(($nextslot+1)):0,virtio-blk,${isofile}
>
> 'isofile' is specified using '-I' argument
>
> $./vmrun.sh -I vm1
>
> Once system is booted, you will see two virtio-block:
>
> 1. vtbd0 -> Boot HDD
>
> 2. vtbd1 -> CDROM image or ISO file.
Yes, it is clear how to do at boot time. I'd like to be able to change
it AFTER the guest is up and running.
By the way, for Windows guest I'm using AHCI, not virtio (per the
instructions):
... -s 4,ahci-cd,$CD ...
I don't see any device created (I'm not sure what's the possible name though).
Thanks,
Sergey
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"
Re: CDROM options in bhyve
Hi Peter, Excerpts from Peter Grehan's message from Thu 17-Dec-15 18:23: > It should be a 'D' drive. Appended is a list from a w2k16 VM, with a > FreeBSD ISO on the ahci-cd drive (so it isn't bootable). You can also view > this graphically using Windows Administrative Tools -> System Information -> > Components -> CDROM. I think I haven't expressed my thoughts properly. Everything is OK on the guest side. The cdrom device is working fine in both Linux and Windows guests. My original question was about changing the cdrom image in the host when the guset is up and running - to make the guest seeing a new disk in the virtual drive. That's why I thought Anish mentioned devices created in the host system (vtbd0), but I was wrong. I was thinking about an idea to use a symlink to an .iso file in the host before the guest is booted, then, if needed, to re-point the symlink to another .iso file. But that doesn't work, of course. Thanks, Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
bhyve PCI pass-through to Linux guest
Hello, I have a working Linux guest in bhyve (Debian). Trying to pass through a PCI device (USB controller) by adding a couple of options: # bhyve -S ... -s 7,passthru,0/20/0 ... That causes bhyve termination right away with error: Unable to setup memory (17) Exactly the same option with passing the same USB controller to Windows 2012 guest works perfectly. The only difference (by my understanding) is that I load UEFI for Windows and use grub-bhyve for Linux. What should I check? Thanks, Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve PCI pass-through to Linux guest
Excerpts from Peter Grehan's message from Sun 20-Dec-15 15:02: > > > > # bhyve -S ... -s 7,passthru,0/20/0 ... > > > Make sure you are also passing the '-S' option to grub-bhyve to force > wiring of memory. Sure! I showed it in the command line above. Without that bhyve says: "passthru requires guest memory to be wired" S. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve PCI pass-through to Linux guest
Excerpts from Peter Grehan's message from Sun 20-Dec-15 15:18: > >>> # bhyve -S ... -s 7,passthru,0/20/0 ... > >>> > >>Make sure you are also passing the '-S' option to grub-bhyve to force > >> wiring of memory. > > > > Sure! I showed it in the command line above. > > That's the bhyve command line (if that's the one you meant). You also > have to pass '-S' when invoking grub-bhyve, since that's when the memory > resources are created. Thanks, Peter! I've missed that! What a foolish omission! Works fine now. S. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: available hypervisors in FreeBSD
Excerpts from Miroslav Lachman's message from Sun 20-Dec-15 09:57: > Peter Ross wrote on 12/20/2015 09:15: > >> As far as my homework digging revealed, FreeBSD supports four > >> hypervisors: > >> > >> * bhyve > >> * KVM > >> * QEMU > >> * VirtualBox > > > > .. and later Xen was mentioned. > > > > Which of the solutions are worth testing? Do you have recommendations? > > > > I am thinking of server software and "containerisation" only, so USB > > passthrough or PCI etc. is not really important. > > > > Stability, performance and resource utilisation (e.g. possible > > over-allocation of RAM) are matter most. > > VirtualBox is the most usable and you can use it in headless mode. If > you are really not satified with VirtualBox, you can try Xen. I agree that VirtualBox is really stable, and I'm using it in production environments for many years. However, there are a couple of possible drawbacks: It does not support VRDP (remote console) and USB2/3 on FreeBSD. Tha latter is probably not really important (although I needed it too). The lack of remote console is bad for troubleshooting and/or remote (re)installation. Currently I have one bhyve Windows Server 2012 machine, which works fine, although it's not really loaded at the moment. Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: available hypervisors in FreeBSD
Excerpts from Adam Vande More's message from Sun 20-Dec-15 09:36: > On Sun, Dec 20, 2015 at 9:25 AM, Sergey Manucharian wrote: > > > I agree that VirtualBox is really stable, and I'm using it in production > > environments for many years. However, there are a couple of possible > > drawbacks: It does not support VRDP (remote console) and USB2/3 on FreeBSD. > > > > Tha latter is probably not really important (although I needed it too). > > The lack of remote console is bad for troubleshooting and/or remote > > (re)installation. > > > > Remote console is available via VNC, not RDP. It is VNC, and I use it Linux hosts, it's rather confusing since the option is "--vrde on|off". But isn't it a part of the extension pack, which is not available for FreeBSD? https://www.virtualbox.org/manual/ch07.html S. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve PCI pass-through to Linux guest
Excerpts from Sergey Manucharian's message from Sat 19-Dec-15 22:36: > Excerpts from Peter Grehan's message from Sun 20-Dec-15 15:18: > > >>> # bhyve -S ... -s 7,passthru,0/20/0 ... > > > > That's the bhyve command line (if that's the one you meant). You also > > have to pass '-S' when invoking grub-bhyve, since that's when the memory > > resources are created. > > Works fine now. This is pretty reproducible: I pass trough a PCI device (USB controller) to a Linux guest. It works properly. Then I halt the VM, make sure that bhyve destroyed it and run Windows guest with the same PCI device passed-through. Windows device manager does show the device, however, e.g. a flash drive plugged in is not presented to Windows, instead it's being processed by FreeBSD. After that it does not work in Linux guest as well. Kernel module (vmm) unloading and reloading does not help. Of course, I never run two guests with the same PCI pass-through device. Thanks for advices, Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve PCI pass-through to Linux guest
Excerpts from Peter Grehan's message from Tue 22-Dec-15 13:09: > Hi Sergey, > > > This is pretty reproducible: > > > > I pass trough a PCI device (USB controller) to a Linux guest. It works > > properly. Then I halt the VM, make sure that bhyve destroyed it and run > > Windows guest with the same PCI device passed-through. > > > > Windows device manager does show the device, however, e.g. a flash drive > > plugged in is not presented to Windows, instead it's being processed by > > FreeBSD. > > > > After that it does not work in Linux guest as well. Kernel module (vmm) > > unloading and reloading does not help. > > The flash drive being processed by FreeBSD would indicate that it has > ownership of the device. Would you be able to try a 'pciconf -vl' after > the Linux guest exists, and after the Windows guest exits ? OK, I've experimented more and found that even with the same Linux VM after halting it once, the pass-through device doesn't work when that Linux guest is restarted again. It looks that both host and guest report exactly the same data before and after restarting the guest: Linux - first run: = $ lspci -v 00:07.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) (prog-if 30 [XHCI]) Subsystem: Lenovo Device 21f3 Flags: bus master, medium devsel, latency 0, IRQ 24 Memory at c001 (64-bit, prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0781:5530 SanDisk Corp. Cruzer Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub FreeBSD when Linux is running first time: = $ pciconf -v ppt0@pci0:0:20:0: class=0x0c0330 card=0x21f317aa chip=0x1e318086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '7 Series/C210 Series Chipset Family USB xHCI Host Controller' class = serial bus subclass = USB Linux - second run: === $ lspci -v 00:07.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) (prog-if 30 [XHCI]) Subsystem: Lenovo Device 21f3 Flags: bus master, medium devsel, latency 0, IRQ 24 Memory at c001 (64-bit, prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Kernel driver in use: xhci_hcd FreeBSD when Linux is running second time: == $ pciconf -lv ppt0@pci0:0:20:0: class=0x0c0330 card=0x21f317aa chip=0x1e318086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '7 Series/C210 Series Chipset Family USB xHCI Host Controller' class = serial bus subclass = USB -- Thanks, Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Re: {Spam?} Re: bhyve PCI pass-through to Linux guest
Excerpts from Trent Thompson's message from Mon 21-Dec-15 20:48: > I've seen some success passing through devices that have their driver > disabled in the FreeBSD kernel. > See the USB 3.0 pass through that Eresia set up in iohyve. > https://github.com/pr1ntf/iohyve/wiki/USB-3.0-PCI-Controller-Pass-through > > When he disabled the kernel module in FreeBSD, he can then use the device > in the bhyve guest. Thank you for the advice, Trent. Of course, that's probably a good work-around. However if it works once there should be a way to rectify that behaviour. Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve PCI pass-through to Linux guest
Excerpts from Anish's message from Mon 21-Dec-15 21:48: > >ppt0@pci0:0:20:0: class=0x0c0330 card=0x21f317aa chip=0x1e318086 > Passthrough stub driver, part of vmm, controls the USB controller. > > Can you share output of /usr/sbin/devinfo from FreeBSD host, highlighting > the usb mass/flash device in tree? > Before I start the guest VM the flash drive is not in the list. Right after shuting down the guest OS it appears: pcib1 pci1 sdhci_pci0 pcib2 pci2 iwn0 pcib3 pci3 ehci1 usbus1 uhub1 uhub3 umass0 As you can see it's under "ehci", it looks that my USB3 controller is fully USB2 backward compatible and work with "ehci" driver. I tried (as Trent suggested in this thread) to recompile the kernel without "xhci", and nothing changed, still behaves exactly the same way.. S. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve PCI pass-through to Linux guest
Excerpts from Peter Grehan's message from Tue 22-Dec-15 13:09: > > I pass trough a PCI device (USB controller) to a Linux guest. It works > > properly. Then I halt the VM, make sure that bhyve destroyed it and run > > Windows guest with the same PCI device passed-through. > > > > Windows device manager does show the device, however, e.g. a flash drive > > plugged in is not presented to Windows, instead it's being processed by > > FreeBSD. > > > > After that it does not work in Linux guest as well. Kernel module (vmm) > > unloading and reloading does not help. > > The flash drive being processed by FreeBSD would indicate that it has > ownership of the device. Would you be able to try a 'pciconf -vl' after > the Linux guest exists, and after the Windows guest exits ? First of all I found that I do not need to switch between guests. It is 100% reproducible with a single Linux VM. In freshly booted FreeBSD the USB ports (ones passed through) do not sense any device plugged in. When I boot Linux VM, it fully controls those ports, and I see the USB flash in Linux. As soon as I halt Linux, the flash drive appears in the host! Today I've checked out the latest sources and recompiled the whole system. Nothing has changed. Here is the corresponding output of pciconf iand devinfo after Linux exits: $ pciconf -vl ppt0@pci0:0:20:0: class=0x0c0330 card=0x21f317aa chip=0x1e318086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '7 Series/C210 Series Chipset Family USB xHCI Host Controller' class = serial bus subclass = USB $ devinfo | grep -B15 mass pcib1 pci1 sdhci_pci0 pcib2 pci2 iwn0 pcib3 pci3 ehci1 usbus1 uhub1 uhub3 umass0 -- S. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
floppy image in bhyve
Hi folks, It there a way to use a floppy image in bhyve? Could it be used with one of virtio-blk or ahci-hd? I need to present it to MS Windows 7 at boot time. Thanks for advices, Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: floppy image in bhyve
Thanks, Peter! Excerpts from Peter Grehan's message from Wed 20-Jan-16 10:18: > >I need to present it to MS Windows 7 at boot time. > > If this is for a Windows driver, you could potentially extract the files > from the floppy image and then put it on an ISO (or even put it on the > repacked install ISO if this is during installation) and use ahci-cd. In this particular case it doesn't work. I have a floppy image with BitLocker encryption key. I copied that file to an iso image, but Windows doesn't like it. Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: floppy image in bhyve
Excerpts from Marie's message from Thu 21-Jan-16 01:56: > > In this particular case it doesn't work. I have a floppy image with > > BitLocker encryption key. I copied that file to an iso image, but > > Windows doesn't like it. > > As a workaround: How about plugging in a USB floppy drive and do a > pass-through of it? Yes, that a good idea especially taking into account that I have many variables. I'm trying to migrate Windows 7 on an encrypted volume from VBox to bhyve. The advantage of a floppy drive is that it's drive letter in Windows is always "A:". I believe the ecnryption key is tied to it too. Currently I'm going to decrypt it first to make sure that the migration itself works. Then will follow in particular your advice. The USB contrell pass-trough is a must for me since I need many USB devices in that virtualized Windows. Thanks, Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
bhyve guest from physical disk
Is it possible to run a bhyve guest from physical disk? I tried adding this option: -s 3,ahci-hd,/dev/ada2 but it doesn't work. Here is the output I see on the serial console, then it falls into EFI shell. -8<- Buffer: EFI Hard Drive Overriding HandleProtocol for bhyve guests Memory Previous CurrentNext TypePages Pages Pages == 0A0004 0001 0004 090008 0008 0008 000004 0004 060024 0042 0052 050030 004A 005C 030180 03A6 048F 040F00 0C9A 0F00 Booting EFI Hard Drive BlockSize : 512 LastBlock : 1D1A94A1 BlockSize : 512 LastBlock : 1FF BlockSize : 512 LastBlock : 1B1A8CA1 PlatformBdsBootFail Boot Failed. EFI Hard Drive . -8<- ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve guest from physical disk
Thanks, Allan! Excerpts from Allan Jude's message from Thu 21-Jan-16 10:22: > On 2016-01-21 10:11, Sergey Manucharian wrote: > > Is it possible to run a bhyve guest from physical disk? > > I tried adding this option: > > > > -s 3,ahci-hd,/dev/ada2 > > > > but it doesn't work. > > Make sure that the device is not in use by anything else. Also, does > that device contain an EFI boot partition? This is a great question. Most likely not, besides the main one, it has only regular 100M Windows boot partition. However EFI should support legacy boot anyway, correct? Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve with Linux guest, how to safely handle updates?
Hi Dean, Excerpts from dweimer's message from Tue 26-Jan-16 08:26: > I installed some updates using Aptitude within the > Debian guest which promptly broke the VM. Additional info is needed to help: - bhyve command line you use to start the VM - what error messages do you see stating that it's broken? Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve with Linux guest, how to safely handle updates?
Excerpts from dweimer's message from Tue 26-Jan-16 19:07: > > Is there anything that normally needs to be done after a Linux kernel > update to refresh the grub2-bhyve setup? The kernel update should not have any effect since grub-bhyve uses the virtual disk mapping file, which should point to your linux drive. I'm using the following command: $ sudo grub-bhyve -m /path/to/device.map -r hd0,msdos1 -M 1024M debian where "device.map" contains the following: (hd0) /dev/zvol/zroot/linuxdisk1 (cd0) /stuff/vm/bhyve/debian/debian-testing-amd64-2015-11-30.iso "hd0" can be a real disk device, e.g. /dev/sda, or an image file (in my case it's a ZFS volume). How do you use that VM in VBox? If it's a .vdi file, bhyve will not be able to recognize it. You should use a raw HDD image file. To make it compatible with VBox you can create a .vmdk file pointing to that raw image. -- Sergey ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
