Re: NVMe and Bhyve
> On Mon, 18 Feb 2019 at 02:58, Victor Sudakov wrote: > > > > > Or at least please tell me how I can attach another iso image (with > > drivers) when running "vm install myhost windows.iso" > > > Technically, you should be able to define something like: > > disk1_type="ahci-cd" > disk1_name="virtio-win-0.1.164.iso" > disk1_dev="file" or disk1_dev="custom" if you wish to use a path in disk1_name, I still do not know why this needs to be treated differently, a path should just work :-( > in the vm.conf file if the virtio-win-0.1.164.iso is located in > /vm/servername/ directory. -- Rod Grimes rgri...@freebsd.org ___ 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: NVMe and Bhyve
On Mon, 18 Feb 2019 at 12:09, Victor Sudakov wrote: > > Well, disk0 will be the guest HDD to install to, disk1 will be the ISO with > drivers, and which disk will be the ISO attached by the "vm install" > command? > > From a user perspective, this is not of any value to know. vm-bhyve manages that in the background and usually puts the regular disk0 as -s 4:0 regardless of normal boot or install and when the installer is invoked, puts the installer iso in as -s 3:0 So based on previous examples, you'd see something like this in the log: -s 3:0,ahci-cd,/vm/.iso/myinstaliso.iso -s 4:0,ahci-hd,/dev/zvol/mypool/vm/myserver/disk0 -s 5:0,ahci-cd,/vm/myserver/virtio-win-0.1.164.iso ___ 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: NVMe and Bhyve
Jason Tubnor wrote: > On Mon, 18 Feb 2019 at 02:58, Victor Sudakov wrote: > > > > > Or at least please tell me how I can attach another iso image (with > > drivers) when running "vm install myhost windows.iso" > > > Technically, you should be able to define something like: > > disk1_type="ahci-cd" > disk1_name="virtio-win-0.1.164.iso" > disk1_dev="file" > > in the vm.conf file if the virtio-win-0.1.164.iso is located in > /vm/servername/ directory. Well, disk0 will be the guest HDD to install to, disk1 will be the ISO with drivers, and which disk will be the ISO attached by the "vm install" command? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ signature.asc Description: PGP signature
Re: NVMe and Bhyve
On Mon, 18 Feb 2019 at 02:58, Victor Sudakov wrote: > > Or at least please tell me how I can attach another iso image (with > drivers) when running "vm install myhost windows.iso" Technically, you should be able to define something like: disk1_type="ahci-cd" disk1_name="virtio-win-0.1.164.iso" disk1_dev="file" in the vm.conf file if the virtio-win-0.1.164.iso is located in /vm/servername/ directory. ___ 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 2019 server
On Sun, 17 Feb 2019 at 23:35, The Doctor via freebsd-virtualization < freebsd-virtualization@freebsd.org> wrote: > On Sun, Feb 17, 2019 at 08:31:58AM +0100, Florian Smeets wrote: > > On 16.02.19 13:38, The Doctor via freebsd-virtualization wrote: > > > Anyone got Windows 2019 server running in bhyve ? > > > > > > > Yes, on stable/12 (r343339) using > > https://github.com/churchers/vm-bhyve/wiki/Running-Window. Worked like a > > charm. > > > > I am on FreeBSD 11.2 FYI > > > Yes, on 11.2 using ahci-hd storage presentation to the installer and UEFI boot. ___ 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"
[Bug 212782] [bhyve] Increasing VM_MAXCPU to >= 26 will result in ACPI MADT table corruption
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212782 Rodney W. Grimes changed: What|Removed |Added Flags||mfc-stable11+, ||mfc-stable12+ Status|New |In Progress -- You are receiving this mail because: You are on the CC list for the bug. ___ 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: NVMe and Bhyve
Victor Sudakov wrote: > > If anyone has been successful with viostor(?), please share your experience. Or at least please tell me how I can attach another iso image (with drivers) when running "vm install myhost windows.iso" -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ signature.asc Description: PGP signature
[Bug 215077] bhyve should allow per-guest configuration of CPU socket/cores/threads
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215077 --- Comment #4 from Rodney W. Grimes --- (In reply to Tsaukpaetra from comment #1) I have WIP to fix that very issue, but first I had to fix several issues that do not even allow us to go above 21 or 24 CPU's, corrections for that which allow us to go up to 254 vCPU are now in review: https://reviews.freebsd.org/D18815 https://reviews.freebsd.org/D18816 https://reviews.freebsd.org/D18998 and first steps in removing VM_MAXCPU are also in review: https://reviews.freebsd.org/D18846 https://reviews.freebsd.org/D18755 Also you do not need to rebuild the kernel, there is a shorter list of what needs to be rebuilt. The most overlooked one is to run (cd /usr/src; make includes) so that the change of vmm.h gets installed into /usr/include, after that you just need to rebuild vmm.ko, libvmmapi, and bhyve/bhyveload. This work is still not merged to stable/11, iirc I ran into other intervening commits that have blocked that merge. -- You are receiving this mail because: You are on the CC list for the bug. ___ 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 2019 server
On Sun, Feb 17, 2019 at 08:31:58AM +0100, Florian Smeets wrote: > On 16.02.19 13:38, The Doctor via freebsd-virtualization wrote: > > Anyone got Windows 2019 server running in bhyve ? > > > > Yes, on stable/12 (r343339) using > https://github.com/churchers/vm-bhyve/wiki/Running-Window. Worked like a > charm. > I am on FreeBSD 11.2 FYI > Florian > -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism Do not consider painful what is good for you. -Euripides ___ 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"
does vtnet require iflib in the kernel?
Hi, Does vtnet require iflib in the kernel? thanks, -- J. ___ 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 2019 server
On 16.02.19 13:38, The Doctor via freebsd-virtualization wrote: > Anyone got Windows 2019 server running in bhyve ? > Yes, on stable/12 (r343339) using https://github.com/churchers/vm-bhyve/wiki/Running-Window. Worked like a charm. Florian signature.asc Description: OpenPGP digital signature
