[KPUG] Building a Virtual Machine

[Griffin Kelton]

Trevor,

I was already configuring my network settings using "Bridget network" and
manually adjusting /etc/network/interfaces. Oddly enough, I did the exact
same thing today on a fresh install and it worked without a hitch. Today
I'm in a coffee shop, yesterday it was at my house. Could it be something
my with NAT?

Griffin Kelton
(919)306.1135
www.griffinkelton.com

Please consider the environment before printing this email.


On Tue, Sep 11, 2012 at 11:27 AM, Trevor Hall <trevor at goldenguru.com> wrote:

>
> Hi Griffin,
>
> That's likely due to a misconfiguration of your ethernet adapter(s). I've
> always used "Bridged networking" to bridge the network between the VM and
> the host box. And in the past, I've had to manually adjust the
> /etc/network/interfaces file to have my adapter(s) pull DHCP from my host
> computer.
>
> Here is some information on how to network in VB:
> http://www.virtualbox.org/manual/ch06.html
>
> Learning how to update the interfaces file is relatively straight forward
> as well, and easily googleable (Pro Tip: Ubuntu is a derivative of Debian,
> but doesn't always mean all solutions will work on both systems).
>
>  - Trevor
>
> On Sep 11, 2012, at 7:47 AM, Griffin Kelton wrote:
>
> Gryphon (or anyone else out there),
>
> Is there any reason why using Debian 64-bit within Virtual Box, after
> making changes to /etc/apt/source.list, every call to the server
> ftp.us.debian.org or sources.debian.org returns the error: Could not
> resolve [domain name]. I asked Debian to ping both domain names and
> received the error: unknown host. I tripled check to make sure sources.list
> was updated correctly. Additionally, both of the aforementioned URLs return
> a result on my machine within a browser and *Debian 32-bit does not have
> this issue*. Simply curious as to the cause.
>
> Thanks,
>
> Griffin Kelton
> (919)306.1135
> www.griffinkelton.com
>
> Please consider the environment before printing this email.
>
>
> On Tue, Sep 11, 2012 at 10:37 AM, Gryphon Shafer <
> gryphon at gryphonshafer.com> wrote:
>
>>  Greetings all,
>>
>> Good tip, Griffin. I expect that will work, but if it doesn't, try using
>> a 32-bit version of Debian. Start with the amd64 though since you'll
>> benefit from the 64-bit kernel.
>>
>> Everybody: If you don't already know the answer, this might be a good
>> opportunity to Google "difference between 32 bit and 64 bit" and scan a few
>> of the results.
>>
>> Gryphon (the other Griffin)
>>
>>
>>  On 9/11/2012 7:32 AM, Griffin Kelton wrote:
>>
>> Mason,
>>
>> The debian FAQ recommends running the amd64 iso on all 64 bit
>> architecture, whether you have an AMD or Intel chipset. Try downloading
>> that iso.
>>
>> *If your PC has a 64-bit AMD or Intel processor, you will most likely
>> need the amd64 <http://www.debian.org/ports/amd64/> images (though i386 is
>> also fine), the ia64 <http://www.debian.org/ports/ia64/> images will not work.
>> (Source: http://www.debian.org/CD/faq/#which-cd)*
>>
>> Let me know if this resolves your issue.
>> On Sep 11, 2012 2:02 AM, "Mason Merker" <foolster41 at gmail.com> wrote:
>>
>>> Nope, using Windows 7 (64 bit).
>>> I tried installing Debian, but it gives me the error "“This kernel
>>> requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot –
>>> please use a kernel appropriate for your CPU”. One site I found about this
>>> said the solution is to change a BIOs setting, but I'm concerned
>>> about changing BIOs settings. Is this really the solution? Did I get the
>>> wrong Debian iso?
>>> -Thanks.
>>>
>>> _______________________________________________
>>> KPUG-PM mailing list
>>> KPUG-PM at pm.org
>>> http://mail.pm.org/mailman/listinfo/kpug-pm
>>>
>>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/kpug-pm/attachments/20120911/4808f87e/attachment.html>