similar to: The trouble with WINE

You are very welcome. One thing that I am working on now involves removing the step toward the beginning: xe pif-reconfigure-ip uuid=<UUID of the bond created above> mode=static gateway=<GATEWAY> IP=<IP ADDRESS> netmask=<NETMASK> DNS=<DNS SERVER ADDRESS> I do not believe that this step is necessary since we will not use the pif directly. We will use

While I am still in the process of working through this here are the steps I am taking to set up each machine. 1) Since each of my servers have multiple NIC ports I bond them together (see page 34 of the Administrators Guide) first. This is best down from the physical server and not via the remote console. If you do it remotely you will then have to reconfigure the management port before

Package: xcp-xapi Version: 1.3.2-6 Severity: minor Tags: upstream If xe pif-configure-ip called twice with different IP, it did not remove old IP from interface (but didn't store both addresses in database). (Checked for management interface) Steps to reproduce: xe pif-reconfigure-ip uuid=... ip=IP1 .... xe pif-reconfigure-ip uuid=(same) ip=IP2 ... 'ip addr show' shows both

Package: xcp-xapi Version: 1.3.2-13 Severity: critical I get this bug when installing XCP and configuring the network portion of it. When I issue the following command: xe pif-reconfigure-ip uuid=$PIF_UUID mode=static IP=10.0.0.10 netmask=255.255.255.240 gateway=10.0.0.1 DNS=10.5.1.2,10.5.1.3 My network interface looks like this (Broken): eth2 Link encap:Ethernet HWaddr 00:50:ec:24:c7:43

Hi, After reading XenServer documents and debugging, I found the previous configuration is correct, here is the one I've configured to work: In XCP, as in XenServer, system's network configuration doesn't really matter, it only make sense before XCP starts and handles the network settings. So there is no need to configure VLAN on host machine, and you only need a minimal one active

control: severity +2 serious I would call this an RC bug (serious), but not critical It would be critical if the user lost data from some unrelated application, etc It is serious because a) it makes the package and the whole system unusable for all but one very specific network configuration (users with a /24) b) using good old `xm' style Xen I never experienced any issue like this,

Package: src:xen-api Version: 1.3.2-9 Severity: wishlist Hi, In /usr/share/doc/xcp-xapi/README.Debian.gz, line 149: 149 PIF_UUID=`xe pif-list device=eth0` 150 xe pif-reconfigure-ip uuid=$PIF_UUID mode=static \ 151 IP=1.2.3.4 netmask=255.255.255.0 gateway=1.2.3.1 The command for acquiring the pif-uuid is missing a --minimal parameter, which makes it output the UUID only. -- Regards,

Hello, I have been playing with the XCP for a while now, and must say I''m very exited about the technology. I had no prior experience with Xen so it has taken me a while to understand the concepts, but now I feel most important issues are solved and I''ve purchased some hardware to build my (tiny) cloud on. The box is a Supermicro 1026TT-IBXF, so I have 2 x Ethernet and 1 x

This is being offered gratis till the end of december by Mackie. This one might just be coaxed into running under Wine which would be quite an achievement. Kudos: 1. The program, though free, needs be registered to a "machine number". Did this under Windows, did not get that far using Wine. Might need a second copy just for the Linux runs. 2. The program searches for all its own

My wine installation works perfectly with many apps. However, when I am trying to install one Win app (Parashara's Light) through wine, I am getting the following error: <errorcode> 16 bit DOS subsystem: C:\windows\temp\dosshell.pif Invalid program file name. Check your pif file. The pif seems to be in some weird format. Cat produces following output: cat "/[path to wine

Greetings -- I have a DOS .exe file that I would like to run in Wine (the underlying Windows is Win2K); it gives the error "Needs 1024K of expanded memory." I have a PIF file which supposedly sets up this memory environment, but .PIF files cannot be loaded by Wine. Possible solutions: * Make wine make the .exe think there is 1024K of expanded memory. * Make wine run the .pif file

----- Message d'origine ---- > De : David Baron <d_baron at 012.net.il> > ? : wine-users at winehq.org > Envoy? le : Jeudi, 28 F?vrier 2008, 18h53mn 08s > Objet : Re: [Wine] How about this replacement of WINE. > > > However, it's a great, great project IMO. It was about time something > > > like that should've been made. Redirecting calls is simply

It appears that this issue may be a result of documentation problems When I was having this problem, I had xenbr0 declared in my /etc/network/interfaces file. I have now stripped out everything in the interfaces file except the loopback interface, rebooted, and now my xcp+openvswitch system appears to be adding domUs to the bridge automatically, so the problem is no longer there. Specifically,

Processing commands for control at bugs.debian.org: > severity 695221 serious Bug #695221 [xcp-xapi] xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet netmask Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 695221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695221

Processing commands for control at bugs.debian.org: > severity 695221 important Bug #695221 [xcp-xapi] xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet netmask Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 695221:

Package: xcp-xapi Version: 1.3.2-15 Severity: important New wheezy box Follow the setup instructions for xcp-xapi, choosing openvswitch networking Only loopback is defined in /etc/network/interfaces (the way it should be for XCP) IP address, router, DNS has been configured statically with pif-reconfigure-ip After reboot, the IP address is assigned correctly on the bridge interface but some

Package: src:xen-api Severity: wishlist I've tried to configure VLAN using XCP + openvswitch using Wheezy, though it's still not fully working, I think VLAN configuration on dom0 can be better documented. It's fair easy to configure VLAN in Debian. First you need to ensure that your physical switch is in trunk mode, which means it will pass all kinds of VLAN tagged network flow, and

Esta e uma mensagem automatica. por favor nao responda ela. (This is an automatic message. Don't reply please) (see below for the english version) Voce enviou uma mensagem contaminada com o(s) virus: 00]/text infected: I-Worm.Sobig.f.txt /var/tmp/vir-1061498500-18279/email.eml/[From <samba@lists.samba.org>][Date Thu, 21 Aug 2003 22:41:29 +0200]/document_all.pif packed: PE_Patch

--- David Baron <d_baron@012.net.il> wrote: > On Tuesday 15 March 2005 00:00, > wine-users-request@winehq.org wrote: > > found that when trying to run Sonar XL 2.2 under > > Wine, adding additional fonts will void out the > > notation font. :) > > Really? Home studio, Sonar's not-so-little sister > will not run at all. > Get "Unknown error in

Hi, My name is Monenci Nicolae. I'm from Romania, an i have a problem that i could not find any answer on net. I have an "Samba version 3.013" instaled. I have atach-ed the smb.conf that i have configured my self. So my problem is: I have a network of 10 PC. (5 windows XP, 2 windows 2000, 3 windows NT) I have installed 1 new PC with windows XP. After i installed