Custom Query (16363 matches)
Results (1123 - 1125 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18367 | fixed | When moving main window, its position is saved incorrectly -> fixed in 6.0.4 | ||
| Description |
Result: The main window appears shifted from the previous position to the right+down.
Details: It appears that the coordinates are stored incorrectly in the VirtualBox.xml. For example, when I moved the window to position (104, 382) and close the window I can see that GUI/LastWindowPosition assumes the value "390,134,761,854", so it's 8 pixels lower and 30 pixels to the right from where it was, so obviously next time I start VB it will appear at those shifted coordinates (134, 390). If I don't move the main window at all, its position in the XML is not changed, and upon restart the window position remains the same. That's why I think it's something wrong with the current position calculation when I move the window. Host OS: Windows 7 x64 SP1, Aero theme. |
|||
| #18365 | invalid | exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen | ||
| Description |
Hello, I am using Fedora 29 as a host, which runs 5 VMs, a mix of Linux and FreeBSD. I never had problems with VirtualBox 5.x, I recently upgraded to 6.0.2. Yesterday, while working on one of the VMs, something strange happened that I've never seen before. ALL the VM consoles suddenly printed SATA errors, at the same time. Here are the relevant parts of /var/log/messages from three of those VMs. VM1 Jan 26 03:03:07 vm1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 26 03:03:07 vm1 kernel: ata1.00: failed command: FLUSH CACHE
Jan 26 03:03:07 vm1 kernel: ata1.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 7#012 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 26 03:03:07 vm1 kernel: ata1.00: status: { DRDY }
Jan 26 03:03:07 vm1 kernel: ata1: hard resetting link
Jan 26 03:03:07 vm1 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 26 03:03:07 vm1 kernel: ata1.00: configured for UDMA/133
Jan 26 03:03:07 vm1 kernel: ata1.00: retrying FLUSH 0xe7 Emask 0x4
Jan 26 03:03:08 vm1 kernel: ata1.00: device reported invalid CHS sector 0
Jan 26 03:03:08 vm1 kernel: ata1: EH complete
VM2 Jan 26 03:09:10 vm2 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 26 03:09:10 vm2 kernel: ata1.00: failed command: FLUSH CACHE
Jan 26 03:09:10 vm2 kernel: ata1.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0#012 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 26 03:09:10 vm2 kernel: ata1.00: status: { DRDY }
Jan 26 03:09:10 vm2 kernel: ata1: hard resetting link
Jan 26 03:09:11 vm2 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 26 03:09:11 vm2 kernel: ata1.00: configured for UDMA/133
Jan 26 03:09:11 vm2 kernel: ata1.00: retrying FLUSH 0xe7 Emask 0x4
Jan 26 03:09:11 vm2 kernel: ata1.00: device reported invalid CHS sector 0
Jan 26 03:09:11 vm2 kernel: ata1: EH complete
VM3 Jan 26 03:03:08 vm3 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 26 03:03:08 vm3 kernel: ata1.00: failed command: FLUSH CACHE
Jan 26 03:03:08 vm3 kernel: ata1.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 17#012 res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 26 03:03:08 vm3 kernel: ata1.00: status: { DRDY }
Jan 26 03:03:08 vm3 kernel: ata1: hard resetting link
Jan 26 03:03:08 vm3 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 26 03:03:08 vm3 kernel: ata1.00: configured for UDMA/133
Jan 26 03:03:08 vm3 kernel: ata1.00: retrying FLUSH 0xe7 Emask 0x4
Jan 26 03:03:08 vm3 kernel: ata1.00: device reported invalid CHS sector 0
Jan 26 03:03:08 vm3 kernel: ata1: EH complete
I tried to send a reboot command via ssh and out of the five VMs only two responded, the other three wouldn't accept connections. I tried the "ACPI Shutdown" option directly, but they still wouldn't respond or reboot. Eventually I had to forcefully turn them off. On reboot, everything seems back to normal. Here is a part of the VBox log 00:00:01.048370 VD#0: Cancelling all active requests
00:00:01.048446 VD#0: Cancelling all active requests
00:00:10.824386 VD#0: Cancelling all active requests
00:00:10.828057 VD#0: Cancelling all active requests
74:34:19.969034 VD#0: Flush request was active for 29 seconds
74:40:22.518388 VD#0: Cancelling all active requests
74:40:22.518414 VD#0: Request{0x007fcddc19d740}:
74:40:22.970057 VD#0: Flush request was active for 61 seconds
74:40:22.970084 VD#0: Aborted flush returned rc=VERR_PDM_MEDIAEX_IOREQ_CANCELED
91:03:11.731269 FPUIP=00000000 CS=0000 Rsrvd1=0000 FPUDP=00000000 DS=0000 Rsvrd2=0000
91:03:11.731485 FPUIP=00000000 CS=0000 Rsrvd1=0000 FPUDP=00000000 DS=0000 Rsvrd2=0000
All VMs are stored on the host as a RAID1 array (ext4). |
|||
| #18364 | duplicate | Can't Drag & Drop Files from Win10 Guest to Win10 Host | ||
| Description |
VirtualBox Version: 6.02 r128162
I can successfully copy and paste text bidirectionally. I can also successfully drag and drop a file from host to guest, but if I try to drag and drop a file from guest to host, it fails with the message:
I've attached verbose logs for both host and guest. I've searched the errors and found many references, but the only one that directly relates to my situation is ticket #18305, which has no posted solution. Thanks in advance for your help. |
|||

