http://bugzilla.suse.com/show_bug.cgi?id=1027742
http://bugzilla.suse.com/show_bug.cgi?id=1027742#c2
Luiz Angelo Daros de Luca changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(luizluca@tre-sc.j |
|us.br) |
--- Comment #2 from Luiz Angelo Daros de Luca ---
I guess it is a problem specific with Tumbleweed. I recently replaced my
tumbleweed machine with a clean installation. Since then, VBox simple gives me
an empty (and down) interface. It seems that some "default" configuration
changed or something else (like the kernel or virtualbox) that broke host-only
net when it got updated.
I created a detailed recipe with outputs:
On LEAP 42.2, it works nicely (check "ip" command outputs):
# zypper in virtualbox
# /etc/init.d/vboxdrv start
# usermod -a -G vboxuser myuser
# su - myuser
$ VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'vboxnet0' was successfully created
$ VBoxManage hostonlyif ipconfig vboxnet0 --ip 192.168.5.1
$
$ ip a show dev vboxnet0
3: vboxnet0: mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.5.1/24 brd 192.168.5.255 scope global vboxnet0
valid_lft forever preferred_lft forever
$
$ VM=test
$ VBoxManage createhd --filename $VM.vdi --size $((5000))
$ VBoxManage createvm --name $VM --ostype "Linux_64" --register
$ VBoxManage storagectl $VM --name "SATA Controller" --add sata --controller
IntelAHCI
$ VBoxManage storageattach $VM --storagectl "SATA Controller" --port 0 --device
0 --type hdd --medium $VM.vdi
$ VBoxManage modifyvm $VM --ioapic on
$ VBoxManage modifyvm $VM --boot1 disk --boot2 none --boot3 none --boot4 none
$ VBoxManage modifyvm $VM --memory 1024 --vram 128
$ VBoxManage modifyvm $VM --nic1 hostonly --hostonlyadapter1 vboxnet0
$
$ VBoxManage startvm $VM
Waiting for VM "test" to power on...
VM "test" has been successfully started.
$
$ ip a show dev vboxnet0
3: vboxnet0: mtu 1500 qdisc pfifo_fast state
UP group default qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.5.1/24 brd 192.168.5.255 scope global vboxnet0
valid_lft forever preferred_lft forever
inet6 fe80::800:27ff:fe00:0/64 scope link
valid_lft forever preferred_lft forever
On Tumbleweed, vboxnet0 never got and IP address (after seconds 'VBoxManage
hostonlyif') and never got UP (after machine went up).
# zypper in virtualbox
# systemctl start vboxdrv
# usermod -a -G vboxuser myuser
# su - myuser
$ VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'vboxnet0' was successfully created
$ VBoxManage hostonlyif ipconfig vboxnet0 --ip 192.168.5.1
$
$ ip a show dev vboxnet0
7: vboxnet0: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
$
$ VM=test
$ VBoxManage createhd --filename $VM.vdi --size $((5000))
$ VBoxManage createvm --name $VM --ostype "Linux_64" --register
$ VBoxManage storagectl $VM --name "SATA Controller" --add sata --controller
IntelAHCI
$ VBoxManage storageattach $VM --storagectl "SATA Controller" --port 0 --device
0 --type hdd --medium $VM.vdi
$ VBoxManage modifyvm $VM --ioapic on
$ VBoxManage modifyvm $VM --boot1 disk --boot2 none --boot3 none --boot4 none
$ VBoxManage modifyvm $VM --memory 1024 --vram 128
$ VBoxManage modifyvm $VM --nic1 hostonly --hostonlyadapter1 vboxnet0
$
$ VBoxManage startvm $VM
Waiting for VM "test" to power on...
VM "test" has been successfully started.
$
$ ip a show dev vboxnet0
7: vboxnet0: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
I also tested inter-VM communication and it worked without problems between two
VM connected to vboxnet0.
If I bring vboxnet0 manually up (ip link set dev vboxnet0 up) and define
manually its ip address, the host machine can talk with VMs using vboxnet0.
--
You are receiving this mail because:
You are on the CC list for the bug.
bugzilla_noreply＠novell.com