VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2158 - 2160 of 16363)

Ticket Resolution Summary Owner Reporter
#1532 invalid cannot use an cloned vdi in Suse 10.3 Giangiacomo
Description

I clone an hd vdi using VBoxManage clonevdi, then I try to use it for a new Virtual machine. At the begininng the VM boot correctly (ask me which type of boot to use) then try to run the SO but stops and give the message: resume device not find.... waiting for device...... want me to fall back...... se attach

I Use VirtualBox on Suse 10.3 and I Cloned a Suse 10.3 SO. I work under root and I moved ./virtualBox/VDI folder under /var

Thanks Giangiacomo

#1534 fixed Video problem with addition (openSUSE 10.3) Giangiacomo
Description

I install VBoxAddition on suse 10.3 VM after reboot video crash. i see several colored pixel. it seem s then so works (I see something moving whene I move mouse)but i cannot recognise enything. Thank giangiacomo

#12175 obsolete Win7 VM freezing associated with kworker load on host ubuntu 12.04 Lachele
Description

64-bit Windows 7 VM hosted on 64-bit Ubuntu 12.04.

The VM freezes up within a few minutes of boot (5 minutes to 20 or so). I can usually re-size the display (e.g., to/from full-screen) with varying success, but the display stops changing, and input from the keyboard and mouse is not registered. Once, after a freeze, audio streaming from the internet continued to work. I haven't been able to test the latter for reproducibility.

It has frozen at least once when the VM was running very limited graphics, during a hard drive check pre-boot.

Not only does the VM freeze, but VirtualBox also becomes unresponsive. It must be killed from within the host operating system. Just after freezing, I can choose from the VirtualBox menu to power off the machine, but it doesn't work. After that, VirtualBox no longer responds to anything at all.

At the moment it freezes, two kworker processes in the host, specficially kworker/u:3 and kworker/u:2, also begin to occupy 100% and 50% CPU, respectively (1.5 procs of a quad-core). The increased kworker load persists until the host machine is rebooted, even if all VirtualBox processes have been killed.

This behavior first appeared associated with a Windows update. Specifically, it seemed to be associated with "Update for Windows7 for x64-based Systems (KB2868116)". However, the relationship might be coincidental because the VM worked for a while after that update was finally applied. But, it has started freezing again. I tried reverting the VM to before the most recent update, but it still freezes.

I'm attaching the log from my most recent attempt to use the VM.

I posted a detailed history/discussion of this to the forum. I will happily repeat that information here if requested. The title of the post has a typo: 12.02 should be 12.04. It is at the link below.

https://forums.virtualbox.org/viewtopic.php?f=7&t=57477

Please let me know anything else I can do to help fix this.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy