miles kuo | 1 Jul 2010 04:21
Picon

Re: How to add two NICs in createing VM?

2010/6/30 Michael Goldish <mgoldish <at> redhat.com>:
> On 06/30/2010 05:19 PM, miles kuo wrote:
>> 2010/6/30 Michael Goldish <mgoldish <at> redhat.com>:
>>> On 06/30/2010 01:35 PM, miles kuo wrote:
>>>> I wanted to add  two NICs to the VM when installed the VM.  But I only
>>>> could add one NIC to it.
>>>>
>>>>     - qemu_kvm_windows_s1:
>>>>         qemu_binary = /usr/bin/qemu-kvm
>>>>         only qcow2
>>>>         only rtl8139 e1000
>>>>         only virtio_blk
>>>>         only smp2
>>>>         only no_pci_assignable
>>>>         only smallpages
>>>>         only Win2008.r2
>>>>         only unattended_install.cdrom boot shutdown
>>>>
>>>> /usr/bin/qemu-kvm -name 'vm1' -monitor
>>>> unix:'/tmp/monitor-humanmonitor1-20100628-140809-2dXG',server,nowait
>>>> -serial unix:'/tmp/serial-20100628-140809-2dXG',server,nowait -drive
>>>> file='/tmp/kvm_autotest_root/images/win2008-r2.qcow2',if=virtio,boot=on
>>>> -net nic,vlan=0,netdev=idb2uffG,model=rtl8139,macaddr='52:54:00:12:34:56'
>>>> -netdev user,id=idb2uffG -m 1024 -smp 2 -drive
>>>> file='/tmp/kvm_autotest_root/isos/windows/en_windows_server_2008_r2_standard_enterprise_datacenter_and_web_x64_dvd_x15-59754.iso',index=2,media=cdrom
>>>> -drive file='/tmp/kvm_autotest_root/isos/windows/winutils.iso',index=3,media=cdrom
>>>> -fda '/opt/autotest/autotest/client/tests/kvm/images/win2008-r2-64/floppy.img'
>>>> -redir tcp:5000::22 -redir tcp:5001::12323 -vnc :0  -boot d
>>>>
>>>> The qemu command showed that only rtl8139 added to the VM.
(Continue reading)

miles kuo | 1 Jul 2010 04:50
Picon

Re: How to add two NICs in createing VM?

2010/7/1 miles kuo <miles.kuo <at> gmail.com>:
> 2010/6/30 Michael Goldish <mgoldish <at> redhat.com>:
>> On 06/30/2010 05:19 PM, miles kuo wrote:
>>> 2010/6/30 Michael Goldish <mgoldish <at> redhat.com>:
>>>> On 06/30/2010 01:35 PM, miles kuo wrote:
>>>>> I wanted to add  two NICs to the VM when installed the VM.  But I only
>>>>> could add one NIC to it.
>>>>>
>>>>>     - qemu_kvm_windows_s1:
>>>>>         qemu_binary = /usr/bin/qemu-kvm
>>>>>         only qcow2
>>>>>         only rtl8139 e1000
>>>>>         only virtio_blk
>>>>>         only smp2
>>>>>         only no_pci_assignable
>>>>>         only smallpages
>>>>>         only Win2008.r2
>>>>>         only unattended_install.cdrom boot shutdown
>>>>>
>>>>> /usr/bin/qemu-kvm -name 'vm1' -monitor
>>>>> unix:'/tmp/monitor-humanmonitor1-20100628-140809-2dXG',server,nowait
>>>>> -serial unix:'/tmp/serial-20100628-140809-2dXG',server,nowait -drive
>>>>> file='/tmp/kvm_autotest_root/images/win2008-r2.qcow2',if=virtio,boot=on
>>>>> -net nic,vlan=0,netdev=idb2uffG,model=rtl8139,macaddr='52:54:00:12:34:56'
>>>>> -netdev user,id=idb2uffG -m 1024 -smp 2 -drive
>>>>> file='/tmp/kvm_autotest_root/isos/windows/en_windows_server_2008_r2_standard_enterprise_datacenter_and_web_x64_dvd_x15-59754.iso',index=2,media=cdrom
>>>>> -drive file='/tmp/kvm_autotest_root/isos/windows/winutils.iso',index=3,media=cdrom
>>>>> -fda '/opt/autotest/autotest/client/tests/kvm/images/win2008-r2-64/floppy.img'
>>>>> -redir tcp:5000::22 -redir tcp:5001::12323 -vnc :0  -boot d
>>>>>
(Continue reading)

Amos Kong | 1 Jul 2010 05:29
Picon
Favicon
Gravatar

Re: [PATCH] KVM-test: Rename reboot_timeout to login_timeout

On Thu, Jun 24, 2010 at 04:12:14PM +0800, Amos Kong wrote:
> This commit(a20956ef6315480089ee7a6877071339d634109a) make login timeout can be
> configuration. This patch just rename reboot_timeout/boot_timeout to
> login_timeout.

Hi Lucas,

Could you give some comments with this patch ? thanks.

Amos

> Signed-off-by: Amos Kong <akong <at> redhat.com>
> ---
>  0 files changed, 0 insertions(+), 0 deletions(-)
> 
> diff --git a/client/tests/kvm/tests/boot.py b/client/tests/kvm/tests/boot.py
> index 9b3f392..8cc0218 100644
> --- a/client/tests/kvm/tests/boot.py
> +++ b/client/tests/kvm/tests/boot.py
>  <at>  <at>  -16,9 +16,8  <at>  <at>  def run_boot(test, params, env):
>       <at> param env: Dictionary with test environment.
>      """
>      vm = kvm_test_utils.get_living_vm(env, params.get("main_vm"))
> -    session = kvm_test_utils.wait_for_login(vm, 0,
> -                                         float(params.get("boot_timeout", 240)),
> -                                         0, 2)
> +    timeout = float(params.get("login_timeout", 240))
> +    session = kvm_test_utils.wait_for_login(vm, 0, timeout, 0, 2)
>  
>      try:
(Continue reading)

Michael Goldish | 1 Jul 2010 11:37
Picon
Favicon

Re: How to add two NICs in createing VM?

On 07/01/2010 05:21 AM, miles kuo wrote:
> 2010/6/30 Michael Goldish <mgoldish <at> redhat.com>:
>> On 06/30/2010 05:19 PM, miles kuo wrote:
>>> 2010/6/30 Michael Goldish <mgoldish <at> redhat.com>:
>>>> On 06/30/2010 01:35 PM, miles kuo wrote:
>>>>> I wanted to add  two NICs to the VM when installed the VM.  But I only
>>>>> could add one NIC to it.
>>>>>
>>>>>     - qemu_kvm_windows_s1:
>>>>>         qemu_binary = /usr/bin/qemu-kvm
>>>>>         only qcow2
>>>>>         only rtl8139 e1000
>>>>>         only virtio_blk
>>>>>         only smp2
>>>>>         only no_pci_assignable
>>>>>         only smallpages
>>>>>         only Win2008.r2
>>>>>         only unattended_install.cdrom boot shutdown
>>>>>
>>>>> /usr/bin/qemu-kvm -name 'vm1' -monitor
>>>>> unix:'/tmp/monitor-humanmonitor1-20100628-140809-2dXG',server,nowait
>>>>> -serial unix:'/tmp/serial-20100628-140809-2dXG',server,nowait -drive
>>>>> file='/tmp/kvm_autotest_root/images/win2008-r2.qcow2',if=virtio,boot=on
>>>>> -net nic,vlan=0,netdev=idb2uffG,model=rtl8139,macaddr='52:54:00:12:34:56'
>>>>> -netdev user,id=idb2uffG -m 1024 -smp 2 -drive
>>>>> file='/tmp/kvm_autotest_root/isos/windows/en_windows_server_2008_r2_standard_enterprise_datacenter_and_web_x64_dvd_x15-59754.iso',index=2,media=cdrom
>>>>> -drive file='/tmp/kvm_autotest_root/isos/windows/winutils.iso',index=3,media=cdrom
>>>>> -fda '/opt/autotest/autotest/client/tests/kvm/images/win2008-r2-64/floppy.img'
>>>>> -redir tcp:5000::22 -redir tcp:5001::12323 -vnc :0  -boot d
>>>>>
(Continue reading)

akong | 1 Jul 2010 15:00
Picon
Favicon
Gravatar

[PATCH] KVM test: Release memory after testing with hugepages

From: Amos Kong <akong <at> redhat.com>

After testing with hugepages, memory is not released, it will cause the memory
lack in host. This will make the host running extremely slow and will influence
other tests to be executed.

Signed-off-by: Yiqiao Pu <ypu <at> redhat.com>
Signed-off-by: Amos Kong <akong <at> redhat.com>
---
 client/tests/kvm/tests_base.cfg.sample |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/client/tests/kvm/tests_base.cfg.sample b/client/tests/kvm/tests_base.cfg.sample
index 7f59bfc..1ed5237 100644
--- a/client/tests/kvm/tests_base.cfg.sample
+++ b/client/tests/kvm/tests_base.cfg.sample
 <at>  <at>  -1452,6 +1452,7  <at>  <at>  variants:
     -  <at> smallpages:
     - hugepages:
         pre_command += " scripts/hugepage.py /mnt/kvm_hugepage;"
+        post_command += " echo 0 > /proc/sys/vm/nr_hugepages; umount /mnt/kvm_hugepage;"
         extra_params += " -mem-path /mnt/kvm_hugepage"

 
--

-- 
1.7.0.4
Lucas Meneghel Rodrigues | 1 Jul 2010 15:10
Picon
Favicon
Gravatar

Re: [PATCH] KVM test: Release memory after testing with hugepages

On Thu, 2010-07-01 at 21:00 +0800, akong <at> redhat.com wrote:
> After testing with hugepages, memory is not released, it will cause
> the memory
> lack in host. This will make the host running extremely slow and will
> influence
> other tests to be executed.

Applied, thanks!

> Signed-off-by: Yiqiao Pu <ypu <at> redhat.com>
> Signed-off-by: Amos Kong <akong <at> redhat.com> 
Michael Goldish | 1 Jul 2010 15:08
Picon
Favicon

Re: [PATCH] KVM test: Release memory after testing with hugepages

On 07/01/2010 04:00 PM, akong <at> redhat.com wrote:
> From: Amos Kong <akong <at> redhat.com>
> 
> After testing with hugepages, memory is not released, it will cause the memory
> lack in host. This will make the host running extremely slow and will influence
> other tests to be executed.
> 
> Signed-off-by: Yiqiao Pu <ypu <at> redhat.com>
> Signed-off-by: Amos Kong <akong <at> redhat.com>
> ---
>  client/tests/kvm/tests_base.cfg.sample |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/client/tests/kvm/tests_base.cfg.sample b/client/tests/kvm/tests_base.cfg.sample
> index 7f59bfc..1ed5237 100644
> --- a/client/tests/kvm/tests_base.cfg.sample
> +++ b/client/tests/kvm/tests_base.cfg.sample
>  <at>  <at>  -1452,6 +1452,7  <at>  <at>  variants:
>      -  <at> smallpages:
>      - hugepages:
>          pre_command += " scripts/hugepage.py /mnt/kvm_hugepage;"
> +        post_command += " echo 0 > /proc/sys/vm/nr_hugepages; umount /mnt/kvm_hugepage;"
>          extra_params += " -mem-path /mnt/kvm_hugepage"
>  
>  

post_command is executed after every test. This means that at the end of
the boot test for example, while the VM is still alive, the command will
be executed.  Won't that bother the VM?
(Continue reading)

Lucas Meneghel Rodrigues | 1 Jul 2010 15:30
Picon
Favicon
Gravatar

Re: [PATCH] KVM test: Release memory after testing with hugepages

On Thu, 2010-07-01 at 16:08 +0300, Michael Goldish wrote:
> On 07/01/2010 04:00 PM, akong <at> redhat.com wrote:
> > From: Amos Kong <akong <at> redhat.com>
> > 
> > After testing with hugepages, memory is not released, it will cause the memory
> > lack in host. This will make the host running extremely slow and will influence
> > other tests to be executed.
> > 
> > Signed-off-by: Yiqiao Pu <ypu <at> redhat.com>
> > Signed-off-by: Amos Kong <akong <at> redhat.com>
> > ---
> >  client/tests/kvm/tests_base.cfg.sample |    1 +
> >  1 files changed, 1 insertions(+), 0 deletions(-)
> > 
> > diff --git a/client/tests/kvm/tests_base.cfg.sample b/client/tests/kvm/tests_base.cfg.sample
> > index 7f59bfc..1ed5237 100644
> > --- a/client/tests/kvm/tests_base.cfg.sample
> > +++ b/client/tests/kvm/tests_base.cfg.sample
> >  <at>  <at>  -1452,6 +1452,7  <at>  <at>  variants:
> >      -  <at> smallpages:
> >      - hugepages:
> >          pre_command += " scripts/hugepage.py /mnt/kvm_hugepage;"
> > +        post_command += " echo 0 > /proc/sys/vm/nr_hugepages; umount /mnt/kvm_hugepage;"
> >          extra_params += " -mem-path /mnt/kvm_hugepage"
> >  
> >  
> 
> post_command is executed after every test. This means that at the end of
> the boot test for example, while the VM is still alive, the command will
> be executed.  Won't that bother the VM?
(Continue reading)

Michael Goldish | 1 Jul 2010 15:51
Picon
Favicon

Re: [PATCH] KVM test: Release memory after testing with hugepages

On 07/01/2010 04:30 PM, Lucas Meneghel Rodrigues wrote:
> On Thu, 2010-07-01 at 16:08 +0300, Michael Goldish wrote:
>> On 07/01/2010 04:00 PM, akong <at> redhat.com wrote:
>>> From: Amos Kong <akong <at> redhat.com>
>>>
>>> After testing with hugepages, memory is not released, it will cause the memory
>>> lack in host. This will make the host running extremely slow and will influence
>>> other tests to be executed.
>>>
>>> Signed-off-by: Yiqiao Pu <ypu <at> redhat.com>
>>> Signed-off-by: Amos Kong <akong <at> redhat.com>
>>> ---
>>>  client/tests/kvm/tests_base.cfg.sample |    1 +
>>>  1 files changed, 1 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/client/tests/kvm/tests_base.cfg.sample b/client/tests/kvm/tests_base.cfg.sample
>>> index 7f59bfc..1ed5237 100644
>>> --- a/client/tests/kvm/tests_base.cfg.sample
>>> +++ b/client/tests/kvm/tests_base.cfg.sample
>>>  <at>  <at>  -1452,6 +1452,7  <at>  <at>  variants:
>>>      -  <at> smallpages:
>>>      - hugepages:
>>>          pre_command += " scripts/hugepage.py /mnt/kvm_hugepage;"
>>> +        post_command += " echo 0 > /proc/sys/vm/nr_hugepages; umount /mnt/kvm_hugepage;"
>>>          extra_params += " -mem-path /mnt/kvm_hugepage"
>>>  
>>>  
>>
>> post_command is executed after every test. This means that at the end of
>> the boot test for example, while the VM is still alive, the command will
(Continue reading)

Lucas Meneghel Rodrigues | 1 Jul 2010 18:05
Picon
Favicon
Gravatar

Re: [PATCH] KVM test: Disable HPET on windows timedrift tests

On Thu, 2010-07-01 at 17:42 +0300, Avi Kivity wrote:
> On 06/30/2010 06:39 PM, Lucas Meneghel Rodrigues wrote:
> > By default, HPET is enabled on qemu and no time drift
> > mitigation is being made for it. So, add -no-hpet
> > if qemu supports it, during windows timedrift tests.
> >
> >    
> 
> Hm, you're compensating for a qemu bug by not testing it.
> 
> Can we have an XFAIL for this test instead?

Certainly we can. In actuality, that's what's being done on our internal
autotest server - this particular test is linked to the upstream bug
https://bugs.launchpad.net/qemu/+bug/599958

We've discussed about this issue this morning, it boils down to the way
people are more comfortable with handling this issue. My first thought
was to disable HPET until someone come up with a time drift mitigation
strategy for it.

But your approach makes more sense, unless someone has something else to
say about it, I'll drop the patch from autotest shortly.

Lucas

Gmane