Search results

The log files was my fault. I forgot to enable the rsyslog. That is working now. I am not seeing anywhere that udev is running at this time. Where would you suggest I check this? Thank you, Ben

I did notice one more thing. When I create a new container I am getting this now: tcgetattr: Inappropriate ioctl for device

Today is the first time since I have created new container since the last update. There are two things that seem very odd to me now. First, I am noticing that when I create a new container /dev is showing up in the df command but the file system is "none". In the past the /dev was just under...

How can I tell it does not work is simple. The server does not appear on the network. As a test I installed mt-daapd on it. When I went to start the program it would fail because it was not able to connect to the dbus.

Try this on a clean install of Fedora 9 template: /etc/init.d/avahi-daemon start You should get (or at least I am): /etc/init.d/avahi-daemon: line 33: [: =: unary operator expected Starting Avahi daemon... [FAILED] In the /var/log/messages I get the...

With everything else going on I know this will be a low priority, but I tried doing this again with the new prebuilt centos container in version 1. I have the same issue with dbus not wanting to start. Any thoughts?

As always thank you all for your support of this great product! Thank you, Ben

It worked! Thank you so much. I believe you are correct that I was not running beta 2. I think.. Anyway I can check for you or is it too late?

O.k. one node is running fine! The other node.. not so much. the network is now up (pve-firmware). However the pve-kernel and pve-kvm are still Not correctly Installed. When I go to install the pve-kvm I get this error: Unpacking pve-kvm (from .../pve-kvm_75-1_amd64.deb) ... dpkg: error...

How do I install the kernel and other packages when I do not have access network access from the node? I do have the CD and used the pveboot to start each node. Thank you, Ben

Yes I did follow the instructions step by step.

I was able to boot using the CD. I have no network access and a ton of errors during start up. When I run pveversion -v I get the following: pve-manager: 1.0-2 (pve-manager/1.0/3399) qemu-server: 1.0-1 pve-kernel: Not correctly Installed pve-kvm: Not correctly Installed pve-firmware: Not...

I am downloading the CD now. When I hit escape after the root (hd0,0) all I get is the GNU Grub version, ram info, and such) then some text about minimal bash. FYI I just did another node upgrade and I have the same exact error on it...

Command: root (hd1,0) Result: Error 21: Selected Disk does not exist Tried this: Command: root( hd0,0) Result: Filesystem type is ext2fs partition type 0x83 Command: boot Result: Error 8: Kernel must be loaded before rebooting I am at a loss. I am hoping this is an easy fix. Thank...

Followed the upgrade step by step on two nodes. Rebooted on of them and it came right back up. However the other rebooted into the grub> prompt and I can't get anywhere beyond this. Only difference between the two nodes is one has a raid 5 system and the other has a raid 0 drive. Any help...

O.k. I can hold off for the new version and start again then. I have too many other projects on deck right now anyway. Thank you as always for the support for a great product, Ben

O.k. I tried making a containter with the veth option. In the OS I created a new file: /etc/sysconfig/network-scripts/ifcfg-eth0 with the following settings: DEVICE=venet0 BOOTPRO=static ONBOOT=yes IPADDR=x.x.x.x NETMASK=255.255.0.0 BROADCAST=x.x.x.x I do a service network restart and...

The node does have additional ethernet ports. How hard would it be to enable an additional one. Then just have the container connect directly to that port?

O.k. Did that. Started the container. Went to the network tab. Under "Bridged Ethernet Devices", Next to ETH0, I selected vmbr0 and clicked save. I get the following error: Error: unable to apply VM settings, command failed: /usr/bin/ssh -n -o BatchMode=yes x.x.x.x /usr/bin/pvectl vzset 109...

Now would I need to have a seperate physical ethernet device enabled on the node (ie eth1) then bridged? Or does the bridge still work on a single ethernet device (ie vmbr0 which I believe goes to eth0)? Thank you again, Ben