VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1345 - 1347 of 16363)

Ticket Resolution Summary Owner Reporter
#8891 fixed Reproducible Fedora 6 SMP guest crashes Timothe Litt
Description

I virtualized a server that has been running on dedicated hardware for several years by cloning the original disk to a disk image on a larger server. Minimal configuration changes since, so "before" and "after" statements are attributable to virtualization.

The original server has 2 CPUs according to linux - it is 1-CPU hyperthreaded (Intel P4 630 (P) HT 3.0 GHz with 915GV chipset).

The virtual machine will crash simply by running backup if 2 CPUs are configured. The crash typically occurs after about 3-4GB are written to the (gziped) .tar file.

The virtual machine completes the backup successfully if 1 CPU is configured (leaving the IOAPIC enabled). The full tar file is about 64GB.

I can't rule out the possibility that this is a linux bug. But since linux treats hyperthreads the same as physical processors and the original machine ran for so long without error, first assumption is that something is wrong with the SMP virtualization.

The backup is written to a remote fileserver (nfs mounted from the VM). This is the same as was used for backing up the original server. (The backup script is unchanged.)

Guest is fedora core 6 (2.6.22.14-72); host is fedora core 14. Host has 2 quad-core CPUs, and is running 3 VMs. This VM is the only one configured with more than one CPU.

Failing command (on the virtual machine, via SSH):

tar --totals --one-file-system --xattrs \
     --exclude var/www/servers/PhotoGallery/FileCache \
     --exclude dev --exclude proc --exclude sys \
     --exclude mnt --exclude tmp --exclude var/cache \
     -czpf /mnt/backup/overkill/Sat.tar.z * \
          | tee /mnt/backup/overkill/Sat.log  \
          | grep -v ': socket ignored' \
          | grep -v 'Total bytes written:' \
          | grep -v ': file changed as we read it' \
          | grep -v '/.beagle/' \
          | grep -v ': Error exit delayed from previous errors'

I have seen these failures running headless (normal for me), and under VirtualBox (for debugging this issue.)

I saw the same failures with the disk chipset set to pix4 and to ich6. (The original server has an ICH6 according to linux device manager, so that's what I picked for the VM.)

I configured a serial port on the VM and captured a log of the panic which, is in the attached tar file. The vbox.log files are also in the file.

#14038 fixed VRDP not listening for IPv6 on Linux host [Fixed in SVN] Timothe Litt
Description

Host OS Fedora 17

4.3 claims IPv6 support for RDP, but it isn't listening.

In VBox.log:

VirtualBox VM 4.3.26_OSE r98988 linux.amd64 (Mar 24 2015 20:06:06) release log

00:00:00.258916 VRDP: TCP server listening on port 3392 (IPv4 and IPv6).

netstat -nltp | grep 3392
tcp 0 0 0.0.0.0:3392 0.0.0.0:*  LISTEN  24636/VBoxHeadless

If VRDP was listening on IPv6, there would be a tcp 0 0 :::3392 line

telnet :: 3392
Trying ::...
telnet: connect to address ::: Connection refused

The confusion may be that on some OSs a wildcard socket listen will accept connections from any address family. Or assume IPv4-compatible IPv6 addresses when listening on IPv6 sockets.

This is not the case on all Linux distributions. I don't think any accept either address family on an IPv4 listen. And whether IPv6 sockets accept IPv4 connections depends on the default for IPV6_ONLY, the default for which is configurable in /proc and varies by distribution.

VDRP appears to be listening on IPv4 0.0.0.0.

In the general case, VRDP needs to listen on two sockets to accept connections from both IPv4 and IPv6. This will work on any OS. Or there could be a configuration option to specify which address family to listen to.

In any case, the current log message is wrong and it doesn't seem possible to connect to VirtualBox's RDP over IPv6 on Fedora.

Related: it should be possible to bind the listen(s) to a specific IP address (v4 and/or v6). In a multihomed environment (which all IPv6 environments are), this can be useful. For example, one could use the default RDP port for all VMs if one could specify a dedicated IP address for each VM's RDP listener. Filtering by address can also reduce the number of rules required for some firewall situations.

#15040 worksforme Can't specify DHCP pool range for NAT Networks Timothe Litt
Description

Nat Networks have a DHCP server if you specify 'Supports DHCP', but it doesn't seem to be possible - certainly not in the GUI - to specify the DHCP pool range in a NAT Network. (It is possible in a host-only network.)

There should be a way to specify the DHCP address pool limits. (Of course, within the CIDR.)

Consider the case (which I have), where a NAT Network has a mix of client OSs that do DHCP, and servers that have static addresses (for port forwarding). The clients and servers have private conversations (think manageability.)

The normal solution is to reserve an address range for static IP assignments, and allocate the rest of the subnet to DHCP.

Otherwise, there can be address conflicts when the DHCP server inadvertently issues a static IP address to a dynamic client.

This can happen even if the DHCP server pings before assigning, as the server might be down at the time the client requests an address.

Because of this issue, I'm classifying this as a defect rather than an enhancement request.

A typical allocation might be:

10.0.100.0/24 CIDR
  10.0.100.1 Gateway
  10.0.100.2-99 Static hosts
  10.0.100.100-254 DHCP << It should be possible to specify this.
  10.0.100.255 Broadcast

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