VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (841 - 843 of 16363)

Ticket Resolution Summary Owner Reporter
#9840 obsolete virtio driver with WinXP breaks connection to FileMaker Server since upgrade to 4.1.4 virtwolf
Description

The setup: A LAN with three virtual Windows XP machines on one and a Windows Server 2003 installation running on another Linux (Debian Squeeze) host, both with latest VirtualBox 4.1.4 installations and Extensions. All virtual machines have their designated bridged tap interfaces on the respective Linux hosts.

The XP machines have FileMaker Pro 11 clients installed, the server has FileMaker Server 11. Two FM clients can log into the FM database, the third one does not get through. I can ping from the underlying XP to the W2K3 server but that is all. The error from FileMaker server is

Warning 200 SERVERNAME Client "(hostname) [192.168.1.99]" denied access because the license key is already in use by client "myusername (hostname) [192.168.1.99]"

The problem was the broken XP client system's network configuration: It was connected to the LAN through a RedHat VirtIO network driver (Adapter 2) with which I had been experimenting a while ago. Simple switching back in VirtualBox to the previously installed Intel (R) PRO/1000 MT driver (Adapter 1) restored full FileMaker network functionality. The other clients also use the Intel drivers.

I am not sure whether the problem is the use of the virtio interface per se or the fact that both virtual adapters, virtio and Intel, were configured with the same IP address (had to click away a Windows alert to confirm this setting) and therefore perhaps the request from FMPro that went to FMServer may have been passed through both Windows guest interfaces simultaneously although the device manager only shows one interface. However, logging into Windows via a remote rdp connection while using the virtio interface triggered the Windows jingle and shortly afterwards I could hear a second jingle, like an echo. This does not happen when the Intel driver is being used.

It is also not clear how exactly the upgrade from 4.1.2 to 4.1.4 could have caused the problem. It appeared after the upgrade but I do not know whether it may have swapped the activated Adapter from Intel to virtio (both were previously installed but only one was activated), or has something in the previously functional virtio driver been changed for worse?

#5440 worksforme Lost Disk Space Ryan McKee
Description

I too experienced the problem described in this ticket http://www.virtualbox.org/ticket/3410

I had a Virtual Machine Running On Windows 7 running Linux Mint as a Guest OS, during the installation of the Guest OS I encountered an out of space warning. Before the Guest OS I had allocated 8GB while 10GB were free, sometime during the installation of the Guest OS the free disk space warning come up, so I closed out of the Virtual Machine, went to the VirtualBox Media Manager, detached the hard drive and then "removed" it. After doing this and shutting down Virtual Box, Windows Claimed I had only 732 KBs of Free Disk space left. No installation of programs or additional data was implemented during this issue. There is clearly something wrong here, I started out with 10GB of free disk space and now even after removing the Virtal Hard Disk, I'm down to 732 KBs! That is a tremendous unbearable loss. I need a solution as I have programs and personal data on this machine that I wish to retain and do not wish to have to reformat and spend days or even a week reinstalling and configuring and setting up my computer the way I like it due to a flaw in Virtal Box. Please tell me how to recover the disk space that VirtualBox allocated for the Virtal Machine.

#15826 invalid Linux guest always suddenly drops to text video mode glitch. LXC/mount/net/no MTRR for e0000000,1000000 -> guest system bug virtualreport
Description

This happens also on newest build 5.1.5 r110255

In some situations, always, the screen mode changes to a glitched text mode: The video output seen in VirtualBox looks as if the video memory was stil filled with the RGB data of the graphical mode, but it is shown as text (as "DOS text mode"/VGA text mode - with ASCII characters and foreground/bg colors). You can still see the glitched letters make up shape of the graphcis from video mode.

The machnie seems to keep working otherwise, and if you get it to do a graphics mode change (e.g. cause it to exit X destkop session and drop back to kdm/gdm login screen, that has other resolution and causes another video mode change) then it's all back to normal.

So I would say the video "BIOS" of VirtualBox for some reason wrongly changes to video mode to text mode suddenly.

I think this is the part of log showing how VB sees the change:

01:02:58.389101 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=900 h=400 bpp=0 cbLine=0x0 flags=0x1 01:02:58.389281 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=900x400, Sending to async-handler 01:02:58.389364 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=900x400 01:02:58.389375 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=900x400 01:02:58.389405 GUI: UIFrameBufferPrivate::performResize: Size=900x400, Directly using source bitmap content

and in the guest, /var/log/messages (shows the network cards/mount operations related to LXC container creation) and then:

Aug 18 07:15:52 debian kernel: [ 7235.135859] IPv6: ADDRCONF(NETDEV_CHANGE): vethILWQYJ: link becomes ready Aug 18 07:16:07 debian kernel: [ 7249.971535] br0: port 1(vethILWQYJ) entered forwarding state Aug 18 07:16:25 debian org.a11y.atspi.Registry[1163]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Aug 18 07:16:25 debian org.a11y.atspi.Registry[1163]: after 2055 requests (2055 known processed) with 0 events remaining. Aug 18 07:16:25 debian org.a11y.atspi.Registry[1540]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Aug 18 07:16:25 debian org.a11y.atspi.Registry[1540]: after 2053 requests (2053 known processed) with 0 events remaining. Aug 18 07:16:25 debian org.gtk.vfs.Daemon[1481]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Aug 18 07:16:25 debian org.gtk.Private.UDisks2VolumeMonitor[1481]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

and it's /var/log/kernel:

Aug 18 07:15:52 debian kernel: [ 7235.114879] EXT4-fs (loop7): couldn't mount as ext2 due to feature incompatibilities Aug 18 07:15:52 debian kernel: [ 7235.117191] EXT4-fs (loop7): mounted filesystem with ordered data mode. Opts: (null) Aug 18 07:15:52 debian kernel: [ 7235.135859] IPv6: ADDRCONF(NETDEV_CHANGE): vethILWQYJ: link becomes ready Aug 18 07:16:07 debian kernel: [ 7249.971535] br0: port 1(vethILWQYJ) entered forwarding state Aug 18 07:16:26 debian kernel: [ 7269.358927] mtrr: no MTRR for e0000000,1000000 found Aug 18 07:16:30 debian kernel: [ 7273.037129] br0: port 1(vethILWQYJ) entered disabled state Aug 18 07:16:30 debian kernel: [ 7273.057648] device vethILWQYJ left promiscuous mode Aug 18 07:16:30 debian kernel: [ 7273.057655] br0: port 1(vethILWQYJ) entered disabled state

When this happens: 1) It's report to happen on Ubuntu guest when it is starting up, each time, as demonstrated in video: https://www.youtube.com/watch?v=guM0AlQV_S4

2) But more important - on Debian guest, when it e.g. compiles certain source code. It happens each time (tested around 15 times). It compiles the source code using on guest LXC (linux containers), which also calls a mount operation. Perhaps that is related somehow.

It seems that compiling other source code e.g. the kernel sources does not cause the problem, or at least takes longer to trigger it.

For case (2) it was tested on host Windows10.

The work around with changing settings of video mode acceleartion (in VM, then starting machine again) seems to not help.

How ever, this was not happening before. It started it seems after I tried other acceleration settings, enabled some settings among NX bit, nested virtual pages, and so on. But now I can not get it back into usable state.

In addition when I was first changing the settings, AFAIR I managed to save them even though the GUI of VB settings was showing exclamation mark warning that this settings are not valid. Perhaps this somehow corrupted the machine configuration to a state that always causes this video mode glitch.

Btw, I seen a bug report also of Linux KVM (qemu) program (not Virtual Box) that happened in same place: when running the build inside machine and in the machine it starts to use LXC (and/or KVM maybe, inside the machine), this managed to show some text mode glitch on screen, this can be related but maybe not identical problem... Setting VB virtualization type to Minimal, Default, KVM, did not helped afair.

STEPS TO REPRODUCE:

I suspect that running any Gitian build that uses LXC, or maybe any use of LXC inside machine should trigger it.

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