Custom Query (16363 matches)
Results (2272 - 2274 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10849 | obsolete | Changing VM names breaks snapshot path, Causes ProgressProxy error | ||
| Description |
<HardDisk uuid="{xxx}" location="C:/Users/Era/VirtualBox VMs/Base/DirectVM.vdi" format="VDI" type="Normal">
</HardDisk>
|
|||
| #10850 | obsolete | linux host multiple screens windows guest spanning screens fails when restarted | ||
| Description |
i have a linux host running a w7 guest. i normally run this guest at full size spanning both monitors on my two monitor setup. when i restart the guest it only expands to one of the two monitors. i need to manually resize to fit across both monitors again. this has happened for many releases. virtualbox details: version 4.1.20 r80170 with matching extensions and guest extensions. runtime attributes are:
guest details w7 with three virtual screens. host details: the linux host (ubuntu 11.04 up to date) consists of two monitors joined w/o xinerama (e.g. when i hit expand to full screen, windows expand only to the size of a single screen, not both of them). if it matters, i'm rotating both monitors 90 to vertical position. i'll attach my /etc/X11/xorg.conf file if given the chance later. i have six virtual screens using gnome arranged in a 3x2 grid. the top three virtual screens are assigned to one each of the three virtual guest screens. when i boot my guest it always starts with the three virtual guest monitors on the same host monitor. each virtual guest monitor is tiny. i have to stretch it across the entire display spanning both guest monitors and then move it to the correct gnome virtual monitor. if i do nothing, all three guest monitors will be started on whatever gnome host monitor i started the guest on. each guest monitor will expand to it's remembered size, but only one one of the two screens. i must then grab an edge of the virtual guest monitor and drag it across to the other screen. i realize there are a lot of moving pieces here and i am happy to add some additional pictures if someone is interested in it. i have a work around which is to move the screen around where i want them. it's just getting to be a royal pita and i thought you might not know about this issue since it's been around for so long already so i decided to forward it. also... i stupidly created 'winksmit' as my nick, but i typed it too fast and it should be 'winksmith' (missing the 'h'). if someone could fix that, it'd be super. thanks. |
|||
| #10854 | obsolete | VM stuck in powering off state | ||
| Description |
My problem is when powering off the VM it gets stuck in the "powering off" state and never resumes. The only temporary fix is to kill the VM process/reboot the host machine. I am using Virtual-Box 4.1.6 Guest OS: Red Hat 2.6.32 Host Machine Operating System: Linux. I've tried researching this problem extensively, the only solutions I've found is to use 3.x series, but looking at similar issues the problem can also exist with old versions such as vb 1.6. Tickets have been opened in the past with no appropriate fix: https://forums.virtualbox.org/viewtopic.php?f=1&t=6747&p=233895#p233895 https://www.virtualbox.org/ticket/8016 I've also seen some have solved the problem by turning off 3D Acceleration for display, I already have this option set to off and the problem persists. Anything I've found seems to be quite dated, I am a new user to Virtual Box so I was wondering if there are any up to date solutions for VB 4.1.6 ? Unfortunately it is not possible for me to post my log file but the only useful information in it is the following: 00:43:44.507 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0xca (50760579 usec ago) CmdIf1=0x00 (-1 usec ago) 00:43:45.014 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 00:43:46.034 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 00:43:47.054 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 00:43:48.073 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 00:43:49.094 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 00:43:50.114 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 00:43:51.135 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 00:43:52.155 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 00:43:53.175 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 00:43:54.195 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 00:43:55.215 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting 00:43:56.235 PIIX3 ATA: Async I/O thread probably stuck in operation, interrupting However the links I have have included include log files which as similar. I posted this issue on the user mailing list to try get an appropriate fix and had been advised to create a ticket: http://www.mail-archive.com/vbox-users-community@lists.sourceforge.net/msg03717.html |
|||

