Re: Bhyve tests and findings

2016-08-10 Thread Victor Sudakov 
Yamagi Burmeister wrote:
> Hi,
> to be able to use the GOP instructions on FreeBSD 10.3 you'll need to
> merge r296103 [0]. If it's an AMD system it's a good idea to merge
> r297806 [1], too. Otherwise most Linux distros will panic at startup.

I'd rather abandon the idea and get a separate box with FreeBSD 11 for
UEFI-GOP testing. 

Matt and others, thanks for the effort.


-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
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 tests and findings

2016-08-10 Thread Yamagi Burmeister 
Hi,
to be able to use the GOP instructions on FreeBSD 10.3 you'll need to
merge r296103 [0]. If it's an AMD system it's a good idea to merge
r297806 [1], too. Otherwise most Linux distros will panic at startup.

Regards,
Yamagi

0: https://svnweb.freebsd.org/base?view=revision=296103
1: https://svnweb.freebsd.org/base?view=revision=297806

On Wed, 10 Aug 2016 20:36:34 +0700
Victor Sudakov  wrote:

> Matt Churchyard wrote:
> > 
> > >I have tried replicating manually all the options vm is passing to bhyve, 
> > >like 
> > 
> > >bhyve -c 1 -m 1G -Hwl bootrom,/d02/vm/.config/BHYVE_UEFI.fd \
> > >-U 093f9134-5e18-11e6-9502-5404a6b49a66 \
> > >>-s 0,hostbridge -s 31,lpc -s 4:0,ahci-hd,/d02/vm/win/disk0.img \
> > >-s 5:0,virtio-net,tap5,mac=58:9c:fc:03:77:3b -s 
> > > 6:0,fbuf,tcp=0.0.0.0:5900,wait \
> > >-l com1,stdio \
> > >   -s 3:0,ahci-cd,/d02/vm/.iso/bhyve_win7_x64.iso
> > 
> > > But bhyve just spits out the "usage" help (that's why it exits 
> > > immediately). But I cannot find out what's incorrect with the options.
> > 
> > You just need the vm name (win) on the end:
> > 
> > # bhyve [options] vm-name
> > 
> 
> Sorry, I was being stupid. With the vm name on the end, it just exits
> with error code 1 and without printing anytning.
> 
> I have recompiled bhyve itself and the libvmmapi, maybe it's not
> enough? The kernel module? It still remains that from 10.3
> 
> -- 
> Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> sip:suda...@sibptus.tomsk.ru
> ___
> 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"


-- 
Homepage:  www.yamagi.org
XMPP:  yam...@yamagi.org
GnuPG/GPG: 0xEFBCCBCB
___
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 tests and findings

2016-08-10 Thread Matt Churchyard via freebsd-virtualization 
> [..]
> 
> You just need the vm name (win) on the end:
> 
> # bhyve [options] vm-name
> 

>Sorry, I was being stupid. With the vm name on the end, it just exits with 
>error code 1 and without printing anytning.
>I have recompiled bhyve itself and the libvmmapi, maybe it's not enough? The 
>kernel module? It still remains that from 10.3

Definitely sounds like something not right with bhyve; It shouldn't exit like 
that.
You can try building vmm from 11, although I'm not really a kernel dev and 
can't help much with trying to merge 11 code into 10.

Matt

___
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 tests and findings

2016-08-10 Thread Victor Sudakov 
Matt Churchyard wrote:
> 
> >I have tried replicating manually all the options vm is passing to bhyve, 
> >like 
> 
> >bhyve -c 1 -m 1G -Hwl bootrom,/d02/vm/.config/BHYVE_UEFI.fd \
> >-U 093f9134-5e18-11e6-9502-5404a6b49a66 \
> >>-s 0,hostbridge -s 31,lpc -s 4:0,ahci-hd,/d02/vm/win/disk0.img \
> >-s 5:0,virtio-net,tap5,mac=58:9c:fc:03:77:3b -s 
> > 6:0,fbuf,tcp=0.0.0.0:5900,wait \
> >-l com1,stdio \
> >   -s 3:0,ahci-cd,/d02/vm/.iso/bhyve_win7_x64.iso
> 
> > But bhyve just spits out the "usage" help (that's why it exits 
> > immediately). But I cannot find out what's incorrect with the options.
> 
> You just need the vm name (win) on the end:
> 
> # bhyve [options] vm-name
> 

Sorry, I was being stupid. With the vm name on the end, it just exits
with error code 1 and without printing anytning.

I have recompiled bhyve itself and the libvmmapi, maybe it's not
enough? The kernel module? It still remains that from 10.3

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
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 tests and findings

2016-08-09 Thread Victor Sudakov 
Matt Churchyard wrote:
> > > > > > > 
> > > > > > > uefi="yes"
> > > > > > > graphics="yes"
> > > > > > 
> > > > > > Dear Colleagues,
> > > > > > 
> > > > > > Can I enjoy and test all those nice "UEFI-GOP" features on a
> > > > > > 10.3-RELEASE system, or do I have to install CURRENT for that?
> > > > > 
> > > > > AFAIK you can checkout usr.sbin/bhyve from the 11 branch and compile 
> > > > > it
> > > > > on 10.3.
> > > > 
> > > > I'm not sure how to compile something from a different branch without
> > > > compiling the whole world. make what?
> > > 
> > > For bhyve it's easy. Check out the sources, go to usr.sbin/bhyve and run
> > > 
> > > make depend; make obj; make; make install. 
> > 
> > >Unfortunately, after all my efforts, with libvmmapi and bhyve compiled from
> > >CURRENT sources:
> > 
> > >Aug 09 12:46:52: warning; UEFI graphics is only available in FreeBSD 11 
> > >and newer
> > >Aug 09 12:46:52: booting
> > 
> > >Bummer!
> > 
> > It's possible that you do have a bhyve system with graphics support. 
> > Unfortunately vm-bhyve isn't aimed at users who have manually merged 
> > changes, and will blindly tell anyone that isn't running 11+ that they 
> > don't have graphics support. 
> > 
> > You have a couple of options -
> > 
> > 1) Run bhyve manually rather than using vm-bhyve
> > 2) Upgrade to the 11 beta
> > 3) Modify vm-bhyve to not automatically skip graphics support if the 
> > version is less than 11 
> 
> >Aha! I've commented out the version check from vm-run, and now when
> >trying to install, I get:
> 
> >авг 09 17:01:05: initialising
> >авг 09 17:01:05:  [loader: none]
> >авг 09 17:01:05:  [uefi: yes]
> >авг 09 17:01:05:  [cpu: 1]
> >авг 09 17:01:05:  [memory: 1G]
> >авг 09 17:01:05:  [hostbridge: standard]
> >авг 09 17:01:05:  [com ports: com1]
> >авг 09 17:01:05:  [uuid: 093f9134-5e18-11e6-9502-5404a6b49a66]
> >авг 09 17:01:05:  [utctime: no]
> >авг 09 17:01:05:  [debug mode: no]
> >авг 09 17:01:05:  [primary disk: disk0.img]
> >авг 09 17:01:05:  [primary disk dev: file]
> >авг 09 17:01:05: generated static mac 58:9c:fc:03:77:3b (based on 
> >'win:0:1470736865:0')
> >авг 09 17:01:05: initialising network device tap5
> >авг 09 17:01:05: adding tap5 -> bridge1 (isolated)
> >авг 09 17:01:05: dynamically allocated port 5900 for vnc connections
> >авг 09 17:01:05: booting
> >авг 09 17:01:05:  [bhyve options: -c 1 -m 1G -Hwl 
> >bootrom,/d02/vm/.config/BHYVE_UEFI.fd -U 
> >093f9134-5e18-11e6-9502-5404a6b49a66]
> >авг 09 17:01:05:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 
> >4:0,ahci-hd,/d02/vm/win/disk0.img -s 
> >5:0,virtio-net,tap5,mac=58:9c:fc:03:77:3b -s >6:0,fbuf,tcp=0.0.0.0:5900,wait]
> >авг 09 17:01:05:  [bhyve console: -l com1,/dev/nmdm0A]
> >авг 09 17:01:05:  [bhyve iso device: -s 
> >3:0,ahci-cd,/d02/vm/.iso/bhyve_win7_x64.iso]
> >авг 09 17:01:05: starting bhyve (run 1)
> >авг 09 17:01:05: bhyve exited with status 1
> >авг 09 17:01:05: destroying network device tap5
> >авг 09 17:01:05: stopped
> 
> Looks like bhyve is exiting immediately. Easiest thing is to probably add 
> debug="yes" to  the guest config file then try and run it again. Any output 
> from the bhyve command will be written to bhyve.log (note that's a different 
> file to vm-bhyve.log).
> 

Tried that.

root@vas:/d02/vm/win # file bhyve.log
bhyve.log: empty

root@vas:/d02/vm/win # more win.conf
guest="windows"
uefi="yes"
graphics="yes"
cpu=1
memory=1G
network0_type="virtio-net"
network0_switch="isolated"
disk0_type="ahci-hd"
disk0_name="disk0.img"
debug="yes"
uuid="093f9134-5e18-11e6-9502-5404a6b49a66"
network0_mac="58:9c:fc:03:77:3b"
root@vas:/d02/vm/win #

I have tried replicating manually all the options vm is passing to
bhyve, like 

bhyve -c 1 -m 1G -Hwl bootrom,/d02/vm/.config/BHYVE_UEFI.fd \
-U 093f9134-5e18-11e6-9502-5404a6b49a66 \
-s 0,hostbridge -s 31,lpc -s 4:0,ahci-hd,/d02/vm/win/disk0.img \
-s 5:0,virtio-net,tap5,mac=58:9c:fc:03:77:3b -s 
6:0,fbuf,tcp=0.0.0.0:5900,wait \
-l com1,stdio \
-s 3:0,ahci-cd,/d02/vm/.iso/bhyve_win7_x64.iso

But bhyve just spits out the "usage" help (that's why it exits
immediately). But I cannot find out what's incorrect with the options.

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
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 tests and findings

2016-08-09 Thread Matt Churchyard via freebsd-virtualization 
> > > > > > 
> > > > > > uefi="yes"
> > > > > > graphics="yes"
> > > > > 
> > > > > Dear Colleagues,
> > > > > 
> > > > > Can I enjoy and test all those nice "UEFI-GOP" features on a
> > > > > 10.3-RELEASE system, or do I have to install CURRENT for that?
> > > > 
> > > > AFAIK you can checkout usr.sbin/bhyve from the 11 branch and compile it
> > > > on 10.3.
> > > 
> > > I'm not sure how to compile something from a different branch without
> > > compiling the whole world. make what?
> > 
> > For bhyve it's easy. Check out the sources, go to usr.sbin/bhyve and run
> > 
> > make depend; make obj; make; make install. 
> 
> >Unfortunately, after all my efforts, with libvmmapi and bhyve compiled from
> >CURRENT sources:
> 
> >Aug 09 12:46:52: warning; UEFI graphics is only available in FreeBSD 11 and 
> >newer
> >Aug 09 12:46:52: booting
> 
> >Bummer!
> 
> It's possible that you do have a bhyve system with graphics support. 
> Unfortunately vm-bhyve isn't aimed at users who have manually merged changes, 
> and will blindly tell anyone that isn't running 11+ that they don't have 
> graphics support. 
> 
> You have a couple of options -
> 
> 1) Run bhyve manually rather than using vm-bhyve
> 2) Upgrade to the 11 beta
> 3) Modify vm-bhyve to not automatically skip graphics support if the version 
> is less than 11 

>Aha! I've commented out the version check from vm-run, and now when
>trying to install, I get:

>авг 09 17:01:05: initialising
>авг 09 17:01:05:  [loader: none]
>авг 09 17:01:05:  [uefi: yes]
>авг 09 17:01:05:  [cpu: 1]
>авг 09 17:01:05:  [memory: 1G]
>авг 09 17:01:05:  [hostbridge: standard]
>авг 09 17:01:05:  [com ports: com1]
>авг 09 17:01:05:  [uuid: 093f9134-5e18-11e6-9502-5404a6b49a66]
>авг 09 17:01:05:  [utctime: no]
>авг 09 17:01:05:  [debug mode: no]
>авг 09 17:01:05:  [primary disk: disk0.img]
>авг 09 17:01:05:  [primary disk dev: file]
>авг 09 17:01:05: generated static mac 58:9c:fc:03:77:3b (based on 
>'win:0:1470736865:0')
>авг 09 17:01:05: initialising network device tap5
>авг 09 17:01:05: adding tap5 -> bridge1 (isolated)
>авг 09 17:01:05: dynamically allocated port 5900 for vnc connections
>авг 09 17:01:05: booting
>авг 09 17:01:05:  [bhyve options: -c 1 -m 1G -Hwl 
>bootrom,/d02/vm/.config/BHYVE_UEFI.fd -U 093f9134-5e18-11e6-9502-5404a6b49a66]
>авг 09 17:01:05:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 
>4:0,ahci-hd,/d02/vm/win/disk0.img -s 5:0,virtio-net,tap5,mac=58:9c:fc:03:77:3b 
>-s >6:0,fbuf,tcp=0.0.0.0:5900,wait]
>авг 09 17:01:05:  [bhyve console: -l com1,/dev/nmdm0A]
>авг 09 17:01:05:  [bhyve iso device: -s 
>3:0,ahci-cd,/d02/vm/.iso/bhyve_win7_x64.iso]
>авг 09 17:01:05: starting bhyve (run 1)
>авг 09 17:01:05: bhyve exited with status 1
>авг 09 17:01:05: destroying network device tap5
>авг 09 17:01:05: stopped

Looks like bhyve is exiting immediately. Easiest thing is to probably add 
debug="yes" to  the guest config file then try and run it again. Any output 
from the bhyve command will be written to bhyve.log (note that's a different 
file to vm-bhyve.log).

Matt
___
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 tests and findings

2016-08-09 Thread Victor Sudakov 
Matt Churchyard wrote:
> > > > > > 
> > > > > > uefi="yes"
> > > > > > graphics="yes"
> > > > > 
> > > > > Dear Colleagues,
> > > > > 
> > > > > Can I enjoy and test all those nice "UEFI-GOP" features on a
> > > > > 10.3-RELEASE system, or do I have to install CURRENT for that?
> > > > 
> > > > AFAIK you can checkout usr.sbin/bhyve from the 11 branch and compile it
> > > > on 10.3.
> > > 
> > > I'm not sure how to compile something from a different branch without
> > > compiling the whole world. make what?
> > 
> > For bhyve it's easy. Check out the sources, go to usr.sbin/bhyve and run
> > 
> > make depend; make obj; make; make install. 
> 
> >Unfortunately, after all my efforts, with libvmmapi and bhyve compiled from
> >CURRENT sources:
> 
> >Aug 09 12:46:52: warning; UEFI graphics is only available in FreeBSD 11 and 
> >newer
> >Aug 09 12:46:52: booting
> 
> >Bummer!
> 
> It's possible that you do have a bhyve system with graphics support. 
> Unfortunately vm-bhyve isn't aimed at users who have manually merged changes, 
> and will blindly tell anyone that isn't running 11+ that they don't have 
> graphics support. 
> 
> You have a couple of options -
> 
> 1) Run bhyve manually rather than using vm-bhyve
> 2) Upgrade to the 11 beta
> 3) Modify vm-bhyve to not automatically skip graphics support if the version 
> is less than 11 

Aha! I've commented out the version check from vm-run, and now when
trying to install, I get:

авг 09 17:01:05: initialising
авг 09 17:01:05:  [loader: none]
авг 09 17:01:05:  [uefi: yes]
авг 09 17:01:05:  [cpu: 1]
авг 09 17:01:05:  [memory: 1G]
авг 09 17:01:05:  [hostbridge: standard]
авг 09 17:01:05:  [com ports: com1]
авг 09 17:01:05:  [uuid: 093f9134-5e18-11e6-9502-5404a6b49a66]
авг 09 17:01:05:  [utctime: no]
авг 09 17:01:05:  [debug mode: no]
авг 09 17:01:05:  [primary disk: disk0.img]
авг 09 17:01:05:  [primary disk dev: file]
авг 09 17:01:05: generated static mac 58:9c:fc:03:77:3b (based on 
'win:0:1470736865:0')
авг 09 17:01:05: initialising network device tap5
авг 09 17:01:05: adding tap5 -> bridge1 (isolated)
авг 09 17:01:05: dynamically allocated port 5900 for vnc connections
авг 09 17:01:05: booting
авг 09 17:01:05:  [bhyve options: -c 1 -m 1G -Hwl 
bootrom,/d02/vm/.config/BHYVE_UEFI.fd -U 093f9134-5e18-11e6-9502-5404a6b49a66]
авг 09 17:01:05:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 
4:0,ahci-hd,/d02/vm/win/disk0.img -s 5:0,virtio-net,tap5,mac=58:9c:fc:03:77:3b 
-s 6:0,fbuf,tcp=0.0.0.0:5900,wait]
авг 09 17:01:05:  [bhyve console: -l com1,/dev/nmdm0A]
авг 09 17:01:05:  [bhyve iso device: -s 
3:0,ahci-cd,/d02/vm/.iso/bhyve_win7_x64.iso]
авг 09 17:01:05: starting bhyve (run 1)
авг 09 17:01:05: bhyve exited with status 1
авг 09 17:01:05: destroying network device tap5
авг 09 17:01:05: stopped


-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
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 tests and findings

2016-08-09 Thread Matt Churchyard via freebsd-virtualization 
>Lars Engels wrote:
> > > > > 
> > > > > uefi="yes"
> > > > > graphics="yes"
> > > > 
> > > > Dear Colleagues,
> > > > 
> > > > Can I enjoy and test all those nice "UEFI-GOP" features on a
> > > > 10.3-RELEASE system, or do I have to install CURRENT for that?
> > > 
> > > AFAIK you can checkout usr.sbin/bhyve from the 11 branch and compile it
> > > on 10.3.
> > 
> > I'm not sure how to compile something from a different branch without
> > compiling the whole world. make what?
> 
> For bhyve it's easy. Check out the sources, go to usr.sbin/bhyve and run
> 
> make depend; make obj; make; make install. 

>Unfortunately, after all my efforts, with libvmmapi and bhyve compiled from
>CURRENT sources:

>Aug 09 12:46:52: warning; UEFI graphics is only available in FreeBSD 11 and 
>newer
>Aug 09 12:46:52: booting

>Bummer!

It's possible that you do have a bhyve system with graphics support. 
Unfortunately vm-bhyve isn't aimed at users who have manually merged changes, 
and will blindly tell anyone that isn't running 11+ that they don't have 
graphics support. 

You have a couple of options -

1) Run bhyve manually rather than using vm-bhyve
2) Upgrade to the 11 beta
3) Modify vm-bhyve to not automatically skip graphics support if the version is 
less than 11 

Matt
___
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 tests and findings

2016-08-05 Thread Michael Reifenberger 


Zitat von Matt Churchyard :


Zitat von Peter Grehan :



Hi Mike,


- Windows 8, 8.1 and 10 installs and runs in graphical mode flawlessly.


 Have you had any issues with the XHCI mouse on 8/8.1 ?


- I was able to graphically Restore/Reconfigure a Acronis
Windows-Backup into a Bhyve instance  using the Acronis Restore-CD
(Converting a BIOS Win8.1 to UEFI Win8.1)


 Very nice !


- Only vnclient from FreeBSD can connect to the bhyve VNC Server.
 I havn't found any vncviewer running on Windows which where able to
work (tried UltraVNC, RealVNC, ...)


 Some VNC clients refuse to connect when only null-auth is advertized
by the server. There is a patch to bhyve to support VNC password-auth,
which may fix the issue with these clients.




Yes, that sounds reasonable.



- in VNC only most basic Keys work most special characters like (*\@)
(and of course no german localization)  but at least a usual US-kbd
would be helpful.
 (Is there a way to debug the keystrokes or duplicate a localized VNC
kbd from some VNC server)


 Nothing outside of modifying the source, but it seems useful enough
to add a parameter for this.


- For the SAP-Systems it seems that only 4 disks get used when the
disk type is virtio-blk.
 (Is this intentionally or a feature of vm-bhyve? How to provide more
disks)


 I'll let Matt comment on that. There's no limitation with guests that
support MSI interrupts for adapters. Unfortunately, Windows guests
require legacy interrupts for the AHCI controller, which is where the
restriction originates.




I'd like to use a 6 disks setup with Centos7.
Centos7 on XEN PVM has no issue with supporting 6 paravirtulized disks.


Thats the config (for vm-bhyve) where only the first 4 disks are  
used for the guest (Centos7):



uefi="yes"
cpu=1
memory=2G
network0_type="virtio-net"
network0_switch="public"
disk0_name="root"
disk0_type="virtio-blk"
disk0_dev="zvol"
disk1_name="swap"
disk1_type="virtio-blk"
disk1_dev="zvol"
disk2_name="sapmnt"
disk2_type="virtio-blk"
disk2_dev="zvol"
disk3_name="usrsap"
disk3_type="virtio-blk"
disk3_dev="zvol"
disk4_name="db"
disk4_type="virtio-blk"
disk4_dev="zvol"
disk5_name="log"
disk5_type="virtio-blk"
disk5_dev="zvol"
graphics="yes"
graphics_port="5903"
graphics_listen="0.0.0.0"
graphics_res="1600x900"
graphics_wait="no"
xhci_mouse="yes"


Sorry I didn't actually spot that you were using my vm-bhyve code to  
run the guest the first time.


The UEFI code in vm-bhyve is currently limited to using slots 4/5/6  
for disks so you should only see 3... (I put a CD device on slot 3)
If you look in the /path/to/guest/vm-bhyve.log log file you'll  
probably see something like "ending disks as disk2 due to UEFI  
limitations".


I've never been 100% on which guests have the limitation and which  
don't, so in UEFI mode I played it safe and just used the 3 slots.  
If you run the guest with the grub loader instead of UEFI you should  
get all the disks.


If you want, you can comment out the limitation in the vm-bhyve  
source and see if the guest will pick up the extra disks. It's the 4  
lines after the "can't go past slot 6" comment around line 364 of  
lib/vm-run. If it works it may be worth me adding a configuration  
option to toggle this limit.




Cool!
Commenting out:
...
# stop at slot 6 on uefi
#if [ ${_slot} -ge 7 ]; then
#util::log "guest" "${_name}" "ending disks at  
disk${_num} due to UEFI firmware limitations"

#break
#fi
...

Gives me all disks in Centos7:

[0.755083] ahci :00:03.0: version 3.0
[0.759512] ahci :00:03.0: irq 25 for MSI/MSI-X
[0.759548] ahci :00:03.0: SSS flag set, parallel bus scan disabled
[0.759661] ahci :00:03.0: AHCI 0001.0300 32 slots 6 ports 6  
Gbps 0x1 impl SATA mode
[0.759663] ahci :00:03.0: flags: 64bit ncq sntf ilck stag pm  
led clo pio slum part sxs apst

[0.767612] scsi host0: ahci
[0.774675] scsi host1: ahci
[0.783392] virtio-pci :00:04.0: irq 26 for MSI/MSI-X
[0.783407] virtio-pci :00:04.0: irq 27 for MSI/MSI-X
[0.784850]  vda: vda1 vda2 vda3 vda4
[0.785013] virtio-pci :00:05.0: irq 28 for MSI/MSI-X
[0.785027] virtio-pci :00:05.0: irq 29 for MSI/MSI-X
[0.785609]  vdb: unknown partition table
[0.785725] virtio-pci :00:06.0: irq 30 for MSI/MSI-X
[0.785739] virtio-pci :00:06.0: irq 31 for MSI/MSI-X
[0.786817]  vdc: unknown partition table
[0.786925] virtio-pci :00:07.0: irq 32 for MSI/MSI-X
[0.786939] virtio-pci :00:07.0: irq 33 for MSI/MSI-X
[0.790069] virtio-pci :00:0a.0: irq 34 for MSI/MSI-X
[0.790083] virtio-pci :00:0a.0: irq 35 for MSI/MSI-X
[0.790097] virtio-pci :00:0a.0: irq 36 for MSI/MSI-X
[0.790895]  vdd: unknown partition table
[0.791026] virtio-pci :00:08.0: irq 37 for MSI/MSI-X
[0.791040] virtio-pci :00:08.0: irq 38 for

RE: Bhyve tests and findings

2016-08-05 Thread Matt Churchyard via freebsd-virtualization 
> 
> uefi="yes"
> graphics="yes"

> Dear Colleagues,

> Can I enjoy and test all those nice "UEFI-GOP" features on a 10.3-RELEASE 
> system, or do I have to install CURRENT for that?

I believe you should also be able to use the 11 beta.

Matt
___
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 tests and findings

2016-08-05 Thread Lars Engels 
On Fri, Aug 05, 2016 at 01:59:45PM +0700, Victor Sudakov wrote:
> Lars Engels wrote:
> > > > 
> > > > uefi="yes"
> > > > graphics="yes"
> > > 
> > > Dear Colleagues,
> > > 
> > > Can I enjoy and test all those nice "UEFI-GOP" features on a
> > > 10.3-RELEASE system, or do I have to install CURRENT for that?
> > 
> > AFAIK you can checkout usr.sbin/bhyve from the 11 branch and compile it
> > on 10.3.
> 
> I'm not sure how to compile something from a different branch without
> compiling the whole world. make what?

For bhyve it's easy. Check out the sources, go to usr.sbin/bhyve and run

make depend; make obj; make; make install. 


pgp4n7um3bsJ4.pgp
Description: PGP signature

Re: Bhyve tests and findings

2016-08-05 Thread Victor Sudakov 
Lars Engels wrote:
> > > 
> > > uefi="yes"
> > > graphics="yes"
> > 
> > Dear Colleagues,
> > 
> > Can I enjoy and test all those nice "UEFI-GOP" features on a
> > 10.3-RELEASE system, or do I have to install CURRENT for that?
> 
> AFAIK you can checkout usr.sbin/bhyve from the 11 branch and compile it
> on 10.3.

I'm not sure how to compile something from a different branch without
compiling the whole world. make what?



-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
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 tests and findings

2016-08-05 Thread Lars Engels 
On Fri, Aug 05, 2016 at 08:31:02AM +0700, Victor Sudakov wrote:
> > 
> > uefi="yes"
> > graphics="yes"
> 
> Dear Colleagues,
> 
> Can I enjoy and test all those nice "UEFI-GOP" features on a
> 10.3-RELEASE system, or do I have to install CURRENT for that?

AFAIK you can checkout usr.sbin/bhyve from the 11 branch and compile it
on 10.3.


pgpjuLGPrDS8h.pgp
Description: PGP signature

Re: Bhyve tests and findings

2016-08-04 Thread Victor Sudakov 
> 
> uefi="yes"
> graphics="yes"

Dear Colleagues,

Can I enjoy and test all those nice "UEFI-GOP" features on a
10.3-RELEASE system, or do I have to install CURRENT for that?


-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:suda...@sibptus.tomsk.ru
___
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 tests and findings

2016-08-04 Thread Michael Reifenberger 


Zitat von Peter Grehan :


Hi Mike,


- Windows 8, 8.1 and 10 installs and runs in graphical mode flawlessly.


 Have you had any issues with the XHCI mouse on 8/8.1 ?


- I was able to graphically Restore/Reconfigure a Acronis Windows-Backup
into a Bhyve instance
 using the Acronis Restore-CD (Converting a BIOS Win8.1 to UEFI Win8.1)


 Very nice !


- Only vnclient from FreeBSD can connect to the bhyve VNC Server.
 I havn't found any vncviewer running on Windows which where able to
work (tried UltraVNC, RealVNC, ...)


 Some VNC clients refuse to connect when only null-auth is  
advertized by the server. There is a patch to bhyve to support VNC  
password-auth, which may fix the issue with these clients.




Yes, that sounds reasonable.


- in VNC only most basic Keys work most special characters like (*\@)
(and of course no german localization)
 but at least a usual US-kbd would be helpful.
 (Is there a way to debug the keystrokes or duplicate a localized VNC
kbd from some VNC server)


 Nothing outside of modifying the source, but it seems useful enough  
to add a parameter for this.



- For the SAP-Systems it seems that only 4 disks get used when the disk
type is virtio-blk.
 (Is this intentionally or a feature of vm-bhyve? How to provide more
disks)


 I'll let Matt comment on that. There's no limitation with guests  
that support MSI interrupts for adapters. Unfortunately, Windows  
guests require legacy interrupts for the AHCI controller, which is  
where the restriction originates.




I'd like to use a 6 disks setup with Centos7.
Centos7 on XEN PVM has no issue with supporting 6 paravirtulized disks.

Thats the config (for vm-bhyve) where only the first 4 disks are used  
for the guest (Centos7):


uefi="yes"
cpu=1
memory=2G
network0_type="virtio-net"
network0_switch="public"
disk0_name="root"
disk0_type="virtio-blk"
disk0_dev="zvol"
disk1_name="swap"
disk1_type="virtio-blk"
disk1_dev="zvol"
disk2_name="sapmnt"
disk2_type="virtio-blk"
disk2_dev="zvol"
disk3_name="usrsap"
disk3_type="virtio-blk"
disk3_dev="zvol"
disk4_name="db"
disk4_type="virtio-blk"
disk4_dev="zvol"
disk5_name="log"
disk5_type="virtio-blk"
disk5_dev="zvol"
graphics="yes"
graphics_port="5903"
graphics_listen="0.0.0.0"
graphics_res="1600x900"
graphics_wait="no"
xhci_mouse="yes"




- It seems to miss a way to add an ISO CD/DVD without booting from it
automatically.


 There is work ongoing to support UEFI NVVARs, which mostly fix the  
boot-device selection issues.



 Also ISO's seem to miss a hot-plug feature (f.e. for inserting driver
CD's after installation.


 Yes, also not there.


Some additional questions:
- Can one over-provisioning/ballooning guest memory's ?


 Over-provisioning is fine - bhyve guest memory is backed by swap by  
default. There is currently no balloon driver backend in bhyve.



- Is it (speed-wise) better to use ZFS-zvol's or files in regular
ZFS-directories?


 I think that is workload-dependent.


- Are the virtio-blk or ahci-hd disks having the same overhead?


 No - virtio-blk should be better.


- Can ahci-hd be used paravirtualized in Centos?


 Not quite sure what you mean here: virtio-blk is the  
paravirtualized disk interface, and it works fine with Centos.


I mean:
If I use ahci-hd in the bhyve config, is Centos7 smart enough to  
see/use para-virtual disks (/dev/vd*)

or use AHCI-Disks /dev/sd*)

Thanks!

Greetings
---
Mike


Gruß
---
Michael Reifenberger

___
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 tests and findings

2016-08-04 Thread Peter Grehan 

Hi Mike,


- Windows 8, 8.1 and 10 installs and runs in graphical mode flawlessly.


 Have you had any issues with the XHCI mouse on 8/8.1 ?


- I was able to graphically Restore/Reconfigure a Acronis Windows-Backup
into a Bhyve instance
  using the Acronis Restore-CD (Converting a BIOS Win8.1 to UEFI Win8.1)


 Very nice !


- Only vnclient from FreeBSD can connect to the bhyve VNC Server.
  I havn't found any vncviewer running on Windows which where able to
work (tried UltraVNC, RealVNC, ...)


 Some VNC clients refuse to connect when only null-auth is advertized 
by the server. There is a patch to bhyve to support VNC password-auth, 
which may fix the issue with these clients.



- in VNC only most basic Keys work most special characters like (*\@)
(and of course no german localization)
  but at least a usual US-kbd would be helpful.
  (Is there a way to debug the keystrokes or duplicate a localized VNC
kbd from some VNC server)


 Nothing outside of modifying the source, but it seems useful enough to 
add a parameter for this.



- For the SAP-Systems it seems that only 4 disks get used when the disk
type is virtio-blk.
  (Is this intentionally or a feature of vm-bhyve? How to provide more
disks)


 I'll let Matt comment on that. There's no limitation with guests that 
support MSI interrupts for adapters. Unfortunately, Windows guests 
require legacy interrupts for the AHCI controller, which is where the 
restriction originates.



- It seems to miss a way to add an ISO CD/DVD without booting from it
automatically.


 There is work ongoing to support UEFI NVVARs, which mostly fix the 
boot-device selection issues.



  Also ISO's seem to miss a hot-plug feature (f.e. for inserting driver
CD's after installation.


 Yes, also not there.


Some additional questions:
- Can one over-provisioning/ballooning guest memory's ?


 Over-provisioning is fine - bhyve guest memory is backed by swap by 
default. There is currently no balloon driver backend in bhyve.



- Is it (speed-wise) better to use ZFS-zvol's or files in regular
ZFS-directories?


 I think that is workload-dependent.


- Are the virtio-blk or ahci-hd disks having the same overhead?


 No - virtio-blk should be better.


- Can ahci-hd be used paravirtualized in Centos?


 Not quite sure what you mean here: virtio-blk is the paravirtualized 
disk interface, and it works fine with Centos.


later,

Peter.

___
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"