Custom Query (16363 matches)
Results (826 - 828 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11101 | obsolete | All Guests VERY slow on Ubuntu 12.04 64-bit Host (seen in Virtualbox 4.2 and 4.1) | ||
| Description |
I've had extreme slowness on a variety of VirtualBox guests in several versions (at least 4.2 and 4.1) on my Ubuntu 12.04 (also seen on 11.10) server in VBoxHeadless. It's so slow that even booting Arch Linux (guest) takes more than ten minutes (instead of 30 seconds normally). I've got plenty of RAM (8GB of 12GB free right now). The weirdest thing is that restarting the host seems to fix it for a few hours or days. Nothing else helps, not even unloading and reloading all the modules. Currently running VirtualBox version: 4.2.0_OSEr43316 Host: Linux tron 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Host dmesg and Arch Linux Guest 32-bit and 64-bit logs attached. I've seen the problem in Windows Server 2008 as well. |
|||
| #3112 | fixed | All TFTP packages are intercepted on NAT, no matter the server ip => Fixed in SVN | ||
| Description |
Hello, On a Nat VM, I cannot access any tftp server because Vbox capture any TFTP traffic and not just TFTP traffic to its special IP (10.0.2.2). I attached a patch to fix this issue |
|||
| #9615 | fixed | All VDIs lost (not physically): create and delete snapshot after creating VM, restart VirtualBox | ||
| Description |
I create a VM. OS disk is Multi-attach. (Immutable freezes when resuming.) Data disk is Writethrough. I take a snapshot using the UI of the VM while it's powered off in order to create a differencing disk. I delete the snapshot to get rid of the differencing disk but it still leaves a differencing disk, because it's Multi-attach . This is what I wanted. I don't know how to get it otherwise. I restart VirtualBox. I see this on the VM: A differencing image of snapshot {e533c43c-588b-4447-a42e-184097602f56} could not be found. Could not find an open hard disk with UUID {b7de1b6d-ddd7-4367-86a5-2d1391a1c910}. Result Code: E_FAIL (0x80004005) Component: SnapshotMachine Interface: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91} I took the snapshots using VBoxManage with the same results. All disks have disappeared from Virtual Media Manager. Please test creating, configuring, starting, stopping, deleting multiple VMs only with VboxManage you'll run into BSODs. They weren't there before 4.x. Don't take this wrong, I'm just wondering - justifiably, I think: This is 4.x? Really? NO version 4 has this many simple and critical bugs. Do you test these things at all? Does anyone use this actually? I'm feeling like I'm alpha testing some 0.1 version. I hope you can fix all these bugs I've reported immediately, because they are true show-stoppers - I can't use your product while they're there. |
|||

