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. > > I've already commented on the bug, although I'll reply here as well. > If "-S" is found in bhyve_options it does currently affect both commands. I > have decided that a specific wired_memory option is useful though and will > add this to the next release. > > The name limit has been increased to 32 since v1.2 >This is better, but still an artificial limit, the implementation of bhyve >allows this string to be any valid filename, the scripts should be designed to >allow for that as the valid limit. As far as I'm aware bhyve is currently limited to 32 characters, although this obviously may change. We use the name in various situations (interface descriptions, console names, etc) so it's beneficial to make sure it's not excessively long, or contains characters that could cause problems when used in other places. if(name == NULL || strlen(name) >= VM_MAX_NAMELEN) return (EINVAL); #define VM_MAX_NAMELEN 32 >I modified the script so that the vm name is the last column, and removed the >length check all togeather, this allows for the string to be what ever length >and not mess with column widths. >root@x230a:# vm list >DATASTORE LOADER CPUMEMORYVNC AUTOSTART >STATENAME >default bhyveload 1 128M -No >Stopped fb-bld-10-amd64 >default bhyveload 4 2048M -No >Stopped fb-bld-11-amd64 >default bhyveload 4 1024M -No >Stopped fb-bld-11-i386 >default bhyveload 1 128M -No >Stopped fb-bld-11.0-p1-amd64 >default bhyveload 1 128M -No >Stopped fb-bld-11.0-p1-i386 >default bhyveload 4 512M -No >Stopped fb-bld-11.1-amd64 >default bhyveload 4 512M -No >Stopped fb-bld-11.1-i386 >> I didn't realize the changes for cpu topology had actually made it >> into head, although I don't believe it's actually in a release yet? >Yes, they are in head, the MFC has been delayed for other reasons. >It is in the 12.0-ALPHA1 snapshot, and many before that. >> I will plan to support configuration and display of these before 12 >> release. >Thanks. I think mostly just extract the NCPU's from the topology string. The >code actually works now, but due to fixed column width assumptions the output >looks bad. I've added some additional cpu_ settings to control the new cpu fields. "vm list" just shows the original cpu setting so this remains unmodified. "vm info" shows full settings. > > Matt > > > -- > > 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" > > -- 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" ___ 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
Matt Churchyard wrote: > > Sorry, it looks like the change didn't make it into 1.1. You'd need > to upgrade to 1.2, which is in ports but looks like it hasn't made > it into pkg yet. portsmon.freebsd.org is still broken also so I > can't easily confirm whether it's made it into any of the > quarterly/latest pkg repos. (It was in ports over a month ago so > should at least be in latest) I see. My own poudriere has just built vm-bhyve-1.2.3, but I don't use my repo on that bhyve host, I use the official repo there. Does anyone know if I can install just one (or some) package from a different repo, the official one still remaining the default? -- 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"
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. > > I've already commented on the bug, although I'll reply here as well. > If "-S" is found in bhyve_options it does currently affect both commands. I > have decided that a specific wired_memory option is useful though and will > add this to the next release. > > The name limit has been increased to 32 since v1.2 This is better, but still an artificial limit, the implementation of bhyve allows this string to be any valid filename, the scripts should be designed to allow for that as the valid limit. I modified the script so that the vm name is the last column, and removed the length check all togeather, this allows for the string to be what ever length and not mess with column widths. root@x230a:# vm list DATASTORE LOADER CPUMEMORYVNC AUTOSTART STATENAME default bhyveload 1 128M -No Stopped fb-bld-10-amd64 default bhyveload 4 2048M -No Stopped fb-bld-11-amd64 default bhyveload 4 1024M -No Stopped fb-bld-11-i386 default bhyveload 1 128M -No Stopped fb-bld-11.0-p1-amd64 default bhyveload 1 128M -No Stopped fb-bld-11.0-p1-i386 default bhyveload 4 512M -No Stopped fb-bld-11.1-amd64 default bhyveload 4 512M -No Stopped fb-bld-11.1-i386 > I didn't realize the changes for cpu topology had actually made it > into head, although I don't believe it's actually in a release yet? Yes, they are in head, the MFC has been delayed for other reasons. It is in the 12.0-ALPHA1 snapshot, and many before that. > I will plan to support configuration and display of these > before 12 release. Thanks. I think mostly just extract the NCPU's from the topology string. The code actually works now, but due to fixed column width assumptions the output looks bad. > > Matt > > > -- > > 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" > > -- 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: 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. I added virtualization@ to the PR, though it looks as if wired_memory= has already been added as an option, which is what I did locally. -- 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: Curent Centos 7 and bhyve
> Matt Churchyard wrote: > wired_memory option has been added to next release. > Thanks a lot, Matt! May I ask a question: how is the "-S" option supposed to > work if the loader is not bhyveload, but grub2-bhyve or UEFI? In 1.2, if "-S" is found in bhyve_options, it adds this argument to the guest loader. This is done before choosing between bhyveload/grub2-bhyve and will be supplied to either. In 1.3 (GitHub only), which has a new wired_memory option, you will need to use this, as the slightly hacky grep to scan bhyve_options for -S and push this through to the loader has been removed. As far as I'm aware this is not an issue with UEFI as there is now just a single bhyve process (which gets all of bhyve_options) and no separate loader. Matt -- 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" ___ 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
Matt Churchyard wrote: > wired_memory option has been added to next release. Thanks a lot, Matt! May I ask a question: how is the "-S" option supposed to work if the loader is not bhyveload, but grub2-bhyve or UEFI? -- 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"
RE: Curent Centos 7 and bhyve
-Original Message- From: owner-freebsd-virtualizat...@freebsd.org On Behalf Of Victor Sudakov Sent: 13 August 2018 10:53 To: Matt Churchyard Cc: Rodney W. Grimes ; freebsd-virtualization@freebsd.org Subject: Re: Curent Centos 7 and bhyve Matt Churchyard wrote: > > Rodney W. Grimes wrote: > > [dd] > > > I've already commented on the bug, although I'll reply here as well. > If "-S" is found in bhyve_options it does currently affect both > commands. >Sorry, this is not working for me (vm-bhyve 1.1.8_2 from official packages): >Aug 13 16:43:09: bhyve exited with status 1 Aug 13 16:43:09: destroying >network device tap0 Aug 13 16:43:09: stopped Aug 13 16:43:12: initialising Aug >13 16:43:12: [loader: bhyveload] Aug 13 16:43:12: [uefi: no] Aug 13 >16:43:12: [cpu: 1] Aug 13 16:43:12: [memory: 1G] Aug 13 16:43:12: >[hostbridge: standard] Aug 13 16:43:12: [com ports: com1] Aug 13 16:43:12: >[uuid: e148afdb-d4af-11e6-9a94-5404a6b49a66] >Aug 13 16:43:12: [utctime: yes] >Aug 13 16:43:12: [debug mode: no] >Aug 13 16:43:12: [primary disk: disk0.img] Aug 13 16:43:12: [primary disk >dev: file] Aug 13 16:43:12: initialising network device tap0 Aug 13 16:43:12: >adding tap0 -> bridge0 (main) Aug 13 16:43:12: booting Aug 13 16:43:12: >bhyveload -c /dev/nmdm0A -m 1G -e autoboot_delay=3 -d /d02/vm/fido/disk0.img >fido Aug 13 16:43:17: [bhyve options: -c 1 -m 1G -AHP -S -U >e148afdb-d4af-11e6-9a94-5404a6b49a66 -u] Aug 13 16:43:17: [bhyve devices: -s >0,hostbridge -s 31,lpc -s 4:0,virtio-blk,/d02/vm/fido/disk0.img -s >5:0,virtio-net,tap0,mac=58:9c:fc:01:f6:ac] >Aug 13 16:43:17: [bhyve console: -l com1,/dev/nmdm0A] Aug 13 16:43:17: >starting bhyve (run 1) Aug 13 16:43:17: bhyve exited with status 1 Aug 13 >16:43:17: destroying network device tap0 Aug 13 16:43:17: stopped Sorry, it looks like the change didn't make it into 1.1. You'd need to upgrade to 1.2, which is in ports but looks like it hasn't made it into pkg yet. portsmon.freebsd.org is still broken also so I can't easily confirm whether it's made it into any of the quarterly/latest pkg repos. (It was in ports over a month ago so should at least be in latest) Matt >Here is my complete config: >guest="freebsd" >loader="bhyveload" >cpu=1 >memory=1G >network0_type="virtio-net" >network0_switch="main" >disk0_type="virtio-blk" >disk0_name="disk0.img" >utctime="yes" >uuid="e148afdb-d4af-11e6-9a94-5404a6b49a66" >network0_mac="58:9c:fc:01:f6:ac" >bhyve_options="-S" >-- >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" ___ 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
Matt Churchyard wrote: > > Rodney W. Grimes wrote: > > [dd] > > > I've already commented on the bug, although I'll reply here as well. > If "-S" is found in bhyve_options it does currently affect both > commands. Sorry, this is not working for me (vm-bhyve 1.1.8_2 from official packages): Aug 13 16:43:09: bhyve exited with status 1 Aug 13 16:43:09: destroying network device tap0 Aug 13 16:43:09: stopped Aug 13 16:43:12: initialising Aug 13 16:43:12: [loader: bhyveload] Aug 13 16:43:12: [uefi: no] Aug 13 16:43:12: [cpu: 1] Aug 13 16:43:12: [memory: 1G] Aug 13 16:43:12: [hostbridge: standard] Aug 13 16:43:12: [com ports: com1] Aug 13 16:43:12: [uuid: e148afdb-d4af-11e6-9a94-5404a6b49a66] Aug 13 16:43:12: [utctime: yes] Aug 13 16:43:12: [debug mode: no] Aug 13 16:43:12: [primary disk: disk0.img] Aug 13 16:43:12: [primary disk dev: file] Aug 13 16:43:12: initialising network device tap0 Aug 13 16:43:12: adding tap0 -> bridge0 (main) Aug 13 16:43:12: booting Aug 13 16:43:12: bhyveload -c /dev/nmdm0A -m 1G -e autoboot_delay=3 -d /d02/vm/fido/disk0.img fido Aug 13 16:43:17: [bhyve options: -c 1 -m 1G -AHP -S -U e148afdb-d4af-11e6-9a94-5404a6b49a66 -u] Aug 13 16:43:17: [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,virtio-blk,/d02/vm/fido/disk0.img -s 5:0,virtio-net,tap0,mac=58:9c:fc:01:f6:ac] Aug 13 16:43:17: [bhyve console: -l com1,/dev/nmdm0A] Aug 13 16:43:17: starting bhyve (run 1) Aug 13 16:43:17: bhyve exited with status 1 Aug 13 16:43:17: destroying network device tap0 Aug 13 16:43:17: stopped Here is my complete config: guest="freebsd" loader="bhyveload" cpu=1 memory=1G network0_type="virtio-net" network0_switch="main" disk0_type="virtio-blk" disk0_name="disk0.img" utctime="yes" uuid="e148afdb-d4af-11e6-9a94-5404a6b49a66" network0_mac="58:9c:fc:01:f6:ac" bhyve_options="-S" -- 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"
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. I've already commented on the bug, although I'll reply here as well. If "-S" is found in bhyve_options it does currently affect both commands. I have decided that a specific wired_memory option is useful though and will add this to the next release. The name limit has been increased to 32 since v1.2 I didn't realize the changes for cpu topology had actually made it into head, although I don't believe it's actually in a release yet? I will plan to support configuration and display of these before 12 release. Matt > -- > 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" ___ 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: [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"
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"
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. What about VM that don't use bhyveload, but some other kind of loader like grub2-bhyve? > > > > > > 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? -- 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"
Re: Curent Centos 7 and bhyve
> 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. > > > > 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. -- 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: Curent Centos 7 and bhyve
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? > > Its artificial restriction of 16 character VM names is also > a fair bit annoying. Maybe. -- 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"
Re: Curent Centos 7 and bhyve
> Shawn Webb 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. Its artificial restriction of 16 character VM names is also a fair bit annoying. -- 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: Curent Centos 7 and bhyve
On Sat, Aug 11, 2018 at 10:02:27PM +0700, Victor Sudakov wrote: > Shawn Webb 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. I'm aware of it. I'll pass, but thanks for the tip! -- Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal:+1 443-546-8752 Tor+XMPP+OTR:latt...@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE signature.asc Description: PGP signature
Re: Curent Centos 7 and bhyve
Shawn Webb 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. -- 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"
Re: Curent Centos 7 and bhyve
On Sat, Aug 11, 2018 at 09:34:48PM +0700, Victor Sudakov wrote: > Shawn Webb wrote: > > On Sat, Aug 11, 2018 at 12:53:05PM +0700, Victor Sudakov wrote: > > > The Doctor via freebsd-virtualization 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, -- Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal:+1 443-546-8752 Tor+XMPP+OTR:latt...@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE signature.asc Description: PGP signature
Re: Curent Centos 7 and bhyve
The Doctor wrote: > > > The Doctor via freebsd-virtualization 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. > > > > Chokes in my case. > > I have better luck with Debian. Yes, Ubuntu server works too, but do we have anything RPM-based that runs in bhyve? -- 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"
Re: Curent Centos 7 and bhyve
Shawn Webb wrote: > On Sat, Aug 11, 2018 at 12:53:05PM +0700, Victor Sudakov wrote: > > The Doctor via freebsd-virtualization 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? -- 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"
Re: Curent Centos 7 and bhyve
On Sat, Aug 11, 2018 at 09:48:47AM -0400, Shawn Webb wrote: > On Sat, Aug 11, 2018 at 12:53:05PM +0700, Victor Sudakov wrote: > > The Doctor via freebsd-virtualization 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. > Chokes in my case. I have better luck with Debian. > -- > Shawn Webb > Cofounder and Security Engineer > HardenedBSD > > Tor-ified Signal:+1 443-546-8752 > Tor+XMPP+OTR:latt...@is.a.hacker.sx > GPG Key ID: 0x6A84658F52456EEE > GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE -- 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 We cannot direct the wind, but we can adjust the sails. -Bertha Calloway ___ 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
Ganbold Tsagaankhuu wrote: > On Sat, Aug 11, 2018 at 7:46 AM, The Doctor via freebsd-virtualization < > freebsd-virtualization@freebsd.org> wrote: > > > Are there issues with Current CEntos and bhyve? > > > > I have tried 3 installation method. > > > > On 2nd phase, it looks like the xfs indoe are skewered. > > > > > Maybe try to use CentOS-7-x86_64-Minimal-1511.iso. This is 7.2.1551. Later > versions default to XFS which FreeBSD grub2 doesn't seem to support. There > is no known way to switch this from anaconda so you have to use the old ISO > and then update. Does not work even if installed from CentOS-7-x86_64-Minimal-1511.iso. See what happens under FreeBSD 11.2-RELEASE, vm-bhyve-1.1.8_2: [ OK ] Reached target Basic System. [1.297080] vda: vda1 vda2 vda3 [1.508128] input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input2 [1.693391] tsc: Refined TSC clocksource calibration: 3308.829 MHz [1.695742] Switching to clocksource tsc seems good so far [1.693391] tsc: Refined TSC clocksource calibration: 3308.829 MHz [1.695742] Switching to clocksource tsc [ 124.909494] dracut-initqueue[219]: Warning: dracut-initqueue timeout - starting timeout scripts [ 125.424725] dracut-initqueue[219]: Warning: dracut-initqueue timeout - starting timeout scripts [ 125.937988] dracut-initqueue[219]: Warning: dracut-initqueue timeout - starting timeout scripts [ 126.450692] dracut-initqueue[219]: Warning: dracut-initqueue timeout - starting timeout scripts ... [ 185.728954] dracut-initqueue[219]: Warning: dracut-initqueue timeout - starting timeout scripts [ 185.729227] dracut-initqueue[219]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Paths. [ OK ] Reached target Basic System. [ 124.909494] dracut-initqueue[219]: Warning: dracut-initqueue timeout - starting timeout scripts [ 125.424725] dracut-initqueue[219]: Warning: dracut-initqueue timeout - starting timeout scripts [ 185.728954] dracut-initqueue[219]: Warning: dracut-initqueue timeout - starting timeout scripts [ 185.729227] dracut-initqueue[219]: Warning: Could not boot. [ 185.825970] dracut-initqueue[219]: Warning: /dev/mapper/centos-root does not exist Starting Dracut Emergency Shell... Warning: /dev/mapper/centos-root does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. dracut:/# -- 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"
Re: Curent Centos 7 and bhyve
On Sat, Aug 11, 2018 at 12:53:05PM +0700, Victor Sudakov wrote: > The Doctor via freebsd-virtualization 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. -- Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal:+1 443-546-8752 Tor+XMPP+OTR:latt...@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE signature.asc Description: PGP signature
Re: Curent Centos 7 and bhyve
The Doctor via freebsd-virtualization 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 > > I have tried 3 installation method. > > On 2nd phase, it looks like the xfs indoe are skewered. Duh! -- 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"
Re: Curent Centos 7 and bhyve
On Sat, Aug 11, 2018 at 7:46 AM, The Doctor via freebsd-virtualization < freebsd-virtualization@freebsd.org> wrote: > Are there issues with Current CEntos and bhyve? > > I have tried 3 installation method. > > On 2nd phase, it looks like the xfs indoe are skewered. > Maybe try to use CentOS-7-x86_64-Minimal-1511.iso. This is 7.2.1551. Later versions default to XFS which FreeBSD grub2 doesn't seem to support. There is no known way to switch this from anaconda so you have to use the old ISO and then update. Ganbold > -- > 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 > We cannot direct the wind, but we can adjust the sails. -Bertha Calloway > ___ > 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"
