All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Wong <johnw@wonghome.net>
To: Amit Shah <amit.shah@redhat.com>, KVM list <kvm@vger.kernel.org>
Subject: Re: Qemu 0.10.50 CAN NOT get ip from dhcp server
Date: Thu, 16 Jul 2009 20:52:36 +0800	[thread overview]
Message-ID: <4A5F2294.7050204@wonghome.net> (raw)
In-Reply-To: <20090716120216.GA22643@amit-x200.redhat.com>

Amit Shah 提到:
> On (Thu) Jul 16 2009 [19:44:42], John Wong wrote:
>   
>> Amit Shah 提到:
>>     
>>> On (Wed) Jul 15 2009 [16:54:15], John Wong wrote:
>>>   
>>>       
>>>> Yes, kvm-88 fixed this problem.
>>>>
>>>> I also notice another problem, when i use kvm-88(qemu-system-x86_64 
>>>> with  kvm-kmod-2.6.30.1-rc2.tar.gz) installing 64bit OS (window7 & 
>>>> debian &  netbsd),
>>>> the install CD show the error message, say this system is 32bit not   
>>>> 64bit and can not continue to install.
>>>> I did try use -cpu qemu64 or -cpu core2duo, but no help.
>>>>     
>>>>         
>>> Did you run 'make install' after compiling kvm-88?
>>>
>>> 		Amit
>>>   
>>>       
>> Yes, i did it.
>> ./configure --prefix=/opt/kvm-88/ --audio-drv-list="alsa oss"
>> make clean
>> make
>> sudo make install
>>
>> Please help, thank you.
>>     
>
> Any messages in the host kernel's logs? Also can you try running a
> 32-bit VM and report what /proc/cpuinfo shows? I'm assuming you're
> running on a 64 bit host. Can you confirm that?
>
>
> 		Amit
>   
No, i can not found any message is relate kvm.

Yes, i installed Debian/32-bit VM, below is "cat /proc/cpuinfo".

Thank your help.
--------------------------------------------------------------------
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 2
model name    : QEMU Virtual CPU version 0.10.50
stepping    : 3
cpu MHz        : 2999.638
cache size    : 2048 KB
fdiv_bug    : no
hlt_bug        : no
f00f_bug    : no
coma_bug    : no
fpu        : yes
fpu_exception    : yes
cpuid level    : 2
wp        : yes
flags        : fpu de pse tsc msr pae mce cx8 apic mtrr pge mca cmov 
pse36 clflush mmx fxsr sse sse2 pni hypervisor
bogomips    : 5999.27
clflush size    : 64
power management:

processor    : 1
vendor_id    : GenuineIntel
cpu family    : 6
model        : 2
model name    : QEMU Virtual CPU version 0.10.50
stepping    : 3
cpu MHz        : 2999.638
cache size    : 2048 KB
fdiv_bug    : no
hlt_bug        : no
f00f_bug    : no
coma_bug    : no
fpu        : yes
fpu_exception    : yes
cpuid level    : 2
wp        : yes
flags        : fpu de pse tsc msr pae mce cx8 apic mtrr pge mca cmov 
pse36 clflush mmx fxsr sse sse2 pni hypervisor
bogomips    : 5999.27
clflush size    : 64
power management:
--------------------------------------------------------------------------------------------

  reply	other threads:[~2009-07-16 12:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06  2:13 Qemu 0.10.50 CAN NOT get ip from dhcp server John Wong
2009-07-06  4:23 ` Sterling Windmill
2009-07-15  8:00 ` Amit Shah
2009-07-15  8:54   ` John Wong
2009-07-16 11:36     ` Amit Shah
2009-07-16 11:44       ` John Wong
2009-07-16 12:02         ` Amit Shah
2009-07-16 12:52           ` John Wong [this message]
2009-07-16 13:24             ` Amit Shah
2009-07-16 21:18               ` John Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A5F2294.7050204@wonghome.net \
    --to=johnw@wonghome.net \
    --cc=amit.shah@redhat.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.