Custom Query (16363 matches)
Results (814 - 816 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10893 | duplicate | sse4.1 sse4.2 not visible in guest | ||
| Description |
Current installation profile: Virtualbox 4.1.20 Host: Snow Leopard (OS X 10.6.8) Guest: Ubuntu 12.04 On Virtualbox: CPU: Intel(R) Xeon(R) CPU X5650 @ 2.67GHz flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc rep_good nopl pni ssse3 lahf_lm On parallels desktop: CPU: Intel(R) Xeon(R) CPU X5650 @ 2.67GHz flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc arch_perfmon nopl nonstop_tsc aperfmperf pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes hypervisor lahf_lm ida arat dts |
|||
| #6170 | obsolete | spurious VERR_INVALID_PARAMETER on 'VBoxManage convertfromraw' | ||
| Description |
Invocation of the above command can result in this spurious error when in fact there is nothing wrong with the command. Simply retrying the command can result in success on the next iteration or the nth attempt thereafter. Example: VBoxManage convertfromraw hdc7empty.img xp_hdc7.vdi --variant Fixed VirtualBox Command Line Management Interface Version 3.1.2 (C) 2005-2009 Sun Microsystems, Inc. All rights reserved. Converting from raw image file="hdc7empty.img" to file="xp_hdc7.vdi"... Creating fixed image with size 8196271104 bytes (7817MB)... Error while creating the disk image "xp_hdc7.vdi": VERR_INVALID_PARAMETER root@nehalem:/SDA12/vbox> !! VBoxManage convertfromraw hdc7empty.img xp_hdc7.vdi --variant Fixed VirtualBox Command Line Management Interface Version 3.1.2 (C) 2005-2009 Sun Microsystems, Inc. All rights reserved. Converting from raw image file="hdc7empty.img" to file="xp_hdc7.vdi"... Creating fixed image with size 8196271104 bytes (7817MB)... root@nehalem:/SDA12/vbox> |
|||
| #3983 | invalid | specifying guest os version can cause problem | ||
| Description |
VBox allows a user to specify a guest os' version, e.g. for Linux, he can specify Ubuntu, Fedora, openSUSE, etc. this has advantages but can also cause problems that leave the user clueless. for example, running an openSUSE 11.1 + KDE4 live cd image in vbox and specifying the os version as "openSUSE" will cause the live os to stop responding at booting phrase. fedora 9, 10, 11 live os images also have such problems. so i suggest that vbox clearly specify supported versions, e.g. "openSUSE 1.0 - 11.0" instead of "openSUSE", so that if i'm running openSUSE 11.1 in vbox and encounter a problem i would suspect i'm using an unsupported guest os version number. i also suggest that vbox rename "Linux 2.6" to "Linux 2.6 (Use this if you have problems)". |
|||

