VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (655 - 657 of 16363)

Ticket Resolution Summary Owner Reporter
#660 invalid Cloning Debian Etch guest breaks networking Theodore Ruegsegger
Description


See also ticket #645 which says that taking a snapshot breaks networking.

On a Kubuntu Feisty host using VirtualBox 1.5 (and 1.4 before with the same result) I created a Debian Etch guest. Then I cloned the disk and used it to create a new virtual machine, but networking fails in the new machine (eth0 just won't come up).

On the original machine, starting networking reports, among other stuff, that eth0 is up at 100MB, Full-Duplex.

On the cloned machine it just says:

Configuring network interfaces...done.

and all I have is lo. If I try ifup eth0, I get:

[boilerplate omitted]
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth0.

I've tried this numerous times, starting from scratch. The same thing happens whether I use NAT or bridging.

Things I've tried that have failed to solve the problem:

  • Rebooting the guest.
  • Power-cycling the guest.
  • modprobe -r pcnet32 ; modprobe pcnet32
  • Not installing guest additions
  • Installing guest additions.
  • Not installing anything beyond the minimum Debian system.

Haven't tried it with any Guest other than Debian Etch.

#661 invalid Virtual machine inaccessable chuichun
Description

Yesterday I try to install additions for VM (debian4.0) but fail. Then today morning I encountered this problem.

Details:

Could not find a registered CD/DVD image with UUID {817e532d-0576-4118-8cde-10646be5d422}.

Result Code: E_INVALIDARG (0x80070057) Component: VirtualBox Interface: IVirtualBox {d1a2295c-d257-4a4c-a9a6-843d87db6f45}

#662 fixed With AMD-V, Win XP hangs early in the boot process -> fixed in SVN/1.5.2 Rune Kock
Description

I'm running a Debian unstable amd64 host. Using VBox 1.5.0, my winxp (32 bit) guest runs fine, unless I enable AMD-V. If I do that, WinXP hangs very early in the boot process, showing a black screen.

I'm going to attach a log file, which shows guru meditation code -1148. Note that I manually close and save the vm at the end.

I don't really understand the problem, but a wild guess is that it may be an error in the virtualisation in my processor. I'm using an Athlon 64 "orleans", stepping F2, which seems to be the first version to include virtualisation.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy