Bhyve / Windows Server 2016 Issue
Has anyone tried to RPC into a Virtual Windows 2016 server box in FreeBSD Successfully? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism God is dead! Yahweh lives! Jesus his only begotten Son is the Risen Saviour!! ___ 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: Installing Freebsd guests under bhyve without using scripts
Yes, you need bhyveload to load guest OS, setup hypervisor
nested{EPT/NPT] page table etc, see vmrun.sh
${LOADER} -c ${console} -m ${memsize} -d ${BOOTDISK} ${loader_opt} \
${vmname}
LOADER=bhyveload
and then use 'bhyve' to start and run guest/VM.
${FBSDRUN} -c ${cpus} -m ${memsize} ${apic_opt} -A -H -P\
-g ${gdbport}\
-s 0:0,hostbridge\
-s 1:0,lpc\
${devargs}\
-l com1,${console}\
${installer_opt}\
${vmname}
FBSDRUN=bhyve
Of course ${memsize}, ${vmname} etc must match between bhyveload and bhyve.
-Anish
On 2/13/17 1:29 PM, C. L. Martinez wrote:
Hi all,
What are the steps to install freebsd guests under bhyve without using
iocage, vm-bhyve or vmrun.sh??
Do I need to use first bhyveload and after bhyve -A -c 1 -u, etc??
Thanks.
___
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"
___
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"
Installing Freebsd guests under bhyve without using scripts
Hi all, What are the steps to install freebsd guests under bhyve without using iocage, vm-bhyve or vmrun.sh?? Do I need to use first bhyveload and after bhyve -A -c 1 -u, etc?? Thanks. ___ 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 211746] [Hyper-V] UEFI VM can't boot from the iso installation disk
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211746 --- Comment #6 from Marcel Moolenaar --- Check in the EFI memory map whether there's runtime-persistent memory at 0x20 + 45MB (or abouts). Runtime persistent memory are memory allocations of type runtime, firmware, (e.g. ACPI non-reclaimable), etc. I.e anything that the kernel can't use during runtime. If the memory at 0x20 isn't free during runtime, then we have a real problem... Some background: FreeBSD makes an invalid or at least a questionable assumption that the memory map under EFI is compatible with the memory layout as seen under the BIOS. As time goes by, this will probably be less and less valid. The staging area is a side-effect of the kernel wanting to be loaded in a contiguous memory region, starting at 0x20. Something that is can't be done under EFI without a staging area. To wit: The old (and now removed) Itanium kernel used a virtual address space for the kernel. The contiguous virtual kernel address mapped to underlying EFI allocated pages that didn't have to be contiguous. On Itanium the physical memory map could be without addressable memory in the first 4GB even, so no amount of staging would be able to handle that. Hopefully the problem is much more trivial than all of that... -- You are receiving this mail because: You are the assignee 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: tap interfaces disappears after bhyve guests shutdowns
On Mon, Feb 13, 2017 at 12:09:38PM +, C. L. Martinez wrote: > Hi all, > > Why when a bhyve guest shutdowns or reboot tap interfaces goes down and lost > IP assigned address?. I need to use same tap interface for several guests and > assign an IP to this tap interface to act as a router for these guests. > > How can I do a "persistent tap" interface?? > > Thanks. > I > -- > Greetings, > C. L. Martinez Here is wht I do in my /etc/rc.local file /sbin/ifconfig tap8 inet 204.209.81.52 netmask 0xff00 /sbin/ifconfig tap0 inet 204.209.81.53 netmask 0xff00 /sbin/ifconfig tap1 inet 204.209.81.54 netmask 0xff00 /sbin/ifconfig tap7 inet 204.209.81.55 netmask 0xff00 /sbin/ifconfig tap2 inet 204.209.81.56 netmask 0xff00 /sbin/ifconfig tap4 inet 204.209.81.57 netmask 0xff00 /sbin/ifconfig tap3 inet 204.209.81.58 netmask 0xff00 /sbin/ifconfig tap6 inet 204.209.81.59 netmask 0xff00 /sbin/ifconfig bridge0 alias 204.209.81.60 netmask 0xff00 /sbin/ifconfig tap5 inet 204.209.81.61 netmask 0xff00 /sbin/ifconfig tap9 inet 204.209.81.62 netmask 0xff00 /sbin/ifconfig tap10 inet 204.209.81.63 netmask 0xff00 /sbin/ifconfig tap11 inet 204.209.81.64 netmask 0xff00 /sbin/ifconfig tap12 inet 204.209.81.65 netmask 0xff00 /sbin/ifconfig tap13 inet 204.209.81.66 netmask 0xff00 /sbin/ifconfig tap14 inet 204.209.81.67 netmask 0xff00 /sbin/ifconfig tap15 inet 204.209.81.68 netmask 0xff00 You can do something similar in /etc/rc.conf > ___ > 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" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism God is dead! Yahweh lives! Jesus his only begotten Son is the Risen Saviour!! ___ 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 211746] [Hyper-V] UEFI VM can't boot from the iso installation disk
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211746 --- Comment #5 from Dexuan Cui --- (In reply to Dexuan Cui from comment #4) > last = (uint64_t *)staging + (1024*1024*45); I meant last = (uint64_t *) (staging + (1024*1024*45)); (I missed a pair of parentheses) -- You are receiving this mail because: You are the assignee 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"
[Bug 211746] [Hyper-V] UEFI VM can't boot from the iso installation disk
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211746 --- Comment #4 from Dexuan Cui --- (In reply to Marcel Moolenaar from comment #3) Hi Marcel, Thank you for the quick help! Yes, I checked all the AllocatePages() calls and they all succeeded, i.e. returning 0. I found the crash happened in elf64_exec() -> trampoline() -> efi_copy_finish -> *dst++ = *src++; In efi_copy_finish(), I added some printf's to dump the values of the varilables: /boot/kernel/kernel text=0xfe3048 data=0x128b68+0x207fa0 syms=[0x8+0x146f88+0x8+ Booting... Start @ 0x802e2640 ... EFI framebuffer information: addr, size 0xf800, 0x80 dimensions 1024 x 768 stride 1024 masks 0x00ff, 0xff00, 0x00ff, 0xff00 efi_copy_finish : staging=0xf37cb000 efi_copy_finish : staging_end=0xf67cb000 efi_copy_finish : staging_offset=0xf35cb000 efi_copy_finish : src=0xf37cb000, dst=0x20, last=0xf67cb000 If I change the line last = (uint64_t *)staging_end; to last = (uint64_t *)staging + (1024*1024*45); The crash won't happen and the kernel can boot fine. I'm using the releng/10.3 branch, where EFI_STAGING_SIZE is 48MB. This is to say, the kernel can boot fine if I use EFI_STAGING_SIZE=45MB. Any idea? Why do you think is it a Hyper-V firmware bug in AllocatePages()? I'm not familar with UEFI Boot Services. :-) I'll check the memory map before/after the call to AllocatePages(). I'm going to use sys/boot/efi/loader/main.c: command_memmap() as an example to call GetMemoryMap. -- You are receiving this mail because: You are the assignee 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: tap interfaces disappears after bhyve guests shutdowns
On 02/13/17 13:37, Miroslav Lachman wrote: C. L. Martinez wrote on 2017/02/13 13:09: Why when a bhyve guest shutdowns or reboot tap interfaces goes down and lost IP assigned address?. I need to use same tap interface for several guests and assign an IP to this tap interface to act as a router for these guests. IP address is set on the guest, so as long as you have the network set up the IP address will be persistent. What you need is a bridge to which you add all your tap interfaces. Set the kernel state as advised by Martinez and make sure you have it also in /etc/sysctl.conf: #sysctl net.link.tap.up_on_open=1 #echo "net.link.tap.up_on_open=1" >> /etc/sysctl.conf Create a bridge interface: #ifconfig bridge0 create Add your host interface if you want external connectivity for your guests: #ifconfig bridge0 addm em0 Create the tap interfaces for the guests: #ifconfig tap0 create #ifconfig tap1 create Add them to the bridge: #ifconfig bridge0 addm tap0 addm tap1 After booting the guests, they will be both bridged with your physical interface em0 (replace em0 with your actual interface): #ifconfig bridge0 bridge0: flags=8843 metric 0 mtu 1500 description: vm-local ether 02:ed:0d:ca:74:00 nd6 options=1 groups: bridge id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: tap1 flags=143 ifmaxaddr 0 port 5 priority 128 path cost 200 member: tap0 flags=143 ifmaxaddr 0 port 4 priority 128 path cost 200 member: em0 flags=143 ifmaxaddr 0 port 1 priority 128 path cost 2 Perhaps you could use an utility to manage the VMs, like vm-bhyve, iohyve, etc. How can I do a "persistent tap" interface?? I think you need this sysctl: # sysctl -d net.link.tap.up_on_open net.link.tap.up_on_open: Bring interface up when /dev/tap is opened ___ 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" ___ 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: tap interfaces disappears after bhyve guests shutdowns
C. L. Martinez wrote on 2017/02/13 13:09: Why when a bhyve guest shutdowns or reboot tap interfaces goes down and lost IP assigned address?. I need to use same tap interface for several guests and assign an IP to this tap interface to act as a router for these guests. How can I do a "persistent tap" interface?? I think you need this sysctl: # sysctl -d net.link.tap.up_on_open net.link.tap.up_on_open: Bring interface up when /dev/tap is opened ___ 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"
tap interfaces disappears after bhyve guests shutdowns
Hi all, Why when a bhyve guest shutdowns or reboot tap interfaces goes down and lost IP assigned address?. I need to use same tap interface for several guests and assign an IP to this tap interface to act as a router for these guests. How can I do a "persistent tap" interface?? Thanks. I -- Greetings, C. L. Martinez ___ 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"
