search for: node0

...e mapping for Xen 4.0.2-rc1-pre (xen_changeset:Fri Sep 17 17:06:57 2010 +0100 21350:6e0ffcd2d9e0): (XEN) *** Serial input -> Xen (type ''CTRL-a'' three times to switch input to DOM0) (XEN) ''u'' pressed -> dumping numa info (now-0x4B:40CB2A11) (XEN) idx0 -> NODE0 start->0 size->1703936 (XEN) phys_to_nid(0000000000001000) -> 0 should be 0 (XEN) idx1 -> NODE1 start->1703936 size->1572863 (XEN) phys_to_nid(00000001a0001000) -> 1 should be 1 (XEN) CPU0 -> NODE0 (XEN) CPU1 -> NODE1 (XEN) CPU2 -> NODE0 (XEN) CPU3 -> NODE1 (XEN) CP...

...dy can use shares etc, same for mac users. So my guess its a wins/nmbd/netbios issue; not being to resolve my domain name into an ip address it is a clustered (CTDB) setup with 2 nodes, based on gentoo, samba 3.5.8, ldap and glusterfs the setup is like this: 192.168.100.81 static maintenance ip of node0 192.168.100.82 static ip of node1 192.168.100.83 floating/ctdb ip of node1 192.168.100.84 floating/ctdb ip of node0 node0 has domain master = no, preferred master = no, wins server = 192.168.100.82 node1 had domain master = auto, preferred master = yes, wins support = yes in the 192.168.100 subne...

...istic, but it should always return a finite cost solution if one exists. It does this by avoiding early reduction of infinite spill cost nodes via R1 or R2. To illustrate why the early reductions can be a problem here is some output from the original test case which started this thread: graph { node0 [ label="0: [ 1.875000e-02, 0.000000e+00 ]" ] node1 [ label="1: [ inf, 0.000000e+00 ]" ] node2 [ label="2: [ inf, 0.000000e+00 ]" ] node3 [ label="3: [ inf, 0.000000e+00 ]" ] node4 [ label="4: [ 5.357143e-02, 0.000000e+00 ]" ] node5 [ labe...

Hi, I''ve run into the following error when trying to create a domU: root@jupiter:/etc/xen# xm create node0-mgmt -c Using config file "node0-mgmt". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. root@jupiter:/etc/xen# Excerpt from xend.log: [2006-09-25 14:55:48 xend 2015] DEBUG (DevController:110) DevController: writing {''backend-id'': ''0&...

...a finite cost solution if one exists. It does this by > avoiding early reduction of infinite spill cost nodes via R1 or R2. > > To illustrate why the early reductions can be a problem here is some > output from the original test case which started this thread: > > graph { > node0 [ label="0: [ 1.875000e-02, 0.000000e+00 ]" ] > node1 [ label="1: [ inf, 0.000000e+00 ]" ] > node2 [ label="2: [ inf, 0.000000e+00 ]" ] > node3 [ label="3: [ inf, 0.000000e+00 ]" ] > node4 [ label="4: [ 5.357143e-02, 0.000000e+00 ]&qu...

...your help. I have been stuck in continuous availability of samba 4.3.9 for two weeks. Continuous availability in SMB3 is an attractive feature and I am strugling to enable it. smb.conf, ctdb.conf are attached. Cluster file system is cephfs and mount to /CephStorage client: Windows 8 Pro root at node0:~# samba --version Version 4.3.9-Ubuntu root at node0:~# ctdb version CTDB version: 2.5.1 root at node0:~# ctdb status Number of nodes:3 pnn:0 192.168.74.11 OK (THIS NODE) pnn:1 192.168.74.12 OK pnn:2 192.168.74.13 OK Generation:1131631460 Size:3 hash:0 lmaster:0 hash:1 lmaster:1 hash:2...

...hat the problem is. I guess my first question is - do I need to have a partition formatted as ocfs2 on all nodes in the cluster for this to work? I have formatted a partition via ocfs2console on node1, and mounted it as well. However I cannot figure out how to make that filesystem available on node0, where i have not created an ocfs2 partition. I've been assuming that formatting as ocfs2 will destroy existing data, and don't have a spare partition on node0 yet, I can get one if that is required. Basically my overall question is how do I mount the filesystem(s) from various nodes o...

...ged networking performance in para-virtualized Xen 3.0 on Emulab (https://www.emulab.net/) Here is how the 3-node topology looks (This topology is specified by means of an NS-2 file) topology: _______________________________ | | Node0:eth0 ------|Node1:eth0 Node1:eth1|------ Node2:eth0 |_______________________________| Node0 and Node2 run some standard 2.6.* kernel whereas Node1 runs para-virtualized Xen 3.0 using LVM-created root & swap partitions for DomU (2.6.12-xenU) ***********************...

...: 1 cores_per_socket : 2 threads_per_core : 2 cpu_mhz : 1666 hw_caps : bfebfbff:20100800:00000000:00000940:0040e31d:00000000:00000001:00000000 virt_caps : total_memory : 4079 free_memory : 581 node_to_cpu : node0:0-3 node_to_memory : node0:581 node_to_dma32_mem : node0:581 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1-rc5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p xen_scheduler : credit xen_pagesize :...

...: 1 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 2800 hw_caps : bfebfbff:20000800:00000000:00000180:0000641d:00000000:00000000:00000000 virt_caps : total_memory : 6143 free_memory : 2054 node_to_cpu : node0:0-1 node_to_memory : node0:2054 node_to_dma32_mem : node0:1807 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1-rc3 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p xen_scheduler : credit xen_pagesize...

...code to change these behaviors. My experiences are with glusterfs 3.2.4 on CentOS 6 64-bit. Suppose I have a Gluster volume made up of four 1 MB bricks, like this Volume Name: test Type: Distributed-Replicate Status: Started Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: gluster0-node0:/brick0 Brick2: gluster0-node1:/brick1 Brick3: gluster0-node0:/brick2 Brick4: gluster0-node1:/brick3 The mounted Gluster volume will report that the size of the volume is 2 MB, which creates a false impression that it can hold a 2 MB file. This isn't too bad, since people are used to a file sy...

...: 4 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 1995 hw_caps : bfebfbff:20100800:00000000:00000140:0004e33d:00000000:00000001 total_memory : 24570 free_memory : 918 node_to_cpu : node0:0-3 xen_major : 3 xen_minor : 2 xen_extra : -1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000...

...s_per_socket : 4 threads_per_core : 2 cpu_mhz : 2400 hw_caps : bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 24567 free_memory : 22240 node_to_cpu : node0:0-15 node_to_memory : node0:22240 xen_major : 3 xen_minor : 4 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 pla...

...s_per_socket : 4 threads_per_core : 2 cpu_mhz : 2400 hw_caps : bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 24567 free_memory : 22240 node_to_cpu : node0:0-15 node_to_memory : node0:22240 xen_major : 3 xen_minor : 4 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 pla...

Hi Lang, I'm surprised about the fact that you omit R1/R2 reductions in some cases. Can you give a more detailed description of the bug (e.g. a PBQP dump)? Best regards, Sebastian Lang Hames wrote: > Hi Sachin, llvm-dev, > > I've just committed a new PBQP solver which, among other things, > should take care of this bug. > > Please let me know how it works out for you.

...: 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 1995 hw_caps : 178bf3ff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f:00000000 virt_caps : hvm total_memory : 1918 free_memory : 3 node_to_cpu : node0:0-1 node_to_memory : node0:3 node_to_dma32_mem : node0:3 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1-rc1-pre xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_sched...

...: 1 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 2992 hw_caps : bfebfbff:20100000:00000000:00000180:0000641d:00000000:00000000:00000000 virt_caps : total_memory : 4030 free_memory : 2965 node_to_cpu : node0:0-1 node_to_memory : node0:2965 node_to_dma32_mem : node0:2913 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps : xen-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_pa...

...in continuous availability of samba 4.3.9 for two weeks. Continuous availability in SMB3 is an attractive feature and I am strugling to enable it. > > smb.conf, ctdb.conf are attached. Cluster file system is cephfs and mount to /CephStorage > > client: Windows 8 Pro > > root at node0:~# samba --version > Version 4.3.9-Ubuntu > > root at node0:~# ctdb version > CTDB version: 2.5.1 > > root at node0:~# ctdb status > Number of nodes:3 > pnn:0 192.168.74.11 OK (THIS NODE) > pnn:1 192.168.74.12 OK > pnn:2 192.168.74.13 OK > Generation:1131...

...39;/path/port2' mode='client'/> <model type='virtio'/> </interface> when i create the VM the qemu command is like this without 'share=on' parameter: -object memory-backend-file,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,size=1024M,id=ram-node0 -numa node,nodeid=0,cpus=0,memdev=ram-node0 -object memory-backend-file,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,size=1024M,id=ram-node1 -numa node,nodeid=1,cpus=1,memdev=ram-node1

..._socket : 4 threads_per_core : 1 cpu_mhz : 2000 hw_caps : bfebfbff:28100800:00000000:00001b40:009ce3bd:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 12279 free_memory : 3934 node_to_cpu : node0:0-3 node1:4-7 node_to_memory : node0:1996 node1:1938 node_to_dma32_mem : node0:1995 node1:0 max_node_id : 1 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps...