Custom Query (16363 matches)
Results (1366 - 1368 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4501 | fixed | Host hangs/freezes when zones are booted | ||
| Description |
I'm experiencing a show-stopping problem with running VirtualBox 3.0.2 on Solaris hosts. VBox 3 is the latest in a line of releases I've failed to get working reliably on Solaris - various versions of 2 would also hang or panic my host, though with different symptoms to the problem below. The issue I am finding is that with a VBox guest running, my host will freeze/hang if zones are running on the Solaris host. The problem exists on both Solaris 10 U5 and Solaris 10 U7, and I have tried on two different servers - one running new Intel Nehalem X5570 processors (dual processor, quad core), and another running Intel E7320 processors (quad processor, quad core.) Freeze/hang symptoms: The symptoms of the freeze have varied slightly. On my Solaris 10 U5 box (4xE7320 processors), it will simply freeze completely including at the console. On the Solaris 10 U7 (X5570 processors), I lost remote network access but was then sometimes able to login at the console - however it would then freeze completely a couple of minutes later. In all cases, the box will freeze and not panic. Nothing related to VBox is logged in /var/adm/messages or elsewhere, except for the following message: Jul 12 14:20:49 host-us8 vboxdrv: [ID 937234 kern.notice] CPUMSetGuestCpuIdFeature: Disabled x2APIC Note: The above message is logged always, and is not related to the crashing - i.e it appears also when the host does not freeze. Nothing is logged in VirtualBox's log file after initial bootup. There are no log lines near the time of the host freeze/hang. I've attached a sample VBox.log. The log shows messages no later than 2 minutes after the VM booted - the VM caused a host freeze about 15 minutes later. There are no loglines near the time of the freeze. My Configuration: Guest: Windows XP SP3 guest with 1.25GB of RAM, 12MB video ram, one network adapter in NAT mode, USB disabled, CD mounted from ISO, floppy disabled, Intel VT enabled. Installed on a fixed size VDI disk of 20GB. Host: Both Solaris 10 U5 and Solaris 10 U7. Virtualbox installed onto ZFS filesystem. Virtualbox running in the Global zone. Virtualbox running as root. Solaris 10 U5 hardware config: 4 x Quad Core Intel Xeon E7320 processors (16 total cores). 32GB ram. 2 x 500GB SATA disks in UFS root/boot mirror. 2 x 500GB SATA disks in ZFS filesystem (this is where VBox is installed.) 2 x Intel NIC using igb driver. Solaris 10 U7 hardware config: 2 x Quad Core Intel Xeon X5570 processors (8 real cores + HyperThreading = 16 virtual cores.) 36GB ram. 2 x 73GB SAS drives in ZFS root/boot mirror. 2 x 250GB SATA drives in ZFS filesystem (this is where VBox is installed). 1 x Intel NIC using e1000g driver. Solaris 10 U5 using kernel 138889-03. Solaris 10 U7 using kernel 139556-08. My Testing: The following tests/situations describe the problem:
Conclusion: So I have seen that: a) Problem exists equally and seemingly identically on both Solaris 10 U5 and Solaris 10 U7. b) Problem occurs both when VBox is started when zones are already running, and if zones are booted after VBox is running. c) The exact number of running zones required is not fixed, it has been between 19 and 30 in my tests. d) I cannot say 100% if it is actually the process of booting/running a zone that causes the problem, or whether having zones booted causes some other activity that causes the problem. But there is a direct, replicatable connection between zones booted and the host crashing. |
|||
| #14008 | invalid | AHCI Port Reset After 1500 Hours Without Any Warnings | ||
| Description |
Dear VirtualBox community. Our guest suddenly stop working properly after 1500 hours . First we cannot ssh into it although it is still responsive to ping request. After restart we found that guest files and /var/log/messages for the last 5 hours did not written to disk. VBox.log shows that an AHCI port reset occured 5 hours beforehand. By accident our system administrator restart the host instead of the guest, that is why there are no other information in VBox.log.1 after port reset. Unlike bug #9975 this reset did not precede by any warnings nor errors. We make a guess that this is an hard reset and from what we learn from AHCI specification, hard reset is triggered by software, which in this case is linux driver. What we don't know is why the driver reset the port. Is this because something in VD/VDI or AHCI emulation ? Please help us. Another information the host disk is configured as raid-5. Both Host and Guest are linux kernel 3.0.7 Thank you very much. regards, tjiptomangun |
|||
| #2504 | fixed | Networking in Windows guest fails after upgrade from 2.0.2 to 2.0.4 => Check local DNS server | ||
| Description |
All Windows guests now report local connectivity *only* after upgrading. This is true for both Windows Vista and Windows XP guests running on 64-bit Debian: Linux deltani 2.6.26-1-amd64 #1 SMP Thu Oct 9 14:16:53 UTC 2008 x86_64 GNU/Linux No configuration changes were made to the guests before this failure. The only thing that seems to have changed is the 2.0.4 upgrade a few days ago. Releasing and renewing the IP address inside the guest makes no different, nor does running "sudo /etc/init.d/vboxnet restart" or restarting the VirtualBox GUI. In short, all guests are currently unusable because they lack connectivity. I'm attaching some logs, bot from 2.0.2 and 2.0.4 for comparison. |
|||

