Re: Question about bhyve

2018-01-11 Thread Jason Tubnor
On 12 January 2018 at 12:51, Manish Jain 
wrote:

> Hi,
>
> I have a Win 10 vm under bhyve on my FreeBSD 11.1 box. Is there some way
> I can share clipboards between FreeBSD X and Windows ?
>
> If you are referring to copying data from X to a VNC console for your Win
10 instance, then no.  This presentation is purely graphical, mouse and
keyboard inputs.

If you are using an RDP client to your Win 10 instance, then I think you'll
have better luck with achieving this.

Cheers
___
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: Question about bhyve

2018-01-11 Thread Marcelo Araujo
Hi,

You can give a try using devel/libhyve-remote, it is a VNC server based on
libvncserver, clipboard works there.


Best,

2018-01-12 10:13 GMT+08:00 Paul Webster via freebsd-virtualization <
freebsd-virtualization@freebsd.org>:

> I believe if you used TightVNC server on the windows box and the likewise
> client on freebsd you can sync clipboards over it
>
> On 12 January 2018 at 01:51, Manish Jain 
> wrote:
>
> > Hi,
> >
> > I have a Win 10 vm under bhyve on my FreeBSD 11.1 box. Is there some way
> > I can share clipboards between FreeBSD X and Windows ?
> >
> > Thanks for any help.
> > --
> > Manish Jain
> > ___
> > 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"
>



-- 

-- 
Marcelo Araujo(__)ara...@freebsd.org
\\\'',)http://www.FreeBSD.org    \/  \ ^
Power To Server. .\. /_)
___
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: Question about bhyve

2018-01-11 Thread Jason Barbier

Tight can do it but its a pain to get it set up right in X windows. It may be 
better to install rdesktop or freerdp/remmina and use RDP, it will sync a bit 
better with windows and is a bit more reliable in my experience

---
Jason Barbier | E: kusur...@corrupted.io 
GPG: 0x40B8FA1D72EF0D89 (https://keybase.io/kusuriya)

On Thu, Jan 11, 2018, at 6:13 PM, Paul Webster via freebsd-virtualization wrote:
> I believe if you used TightVNC server on the windows box and the likewise
> client on freebsd you can sync clipboards over it
> 
> On 12 January 2018 at 01:51, Manish Jain 
> wrote:
> 
> > Hi,
> >
> > I have a Win 10 vm under bhyve on my FreeBSD 11.1 box. Is there some way
> > I can share clipboards between FreeBSD X and Windows ?
> >
> > Thanks for any help.
> > --
> > Manish Jain
> > ___
> > 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"
___
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: Question about bhyve

2018-01-11 Thread Paul Webster via freebsd-virtualization
I believe if you used TightVNC server on the windows box and the likewise
client on freebsd you can sync clipboards over it

On 12 January 2018 at 01:51, Manish Jain 
wrote:

> Hi,
>
> I have a Win 10 vm under bhyve on my FreeBSD 11.1 box. Is there some way
> I can share clipboards between FreeBSD X and Windows ?
>
> Thanks for any help.
> --
> Manish Jain
> ___
> 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"


Question about bhyve

2018-01-11 Thread Manish Jain
Hi,

I have a Win 10 vm under bhyve on my FreeBSD 11.1 box. Is there some way 
I can share clipboards between FreeBSD X and Windows ?

Thanks for any help.
-- 
Manish Jain
___
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: ena(4) is not in GENERIC, now default for some/all instances on AWS EC2

2018-01-11 Thread Maxim Sobolev
Well, that might work, but I am curious why do we have all other network 40
or so drivers in the GENERIC but not this one. Considering significant
portion of FreeBSD systems deployed these days are going to be running on
the cloud this makes no sense to me. Is there some policy out there which
governs such decisions?

At the very least we need some kind of entry into UPDATING, IMHO.

-Max

On Thu, Jan 11, 2018 at 9:13 AM, Pete Wright  wrote:

>
>
> On 01/10/2018 21:34, Maxim Sobolev wrote:
>
>> Hi, today we've migrated one of our FreeBSD EC2 r4.xlarge instances and
>> painstakingly found that xn(4) interface is no longer provided by the
>> Amazon "hardware". ena(4) seems to be now default for a newly created VMs,
>> but it's not part of the GENERIC kernel. This could affect both new users
>> trying to deploy stock FreeBSD on AWS, as well as existing users migrating
>> their virtual assets running FreeBSD. I am not sure if there any technical
>> reasons for not having it, but perhaps somebody needs to take a look to
>> add
>> it in there if there are none?
>>
>
> (removing cross-posting as I believe this is relevant to the
> virtualization list mostly.)
>
> if_ena.ko is shipped as a kernel module on 11.1 on my end - would using
> configinit to append if_ena.ko to kld_list or loader.conf might be a decent
> workaround?  i would have assumed it would have been loaded at boot time if
> the device was detected, but i've never tested out instances that only
> support the ena(4) adapter.
>
> -p
>
> --
> Pete Wright
> p...@nomadlogic.org
> @nomadlogicLA
>
>
___
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: ena(4) is not in GENERIC, now default for some/all instances on AWS EC2

2018-01-11 Thread Pete Wright



On 01/10/2018 21:34, Maxim Sobolev wrote:

Hi, today we've migrated one of our FreeBSD EC2 r4.xlarge instances and
painstakingly found that xn(4) interface is no longer provided by the
Amazon "hardware". ena(4) seems to be now default for a newly created VMs,
but it's not part of the GENERIC kernel. This could affect both new users
trying to deploy stock FreeBSD on AWS, as well as existing users migrating
their virtual assets running FreeBSD. I am not sure if there any technical
reasons for not having it, but perhaps somebody needs to take a look to add
it in there if there are none?


(removing cross-posting as I believe this is relevant to the 
virtualization list mostly.)


if_ena.ko is shipped as a kernel module on 11.1 on my end - would using 
configinit to append if_ena.ko to kld_list or loader.conf might be a 
decent workaround?  i would have assumed it would have been loaded at 
boot time if the device was detected, but i've never tested out 
instances that only support the ena(4) adapter.


-p

--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA

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