Custom Query (16363 matches)
Results (61 - 63 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18972 | fixed | Application windows disappear when switching to Seamless Mode | ||
| Description |
When I switch to seamless mode, all application windows disappear. Problem experienced under 6.02. Upgraded to 6.12. The problem still exists. This may be an ongoing issue. A search of bug track found reports of seamless mode not working (or not working well, e.g. https://www.virtualbox.org/ticket/15318). The ones reviewed were not specific about the issues experienced. Ubuntu 18.04 |
|||
| #6586 | obsolete | linux loopback mounted disk image != actual hard disk image (linux loop devices) | ||
| Description |
I use loopback devices to create disk image files for development (/dev/loop0 for example). If I create a _filesystem_ only on my loop device, virtualbox can boot from it. For example: dd if=/dev/zero of=diskimage bs=1M count=128 losetup /dev/loop0 mkfs.msdos /dev/loop0 syslinux -s /dev/loop0 (assuming you have a virtualbox disk image file describing loop0). If I instead however, create a _partiton_, with a filesystem on the partition, I cannot boot for some reason. For example, I would use this process to create a compact flash which I could then boot from either in a real device or with QEMU: dd if=/dev/zero of=/dev/sdc bs=1M count=128 fdisk /dev/sdc (create a single partition, sdc1, msdos fat16) mkfs.msdos /dev/sdc1 syslinux -s /dev/sdc1 if I use: dd if=/dev/sdc bs=1M of=myimage and then losetup /dev/loop0 myimage and boot virtualbox with that loopdevice .vdi, it doesn't boot. BUT, qemu has no trouble: qemu -hda myimage /dev/zero This small size disk does have 32/sectors per track and not 63 that most others have. Otherwise I can't see how it would be choking since virtualbox otherwise should be insensitive to the 'type' of device (/dev/sd instead of /dev/loop). |
|||
| #5426 | fixed | USB filter IsActive flag is not editable => Fixed in SVN | ||
| Description |
|
|||

