Couple of starting out questions

[Jas]

Hi I am trying to get started with proxmox.

---

Update / Summary:
I have learnt the following things during the course of this thread.

1. To use the console you need java installed.
2. To use KVM VM's in proxmox I needed to have my BIOS setting of trusted execution set to "OFF" (ESXi worked fine with this setting on.)
3. You can remotely use TigerVNC via this post: http://pve.proxmox.com/wiki/Vnc_2.0. The user name password is root@pam and *not* your user name and password for the proxmox host.
4. To have the console (and tigerVNC) not display very munged graphics go to the Machine > Hardware > Display and double click that line to edit the value and change the setting to VMWare compatible (vmware).
5. To configure the OpenVZ containers you ssh into the proxmox host and execute "vzctl enter <VMID>".

Things I think that could be improved in proxmox:

1. Better error reporting when things go wrong (eg the console should report that java is needed, when starting the KVM VM it should report better diagnostics.)
2. I would like to be able to edit some wiki pages here to make the instructions a little clearer in places.
3. Maybe direct importing of other types of VM's. Eg import VMWare into KVM?

---

First a couple of points I installed proxmox from a USB after several aborted attempts with first trying standard stuff and then finally reading in the instructions the gotcha that the installer doesn't work with unetbootin where most other distros etc work just fine with unetbootin.

So I have logged on and downloaded a template and also managed to scp an iso onto the hosts local storage (after that I found out how to do this with the interface.)

Unfortunately I can't seem to get either the container (I used trac) to work or a KVM ubuntu machine to boot (ubuntu-12.04.3-desktop-i386.iso)

For the KVM machine:
I followed the instructions on http://www.youtube.com/watch?v=0vG0t25wZEI but the interface has changed a bit in a few places. But it looks like I have created it. Then I try to run it and I get the message error: start failed:command 'usr/bin/kvm -id 101 -chardev ............ failed: with exit code 1'

So first question where is this log file stored so I can post this?

Second with the container if I try and create that with a bridged interface I don't see where the IP address is listed. Also the console for the CT trac image is blank.

Any pointers?

Thanks,
Jas

 

[Raymond Burns]

So, just to be clear, howw did you install?

CT: Bridged IP (veth) is just like the network device for KVM. You can set the DNS in Proxmox WebGUI, but the IP is set in the Container. You will probably have to create a new ifcfg-eth0 file.
KVM: This looks like the code I would get when running Proxmox on hardware that wasn't sufficient (No Vt-d). Does your hardware meet the requirements for virtualization? BIOS settings?

CT: In order to set the IP for the CT, you must use (venet). I'm not sure how it works, since all the NICs are available in that mode. I stick with (veth) because I only want certain CT's to access certain networks. Read up on (venet), as it seems to be able to access and vmbr# that is available.

 

[Jas]

Install proxmox? I did it as follows: So since unetbootin didn't work. I tried using SUSE Studio ImageWriter but that had some problems running under windows 7 and even running as an admin didn't work. I messed around with that for a while but I couldn't get it working (It took a little bit to figure out how to rename a file in windows without it still thinking it was an iso. I ended up using the windows terminal to do this.). I then I fell back to using OSX and trying to use the 'dd method'. But I first needed to find out about diskutil list to get the right device. Once that was done, with the normal usb drive mounted in the finder dd just said the device was busy. After googling around for a bit I found out you could get around his by opening diskutility and unmounting the partion but *not* the volume. Then dd managed to do the copy of the image and I finally had an install stick. I installed with that and it looked like it installed correctly... (Whew not an easy introduction...)

So I have proxmox running. It looks visually nice but then it took me a while to find out where to do the upload to the local storage. But I found that.

Or where you asking how I installed trac container? That was comparatively simpler. I did it as the gave in the wiki here: http://pve.proxmox.com/wiki/Installation#Get_Appliance_Templates . Basically I just chose something which I had used before and was fairly standard so I settled on Trac. Then after that had downloaded to my local storage: I simply choose 'create CT' Then
1. In The general Tab I choose: (i)Node Fritzbox (which is the name of the server), (ii) VM ID(default), hostname = quack, resource pool = <left-empty>, storage = local, password I used qwerty.
2. Template Tab: (i) storage = local, (ii) Template choose debian-6-turnkey-trac_12.0-1_i386.tar.gz
3. Resources Tab: (i) Memory = 1024 MB, (ii) swap = 1024MB, (iii) disk =4GB, (iv) CPUs = 1
4. Network Tab: There are only two choices I have played with both and I can't get either to work. If I choose Routed mode (venet) and hard assigned a local address 192.XX.XXX.98 which wasn't being used.
5. DNS Tab. I just left the defaults
6. Confirm

Then the output was:
Creating container private area (/var/lib/vz/template/cache/debian-6-turnkey-trac_12.0-1_i386.tar.gz)
Performing postcreate actions
CT configuration saved to /etc/pve/openvz/100.conf
Container private area was created
TASK OK

Then I started it but I don't see anything in the console. Just the white screen...

As far as the machine: This is just a machine I am testing stuff on but it is a Dell OptiPlex 755 Intel Core 2 Duo E6550 2.33Ghz. It has 4G of ram and 160G drive. I think I have run ESXi on it and that ran stuff. (I have messed around with a lot of configurational stuff, so I am not exactly sure that I have run it on here, but I have enabled everything in the BIOS to the best of my knowledge. I have ESXi running on a similar but faster OptiPlex 755.)

Where would I check the log files, etc?

Thanks!
Jas

 

[Raymond Burns]

Just some pointers on SUSE Image Writer. Run as admin and make sure all Windows Explorers are closed. It will not run with Windows Explorer open. Sounds crazy, but it's true. Also, make sure you rename proxmox ISO to the right extension.
I don't know about the log files, but you won't be able to get to the CT shell command through the "Console" button. There is some more code to be done in order to set the tty
Open a putty instance or whatever you use, and SSH into the proxmox server. When you are logged in as root, use the command

vzctl enter VMID

Replace VMID with whatever the container you want to enter
You can use

vzlist

to show a listing of containers available.
From there, you can setup your network devices.
Again, the routed mode, I am not sure. I believe additional work is needed to the iptables or something in order to have the CT only use certain NICs
You can delete the template the same way you installed it. There is a remove button there. You can upload templates as well. Just go to the openvz website and look at their selection of tar.gz OS. You would upload the same way you upload an iso.

 

[Jas]

Hi Raymond,

Thanks again for your answers. Sorry for the delayed response...

Just some pointers on SUSE Image Writer. Run as admin and make sure all Windows Explorers are closed. It will not run with Windows Explorer open. Sounds crazy, but it's true. Also, make sure you rename proxmox ISO to the right extension.

Yep. That is pretty bizarre. A smoother starting process should likely be given in the instructions (but maybe my experience was just atypical??...)

don't know about the log files, but you won't be able to get to the CT shell command through the "Console" button. There is some more code to be done in order to set the tty
Open a putty instance or whatever you use, and SSH into the proxmox server. When you are logged in as root, use the command
Code:
vzctl enter VMID
Replace VMID with whatever the container you want to enter
You can useCode:
vzlist
to show a listing of containers available.
From there, you can setup your network devices.

Why doesn't the console automatically bring this up? Maybe there are deep and mysterious technical reasons that the proxmox interface isn't doing this, and instead the user has to ssh in and execute this command...Still this seems a big oversight on the surface of it... Additionally, this necessary step isn't listed at all in either http://pve.proxmox.com/wiki/Installation#Get_Appliance_Templates or in http://pve.proxmox.com/wiki/Installation#Container_.28OpenVZ.29

Should I file a ticket on this?

But in good news I can now get the OpenVZ templates running! It turns out that I just wasn't giving the containers long enough to load. Quite strangely I found that after a while, that the site came up. I was thrown by the fact I couldn't see anything in the console (like you do in eg ESXi) and that it took a while. So now I have the containers coming up and I can use them in both modes of networking. Strangely though in the bridged mode the IP address isn't listed. I had to go into my routers local listing of DHCP IPs and find the matching IP.

root@fritzbox:~# vzlist
      CTID      NPROC STATUS    IP_ADDR         HOSTNAME
       101         51 running   -               zurmo.local
       102         59 running   192.XXX.XXX.88 redmine.local
       103         28 running   192.XXX.XXX.89 wiki.local

So the container 101 is bridged but vzlist doesn't list the IP. Why not? Should I file a ticket on this? I looked around for a registration / login so users can edit the wiki but I didn't find any such registration... Is this correct? are the instructions at http://pve.proxmox.com/wiki/FAQ#How...ing_in_an_OpenVZ_Ubuntu.2FDebian_container.3F still necessary then since it looks like this instance of zurmo is picking up an IP after all?

I'll continue my problems with not being able to get a KVM machine working in a new thread...

Thanks again Raymond for the pointers...

Cheers,
Jas

 

[udo]

...
So the container 101 is bridged but vzlist doesn't list the IP. Why not? Should I file a ticket on this? I looked around for a registration / login so users can edit the wiki but I didn't find any such registration... Is this correct? are the instructions at http://pve.proxmox.com/wiki/FAQ#How...ing_in_an_OpenVZ_Ubuntu.2FDebian_container.3F still necessary then since it looks like this instance of zurmo is picking up an IP after all?

I'll continue my problems with not being able to get a KVM machine working in a new thread...

Thanks again Raymond for the pointers...

Cheers,
Jas

Hi,
how looks your network inside the CT? Do you have configured the network (in /etc/network/interface is you use an debian OS)?

BTW: in bridged mode the host can't see the IP - so the field must be empty.
Look with (from the pve-host console):

vzctl enter 101

About kvm: Is the hardwarevirtualisation enabled in the bios?
What is the output if you start the VM from the console:

qm start VMID

How look the config?

cat /etc/pve/qemu-server/VMID.conf

Udo

 

[Raymond Burns]

With most Virtualization Environments, the host is using a full virtualization of the OS, whereas OpenVZ is more like a shared Virtualization environment. At least, that's my understanding.
When the templates were created, they were created without the tty edit that's needed for console. This has been discussed before, but I'm unsure why it's missing, and what is missing. On the other hand, KVM works similar to most virtual host. The console works immediately, and the network setup is easy to configure. OpenVZ or containers work to help reduce OS overhead, but at a cost of simplicity. This is an additive to most virtualization environment.

Just as a note, I had this issue after things were setup the way I wanted. Aside from the time that Proxmox has set, the localtime or TimeZone must be set in your container. For CentOS, I have to remove /etc/localtime and create the proper symlink to the timezone. This was a tragedy after I had a web calendar set up based on the wrong timezone.

 

[Jas]

Hi Udo,

how looks your network inside the CT?

From inside the vzctl session (BTW is there any difference between this and just sshing into the running VM?)

root@zurmo /# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: venet0: <BROADCAST,POINTOPOINT,NOARP> mtu 1500 qdisc noop state DOWN 
    link/void 
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether 32:e5:8a:9b:4e:28 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.37/24 brd 192.168.178.255 scope global eth0
    inet6 fe80::30e5:8aff:fe9b:4e28/64 scope link 
       valid_lft forever preferred_lft forever

root@zurmo /# more /etc/network/interfaces 
# UNCONFIGURED INTERFACES
# remove the above line if you edit this file

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

root@zurmo /#

About kvm: Is the hardwarevirtualisation enabled in the bios?

I am pretty sure but I will double check again. (I had to enable it for virt-manager when I was trying it out with KVM from a minimal fedora install and I think I had ESXi running on it after that as well...)

What is the output if you start the VM from the console:
Code:
qm start VMID

Ahh... I wanted to know how to do that so I could see the output. So for starting the VM from the command line I get:

root@fritzbox:~# qm start 104
Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
start failed: command '/usr/bin/kvm -id 104 -chardev 'socket,id=qmp,path=/var/run/qemu-server/104.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/104.vnc,x509,password -pidfile /var/run/qemu-server/104.pid -daemonize -name hero -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga cirrus -cpu qemu64,+x2apic -k en-us -m 1024 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -drive 'file=/var/lib/vz/template/iso/ubuntu-12.04.3-desktop-i386.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/104/vm-104-disk-1.qcow2,if=none,id=drive-virtio0,format=qcow2,aio=native,cache=none' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=user,id=net0,hostname=hero' -device 'virtio-net-pci,mac=26:EA:75:CC:9D:39,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1
root@fritzbox:~#

For the conf file I have:

root@fritzbox:~# cat /etc/pve/qemu-server/104.conf
balloon: 512
bootdisk: virtio0
cores: 1
cpu: qemu64
ide2: local:iso/ubuntu-12.04.3-desktop-i386.iso,media=cdrom
memory: 1024
name: hero
net0: virtio=26:EA:75:CC:9D:39
ostype: l26
sockets: 1
virtio0: local:104/vm-104-disk-1.qcow2,size=32G

Thanks Udo!

Cheers,
Jas

 

[Jas]

Hey Raymond!

With most Virtualization Environments, the host is using a full virtualization of the OS, whereas OpenVZ is more like a shared Virtualization environment. At least, that's my understanding.
When the templates were created, they were created without the tty edit that's needed for console. This has been discussed before, but I'm unsure why it's missing, and what is missing.

Ok. I assumed of course others knew about it. Strike me down as another person bitten by this gotcha... And I will move on

On the other hand, KVM works similar to most virtual host. The console works immediately, and the network setup is easy to configure. OpenVZ or containers work to help reduce OS overhead, but at a cost of simplicity. This is an additive to most virtualization environment.

Just as a note, I had this issue after things were setup the way I wanted. Aside from the time that Proxmox has set, the localtime or TimeZone must be set in your container. For CentOS, I have to remove /etc/localtime and create the proper symlink to the timezone. This was a tragedy after I had a web calendar set up based on the wrong timezone.

Actually I just checked and my OpenVZ containers have:

root@fritzbox:~# vzctl enter 101
entered into CT 101
root@zurmo /# more /etc/localtime
TZif2
UTC0

Should I follow the timezone resolution of this forum post or is there something else I should do?

Thanks for your help!

Cheers,
Jas

 

[Jas]

Hi Udo, Raymond,

Actually I just checked again and wrote down the relevent settings from my BIOS:

The machine is a dell OptiPlex 755 with a E6550 @2.33GHz and 4G of ram running the latest BIOS A22 which I flashed onto it in the last couple of weeks. (I am using this machine to experiment around with.)

The BIOS settings that looked possibly relevant are:


Integrated NIC=On
Multiple CPU core=On
Speedstep=On
Virtulization=On
VT For Direct I/O = On
Trusted Execution = On
Limit CPUID Value=Off
TPM Security=Off
Execute Disable=On

Thanks,
Jas

 

[udo]

Hi Udo,

From inside the vzctl session (BTW is there any difference between this and just sshing into the running VM?)

Hi Jas,
sorry I don't have read the first posting good enough. With "vzctl enter" you came in the CT also without working network... In your case the Network is working:

root@zurmo /# ip addr
...
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether 32:e5:8a:9b:4e:28 brd ff:ff:ff:ff:ff:ff
    inet [B]192.168.178.37[/B]/24 brd 192.168.178.255 scope global eth0
    inet6 fe80::30e5:8aff:fe9b:4e28/64 scope link 
       valid_lft forever preferred_lft forever

About the console look here: http://forum.proxmox.com/threads/11...for-OpenVZ-Debian-containers-(V2-2-and-later)

...

Ahh... I wanted to know how to do that so I could see the output.

Right - I mean from the command line (console from the pve-host)

So for starting the VM from the command line I get:

root@fritzbox:~# qm start 104
Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
start failed: command '/usr/bin/kvm -id 104 -chardev 'socket,id=qmp,path=/var/run/qemu-server/104.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/104.vnc,x509,password -pidfile /var/run/qemu-server/104.pid -daemonize -name hero -smp 'sockets=1,cores=1' -nodefaults -boot 'menu=on' -vga cirrus -cpu qemu64,+x2apic -k en-us -m 1024 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -drive 'file=/var/lib/vz/template/iso/ubuntu-12.04.3-desktop-i386.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/104/vm-104-disk-1.qcow2,if=none,id=drive-virtio0,format=qcow2,aio=native,cache=none' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=user,id=net0,hostname=hero' -device 'virtio-net-pci,mac=26:EA:75:CC:9D:39,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1
root@fritzbox:~#

This only happens, when the kernel-module isn't loaded (virtualisation not enabled).
But your bios settings looks ok for me.
Is the installation an standard-installation?

One posibility (but not realy, because ou have checked allready your bios setting): you have updated your kernel but not booted again (so the module don't fit to the running kernel).

What is the output of following commands:

lsmod | grep kvm
insmod /lib/modules/`uname -r`/kernel/arch/x86/kvm/kvm-intel.ko
pveversion -v

Udo

 

[Jas]

Hi Udo,

...
One possibility (but not realy, because ou have checked allready your bios setting): you have updated your kernel but not booted again (so the module don't fit to the running kernel).

What is the output of following commands:

lsmod | grep kvm
insmod /lib/modules/`uname -r`/kernel/arch/x86/kvm/kvm-intel.ko
pveversion -v

Udo

Here is the output

root@fritzbox:~# lsmod | grep kvm
kvm                   325606  0 

root@fritzbox:~# insmod /lib/modules/`uname -r`/kernel/arch/x86/kvm/kvm-intel.ko
Error: could not insert module /lib/modules/2.6.32-23-pve/kernel/arch/x86/kvm/kvm-intel.ko: Operation not supported

root@fritzbox:~# pveversion -v
proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve)
pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-7
qemu-server: 3.1-1
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-10
pve-libspice-server1: 0.12.4-1
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2
root@fritzbox:~#

I have rebooted the proxmox host a number of times... I can try wiping the server and reinstalling proxmox again and seeing if that makes a difference?

Cheers & Thanks,
Jas

 

[udo]

Hi Udo,

Here is the output

root@fritzbox:~# lsmod | grep kvm
kvm                   325606  0 

root@fritzbox:~# insmod /lib/modules/`uname -r`/kernel/arch/x86/kvm/kvm-intel.ko
Error: could not insert module /lib/modules/2.6.32-23-pve/kernel/arch/x86/kvm/kvm-intel.ko: Operation not supported

this shows that the virtualisation is not enabled. For double check the installation do an md5sum on the module.
The output must be the same:

md5sum /lib/modules/2.6.32-23-pve/kernel/arch/x86/kvm/kvm-intel.ko
a3c182f59d5009e5d94f535c237798e0  /lib/modules/2.6.32-23-pve/kernel/arch/x86/kvm/kvm-intel.ko

Try to disable the Virtualisation in the BIOS; boot and enable the virtualisation again after this. (Perhaps you can also try to switch "Execute Disable", but this should not change anything).

root@fritzbox:~# pveversion -v
proxmox-ve-2.6.32: 3.1-109 (running kernel: 2.6.32-23-pve)
pve-manager: 3.1-3 (running version: 3.1-3/dc0e9b0e)
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-7
qemu-server: 3.1-1
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-10
pve-libspice-server1: 0.12.4-1
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.0-2
root@fritzbox:~#

after checking the md5sum you can do an "aptget update" and "aptget dist-upgrade" for the recent kernel (don't forget the reboot).

I have rebooted the proxmox host a number of times... I can try wiping the server and reinstalling proxmox again and seeing if that makes a difference?

Cheers & Thanks,
Jas

No, new installation don't change anything - it's linux not windows

Udo

 

[Jas]

this shows that the virtualisation is not enabled. For double check the installation do an md5sum on the module.
The output must be the same:

md5sum /lib/modules/2.6.32-23-pve/kernel/arch/x86/kvm/kvm-intel.ko
a3c182f59d5009e5d94f535c237798e0  /lib/modules/2.6.32-23-pve/kernel/arch/x86/kvm/kvm-intel.ko

Yep. I can execute this and I get the same thing:

root@fritzbox:~# md5sum /lib/modules/2.6.32-23-pve/kernel/arch/x86/kvm/kvm-intel.ko
a3c182f59d5009e5d94f535c237798e0  /lib/modules/2.6.32-23-pve/kernel/arch/x86/kvm/kvm-intel.ko

after checking the md5sum you can do an "aptget update" and "aptget dist-upgrade" for the recent kernel (don't forget the reboot).

Strangely I am getting what appears to be an error in the apt-get update:

root@fritzbox:~# apt-get update
Hit http://ftp.nz.debian.org wheezy Release.gpg
Hit http://ftp.nz.debian.org wheezy Release             
Hit http://ftp.nz.debian.org wheezy/main amd64 Packages                       
Hit http://ftp.nz.debian.org wheezy/contrib amd64 Packages
Hit http://ftp.nz.debian.org wheezy/contrib Translation-en
Hit http://ftp.nz.debian.org wheezy/main Translation-en 
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://security.debian.org wheezy/updates Release
Hit http://security.debian.org wheezy/updates/main amd64 Packages
Ign https://enterprise.proxmox.com wheezy Release.gpg
Hit http://security.debian.org wheezy/updates/contrib amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib Translation-en
Hit http://security.debian.org wheezy/updates/main Translation-en
Ign https://enterprise.proxmox.com wheezy Release
Err https://enterprise.proxmox.com wheezy/pve-enterprise amd64 Packages
  The requested URL returned error: 401
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-en_US
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-en
W: Failed to fetch https://enterprise.proxmox.com/debian/dists/wheezy/pve-enterprise/binary-amd64/Packages  The requested URL returned error: 401


E: Some index files failed to download. They have been ignored, or old ones used instead.

Try to disable the Virtualisation in the BIOS; boot and enable the virtualisation again after this. (Perhaps you can also try to switch "Execute Disable", but this should not change anything).

I did this. I
1. did all the apt-get updating above, then:
2. Rebooted,
3. dropped into the BIOS settings during boot
4. Changed BIOS settings to: virtulization=OFF, TrustedExecution=OFF, ExecuteDisable=OFF
5. Saved BIOS changes and let a full boot to the command prompt come up.
6. Reboot
7. dropped into the BIOS settings during boot
8. Changed BIOS settings back to: virtulization=ON, TrustedExecution=ON, ExecuteDisable=ON
9. Saved BIOS changes and let a full boot to the command prompt come up again.

Execute the following again:

root@fritzbox:~# insmod /lib/modules/`uname -r`/kernel/arch/x86/kvm/kvm-intel.ko
Error: could not insert module /lib/modules/2.6.32-23-pve/kernel/arch/x86/kvm/kvm-intel.ko: Operation not supported

So still no luck... Should I be trying this on a different computer? (It will not be so easy...)

Thanks Udo!

 

[udo]

...
Strangely I am getting what appears to be an error in the apt-get update:

root@fritzbox:~# apt-get update
...
W: Failed to fetch https://enterprise.proxmox.com/debian/dists/wheezy/pve-enterprise/binary-amd64/Packages  The requested URL returned error: 401


E: Some index files failed to download. They have been ignored, or old ones used instead.

Hi,
that error is normal, because you don't have the enterprise-subscrition. To avoid the harmless message, you can diable the enterprise-repro.

So still no luck... Should I be trying this on a different computer? (It will not be so easy...)

Is the system on a normal sata-disk? Then you can simply put the sata disk to another host and boot - but your network will not work, because the NICs are changed.
For this edit /etc/udev/rules.d/70-persistent-net.rules (or mv on the old system to /etc/udev/rules.d/70-persistent-net.rules-old).

Udo

 

[Jas]

Hi,
that error is normal, because you don't have the enterprise-subscrition. To avoid the harmless message, you can diable the enterprise-repro.
Udo

Ahh... Ok. Got it. Thanks!

Is the system on a normal sata-disk? Then you can simply put the sata disk to another host and boot - but your network will not work, because the NICs are changed.
For this edit /etc/udev/rules.d/70-persistent-net.rules (or mv on the old system to /etc/udev/rules.d/70-persistent-net.rules-old).

Yes. A normal 160G sata drive. Ok this will take a bit... Trying now...

Thanks for the help!

 

[Jas]

Hi,
that error is normal, because you don't have the enterprise-subscrition. To avoid the harmless message, you can diable the enterprise-repro.

Is the system on a normal sata-disk? Then you can simply put the sata disk to another host and boot - but your network will not work, because the NICs are changed.
For this edit /etc/udev/rules.d/70-persistent-net.rules (or mv on the old system to /etc/udev/rules.d/70-persistent-net.rules-old).

Udo

Well I swapped sata drives like you suggested. This time the drive is now in a dell optiplex 755 (this one with a 3 GHz processor).

Once the old drive booted on the new hardware I moved /etc/udev/rules.d/70-persistent-net.rules
to /etc/udev/rules.d/70-persistent-net.rules-old . With this I could access the proxmox host through the web interface. I then tried starting the VM that would not start on the old hardware, and it looks like it starts on the new hardware!

But it look like I can't access it via the console:


The message is:

no connection : Connection timed out
TASK ERROR: command '/bin/nc -l -p 5900 -w 10 -c '/usr/sbin/qm vncproxy 104 2>/dev/null'' failed: exit code 1

Any hints on how to get around this?

Thanks!
Jas

 

[udo]

Well I swapped sata drives like you suggested. This time the drive is now in a dell optiplex 755 (this one with a 3 GHz processor).

Once the old drive booted on the new hardware I moved /etc/udev/rules.d/70-persistent-net.rules
to /etc/udev/rules.d/70-persistent-net.rules-old . With this I could access the proxmox host through the web interface. I then tried starting the VM that would not start on the old hardware, and it looks like it starts on the new hardware!

But it look like I can't access it via the console:
View attachment 1719

The message is:

no connection : Connection timed out
TASK ERROR: command '/bin/nc -l -p 5900 -w 10 -c '/usr/sbin/qm vncproxy 104 2>/dev/null'' failed: exit code 1

Any hints on how to get around this?

Thanks!
Jas

Hi Jas,
this happens, because the java-vnc-viewer take too long for the first start (or you don't have an actual java - but if I remember right you have seen an console before?!).

Simply click on "Reload" inside the Console-Window.

Udo

 

[Jas]

Hi Jas,
this happens, because the java-vnc-viewer take too long for the first start (or you don't have an actual java - but if I remember right you have seen an console before?!).

Simply click on "Reload" inside the Console-Window.

Udo

Ahhh... I don't actually have Java on my normal OSX machine available from the browser. I don't have it installed because of all the perceived security problems... Maybe this is a mistake and java is totally safe but I have seen enough of warnings like this to give me pause...

So I logged into a virtual machine and installed java on that and now I can see the console!!!

I have to say that the warning message:

TASK ERROR: command '/bin/nc -l -p 5900 -w 10 -c '/usr/sbin/qm vncproxy 104 2>/dev/null'' failed: exit code 1

Is a terrible error message. Surely a better error message might be more appropriate here?? Like "Java vnc viewer not found..." or something?

So the next question is can I set things up so that I can use a normal vnc viewer to interact with the machine? Are the instructions here still reasonably up to date: http://pve.proxmox.com/wiki/Vnc_2.0

Also since both dell optiplex 755's have the same BIOS settings is there anything else you would recommend trying to allow proxmox to run on the original machine?

Thanks again for all your help!! (I can honestly say I am not sure how long, or even if, I would have been able to overcome these obstacles...)...

Jas

 

[mir]

So the next question is can I set things up so that I can use a normal vnc viewer to interact with the machine? Are the instructions here still reasonably up to date: http://pve.proxmox.com/wiki/Vnc_2.0

You could also try spice. That way you don't need Java.
http://www.spice-space.org/page/OSX_Client