Siduction Forum
Siduction Forum => Software - Support => Topic started by: Lanzi on 2014/10/04, 14:17:27
-
Virtualbox starts normaly, and if I start one of my Windows' it starts for a moment and I can see the flying Balls (or whatever this :-) ) from Windows7, and then the entire window is gone!
This behavior is new since last DU yesterday
Ich kann Virtualbox normal starten, allerdings bricht der Windowsstart irgendwann dann ab. Ich sehe noch das Windowslogo mit den Bällen und plötzlich ist das ganze Fenster weg.
Hat das noch jemand?
-
Und was spricht das Vbox-Log?
Mal abgeshen davon, solltest Du uns auch Infos zu Deinem Host-System nicht verschweigen!
Ein inxi -v3 wäre das Mindeste, was man erwarten kann.
-
Running windows 10, siduction cinnamon, siduction gnome, my version of e17 with no problems, last du was 2 minutes ago
-
Thanks for the quick answer. Danke für die schnelle Antwort.
Here are the requested infos. Hier die Infos.
System: Host: Siduction Kernel: 3.16-3.towo-siduction-amd64 x86_64 (64 bit gcc: 4.9.1)
Desktop: KDE 4.14.1 (Qt 4.8.6) Distro: siduction 12.2.0 Riders on the Storm - kde - (201212092131)
Machine: Mobo: ASUSTeK model: P8Z77-V PRO v: Rev 1.xx Bios: American Megatrends v: 1708 date: 11/09/2012
CPU: Quad core Intel Core i7-3770 (-HT-MCP-) cache: 8192 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 27289
clock speeds: max: 3900 MHz 1: 2045 MHz 2: 1945 MHz 3: 2188 MHz 4: 3477 MHz 5: 3673 MHz 6: 1772 MHz
7: 3053 MHz 8: 3783 MHz
Graphics: Card: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller bus-ID: 00:02.0
Display Server: X.Org 1.16.1 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1920x1200@59.95hz, 1920x1200@59.95hz
GLX Renderer: Mesa DRI Intel Ivybridge Desktop GLX Version: 3.0 Mesa 10.2.6 Direct Rendering: Yes
Network: Card: Intel 82579V Gigabit Network Connection driver: e1000e v: 2.3.2-k port: f080 bus-ID: 00:19.0
IF: eth0 state: up speed: 100 Mbps duplex: full mac: c8:60:00:dd:81:9c
Drives: HDD Total Size: 18253.6GB (49.7% used) ID-1: model: WDC_WD40EFRX
ID-6: model: Samsung_SSD_840
Info: Processes: 297 Uptime: 2 days Memory: 5278.0/15742.4MB Init: systemd runlevel: 5 Gcc sys: 4.9.1
Client: Shell (bash 4.3.271) inxi: 2.2.14
-
Analogue to this Problem: http://forum.siduction.org/index.php?topic=4992.50;topicseen
I reinstalled new versions of guest addiotns and the extensionpack.
After the second (!) windowsboot it was working!
Thanks to anybody helping