headers
Y. D. | 1 Nov 06:17
Picon

domu network interface number increases

Hi,
 
Every time my domU is created, the eth* number increases, from eth0 to eth70 now.
This is really awkward, and should not happen in theroy, nevertheless I don't know why.
Can anyone identify the problem here?
 
Thanks in advance,
 
Shawn
 
_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users
Permalink | Reply | 2 comments |
headers
Y. D. | 1 Nov 07:17
Picon

Re: Re:domU network not work

Hi,
 
Fixed. Turns out that the promiscuous mode in peth0 is the cause. Don't know why, but it was turned off.
 
Thanks,
 
Shawn
 
_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users
Permalink | Reply | 2 comments |
headers
James Harper | 1 Nov 10:46
Picon

RE: Performance of WinXP after xen tools installed isterrible

> Hi,
> 
> The performance of Windows XP is dreadful.  Absolutely dreadful.
> There are only two VMs on the machine, dom0 and domU.  The system
> supports the Windows XP HVM domain through the good offices of
> the underlying dual-core AMD cpu with AMD-V technology.
> 
> The system spends a huge amount of time running rundll32.exe.
> If I kill the executable, it speeds up a bit.  The performance
> problem has been there since the beginning, and I've scanned
> for viruses.  There are none to be found.
> 
> I've allocated 2GIG for the domain and 2 VCPUs.  Performance
> is so bad as to make the domain almost unusable for many
> tasks.  Deleting files, for some reason, takes forever.
> 
> Are there obvious things for which I can check or set?
> I'm using the latest Citrix distro and I've installed the
> xen-tools.iso tools.  The drivers running in the domain are
> Hypervisor-aware.
> 

Have you tried a complete reinstall of the DomU from scratch with no
extra drivers or anything?

Is it XP sp2? Prior to sp2 I have seen some pretty poor performance of
XP.

What does 'xm dmesg' say?

What are your underlying disks in dom0?

It would probably be useful to post your DomU config file to the list.

James
Permalink | Reply | 1 comment |
headers
Thomas | 1 Nov 12:02
Picon

Re: domu network interface number increases

Yeah I feel it is wrong too. My numbers are around 200 now, I hope
there isn't a wall or a bug when it reaches a special value.
Permalink | Reply | 0 comments |
headers
Itamar - IspBrasil | 1 Nov 12:56
Picon

Re: Performance of WinXP after xen tools installed isterrible

try with only one VCPU

On 11/1/2008 7:46 AM, James Harper wrote:
>> Hi,
>>
>> The performance of Windows XP is dreadful.  Absolutely dreadful.
>> There are only two VMs on the machine, dom0 and domU.  The system
>> supports the Windows XP HVM domain through the good offices of
>> the underlying dual-core AMD cpu with AMD-V technology.
>>
>> The system spends a huge amount of time running rundll32.exe.
>> If I kill the executable, it speeds up a bit.  The performance
>> problem has been there since the beginning, and I've scanned
>> for viruses.  There are none to be found.
>>
>> I've allocated 2GIG for the domain and 2 VCPUs.  Performance
>> is so bad as to make the domain almost unusable for many
>> tasks.  Deleting files, for some reason, takes forever.
>>
>> Are there obvious things for which I can check or set?
>> I'm using the latest Citrix distro and I've installed the
>> xen-tools.iso tools.  The drivers running in the domain are
>> Hypervisor-aware.
>>
>>      
>
> Have you tried a complete reinstall of the DomU from scratch with no
> extra drivers or anything?
>
> Is it XP sp2? Prior to sp2 I have seen some pretty poor performance of
> XP.
>
> What does 'xm dmesg' say?
>
> What are your underlying disks in dom0?
>
> It would probably be useful to post your DomU config file to the list.
>
> James
>
> _______________________________________________
> Xen-users mailing list
> Xen-users <at> lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
>
Permalink | Reply | 0 comments |
headers
AswiniKumar K | 1 Nov 13:18
Picon

xend.err: "kernel image does not exist"

Hi,
I'm new to Xen, and am facing issues in the following scenario:
(1)  Create a paravirtualized domU (installing from SLES10SP2 dvd) using virt-manager.
(2)  Make a copy (using either "cp" or "dd") of the disk image file used by this domU and rename it.
(3)  Mount the root partition of this disk image (identified using "kpartx"), change the network related info etc, and unmount it.
(4)  Using this new copy of the disk image file in a new xen configuration file, create a new domU clone with a different name using "xm create".

This did succeed and I was able to see the new domUclone up and running.  However, after a few reboots, it threw up the following error message:
xend.err: "kernel image does not exist"
and never proceeded from there.  From that moment on, the GUI-created domU also threw the same error if I restarted it, and also, I was not able to create a new domU using virt-manager again [at the end of installation, when this newly created domU was started by virt-manager, it threw the same error].

One more point to note is that, when I deleted all the existing domains (except the dom0) and recreated a domU using virt-manager, it worked fine...and I could clone it too as above and everything worked fine.  I don't know if it again throws up the same scenario, since I stopped here right now.


Can anyone help me understand what could have gone wrong, especially when the same domU VMs were working fine for sometime?
And how to handle that situation?

Thanks in advance.

-AswiniKumar.

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users
Permalink | Reply | 0 comments |
headers
Ivan Lisenkov | 1 Nov 13:27

Re: domu network interface number increases

That because your system assigns random mac to virtual network card every time. You can stop it by providing static mac.

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users
Permalink | Reply | 2 comments |
headers
Thomas | 1 Nov 21:32
Picon

Re: Re: domu network interface number increases

Nope, I force the mac address for each virtual nic.
Permalink | Reply | 1 comment |
headers
Alexander Piavka | 1 Nov 21:36
Picon
Picon
Favicon

Re: domu network interface number increases

On Sat, 1 Nov 2008, Y. D. wrote:

> Hi,
>
> Every time my domU is created, the eth* number increases, from eth0 to eth70 now.
> This is really awkward, and should not happen in theroy, nevertheless I don't know why.
> Can anyone identify the problem here?

  It's due to udev persistent net generation rules, you cat dieable then by deleteing
/etc/udev/rules.d/75-persistent-net-generator.rules
also remove all previously generated interface names by deleting
/etc/udev/rules.d/70-persistent-net.rules

or alternatively use static mac in VM config vif statement, then you only 
need to remove /etc/udev/rules.d/70-persistent-net.rules once

>
> Thanks in advance,
>
> Shawn
>
Permalink | Reply | 0 comments |
headers
Jan Marquardt | 1 Nov 21:42
Picon

Re: Re: domu network interface number increases

Hi Thomas,

do you mean the interface number within in the domU or the number of vif 
in dom0?

Please send us also a config of a domU which is affected by this weird 
behaviour.

Cheers,

Jan

Thomas schrieb:
> Nope, I force the mac address for each virtual nic.
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users <at> lists.xensource.com
> http://lists.xensource.com/xen-users
Permalink | Reply | 0 comments |

Gmane