Custom Query (16363 matches)
Results (1678 - 1680 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18723 | fixed | Error recording from CLI: "The machine is not mutable, saved or running" => fixed in SVN/next maintenance | ||
| Description |
Host: Win10 x64 VM is running in headless mode. I would like to start to record the display from command line. Earlier it was possible by executing this command: VBoxManage controlvm <vm_name> videocap on And when I wanted to stop the recording the following command was executed: VBoxManage controlvm <vm_name> videocap off If I know it well from VBox 6.0(?) this is the valid command for my purpose: VBoxManage controlvm <vm_name> recording on
But now I got these error messages:
VBoxManage.exe: error: The machine is not mutable, saved or running (state is Running) When the GUI of the VBox is used for starting/stopping records (Settings\Display\Recording\Enable Recording) the process is done well but executing from Command Prompt is getting me stuck... |
|||
| #13820 | fixed | Possible Bug With Linux Host and Broadwell CPU's (SMAP feature) | ||
| Description |
I received a Dell latitude e7450 (Broadwell CPU) and as noted in my forum post, Virtualbox Hangs at "0% Starting Virtual Machine". According to the log files it never actually gets to the boot sequence. https://forums.virtualbox.org/viewtopic.php?f=7&t=65932 I noticed another person with a Broadwell CPU was having the same problem here: http://askubuntu.com/questions/581301/virtualbox-stuck-on-starting-virtual-machine/583628 And that leads me to believe that there may be a bug in Virtualbox on Linux Hosts and Broadwell CPU's. To be clear, I enabled Virtualization support in my bios, did a fresh install of Mint 17.1, only installed virtualbox and added my user to vboxusers and it will not boot. If I reboot and load my Windows 7 Partition, Virtualbox works just fine, so the hardware is capable of virtualization, and it works, just not with a Linux host. I've attached logs, hopefully they shed some light on the issue! |
|||
| #4608 | fixed | Failed to attach USB device - DVDROM | ||
| Description |
running virtualbox as root I tried to attach an USB DVDROM - virtual one from ILOM KVM (from Devices/USB Devices/blah), it failed saying: Failed to attach the USB device "blah" to the virtual machine "blah" CALLEE RC: NS_ERROR_FAILURE ( 0x80004005) dmesg: <device connected> Jul 23 11:10:42 bi64-x2250b-prg06 pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata) instance 1 irq 0xf vector 0x41 ioapic 0x8 intin 0xf is bound to cpu 3 Jul 23 11:14:04 bi64-x2250b-prg06 usba: [ID 912658 kern.info] USB 2.0 device (usb46b,ff92) operating at hi speed (USB 2.x) on USB 2.0 root hub: storage@3, ugen0 at bus address 2 Jul 23 11:14:04 bi64-x2250b-prg06 usba: [ID 349649 kern.info] American Megatrends Inc. Composite Device serial Jul 23 11:14:04 bi64-x2250b-prg06 pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata) instance 1 irq 0xf vector 0x41 ioapic 0x8 intin 0xf is bound to cpu 4 <SNIP> Jul 23 11:17:07 bi64-x2250b-prg06 VBoxUSBHelper[1374]: [ID 387370 user.error] VBoxUSBHelper: /usr/sbin/update_drv -a -i pci108e,534f@1d,7/storage@3 ugen Jul 23 11:17:07 bi64-x2250b-prg06 VBoxUSBHelper[1376]: [ID 387370 user.error] VBoxUSBHelper: /usr/sbin/update_drv -d -i pci108e,534f@1d,7/storage@3 ugen Jul 23 11:17:07 bi64-x2250b-prg06 VBoxSVC[1347]: [ID 734376 user.error] USBProxy: failed to capture device American Megatrends Inc. Composite Device. do you need some other logs ? ev. I can give access to the system in SWAN ;) |
|||

