similar to: domU device access : kernel problem

Hi there! I am currently setting up a Xen box on 3 VLans, each VLan interface is in a bridge and currently, dom0 is reachable from on of these and is performing great. My only problem is with domU : it can ping anything but it won''t work for TCP and UDP protocol UNLESS I do a manual tcpdump on my vlan interface. Bridges on dom0: xen-vl97 8000.001372529fbf no

Hi, Is there a reason that the allocate_empty_lowmem_region() function in hypervisor.c is only available in Domain 0. It is only included if CONFIG_XEN_PHYSDEV_ACCESS is defined, however, when I remove this it seems to work fine in DomUs. Thanks, Ross _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello all, I''ve been running Xen 2.0x for some few months and have written a simple top(1)-like tool - xenConsole - which continously displays all running domains, along with their CPU-consumption, load averages, percentual CPU-/memory-usage, domain uptimes and so forth. A screenshot probably explains it better than me: http://www.gothix.dk/xenConsole/xcon-0.10b1-ok.PNG It requires

We have an Intel VT system, and we have successfully installed Xen 3.0 on it, but we cannot find out how to run Windows as a guest OS. Someone on this mailing list has successfully done it, but did not say how. Thanks, - Hao _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello there! I made Debian, Xen 2.0 and CLUSTER/GFS work together :). I wrote this little tutorial to help you setup yours. Any feedback is welcome, except comments about W3C validation of my code :p Note that I am talking about compiling CLUSTER with your XEN kernel, I don''t explain how to setup a working cluster. You can find how to setup those in official RedHat docs. You will see,

I just compile one kernel to the domU but cant see the PCI netcard, i hide the card from dom0 physdev_dom0_hide=''(00:11.0)'' and added to the domU config pci = [ ''0,11,0'' ] and dint work.. any howto to do that? - ariel ariel en BSDlatino . org ariel en ferreras . info http://www.BSDlatino.org http://ariel.BSDlatino.org

Hi, I''m having problems using Xen (2.0.7 and 3.0.0) on newer IBM HS-20 blades, which uses Broadcom network card (tg3 kernel module). Here''s the relevant entry from lspci : 05:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704S Gigabit Ethernet (rev 10) 05:01.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704S Gigabit Ethernet (rev 10) If xend is

hi, i red several mails, but didn''t found a real solution. I want to install hylafax in DomU and i need access to /dev/ttyS1. I hide com2 in grub: title Xen 2.0 / XenLinux 2.6.11 kernel /boot/xen.gz dom0_mem=64000 physdev_dom0_hide=''(00:2f.8)'' max_loop=32 module /boot/xen-linux-2.6.11.12-xen0.xen.kernel root=/dev/hda2 ro i used the entries from dmesg: Serial:

Hi, How do I map certain pci devices directly into a user domain? Has anybody done this? Any leads would be appreciated. thanks deepak _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, Stop me If I am wrong but DELL 1855 aren''t shipped with Dual Core Xeons .... So you shouldn''t have any VT support on your server. Christophe Painchaud -----Message d''origine----- De : xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] De la part de Sadique Puthen Envoyé : Tuesday, October 17, 2006 5:25 PM À : octane indice Cc :

I configured a domU to access to the physical serial port of the dom0 (/dev/ttyS0) typing this in the domU configuration file: irq = [ 4 ] ioports = [ "3f8-3ff" ] The domU starts without any error, but the serial port isn''t recognised. The /dev/ttyS0 device exists on the domU, and I blacklisted the serial_core, the 8250 and 8250_pnp modules on the dom0. What is the problem?

I get the following warning when running xend start, and a similar warning sometimes when doing xm commands: /usr/lib/python/xen/xend/XendNode.py:26: RuntimeWarning: Python C API version mismatch for module xen.lowlevel.xc: This Python has API version 1012, module xen.lowlevel.xc has version 1011. import xen.lowlevel.xc /usr/lib/python/xen/xend/xenstore/xstransact.py:10: RuntimeWarning:

Hi everyone, i''m currently try migrate my mythtv-server into an xen maschine but the ivtv-driver for my Hauppauge PVR350 doesn''t work. Now, a lot of googling and reading later i''m now here. I''ve an error which i can''t exactly allocate: is it an driver or an xen generated error ? I got with the ivtv-drivers following error: (0.2.x ivtv driver)

I keep getting errors in my logs about can not bind to address *.*.*.*:53 address in use.. what did i do wrong in the setup of my server or domain? attached logs and smb.conf along with the output from my provision command. Jeffrey D. Means meaje at meanspc.com Owner / CIO for MeansPC http://www.meanspc.com/ Custom Web Development For Your Needs. (970)308-1298 - The

Did the upgrade by chance install/alter any udev rules causing the UPS devices to now have incorrect permissions? And what user is nut running as? On November 9, 2024 9:58:57 AM EST, Bill Gee <bgee at campercaver.net> wrote: >Running NUT version 2.8.2 on Fedora 40. NUT installed from the Fedora package. CyberPower CP1000AVRLCD connected by USB. > >I updated the system yesterday

Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS seeing the UPS at a low level. I looked through /dev/ but did not see a device that jumps out as the UPS. ===================== [root at mythtv rules.d]# dmesg | grep -i 0764 [ 2.021485] usb 1-1.8: New USB device found, idVendor=0764, idProduct=0501, bcdDevice= 0.01 [ 2.049515]

Check /dev/hidraw6, as noted in your dmesg output (and any other *hid* devices under /dev). User nut has almost zero privs to devices unless a udev rule changes the perms on the dev for nut . . . On November 9, 2024 1:25:29 PM EST, Bill Gee <bgee at campercaver.net> wrote: >Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS

Running NUT version 2.8.2 on Fedora 40. NUT installed from the Fedora package. CyberPower CP1000AVRLCD connected by USB. I updated the system yesterday with all the latest Fedora packages. Now NUT will not run. Chasing the issue through the layers, I come to this: ===================== [root at mythtv rules.d]# upsc cyberpower Error: Driver not connected [root at mythtv rules.d]#

same as above. i compiled xen in ubuntu 5.10 and had amny problem and later found the guide given in ubuntu wiki tell to use this command make CC=gcc-3.4 meaning use gcc 3.4 instead of the gcc 4 that is standard on ubuntu. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users