Custom Query (16363 matches)
Results (2272 - 2274 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4131 | fixed | 64-bit guest crashes if Nested Paging Enabled (amd-v: PGMPOOLKIND_FREE guru) | ||
| Description |
Any 64-bit guest I've tested has entered guru meditation on startup if the Nested Paging option is enabled. Host OS is Debian "Lenny" x86, kernel 2.6.29.4 with PAE / Nested Paging enabled. VirtualBox is official build from VirtualBox repos, 2.2.4 r47978. Note that if I disable nested paging (but of course keep PAE), some 64-bit guests will work, e.g. Lenny-amd64 netinst (albeit slowly). Others, e.g. CentOS 5.3 amd64 netinst, fail outright with a guru meditation. See attached crash logs and system inventory for more info. All the best, -Chris |
|||
| #4132 | fixed | Upgrade must fail if VMs running | ||
| Description |
There was a guest running before upgrade from VB 2.2.2 -> 2.2.4 on Debian Lenny AMD64 (both host and guest). The host was started using VBoxHeadless --comment www --startvm ac682512-b596-4eff-9c07-a499a095e81a & After the upgrade the running host is not shown in VBoxManage list runningvms but the process is still running and guest is accessible. Also note "Cannot unload module vboxnetflt failed!". There isn't anything in manual related to upgrades. I probably should save my guests before VB upgrade, but I tried not to. Please fix this or document how to do upgrades in the manual. $ VBoxManage list runningvms
VirtualBox Command Line Management Interface Version 2.2.2
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
"www" {ac682512-b596-4eff-9c07-a499a095e81a}
$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
virtualbox-2.2
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 39.1MB of archives.
After this operation, 32.8kB of additional disk space will be used.
Do you want to continue [Y/n]?
Get:1 http://download.virtualbox.org lenny/non-free virtualbox-2.2 2.2.4-47978_Debian_lenny [39.1MB]
Fetched 39.1MB in 8s (4522kB/s)
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 59669 files and directories currently installed.)
Preparing to replace virtualbox-2.2 2.2.2-46594_Debian_lenny (using .../virtualbox-2.2_2.2.4-47978%5fDebian%5flenny_amd64.deb) ...
Stopping VirtualBox kernel module:
Cannot unload module vboxnetflt failed!
Shutting down VirtualBox host networking:done..
Unpacking replacement virtualbox-2.2 ...
Setting up virtualbox-2.2 (2.2.4-47978_Debian_lenny) ...
Installing new version of config file /etc/init.d/vboxdrv ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
Stopping VirtualBox kernel module:
Cannot unload module vboxnetflt failed!
Starting VirtualBox kernel module:done..
ctenar@atlas:~$ VBoxManage list runningvms
VirtualBox Command Line Management Interface Version 2.2.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
$ sudo netstat -tulpn | grep VBoxHeadless
tcp 0 0 0.0.0.0:3389 0.0.0.0:* LISTEN 6314/VBoxHeadless
|
|||
| #4133 | fixed | Internal networking not working | ||
| Description |
I created an internal network called "intnet" in a previous version of VirtualBox. It does not work any more in VirtualBox OSE 2.2.4. Cannot connect to the other machine and pings fail. Both guests are Linux. Each has 2 network cards; all 4 are the same type. On one of the guests, the internal networking is attached to the first network card; on the other, it's attached to the second. The other network cards are NAT. The NAT network cards are both configured to do DNS masquerading, which seems to work (I just changed this prior to the upgrade). |
|||

