search for: physdev_dom0_hide

...N modem on Linux in domU domain. I have compiled domU with physical access, but can''t see any devices with ''listpci'' (but it doesn''t complain with any errors). Probably I have to disable access to this device for dom0. In Xen 2.0 there have been command "physdev_dom0_hide". But in Xen 3.0 doesn''t seem to support this. I''ve tried to append this in my Grub configuration: kernel /xen.gz physdev_dom0_hide=(01:08.0) but ''lspci'' in dom0 still gives me the following result: 0000:01:08.0 Communication controller: Tiger J...

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 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: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A...

..." was selected, so i tried disabling that and recompiled. Now the system comes up with no problems, but obviously, i have no access to my PCI device. Is there anything else i need to do besides: 1. hiding the pci''s from dom0 by specifing the pci = [ x,y,z ] in the config file and the physdev_dom0_hide option for xen-2.0.gz 2. enabling CONFIG_XEN_PHYSDEV_ACCESS for the domU kernel 3. including the correct drivers in the domU kernel Do any of you see a reason why my kernel would not come up if i enable "CONFIG_XEN_PHYSDEV_ACCESS" in domU ? Thanks, Ban *********************************...

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

I''m attempting to migrate from vmware to xen, however I need to be able to run more than one bridge. Think of it this way: xen0 xenU-1 xenU-2 xenU-3 ------------------------------------------------------------------------ Inside_bridge_1: eth0 vm1_eth0 vm2_eth0 virtual_switch_2: vm1_eth1 vm2_eth1 vm3_eth1 Outside_bridge_3: eth1 vm2_eth2 vm3_eth0 Now, I can modify the existing

Greetings, Does anyone know if it is possible to give a guest domain access to character device hardware such as a SCSI tape drive (/dev/st0 | /dev/nst0)? I have recompiled the guest xenU kernel with hardware access and declared the pci SCSI card in the config file directive as follows: pci = [ ''4,3,0'' ] The log file when started reports: [2005-11-01 17:24:57 xend] DEBUG

Is it possible to disable one of the (real) Ethernet interfaces from Xen so that Domain 0 doesn''t see it? I.e. when the Domain 0 XenLinux boots up it only has eth0 although there are actually two NICs in the machine. Would it be possible to do this using the "nics=" parameter? I know this can be done for doms>0 but get the impression Domain 0 is different. Alternatively

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro