Custom Query (16363 matches)
Results (1840 - 1842 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12934 | obsolete | full screen fails on OS X host | ||
| Description |
host: OS X 10.9.2 Enabling full screen makes the display go black for some time. After only a small part of the client is shown with no scroll or menu bars. |
|||
| #4090 | fixed | full access to the host filesystem via shared folders | ||
| Description |
Anyone under guest Linux OS will be able to access host filesystem by using the simplest "\.." path traversal technique. "Read only" option in the shared folders list still have its effect. |
|||
| #965 | invalid | full CPU usage when raw disk is attached | ||
| Description |
I've started experimenting with the new feature of using raw disk with vbox. I'm stuck with virtual machine using 50% CPU (one core) right on boot - i.e. in GRUB, any OS booted from mentioned drive, CD or whatever. It is stable but slow. It just takes one CPU core for it's own - no matter what. At the same time disk image-files performs excellent with low load. I know that using raw disks is somehow experimental yet. I did RTFM though and I found nothing about such performance drop. Manual even says: "it allows a guest operating system to access its virtual hard disk much more quickly than with disk images" - which is to be expected. Therefore I guess it deserves a ticket to support you on your great work. Some details: I'm using VirtualBox 1.5.2r25433 (closed source version as open src doesn't have mentioned feature :| ) The vmdk file has been created with following command: VBoxManage internalcommands createrawvmdk -filename /media/hda5/virt/raw.vmdk -partitions 1 -rawdisk /dev/sda (I experimented with other partitions too - no change) My OS is Ubuntu Gutsy # uname -a Linux privateer 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux The drive is a regular SATA HDD, nothing fancy. I have experimented with all ACPI settings combinations of my virtual machine - no change. Changing the amount of memory from 128 to 512MB doesn't change the thing either. I found nothing in syslog or vbox log (attached). |
|||

