similar to: How do I configure Multiple domains/machines?

Processing commands for control at bugs.debian.org: > # reassigning all open bugs reported against versioned xen packages that are no longer in the archive to src:xen > reassign 399073 src:xen 3.0.3-0-2 Bug #399073 [xen-hypervisor-3.0.3-1-i386] xen-hypervisor-3.0.3-1-i386: dom0 crashes with a domU that define more than 6 vdb Warning: Unknown package 'xen-hypervisor-3.0.3-1-i386' Bug

I have a machine with 8 CPU's (2 quad xeons). (Centos 5.4 currently). Currently, I am running 2 domUs. One with 4 CPUs and another with 2. 2 remain unused. I am using routed networking. On the one machine with 4 CPU's, there is a cronjob at 4am which utilizes the CPU/disk pretty heavily. It is rebuilds a mailing list archive (using MHonarc) and rebuilds a search engine index

Hallo, I have running xen-4.2/linux-3.8 (compiled) on any hosts. - dell pe r720: drac, eth0-3:igb squeeze -> boot_xen:ok net:ok bridge:ok - dell pe R620: drac=eth0, eth1-3:tg3 wheezy -> boot_xen:ok net:ok bridge:fail So i running "xend start" (or "xenbridges start") on my patient (R620 with broadcom tg3) network will be lost: RTNETLINK answers: File exists

Any chance we can set up a low-volume "centos-announce" list so that we all don't have to read all of these non-Centos-specific E-mail threads about people figuring out how to admin a Linux box when all we need to know is when major releases/milestones/news items are available? Regards, -Tom

Has anyone done an upgrade from RHEL3 to RHEL4? Is this likely to break a lot of things? How long will Centos be supporting version 3? I just installed Centos 3.4 two weeks ago! The only problem I'm having with Centos is that the perl is a bit old. I have errors with spamassassin. So far bugzilla for spamassasin is blaming it on the version of perl included in RHEL3 and bugs in the

Processing commands for control@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.27 > # does not make the package unusable > severity 414040 important Bug#414040: kernel: xen_net: Memory squeeze in netback driver. Severity set to `important' from `grave' > End of message, stopping processing here. Please contact me if you need assistance.

Processing commands for control at bugs.debian.org: > close 414040 Bug #414040 [src:xen] kernel: xen_net: Memory squeeze in netback driver. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 414040: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414040 Debian Bug Tracking System Contact owner at bugs.debian.org with problems

On 9/24/20 8:53 AM, Aur?lien Aptel wrote: > Ken Bass via samba <samba at lists.samba.org> writes: >> I installed a new Ubuntu 20.4 LTS system (smbd 4.11.6) . Initially I >> tried using the SSSD and 'realm' to join the domain. Everything worked >> similar to my Centos 7 install and I thought I was finished. >> >> The one thing not working is? cifs

I tried today''s unstable on some IBM hardware and get this IRQ message at boot when xenU tries to probe the virtual block device: Xen virtual console successfully installed as tty1 Event-channel device installed. xen_blk: Initialising virtual block device driver Trying to free free IRQ261 vbd: probe of

Hi, I did not find any hints in the web where to configure/setup/manipulate the rx/tx ring buffer allocation within dom0 for xen-unstable, maybe someone here can nudge me towards the right knob. The problem: when booting a handful of domUs and connecting them (comprising a small experimental IP network with links and nodes etc.), some interfaces that have been given by the configuration files

Hi all, I tried to boot up a VM using two options (a) reading boot information from a config file (b) adding boot information directly to the command line. However, I got "IP-Config: Unable to set interface netmask (-22)" problem when using option (b). For (a), I don''t have such problem. The boot information for both (a) and (b) is same. Could you please let me know what I am

> Hi all, > I tried to boot up a VM using two options (a) reading boot > information from a config file (b) adding boot information > directly to the command line. However, I got "IP-Config: > Unable to set interface netmask (-22)" problem when using > option (b). For (a), I don''t have such problem. The boot > information for both (a) and (b) is same.

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: normal See also, bug 660768 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660768 atalkd appears to be unable to open virtual network interfaces when run in a Xen PV guest. With nothing set in atalkd.conf, it reports : eth0: disabled. atalkd: zero interfaces, exiting. Adding "eth0" to atalkd.conf results in :

Hi there, my Server: Debian 4.0, XEN xen-hypervisor-3.0.3-1-i386-pae I have successfully installed and running 13 domU. I have enough free ressources for number 14. I set it up in exactly the same way like the others. Once started this dumU Nr 14, every other domU lost its network connection. If I shutdown Nr 14, everything is working finde again. Is there a maximum number of domUs per Host?

Hi all, First, i''m french and my english is approximately, thanks to be indulgent. I have 2 Xen server 4.0 on Debian Squeeze with this kernel : 2.6.32-5-xen-amd64. In my entreprise I have a multiple networks : - 1 : 10.168.30.0/24 - 2 : 10.168.40.0/22 - 3 : 10.168.50.0/22 - 4 : 10.168.60.0/22 - Admin : 10.168.0.0/20 - Internal : 172.16.8.0/24 On my 2 Xen server I have 6 bridges which

Package: xen-utils-common Version: 4.1.2-3 Severity: normal When configurating a duplicate custom vifname for interfaces in the Xen dom0 that are added to a bridge (which is obviously a configuration error), the hotplug scripts fail silently to rename the new vifX.0 to the custom vifname, if it's already existing. The result of this, is that the domU will start normally, but no network

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1~rc3-1 Severity: normal Hi, I upgrade one server from lenny to squeeze, to start testing xen-hypervisor-3.4 and xen-hypervisor-4.0, but it seems to don't work. The error : xm create -c /etc/xen/slhoka.cfg Using config file "/etc/xen/slhoka.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. The error

I just cant get a Centos 5.1 domU to install under Centos 5.1 dom0. It is maddening! I'm trying to replace a single server that currently uses simple ethernet aliases (eth0:0, eth0:1, etc) with a new server that uses Xen virtualization. Maybe I dont understand bridging properly or something. My dom0 has the following: eth0 Link encap:Ethernet HWaddr 00:00:44:11:22:33 inet

Dear Community, i have a problem with a new debian XEN 64bit squeeze Server, when i started a windows hvm domU. I tested with the routed and now in the bridge network mod. I start the domU with xm create win.cfg and 1 or 2 second the dom0 is reboot. I install a debian domU on the system, and this is without any problems in routed and bridge mod. In the logfile are no informations, in the routed

hi I encounter problem when install debian squeeze domU on centos 5.6 dom0 environment dom0: centos 5.6 xen version: 3.4.3 domU : debian 6 squeeze I follow the instruction with howtoforge(http://www.howtoforge.com/installing-debian-squeeze-6.0-domu-on-centos-5.5-x86_64-dom0), after finishing the installation of debian squeeze, when I chroot the squeeze''s / and execute "apt-get