Date: Fri, 26 May 2017 14:00:53 +0000 From: bugzilla-noreply@freebsd.org To: vbox@FreeBSD.org Subject: [Bug 219556] emulators/virtualbox-ose: VBoxSVC consumes 100% CPU and does not exit Message-ID: <bug-219556-26505-EmXAt7Z8LB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219556-26505@https.bugs.freebsd.org/bugzilla/> References: <bug-219556-26505@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219556 --- Comment #2 from Martin Birgmeier <la5lbtyi@aon.at> --- After some experimentation, the problem turned out to have a quite different cause. On both hosts, the same emulated harddisk is available: on the AMD machine directly via a vmdk file pointing, on the Intel machine via iSCSI. However, the file holding the emulated harddisk was not available. On the AMD machine, this only caused VirtualBox to note that the machine cannot be started. On the Intel machine however, the file seems to get exported as a zero-sized disk; this in turn seems to trip up VBoxSVC. So there are two issues: One, VBoxSVC gets confused about the announced but not really existing iSCSI target, and second, the iSCSI daemon blindly announces to export a file (with zero size) which does not exist (and cannot be created, its path not being available). I think the bigger problem lies with the iSCSI subsystem announcing a target which does not exist. I'll try to reassing the issue to the base system. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219556-26505-EmXAt7Z8LB>