Custom Query (16363 matches)
Results (1615 - 1617 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8899 | obsolete | Repeated login to iscsi disk | ||
| Description |
Hardware: Silicon Mechanics Rackform iServ R109 with 16GB of RAM, 40GB SATA SSD Silicon Mechanics Storform iS703 Software: Physical machine is running Linux version 2.6.32-5-686-bigmem (Debian 2.6.32-31) Virtualbox 4.0.6 Open-E DSS Version 6.0up55.8102.5087 64bit Installed the open-iscsi and iscsitarget pacakges. Able to mount iscsi targets as /dev/sdbX on the physical machine. Setup a VM running Windows XP, installed the iscsi drivers, and mounted an iscsi target as the D: drive. Attached an iscsi target to VM Debian-test using this command: VBoxManage storageattach Debian-Test --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium iscsi --server 192.168.11.1 --target debian-test In the VM settings I can see the disk details including the size of 100GB. Seems to be talking fine to the SAN. VM has an ISO of Debian in the CD slot, and the iscsi target is an empty disk that I will be installing Debian onto, but I don't get that far. When I start the VM, it just hangs waiting for the iscsi target. Checking the VBox.log this line is repeated: iSCSI: login to target debian-test successful I also ran wireshark and captured packets between the SAN and the VM. A constant reset of the iscsi connection appears to be happening. Have attached the VBox.log and wireshark packet capture. |
|||
| #8905 | obsolete | VirtualBox GUI causes system slowness on linux hosts. | ||
| Description |
Hey! I don't have any log output that gives any evidence of the problem, but: i have a dual-xeon system (E5530, so 2 physical cpus, 8 physical cores, 16 virtual cores) with 12GN RAM. if i have one vm (6 cores, 1.5GB RAM) running using the virtualbox SDL gui, and start compiling something on the host (16 jobs in the background), the desktop starts slowing down vastly (i.e. desktop effects hang, scrolling in terminals reduces to 1-update-per-second, applications react with a second delay, etc.). if i start the vm headless, and do the very same, the desktop keeps reacting as usual, no application slows down, etc. btw. i have compiz running if that is of any relevance... i didn't try without though... should i? and, as a side note: when the X server crashes (ever heard of the mieq problem with virtualbox), and a vm has been started using the sdl gui, shouldn't it be possible to save the vm state from the console? it currently isn't, as VBoxManage seems to wait for some reaction of VirtualBox, which it doesn't get, as that one in turn hangs somewhere in an X call... regards, markus |
|||
| #8906 | obsolete | Virtual Machine inaccessible after upgrading to latest VBox and guest additions | ||
| Description |
I run several versions of Windows in Virtual Box here. After the new release installed I first booted W7 and updated the guest additions. I next booted XP and updated the guest additions. After shutting XP down that VM now shows as "Inaccessible", but I can read the machine profile fine using MC. |
|||

