Custom Query (16363 matches)
Results (1132 - 1134 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #6340 | duplicate | Windows XP guest crashes everytime VB is started (Guest in unusable) | ||
| Description |
Hi, The following error is causing the guest OS unusable. Host: Ubuntu Karmic Guest: Windows XP I've attached the log file for more information. 00:01:08.728 !!R0-Assertion Failed!!
00:01:08.728 Expression: cRefs == PGMPOOL_TD_CREFS_PHYSEXT
00:01:08.728 Location : /home/vbox/vbox-3.1.4/src/VBox/VMM/VMMAll/PGMAllPool.cpp(3857) void pgmPoolTrackPhysExtDerefGCPhys(PGMPOOL*, PGMPOOLPAGE*, PGMPAGE*)
00:01:08.728 cRefs=0 pPhysPage=Z--:RAM:00007aa34000:0000000:-0000 pPage=0443fa30:{.idx=94}
00:01:08.728 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:01:08.728 !!
00:01:08.728 !! Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION)
00:01:08.728 !!
00:01:08.728 !!R0-Assertion Failed!!
00:01:08.728 Expression: cRefs == PGMPOOL_TD_CREFS_PHYSEXT
00:01:08.728 Location : /home/vbox/vbox-3.1.4/src/VBox/VMM/VMMAll/PGMAllPool.cpp(3857) void pgmPoolTrackPhysExtDerefGCPhys(PGMPOOL*, PGMPOOLPAGE*, PGMPAGE*)
00:01:08.728 cRefs=0 pPhysPage=Z--:RAM:00007aa34000:0000000:-0000 pPage=0443fa30:{.idx=94}
|
|||
| #12506 | obsolete | PCI-passthrough fails with Ubuntui kernel 3.5 and above | ||
| Description |
Hi, was using PCI passthrough since 1.5 years. Host Ubuntu 12.04 with kernel 3.2.x, VB different versions (4.x to 4.3.4). After upgrade to raring kernel the PCI-passthrough fails. Trying kernel 3.5.x showed the same. The PCI device is one of the USB controllers on the mainboard. The fail situation prevents the windows7 in guest to start the root hub driver (error 43). BTW: USB passthrough is not an option to what I need to achieve. It is too slow if USB devices re-enumerate after a firmware flash, so I cannot debug firmware flashers. Attachments: syslog and VB log for both kernels, and guest.vbox. I can do tests if you need that. |
|||
| #15904 | fixed | Regression: auto logon fails after update from 5.0 | ||
| Description |
Hi, auto logon is a nice feature and I used it for many VMs. Now after I upgraded from 5.0.26 to 5.1.4 it does not work anymore. The login screen shows the passed credentials in different fields. Example from user manual: VBoxManage controlvm "Windows XP" setcredentials "John Doe" "secretpassword" "DOMTEST" The login screen of Win10-1607 shows two users "John Doe" and "secretpassword" in the left lower corner. The password box contains some text (just dots) and below the box is the text "DOMTEST". On Win7 it is generally the same, two users. "DOMTEST" does not show up. It almost looks like the command line is not parsed correctly. My host is Ubuntu 1604. All the years I used this start script: VBoxManage startvm "Windows XP" && VBoxManage controlvm "Windows XP" setcredentials "John Doe" "secretpassword" "DOMTEST" && exit 0 When I run the parts of the script (startvm and controlvm) separate and with enough time between, it still does not work. It behaves slightly different though. Left lower corner shows two users "John Doe" and and "username". Later (after writing this and going back to the VM) it shows garbage (Chinese chars) instead "username" and below the password box. That proofs something is fishy. In the VB log I saw noting related to auto logon. I reinstalled GA with /auto_logon, no change. |
|||

