Custom Query (16363 matches)
Results (2437 - 2439 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 |
|||
| #7411 | fixed | COM Port not visible in Guest machine. => Fixed in SVN | ||
| Description |
The configured serial ports (COM Ports) do not function in the guest virtual machine
I configured my guest machine (running Windows XP) to use two serial ports (COM ports). Both COM ports are available on the host (Windows XP). But the COM ports do not run on the guest virtual machine. Why? |
|||
| #9079 | obsolete | VMs lose connectivity (VRDP, ssh and some times even VBoxManager) | ||
| Description |
Environment:
Repro:
[0]. Please see the attached VM info file to see how it is configured.
Actual Result: Thou the process stays up: [cpuser@rde01 Logs]$ ps -uax | grep cp-t3-u64 Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.7/FAQ cpuser 23038 26.7 0.0 4477400 30640 ? Sl 09:20 12:31 /usr/lib/virtualbox /VBoxHeadless --comment cp-t3-u64 --startvm 5b50bfc5-4f43-4553-a0f0-1f38961457ac cpuser 23159 0.0 0.0 61232 780 pts/3 S+ 10:07 0:00 grep cp-t3-u64 The following is however random (or maybe time dependent): [cpuser@rde01 Logs]$ vbm list runningvms
Oracle VM VirtualBox Command Line Management Interface Version 3.2.12
(C) 2005-2010 Oracle Corporation
All rights reserved.
''[removed the other VMs list]''
"cp-t3-u64" {5b50bfc5-4f43-4553-a0f0-1f38961457ac}
Sometimes VBoxManage still sees the VM up, some times it doesn't [even if the process is still active] (don't know if this is related to this particular issue or is a different bug thou ...). Expected Result: For everything to run smoothly and VM to stay up and accessible.
Comments:
I run top against the VM in the VRDP RDS and when it dies, CPU is usually over 60% (please see attached printScreen). I don't know if this is relevant or not but it does seem to affect the VM's lifespan (as in when I don't execute the mentioned installation the machine stays up much longer). |
|||

