search for: dmarquess

Hello all, Not sure if I am completely missing something but here goes. I have XCP 1.0 running without any issues. I have the mtu set on both the storage network, the corresponding PIF, and the VIF to 9000 and when displayed in ifconfig it shows that this is indeed true. I have several CentOs 5.6 VMs running in HVM mode (i.e. no xen kernel) which attach to the the storage network through these

All, This is a fresh, un-f#$ked-with OpenSUSE install after adding the Tumbleweed repository and doing a dup. I installed the Hypervisor with Tools for which it prompted me for Xen or QEMU and I chose Xen. No bridge was made. When I go to create a fully virtualised machine, it nao has the error: Error: Device 0 (vif) could not be connected. Could not find the bridge, and none was specified.

It seems that in XCP 1.0, VDIs have a size limit of 2TB, even when sm-config:type=raw is set. I understand the 2TB limit when using VHD, but shouldn''t that limit be relaxed for raw? -Dustin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

When creating a vdi with "xe vdi-create", there is a 2TB size limitation imposed, presumably because the default uses VHD, which has this limit. However, when a raw LVM partiton is created with the sm-config:type=raw option, this limitation doesn''t make any sense. Could the 2TB limit please be lifted when sm-config:type=raw is used? Thanks, -Dustin

On NetBSD 6.99.28-CURRENT, nsd 3.2.16 works fine, however nsd 4.0.0 is spinning chewing CPU. The logs show: Nov 28 23:07:00 xxx nsd[466]: sendmmsg failed: Resource temporarily unavailable ktruss shows it getting EAGAIN from sendmmsg(2) over and over again. According to the man page: [EAGAIN|EWOULDBLOCK] The socket is marked non-blocking and the requested