similar to: Bug#429789: peth0: received packet with own address as source address

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: wishlist Xen can run 32bit domU clients on 64bit (amd64) dom0. Unfortunately only amd64 linux-image-xen packages are available on arch amd64. Please provide 686 packages as well (if possible). This would enable the installation of 32bit clients without the need to manually compile a kernel. Feel free to reassign this bug to the correct

Package: xen-utils-common Version: 3.0.3-0-2 Severity: wishlist Tags: patch Currently when hostnames are wider than 10 chars, the xentop output is messed up. Please add the following patch to support up to 20 chars, or better yet, allow the columns to auto size :) #! /bin/sh /usr/share/dpatch/dpatch-run ## xentop-name-width.dpatch by <apeeters@lashout.net> ## ## All lines beginning with

Hi all, Would it be possible to include support for a non-pae capable machines on the demo cd. The 3.0 version worked but the 3.0.3 version fails with Cannot execute PAE-enabled kernel on a PAE-less CPU! (Please CC me since I am not subscribed to the list) Thanks, -- Adriaan Peeters _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Command just times our for me virt-install --paravirt --vcpus=4 --name server1 --ram 4096 --file /opt/xen-images/hlcnwmmp01.img -x "ks=http://10.203.1.11/kickstart/ks-xen.cfg" --file-size 40 --location http://128.61.111.11/pub/centos/5.4/os/x86_64 -b peth0 Starting install... Retrieving file vmlinuz... | 1.9 MB 00:00 Retrieving file initrd.img...

Hi, If one sets xend to use network-bridge and there are no bridges already present then it seems that xend will clone eth0 to peth0, create xenbr0 and add peth0 and vif0.0 as ports on that bridge. If on the other hand xenbr0 is created in /etc/network/interfaces then xend will not do any of that peth0 stuff, nor will it add vif0.0 to xenbr0, yet (barring some changes in iptables rules) things

Hi All, I just started using Xen a few days ago on Ubuntu Feisty Server. Did a binary install of 3.1 and within very little time had 2 windows 2000 domUs up and running. This made me very happy until I realized I was unable to access dom0 or either of the domU''s from the network. The domUs can access the network if they initiate the connection. After attempting to ping dom0 or domU from

Hello, running xen 3.0.4_1 I find the following messages in /var/log/messages: kernel: peth0: received packet with own address as source address Is this something to worry about? The tcpdump shows the following pakets during that time: 14:58:05.546043 fe:ff:ff:ff:ff:ff (oui Unknown) > 09:00:2b:00:00:0f (oui Unknown), ethertype LAT (0x6004), length 81: 0x0000: 2808 0505 0502 131f

hi, When I remove the ether card from the system and attach it back again, it does work any more. I read the documents in wiki, and I know the ip and mac address are copied to eth0. But I''m using dhcp, so the ip address will change. But the eth0 stays the same. What can I do to make it work again? Thx. _______________________________________________ Xen-users mailing list

It seems that with their specific Xen packages, Debian likes to go against the norm, and rather than calling the Xen bridging device something sensible like "xenbr0", they rename the main physical ethernet device "eth0" to "peth0" and create "eth0" as the Xen bridge (as far as I can tell, anyways). Anyone know where exactly they do this so I can reverse it?

Hi, I would like to ask concerning problems after installing xen 3.3 on Centos 5.2 I use 2.6.18.8-xen (xen3.3.1 testing - installing with mercurial). After done with make world and make install, I did mkinitrd and placing it in /boot changing the grub and reboot.. succeded I do not install libvirt and the domUs from the previous xen 3.0 (built-in Centos 5.2) are NOT able to start : [root@wing

Hello list, I have network problems on dom0 I discovered this trying to copy user''s homes from another box onto dom0. I have tried this via mouting tcp nfs and also via ftp. Both methods give me the same problem. When I try to send lots of continuos traffic the tcp connection bottoms out. I get this on dom0 peth0 transmit timed out, tx_status 00 status e000 diagnostic: net 04cc media

Hi! I''m not new to Xen but I''m new to this list. I''m having a truely bizarre problem with Xen bridged networking at the moment. This is a new install, on RHEL4. The symptom is that any domU set up simply fails to talk to anything else. It''s there, and running, and it has an ethernet device, but there''s never any response. After digging through the

Hello, I switched from my PSTN provider to a voip provider. (Voicedata in the Netherlands) >From the moment i switched all inbound calls are terminated after aproximatly 1 minute. The provider tells me it's not their issue since I have no other configuration than all their other users. What can I do. I removed all asterisk functionality by forwarding the inboud call directly to a local

Hi all, I am probably missing something ultimately obvious, but I have a problem configuring freepbx... Using Edgy Eft with the cvs freePBX 2.2.1 and followed the Ubuntu installation guide on freepbx.org. System pxe-boots from a server with NFS root on same Using * 1.2 current (from source, not .deb's) Using mISDN-streams (from source, not .deb's) Using freePBX-2.2.1 (from source, not

hi, i've setup a LDAP server with account information, and compiled samba with ldap support. everything works great, except for the password changes i still have to run two seprate commands ( passwd, smbpasswd ) to change a users password. i've tried to put the pam_smbpasswd.so module into system-auth, but that does work? any pointers? thanks adriaan putter

The only call that PeriodicalUpdater will make periodically to you is the insertion call. I think of onComplete as being ''I''ve done everything I was going to do'', which for Updater is right after it''s done a single update, but for PeriodicalUpdater, it''s after it''s finished all of its updates, so you''ll only get it once for any call

Hi All Apologises if this has been disussed and I missed it. My SetUp I have a sip phone registered to an asterisk box (a1) in one location 1. This phone dials an extension which is in another location, so a1 passes the call via IAX to the other asterisk (a2) in location 2 which then dials the local phone. My Problem The caller ID setup in the sip.conf for the phone registered to a1 is not

Has anyone ran into this issue before? 2 physical nics: eth0 hooked up to 10.175.8.0/21 eth1 hooked up to 10.150.8.0/24 Ifconfig -a looks like this: [root@mgixen1 ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:19:B9:F2:1B:C3 inet addr:10.175.8.158 Bcast:10.175.15.255 Mask:255.255.248.0 inet6 addr: fe80::219:b9ff:fef2:1bc3/64 Scope:Link UP

>From a quick look at the source code, it looks like onComplete is only called when the whole thing is done - in the case of Updater, right after the update, in the case of PeriodicalUpdater, right after it has been stopped. It looks like you need to pass your callback method as an ''insertion'' method in the options. This takes two parameters, the first will probably be the

I've tried to find some details on the wiki, but was unable to get a satisfactory result, so I am asking here: I have a Linux (FC3) box with these specs: vendor_id : AuthenticAMD cpu family : 6 model : 3 model name : AMD Duron(tm) Processor stepping : 1 cpu MHz : 797.388 cache size : 64 KB MEM: currently 256, looking to upgrade to 512/768