Re: VNC server on bhyve
Il 09/03/2016 11:26, Matthias Gamsjager ha scritto: On 17 August 2014 at 21:49, Peter Grehan wrote: Hi Denis, Does (or will include) bhyve VNC server? For the console, currently not. It will hopefully be there at some point. later, Peter. Old post but is there any item on the road map which implements a VNC server to access the console? For Windows install that would really come handy. I am waiting for a VNC server too. On my office server I have three Win7 VM on VirtualBox. Before converting the VM for bhyve I need a VNC server. Regards, Maurizio ___ 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: virtualbox-ose-4.3.16 USB passthrough does not work
Il 09/02/2015 22:34, Miroslav Lachman ha scritto:
Hi,
I have virtualbox-ose-4.3.16 and virtualbox-ose-kmod-4.3.16 installed
on my PC-BSD (FreeBSD 10.1-RELEASE-p8 amd64 GENERIC). I tried to
connect DJ mixer Rane TTM57SL and pass it's USB device (Serato sound
card + special HID) to VBox guest Windows 7 Ultimated 32bit.
I correctly set the USB filter, started the VM and then got following
error:
Failed to attach the USB device Serato TTM57SL to the virtual machine
Windows 7 Ultimate 32 bit.
Failed to create a proxy device for the USB device. (Error:
VERR_READ_ERROR).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
VBoxManage lists the device (the last one):
# VBoxManage list usbhost
Host USB Devices:
UUID: dc25c3c2-88b4-422a-a195-c13dfba58a6c
VendorId: 0x045e (045E)
ProductId: 0x0047 (0047)
Revision: 0.0 ()
Port: 0
USB version/speed: 0/1
Manufacturer: Microsoft
Product:Microsoft 5-Button Mouse with IntelliEyeTM
Address:/dev/ugen1.3
Current State: Busy
UUID: f9613731-eb1c-41a1-a516-86707a4e596a
VendorId: 0x067b (067B)
ProductId: 0x2305 (2305)
Revision: 0.0 ()
Port: 0
USB version/speed: 0/1
Manufacturer: vendor 0x067b
Product:IEEE-1284 Controller
Address:/dev/ugen2.3
Current State: Busy
UUID: 1c22de78-a318-4830-be8d-f6aecd0f3617
VendorId: 0x13e5 (13E5)
ProductId: 0x0003 (0003)
Revision: 0.0 ()
Port: 0
USB version/speed: 0/1
Manufacturer: Serato
Product:TTM57SL
SerialNumber: TTM.01.00
Address:/dev/ugen1.4
Current State: Held
Device permissions are OK:
# ls -l /dev/ugen1.4
lrw-rw-rw- 1 root wheel 9 Feb 9 18:33 /dev/ugen1.4 -> usb/1.4.0
VirtualBox is running as root.
Is USB passthrough supported on this version of VirtualBox?
Should I have some special settings on host to allow this device for
VBox guest?
Miroslav Lachman
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"
Hi,
this bug was solved in version 4.3.20_1. Look at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194196
Regards,
Maurizio
**
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"
Re: [PATCH] virtualbox-ose - VBoxHeadless TCPv6 port value
On 21/06/2012 0.39, Dan Mack wrote: I think this patch is broken. I get : /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/src/VBox/Frontends/VBoxHeadless/FramebufferVNC.cpp:94: error: 'struct _rfbScreenInfo' has no member named 'ipv6port' kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxHeadless/FramebufferVNC.o] Error 1 Dan On Thu, 17 May 2012, Maurizio Vairani wrote: Dear list members, the latest libvncserver has IPv6 enabled by default. VirtualBox uses this library for VNC headless connection without specify the tcp6 port value. Running two or more virtual machines, all are trying to use the same tpc6 port 5900, the default value. Connecting with a VNC viewer to a virtual machine, different from the first started, it crashes with a core dump, probably due a bug in the FreeBSD libvncserver implementation. This simple patch set the tcp6 port value to the same value as tcp4 port avoiding the crash. Regards, Maurizio What version of libvncserver you have ? I have installed v. 0.9.9_2 $ pkg_info | grep libvnc libvncserver-0.9.9_2 Provide an easy API to write one's own vnc server Maurizio ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[PATCH] virtualbox-ose - VBoxHeadless TCPv6 port value
Dear list members, the latest libvncserver has IPv6 enabled by default. VirtualBox uses this library for VNC headless connection without specify the tcp6 port value. Running two or more virtual machines, all are trying to use the same tpc6 port 5900, the default value. Connecting with a VNC viewer to a virtual machine, different from the first started, it crashes with a core dump, probably due a bug in the FreeBSD libvncserver implementation. This simple patch set the tcp6 port value to the same value as tcp4 port avoiding the crash. Regards, Maurizio --- src/VBox/Frontends/VBoxHeadless/FramebufferVNC.cpp.orig 2012-04-26 18:58:42.0 +0200 +++ src/VBox/Frontends/VBoxHeadless/FramebufferVNC.cpp 2012-05-16 15:32:46.651165568 +0200 @@ -89,7 +89,7 @@ vncServer = rfbGetScreen(0, NULL, mWidth, mHeight, 8, 3, 1); vncServer->screenData = (void*)this; if (mVncPort) -vncServer->port = mVncPort; +vncServer->port = vncServer->ipv6port = mVncPort; char *pszDesktopName; rc = RTStrAPrintf(&pszDesktopName, "%s - VirtualBox", pszName); if (rc >= 0) ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
