Virtualbox 4.3.14 in Ubuntu 14.04.1
Virtualbox 4.3.14 in Ubuntu 14.04.1
I upgraded my system from 12.04.5 to 14.04.1 and installed the current release of Vbox in Trusty (4.3.10). My XP VM did not function correctly. The desktop was only partially showing when I started the VM. I had to do a minimize followed by a maximize to see the whole desktop. The same is true for opened application windows. Additionally, the menus have the same issue.
I then removed Vbox 4.3.10 and installed the latest from the Vbox web site, 4.3.14. Same problem.
I am at a loss as to what I need to do to clear this up. Any help would be appreciated.
I then removed Vbox 4.3.10 and installed the latest from the Vbox web site, 4.3.14. Same problem.
I am at a loss as to what I need to do to clear this up. Any help would be appreciated.
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Virtualbox 4.3.14 in Ubuntu 14.04.1
Start by posting the guests log file ( as an attachment )
Re: Virtualbox 4.3.14 in Ubuntu 14.04.1
I have attached the guest log.
- Attachments
-
- Vbox Guest Log.txt
- (98.3 KiB) Downloaded 21 times
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Virtualbox 4.3.14 in Ubuntu 14.04.1
VirtualBox VM 4.3.14 r95030 linux.amd64 (Jul 15 2014 16:36:03) release log
00:00:05.316997 Guest Additions information report: Version 4.1.12 r77218 '4.1.12'
Update the guest additions and see if that helps.
00:00:05.316997 Guest Additions information report: Version 4.1.12 r77218 '4.1.12'
Update the guest additions and see if that helps.
Re: Virtualbox 4.3.14 in Ubuntu 14.04.1
Guest Additions updated to 4.3.14. Same problem. I have attached the Guest Log.
- Attachments
-
- Vbox Guest Log.txt
- (109.6 KiB) Downloaded 10 times
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Virtualbox 4.3.14 in Ubuntu 14.04.1
This is being posted over and over.
Some questions.
1) has the guest ever worked properly, and if so what version of VirtualBox, and what version of the host?
2) I see you are trying to run the guest as SMP. ( ioapic enabled and 4 GB ram ). Has this always been the case?
Also post the results of the following:
From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.
Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.
Code: Select all
00:05:47.292586 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00007f9dcbdf7000 w=1280 h=960 bpp=24 cbLine=0xF00, flags=0x1
00:05:47.292607 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=24, BytesPerLine=3840, Size=1280x960, Sending to async-handler..
00:05:47.305441 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=24, BytesPerLine=3840, Size=1280x960
00:05:47.305460 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid..
00:07:21.473043 Guest Log: VBoxDisp[0]: VBVA enabled
1) has the guest ever worked properly, and if so what version of VirtualBox, and what version of the host?
2) I see you are trying to run the guest as SMP. ( ioapic enabled and 4 GB ram ). Has this always been the case?
Also post the results of the following:
From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.
Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.
Re: Virtualbox 4.3.14 in Ubuntu 14.04.1
1) Yes, Virtualbox worked fine in 12.04 through 12.04.4. When I went to the new HWE, I begin to have these problems in 12.04.5. The Virtualbox version was 4.2, but I can't remember the last digit.Perryg wrote:This is being posted over and over.
Some questions.Code: Select all
00:05:47.292586 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00007f9dcbdf7000 w=1280 h=960 bpp=24 cbLine=0xF00, flags=0x1 00:05:47.292607 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=24, BytesPerLine=3840, Size=1280x960, Sending to async-handler.. 00:05:47.305441 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=24, BytesPerLine=3840, Size=1280x960 00:05:47.305460 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:07:21.473043 Guest Log: VBoxDisp[0]: VBVA enabled
1) has the guest ever worked properly, and if so what version of VirtualBox, and what version of the host?
2) I see you are trying to run the guest as SMP. ( ioapic enabled and 4 GB ram ). Has this always been the case?
Also post the results of the following:
From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.
Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.
2) Yes. I have not changed the options from when it ran correctly.
Code: Select all
VBoxManage showvminfo "Windows XP" --details
Name: Windows XP
Groups: /
Guest OS: Windows XP (32 bit)
UUID: c1e2be05-c9bd-4172-b61b-7beba3eb8581
Config file: /home/butch/VirtualBox VMs/Windows XP/Windows XP.vbox
Snapshot folder: /home/butch/VirtualBox VMs/Windows XP/Snapshots
Log folder: /home/butch/VirtualBox VMs/Windows XP/Logs
Hardware UUID: c1e2be05-c9bd-4172-b61b-7beba3eb8581
Memory size: 4096MB
Page Fusion: off
VRAM size: 128MB
CPU exec cap: 100%
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 1
PAE: on
Long Mode: on
Synthetic CPU: off
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): DVD
Boot Device (2): HardDisk
Boot Device (3): Not Assigned
Boot Device (4): Not Assigned
ACPI: on
IOAPIC: on
Time offset: 0ms
RTC: local time
Hardw. virt.ext: on
Nested Paging: off
Large Pages: off
VT-x VPID: on
VT-x unr. exec.: on
State: powered off (since 2014-08-22T03:33:15.000000000)
Monitor count: 1
3D Acceleration: off
2D Video Acceleration: on
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0): IDE Controller
Storage Controller Type (0): PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
IDE Controller (0, 0): /home/butch/VirtualBox VMs/Windows XP/Windows XP.vdi (UUID: 5f7033f3-f2f2-4d97-88fc-7cf7913100ed)
IDE Controller (0, 1): /usr/share/virtualbox/VBoxGuestAdditions.iso (UUID: c4ef0d50-9af4-4162-b575-d903acc12740)
IDE Controller (1, 0): /dev/sr0 (UUID: 00445644-0000-0000-2f64-65762f737230) (passthrough enabled)
NIC 1: disabled
NIC 2: MAC: 080027231141, Attachment: Bridged Interface 'eth2', Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
LPT 1: disabled
LPT 2: disabled
Audio: enabled (Driver: PulseAudio, Controller: AC97)
Clipboard Mode: Bidirectional
Drag'n'drop Mode: disabled
VRDE: disabled
USB: enabled
EHCI: enabled
USB Device Filters:
Index: 0
Active: yes
Name: HP Deskjet 9800 [0100]
VendorId: 03f0
ProductId: 1212
Revision: 0100
Manufacturer: HP
Product: Deskjet 9800
Remote: 0
Serial Number: MY54G111M3046K
Index: 1
Active: yes
Name: Hewlett-Packard hp scanjet 3500c series [0100]
VendorId: 03f0
ProductId: 2005
Revision: 0100
Manufacturer: Hewlett-Packard
Product: hp scanjet 3500c series
Remote: 0
Serial Number: SCN2BUN809B1P
Index: 2
Active: yes
Name: Nikon LS-50 ED [0102]
VendorId: 04b0
ProductId: 4001
Revision: 0102
Manufacturer: Nikon
Product: LS-50 ED
Remote: 0
Serial Number:
Index: 3
Active: yes
Name: Western Digital Elements 107C [1042]
VendorId: 1058
ProductId: 107c
Revision: 1042
Manufacturer: Western Digital
Product: Elements 107C
Remote: 0
Serial Number: 574343344531333137333131
Available remote USB devices:
<none>
Currently Attached USB Devices:
<none>
Bandwidth groups: <none>
Shared folders:
Name: 'Data', Host path: '/media/Data' (machine mapping), writable
VRDE Connection: not active
Clients so far: 0
Video capturing: not active
Capture screens: 0
Capture file: /home/butch/VirtualBox VMs/Windows XP/Windows XP.webm
Capture dimensions: 1024x768
Capture rate: 512 kbps
Capture FPS: 25
Guest:
Configured memory balloon size: 0 MB
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtualbox 4.3.14 in Ubuntu 14.04.1
Probably irrelevant, but here are my notes:
- IMHO it isn't a good idea to give 4GB to a 32bit guest - it makes it a 64bit guest. I'd give 3.5GB max.
- The GAs ISO is still mounted. Good practice is to eject immediately after use.
- The guest seems to be jumping around all over the place with the display size. This might be caused by registry corruption. Perhaps try booting in safe mode, go from there.
Re: Virtualbox 4.3.14 in Ubuntu 14.04.1
I reduced the memory size to 2 GB. No Change.mpack wrote:Probably irrelevant, but here are my notes:
- IMHO it isn't a good idea to give 4GB to a 32bit guest - it makes it a 64bit guest. I'd give 3.5GB max.
- The GAs ISO is still mounted. Good practice is to eject immediately after use.
- The guest seems to be jumping around all over the place with the display size. This might be caused by registry corruption. Perhaps try booting in safe mode, go from there.
How do you eject the GA iso?
I ran regedit and found under HKEY_LOCAL_MACHINE>HARDWARE>DEVICEMAP>VIDEO four video devices: \Device\Video0, \Device\Video1, \Device\Video2, and \Device\Video3.
When I look at HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Control>Video, I see that there are five entries. Two of these show Device description = VirtualBox Graphics Adapter and InstalledDisplayDrivers = VBoxDisp. Of these two, only one corresponds to one of the four listed video devices. That one is Video0. However, also under HKEY_LOCAL_MACHINE>HARDWARE>DEVICEMAP>VIDEO there is an entry named VgaCompatible, and that is \Device\Video1.
As I am not very conversant about the Registry, I am not sure if this is an issue or not.
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Virtualbox 4.3.14 in Ubuntu 14.04.1
I can not reproduce this myself, so that is the reason for me not replying. Maybe mpack has an idea but if it were me, I would try to install another guest XP and see if it works properly or if it has the same issue.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtualbox 4.3.14 in Ubuntu 14.04.1
No, I have nothing to add to the notes I gave already.
Re: Virtualbox 4.3.14 in Ubuntu 14.04.1
Well, I finally had enough time to create a new XP VM. It works like a charm.
I have one question though. I used the same virtual disk I had used for the original VM. If I delete the original VM, will I lose the virtual disk, thereby leaving my new VM with no virtual disk?
I have one question though. I used the same virtual disk I had used for the original VM. If I delete the original VM, will I lose the virtual disk, thereby leaving my new VM with no virtual disk?
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtualbox 4.3.14 in Ubuntu 14.04.1
Quite possibly, if that VM can still access the disk. The disk in effect is the property of that VM. You can clone the disk then install in VM2 for it's exclusive use: that means locate it in the VM2 folder and then mount it using the Storage settinsg for the VM. To clone a VDI see File|Virtual Media Manager|Copy.oldcarp wrote:If I delete the original VM, will I lose the virtual disk, thereby leaving my new VM with no virtual disk?