[SOLVED] debian jessie kvm installation

not to discuss here, but there is no anything like gluster or ceph production ready. These technologies are young. So at this point I would say, that gluster is mature enough if you exactly know, what you need.
May be ceph got some advantages, but it is definitely much more slower. So just have to stick to one of them and wait for another to die :) RH won't develop both of them.
 
Okay,
It seems that only nodes with I210 are effected. But why only with D8? And there is lots of stuff about this NIC and igb driver. Going to investigate it further.
Any comments?
 
No, it is not I210 issue.
I'm still not able to install jessie as VM on proxmox. Upgraded glusterfs to 3.6.4, still same problem on every proxmox node and does not matter really is it HA or DISTR volume. Today installation of Ubuntu 14.04 LTS with Mate went just fine. So it seems like Debian8 problem...
Could you guys from devs team just create a simple lab and give it a test?

Use GlusterFS as storage backend and try to install debian8 as VM guest. I really want to solve this problem.
 
here is one of the errors example. its like files that debian installer copies to the virtual disk that is located on glusterfs storage are getting corrupted.
in-target is /dev/vda1
 

Attachments

  • debian.png
    debian.png
    86.3 KB · Views: 9
I tried it now on my systems and I noticed some delays when installing debian8 on glusterfs when using virtio. After using iscsi it seems ok to me. Maybe it could help to change cache or drive settings? Anyway, I can only use vm on glusterfs when using cache write through.
 
How your glusterfs is configured? you add storage via promox GUI or from console? I do not use caching for any VM and they run well.
But thanks for sharing your experience. Could you describe you setup please?
 
I added storage through GUI. I have two servers mirroring data for other hosts via gluster and ceph. My config follows some howtos on proxmox wiki and other sources:
Code:
Volume Name: virtual
Type: Replicate
Volume ID: c18748c4-b9f6-45a5-8f51-e7a4c1e32cb0
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: cl1.ucl:/big/gluster/virtual
Brick2: cl2.ucl:/big/gluster/virtual
Options Reconfigured:
performance.write-behind: off
server.allow-insecure: on
diagnostics.brick-log-level: WARNING
diagnostics.client-log-level: WARNING
nfs.enable-ino32: on
nfs.addr-namelookup: off
nfs.disable: on
performance.cache-max-file-size: 2MB
performance.cache-refresh-timeout: 4
performance.cache-size: 256MB
performance.write-behind-window-size: 4MB
performance.io-thread-count: 32
 
thanx.
these two seem to me weird:

performance.write-behind: off
performance.write-behind-window-size: 4MB

if its off why you specify its window-size?
but well, it does not matter anyway. Doesn't seem like some of these options could really affect something
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!