search for: tap1.0

I''m having an issue forwarding through an Intel on-board graphics adapter. This is on a Dell Optiplex 780 with 8GB of RAM. The pass-through works perfectly fine if I have 2GB of RAM assigned to the HVM domU. If I try to assign 3GB or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch()

I''m having an issue forwarding through an Intel on-board graphics adapter. This is on a Dell Optiplex 780 with 8GB of RAM. The pass-through works perfectly fine if I have 2GB of RAM assigned to the HVM domU. If I try to assign 3GB or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch()

Hi there. I''m having trouble with Xen after reboot my system. ifconfig -a Now, ifconfig -a gives me only vif1.0 network device, but recently (before reboot) it have gived one tap1.0 device. I''m asking because of network: it''s no longer available ;-( Everything was good. No kernel or Xen recompilation. And no tap1.0 device anymore ;-( The settings for network is the

Hi, I would like to know if somebody can point me out how to configure several DomUs in a private LAN (for example 192.168.100.0/24) and one DomU with two interfaces (one - 192.168.100.0/24 and two - internet). So far I have enabled in xend-config.sxp: (network-script network-route) (vif-script vif-route) My config files have: /mnt/VM/1.cfg:vif = [''ip=192.168.1.3'']

Hi, I''m now blocked for 2 days on getting the network to work in my domU. Here is the problem : The domU refuses to start when a vif is configured. It''s just staying paused for about 1m40s, then the xm create command line give back with an "Error: Device 0 (vif) could not be connected. Hotplug scripts not working.", and the domU is destroyed. Nothing particular

Hi xen developers, Does any of you know how to disable the cirrus-vga emulation for hvm in xen? I have been trying to disable that from the source codes, but even with that, I still see a VGA controller when I boot up my guest domain. In particular, I would like to do this because I am passing through a graphics card to my guest domain using direct pass through. Thanks, - billy

Hi, the problem is as follows:(And then, others can't login mostly because of the os' busing and you can't do anything else.) [**@xentest ::三 12月 21::~]$ sudo xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1748 2 r----- 29396.3 xp-101 1 256

Hi all, I have started stubdom, thank all of you. But I still met a problem, that is I found stubdom block when it run 107s. the message in "xm li" : Domain-0 0 1719 2 r----- 171.9 hvmachine 1 256 1 -b---- 110.6 hvmachine-dm

Hi All, I''m having a similar issue as Ian Tobin some weeks ago here: http://lists.xensource.com/archives/html/xen-users/2010-02/msg00645.html I''m using Debian Squeeze amd64, downloaded the experimental debian xen-amd64 kernel with pv_ops support. linux-headers-2.6.32-5-common-xen_2.6.32-13_amd64.deb linux-headers-2.6.32-5-xen-amd64_2.6.32-13_amd64.deb

We had problem using tagged vlans inside domU. Testing shows that this is caused by changing network interfaces in network-bridge script. Following patch should allow to use vlans in guest. Testing scenario: configure vlan network (e.g. vlan 1 on eth0 => eth0.1) start xend create domU and configure same vlan inside it You can see that vlan is still <interface>.<vlan_id>. You can

(If this is a double post, I apologize, my email client crashed when I first sent it) I need some help to configure a secure network on my Xen server. I have been looking online and it seems a I need a routed network. But I am having a terrible time implementing it. My setup: Xen 3.4.2 CentOS 5.5 Dom0 1 NIC (eth0) All guests will be HVM What I want to do is something similar to a firewall

When I try to use stubdom-dm in lieu of qemu-dm, the guest domain crashes almost immediately if I specify an emulated NIC (''vif='') in the guest configuration file. If I don''t specify a vif, it works fine. If I use the same configuration with qemu-dm instead of sutbdom-dm, it works fine. Is there some reason QEMU emulated networking doesn''t work with stub domains