Custom Query (16612 matches)
Results (76 - 78 of 16612)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #21820 | fixed | VRDP segfault when connecting using MS RemoteDesktop from an M2 Mac => fixed in SVN/next 7.0.x maintenance | ||
| Description |
I'm running VirtualBox on a Oracle Linux 9 host with a Windows 11 guest OS with VRDP configured (on the RDP port (port 3389) of the host OS). When I connect to that port using a Microsoft Remote desktop client running on an M2 Mac, the Win11 VirtualBox crashes (in a consistently reproducible manner)). The detailed setup is as follows:
Other notes:
Here are the relevant parts (showing the connection attempt) in the virtualbox log (i.e. the VBox.log file under the VM's Logs directory) when the crash happens (full log attached): ... 02:05:30.046773 VRDP: New connection: 02:05:30.046849 VRDP: Connection opened (IPv4): 20 02:05:30.047506 VRDP: Negotiating security method with the client. 02:05:30.048900 VRDP: Connection closed: 20 02:05:30.071544 VRDP: New connection: 02:05:30.071585 VRDP: Connection opened (IPv4): 21 02:05:30.072096 VRDP: Negotiating security method with the client. 02:05:39.181010 VRDP: Methods 0x0000001b 02:05:39.181059 VRDP: Channel: [rdpdr] [1004]. Accepted. 02:05:39.181062 VRDP: Channel: [rdpsnd] [1005]. Accepted. 02:05:39.181064 VRDP: Channel: [cliprdr] [1006]. Accepted. 02:05:39.181066 VRDP: Channel: [drdynvc] [1007]. Accepted. 02:05:39.181068 VRDP: Unsupported SEC_TAG: 0xC006/8. Skipping. 02:05:39.181070 VRDP: Unsupported SEC_TAG: 0xC00A/8. Skipping. 02:05:39.214120 VRDP: Client seems to be MSFT. 02:05:39.214140 VRDP: Logon: macbookM2 (10.0.0.32) build 67676. User: [xxxxxxxxx] Domain: [] Screen: 0 02:05:39.215346 AUTH: User: [xxxxxxxxxx]. Domain: []. Authentication type: [External] 02:05:39.460198 AUTH: external authentication module returned 'access granted' 02:05:39.460241 AUTH: Access granted. 02:05:39.466217 VRDP: Enabling upstream audio. 02:05:39.466310 VBVA: VRDP acceleration has been requested. 02:05:39.482448 VMMDev: SetVideoModeHint: Got a video mode hint (1708x1069x32)@(0x0),(1;0) at 0 02:05:39.482498 VRDP: SunFlsh disabled. 02:05:39.482554 VMMDev: Guest Log: Got multi resize request 1 displays 02:05:39.482581 VMMDev: Guest Log: [0]: 0 0x39 0,0 1708x1069 32 02:05:39.497029 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007fdb68000000 w=1708 h=1069 bpp=32 cbLine=0x1AB0 flags=0x1 origin=0,0 02:05:39.507097 VRDP: SCARD enabled for 22 And here is the relevant part from /var/log/messages on the host (Linux) system, showing the VRDP crash: ... Aug 26 14:37:32 ol9 kernel: VRDP-IN[67659]: segfault at 0 ip 00007fdbbe3eaefd sp 00007fdbac4321a8 error 4 in libc.so.6[7fdbbe3cb000+100000] Aug 26 14:37:32 ol9 kernel: Code: xxxxxxxxxxxx Aug 26 14:37:32 ol9 systemd[1]: Started Process Core Dump (PID 91471/UID 0). Aug 26 14:37:32 ol9 systemd-coredump[91472]: Resource limits disable core dumping for process 67639 (VBoxHeadless). Aug 26 14:37:32 ol9 systemd-coredump[91472]: Process 67639 (VBoxHeadless) of user 1000 dumped core. Aug 26 14:37:32 ol9 systemd[1]: systemd-coredump@22-91471-0.service: Deactivated successfully. Aug 26 14:37:32 ol9 kernel: device enp0s13f0u2u4 left promiscuous mode Aug 26 14:37:32 ol9 kernel: vboxnetflt: 0 out of 699226 packets were not sent (directed to host) Searching the existing VirtualBox bugs, #17132 seems to be somewhat similar to this issue (albeit very old, from 2017) More detailed information (unsanitized full logs, core dumps) available (privately) upon request |
|||
| #21816 | invalid | Shared folders group owner set to root instead of vboxsf | ||
| Description |
Mounting a shared folders in a Linux guest VM, the owner group is set to
My VB host is Linux Mint 20.3, and guests where I observed the issue are MXLinux 23 and Linux Mint 21.2. Step to reproduce the issue:
As workaround you have mount the shared folder passing the gid parameter to force the ownership to vboxsf. sudo mount -o gid=<vboxsf gid> -t vboxsf <sf_name> <sf_mountpoint>
|
|||
| #21813 | duplicate | iPXE ISO with virtio-net drivers fails to work in Virtualbox (nic not detected). Works in QEMU. | ||
| Description |
Hi, I am creating a custom iPXE ISO from latest github source, to contain only the virtio-net and also the Intel 82545EM drivers just as a sanity check. Intel 8254EM works fine in VirtualBox. If I switch to VirtIO NIC then it is not detected. I initially thought it was a problem with the ISO, but it works fine in QEMU. This is testing on i386 guest, but it's the same with x64 and EFI. If you use the official "all-drivers" ipxe.iso then EFI appears to work, however it is using SNP rather than the virtio driver. Script to build the ISO:- #!/bin/bash # Build test script for ISO cat <<EOF >/tmp/isoboot.ipxe #!ipxe ifstat || echo ifstat error dhcp || echo dhcp error prompt reboot EOF cd ~/ipxe/src # Build ISO with just Intel 82545EM and virtio-net drivers rm -f bin/82545em--virtio-net.iso make bin/82545em--virtio-net.iso EMBED=/tmp/isoboot.ipxe DEBUG=intel:3,virtio-net:3 I run it in QEMU using all 3 variants of the virtio driver and it detects the nic fine:- qemu-system-i386 -boot d -cdrom 82545em--virtio-net.iso -m 64 -nic user,model=virtio-net-pci qemu-system-i386 -boot d -cdrom 82545em--virtio-net.iso -m 64 -nic user,model=virtio-net-pci-non-transitional qemu-system-i386 -boot d -cdrom 82545em--virtio-net.iso -m 64 -nic user,model=virtio-net-pci-transitional Attached: Screenshot of failure. Thanks in advance. |
|||

