This PC has 8gb of ram total. I opened Task Manager and saw that it was using 16gb ram for Virtualbox. I'm not really sure how that's possible. I decreased the RAM available to the VM down to 400MB, and now Task Manager says that It's using < 100MB RAM, but it's still hanging onOn Sun, Apr 24, 2016 at 10:50 AM, Michael Sullivan
msulli1355@gmail.com [LINUX_Newbies] <LINUX_Newbies@yahoogroups.com>
wrote:
> On 04/24/2016 04:55 AM, Scott scottro@nyc.rr.com [LINUX_Newbies] wrote:
>> On Sat, Apr 23, 2016 at 09:58:01PM -0500, Michael Sullivazn
>> msulli1355@gmail.com [LINUX_Newbies] wrote:
>> > I finished my new VB install. I ran grub2-install /dev/sda. I ran
>> > grub2-mkconfig -o /boot/grub/grub.cnf. I rebooted the virtualbox. It
>> > gave me a grub prompt. Not the grub screen I was expecting. A promt
>> > that says grub> How do I find resources to tell me what to do here? I
>> > really really REALLY don't want to have to boot off that livecd iso
>> > again. Please help me!
>>
>> I haven't been following this closely, but if it's Fedora or CentOS, it
>> would be grub2-mkconfig -o /boot/grub2/grub.cfg. So, if you haven't typoed
>> what you put here, that might explain it.
>>
> The grub problem is resolved. Now it's giving me a problem I don't
> think you guys can help with. It's some kind of memory problem that
> causes the booting process to hang at the end of the numbers that I
> described the other day. I'm hoping that if I completely close
> VirtualBox and reload it, it will load it at a different memory address.
> I tried booting it and choosing Advanced Grub configuration utility
> (or something like that) and it reported that it couldn't read memory
> address <some long hex number>. I might have to keep booting with the
> liveCD image after all.
Are you sure you're not overcommitting (e.g. you have 2GB free RAM and
try to launch a VM that is defined with 4GB RAM). In theory, that
should be OK, so this is just curiosity on my part. I haven't had
time to follow posts to this group closely because of work.
[ 12.856041] Switched to clocksource tsc
After I opened the Task Manager, a new line is added:
[ 27.337770] atkbd sereo0: Spurious NAK on isa0060/serio0. Some program might be trying to access hardware directly.
How do I get rid of that clocksource thing?
I've never had a problem like that appear in a VM personally, but I
also don't overcommit the resources on them either, that tends to
cause issues, IME.
Posted by: Michael Sullivazn <msulli1355@gmail.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (5) |
No comments:
Post a Comment