VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1654 - 1656 of 16363)

Ticket Resolution Summary Owner Reporter
#3268 wontfix host floppy drive cannot be configured for a guest on a solaris host jkeil
Description

On a Solaris host (SX:CE build 104, bfu'ed to onnv-b108) the host's PS/2 floppy drive cannot be configured as the floppy drive for a guest.

In the GUI settings window for the guest under "Floppy" -> "Mount Floppy Drive": "Host Floppy Drive" is checked, but the pop-up menu that should list the hosts's floppy drives is empty. I'd expecting to have an entry with /dev/rdiskette in the pop-up menu.

A floppy media is mounted on the host:

% df -h /media/floppy/
Filesystem             size   used  avail capacity  Mounted on
/dev/diskette0         1.4M   1.4M    34K    98%    /media/floppy

"VBoxManage list hostfloppies" doesn't list floppies, either:

% /opt/VirtualBox/VBoxManage list hostfloppies
VirtualBox Command Line Management Interface Version 2.1.2
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

% 

Workaround: Transfer contents of floppy media to a file on the host, and use an "Image File" instead of the "Host Floppy Drive".

#2300 fixed host floppy access doesn't work Wolfgang Rosenauer
Description

I'm running Win XP (32bit) in a VM above openSUSE 11.0 (x86-64) and VBox 2.0.2. If I connect the floppy device to my host device /dev/fd0 the floppy LED is just on permanently and access to a inserted disk is not possible. Windows keeps saying I should insert a disk. My user has rw access to /dev/fd0.

#13656 invalid host eth0 interface changes to 192.168.56.1 after first run of virtualbox GUI breaking host network Luis Nunes
Description

Host runs Oracle Linux 6.2 Virtual Box 4.3.18, but also affects previous versions 4.2.

Upon Host boot the default active network is "eth0" with IP 192.168.1.50.

eth0      Link encap:Ethernet  ...
          inet addr:192.168.1.50  Bcast:192.168.1.255  Mask:255.255.255.0

The first time running virtualbox, or vboxmanage, or vboxheadless the interface "vboxnet0" is created and it becomes the default active network, and the interface eth0 IP is changed to 192.168.56.1, breaking the host network access.

eth0      Link encap:Ethernet  ...
          inet addr:192.168.56.1  Bcast:192.168.56.255  Mask:255.255.255.0

vboxnet0  Link encap:Ethernet  HWaddr 0A:00:27:00:00:00

The host is not reachable remotely. The workaround, if near to the host to login, is to switch the active interface "vboxnet0" to "eth0". The local access is not always possible if the host is on remote site. The result of switching back to "eth0" from the host GUI, is the IPs are corrected:

eth0      Link encap:Ethernet  ...
          inet addr:192.168.1.50  Bcast:192.168.1.255  Mask:255.255.255.0

vboxnet0  Link encap:Ethernet  HWaddr 0A:00:27:00:00:00
          inet addr:192.168.56.1  Bcast:192.168.56.255  Mask:255.255.255.0

After the interface switch, all other further runs of "virtualbox" GUI will not affect the interfaces. Need some clue how to solve this situation. Before the switch, If I work locally from the host, I can run the GUI and start the VMs. But I also have to switch the interfaces if I want to access the outside world from either the host or the guests.

Additional Host network info:

# cat ifcfg-eth0
DEVICE=eth0
NM_CONTROLLED=yes
ONBOOT=yes
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth0"
IPADDR=192.168.1.50
PREFIX=24
GATEWAY=192.168.1.254
DNS1=192.168.1.254
HWADDR=C8:60:00:??:??:??
USERCTL=no

# cat ifcfg-vboxnet0
TYPE=Ethernet
BOOTPROTO=none
IPADDR=192.168.56.1
PREFIX=24
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME=vboxnet0
ONBOOT=yes
GATEWAY=192.168.1.254
DEVICE=vboxnet0
USERCTL=no

Network rules

# cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="c8:60:00:??:??:??", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# USB device 0x07d1:0x3c09 (usb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1c:f0:??:??:??", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"

Appreciate help, solution. Thanks

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