Re: Curent Centos 7 and bhyve
Rodney W. Grimes wrote: [dd] > > > > > > > > > > Though it has a lot of features, it also has some short comings, > > > > > like you can not spec a vm to be wired in memory, which IMHO is > > > > > the only way to insure consistent VM performance. > > > > > > > > Well, we have "bhyve_options" configuration option in the vm config, > > > > why not put "-S" there, is that what you mean by wiring the vm in > > > > memory? > > > > > > I believe that fails as that only adds the -S to bhyve, and > > > you must specify it both on bhyveload and bhyve for it to > > > work. > > > > I think it is totally doable becase vm-bhyve is nothing but a suit of > > scripts. A PR with a feature request would be appropriate. > > I made several attempts to contact the author at the email address > provided at the git hub while making other bhyve changes to try > and coordinate with him. I got no response after 3 attempts, > so have stopped trying to contact them. (This was while I was > adding the -c cpu topology modifications.) You can add yourself to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230580 maybe something useful comes out of it. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN AS43859 ___ 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 230402] With buildworld, the system can not use swap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230402 Mark Linimon changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2304 ||54 Severity|Affects Only Me |Affects Some People -- 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"
[Bug 230402] With buildworld, the system can not use swap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230402 Mark Linimon changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2276 ||09 -- 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"
[Bug 230402] With buildworld, the system can not use swap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230402 --- Comment #9 from Mark Millard --- (In reply to Mark Millard from comment #8) Other bugzilla's are: 227609 230454. -- 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"
[Bug 230402] With buildworld, the system can not use swap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230402 --- Comment #8 from Mark Millard --- (In reply to Mark Millard from comment #7) [This is extracted from another context that involved the Pine64+ 2GB.] As of updating to -r337400 the Pine64+ 2GB no longer will boot from the e.MMC on the microsd adapter card. (I switched to tracking fully modern dts use, u-boot, etc.) So I tried a build via a USB SSD as the root file system and swap partition. As reported in: https://lists.freebsd.org/pipermail/freebsd-arm/2018-August/018605.html it failed with an OOM kill. This should have avoided I/O latency problems being involved. (That message is part of a long on-going thread tied to OOM kills, most of the reports involving large I/O latencies being involved.) I can not change the "Afects Only Me" status. -- 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: Curent Centos 7 and bhyve
> Rodney W. Grimes wrote: > > > Rodney W. Grimes wrote: > > > > > > > > > > Are there issues with Current CEntos and bhyve? > > > > > > > > > > > > > > > > > > Sure there are, please look at > > > > > > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230453 > > > > > > > > > > > > > > > > Booting in UEFI mode works. > > > > > > > > > > > > > > This means we need an update to > > > > > > > /usr/local/share/examples/vm-bhyve/centos7.conf ? > > > > > > > It says 'loader="grub"' for the present. > > > > > > > > > > > > > > Do you have a vm config to boot centos7 in UEFI mode you could > > > > > > > share? > > > > > > > > > > > > I just use /usr/share/examples/bhyve/vmrun.sh. I don't use any > > > > > > third-party utility to manage bhyve VMs. vmrun.sh is pretty > > > > > > straight-forward. > > > > > > > > > > Thanks for replying. However, I highly recommend vm-bhyve, maybe you > > > > > should give it a try. You will love the ease of VM creation and > > > > > provisioning, network management, ZFS integration (VM snapshots and > > > > > cloning), console and datastore management etc. > > > > > > > > Though it has a lot of features, it also has some short comings, > > > > like you can not spec a vm to be wired in memory, which IMHO is > > > > the only way to insure consistent VM performance. > > > > > > Well, we have "bhyve_options" configuration option in the vm config, > > > why not put "-S" there, is that what you mean by wiring the vm in > > > memory? > > > > I believe that fails as that only adds the -S to bhyve, and > > you must specify it both on bhyveload and bhyve for it to > > work. > > I think it is totally doable becase vm-bhyve is nothing but a suit of > scripts. A PR with a feature request would be appropriate. I made several attempts to contact the author at the email address provided at the git hub while making other bhyve changes to try and coordinate with him. I got no response after 3 attempts, so have stopped trying to contact them. (This was while I was adding the -c cpu topology modifications.) > > What about VM that don't use bhyveload, but some other kind of loader > like grub2-bhyve? I am not sure how vm-bhyve deals with that as I have none of those type VM's. > > > > > > > > > Its artificial restriction of 16 character VM names is also > > > > a fair bit annoying. > > > > > > Maybe. > > > > Maybe? No, factually. I migrated a number of ESXi VM's and > > had to patch vm-bhyve to not have this restriction, so it is > > annoying. > > Did you send your patches upstream? Could not even get an email ack from upstream. -- 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"
[Bug 230402] With buildworld, the system can not use swap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230402 Mark Linimon changed: What|Removed |Added Component|bin |misc -- 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"
[Bug 184046] bhyve(4) manpage references non-existant manpages bhyvectl(8), vmm(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184046 Mateusz Piotrowski <0...@freebsd.org> changed: What|Removed |Added CC||0...@freebsd.org Resolution|--- |FIXED Status|In Progress |Closed -- 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"
