You are not logged in.
My computer power off while I open virtualbox, it just like I click the restart button on the computer. Then the system restart from the beginning. I think not enough power cause this problem. While In ubuntu it is OK.
Here is my system info:
Linux zp 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 09:14:51 CEST 2012 x86_64 GNU/Linux
Is there any thing else I should provide?
Last edited by robotment (2012-09-12 04:57:55)
Offline
Logs (/var/log/everything.log). However, they may not be much use if your system reboots before syncing them to disk. Hardware information would also be helpful (use a tool like hwinfo or lshw).
Steven [ web : git ]
GPG: 327B 20CE 21EA 68CF A7748675 7C92 3221 5899 410C
Do not email: honeypot@stebalien.com
Offline
Here is my hardware info: https://gist.github.com/3689071
everything.log: https://gist.github.com/3689081
Offline
Does anyone know how to handle this problems? I have found that it only happens when I open virtualbox and start 'window xp'. Even if I got high load average with some heavily work, it was fine.
Offline
Everything.log has dbus errors related to bluez and networkmanager, but i don't see clues about the crash reboot.
How far do you get with starting windows xp ?
Does it matter if you do something in windows xp, or does the crash reboot also happen if you just start it and do nothing in it ?
Does virtualbox also do this with other VMs ?
In case you don' t have other VMs, does creating a fresh install of windows xp crash ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
I found it has connections with network. When I don't choose any network, it is fine. When I choose the 'NAT' network, it crash reboot after logging in 'xp'. I have already tried to install a new fresh, it is the same.
Offline
Ok, that narrows dows the cause a lot.
While the archwiki doesn't say much about virtualbox and networking, under troubleshooting there's a part that might help : failed_to_create_the_host-only_network_interface
check if the modules mentioned there are installed/active (lsmod !grep vbox ) .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
I haven't found vboxnetadp or vboxnetflt installed. Some thing badly happens. Even if i choose no network in virtualbox settins, it still reboot my arch linux.
I found this https://bbs.archlinux.org/viewtopic.php?id=137673.. I will try to install window-7 64bit tomorrow.
Offline
Problem solved. I tried to install window-7 64bit, it work fine until now. I think it is bug in virtualbox. Here is my advice: if your host is using 64-bit operation, so is the guest system in virtualbox.
Offline
No, problem is not solved (at least for me). I tried today run Windows 7 64-bit guest in my Archlinux x86_64 host. When I clicked "run" in VB then system do REBOOT (without my permission ). Host Archlinux is up to date (newest stable packages from stable official repositories). Is this a bug in the VirtualBox 4.1.22 ?
Last edited by amen (2012-09-13 10:16:25)
Offline