Custom Query (16363 matches)
Results (244 - 246 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3601 | obsolete | PXE Boot gives up | ||
| Description |
When booting a VM through PXE, the current behavior is to try Interface 1 for some time, then go over to the next interface, and when there are now more interfaces, give up. A better behavior would be to go round-robin, so that when there are no more interfaces, in would start over from interface 1. In the case of the server facilitating the PXE boot also being a VM, it might not be booted before the other VM's PXE boot has given up. It would also be useful to select which interface(s) should boot, so that one doesn't have to wait for an interface which is on a different net to time out. |
|||
| #3603 | fixed | Request for Start in Paused Mode | ||
| Description |
We use multiple VMs to build clusters. When saving states of the VM, it's quite easy for us to quickly pause all machines, and then save their individual states. But when starting the VMs we get trouble, because before we have started up all VMs the first one started gets network timeouts when looking for the other nodes. What would be needed is that the nodes gets paused as soon as they are restored, so that they can be resumed all at the same time. We've tried to issue a VBoxManage controlvm <node> pause as soon as VBoxManage startvm has returned, but in the case of restoring from a state, the VM is not in a pauseable state after returning from VBoxMaange startvm <node>. The feature we'd need is a 'pause' option to VBoxManage startvm, that would set the VM in a paused state as soon as it's possible to do so. Alternatively a way to make VBoxManage startvm only to return when the state 'running' has actually been reached. |
|||
| #4118 | fixed | Multiple VMs on single TAP device fails | ||
| Description |
When I start multiple VMs that all have Host Interface Networking, and are using the same TAP device, only the one started first successfully start. The subsequently started VM fail with: "Failed to open Host Interface Network device driver (VERR_PDM_HIF_OPEN_FAILED)" The Host OS is Vista 32-bit. The Guest OSes is Linux 64-bit. The virtual NICs are PCnet-FAST III. This configuration works well on Linux with a TAP device. The way I see it, using a single TAP with multiple VMs is the only way to go if you need a configuration where there is two-way communication between both Guest-Host and Guest-Guest. I haven't tested this in a newer version that 2.1.4, because I found no fitting fixed bug rapport in the release notes of the newer versions. The errors reported in the logs: "00:00:01.609 PDM: Failed to construct 'pcnet'/0! VERR_PDM_HIF_OPEN_FAILED (-2852) - Unable to open the host interface. 00:00:01.611 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={e3c6d4a1-a935-47ca-b16d-f9e9c496e53e} aComponent={Console} aText={Failed to open Host Interface Networking device driver (VERR_PDM_HIF_OPEN_FAILED). 00:00:01.611 Unknown error creating VM (VERR_PDM_HIF_OPEN_FAILED)} aWarning=false, preserve=false 00:00:01.619 Power up failed (vrc=VERR_PDM_HIF_OPEN_FAILED, rc=E_FAIL (0X80004005)) 00:01:04.004 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={e3c6d4a1-a935-47ca-b16d-f9e9c496e53e} aComponent={Console} aText={Invalid machine state: 1)} aWarning=false, preserve=false" |
|||

