Search results

@e100 I think this might be a unrelated issue that you have there. Problems that people have is that without any evidence on host the virtio_scsi will cause corruption of data between guest-disk ... Also logs will "just end" if you have a kernel panic within guest, I think the best way for...

Just FYI I can reproduce this without any FS, just by having DD write data to passed through disk in VM. ps. I've received an email few days ago from proxmox to root at my company domain that is diverted to my mailbox ... and it let me know that there was a smart discovered bad sector on...

Yep - I discovered it on btrfs and then was able to replicate it with dd directly to disk device :/ But it seems here that if it's not following "the ceph of lvm way" it's not worth the bother - even devs can't commit to test it as described in original post ... they use network iscsi :/ Can...

Just FYI, (since I've had few hours free in new year) when downgrading kernel to version used on proxmox 4.3 it's all the same :/ uname -a Linux proxmox-dl180-14bay-2 4.4.19-1-pve #1 SMP Wed Sep 14 14:33:50 CEST 2016 x86_64 GNU/Linux So bottom line is that irrespective of hardware...

In terms of logs - nothing on host :/ In terms of your passthrough logic - you are slightly wrong, if you use virtio_scsi_pci with image backing it will emulate SCSI for you (actually using a separate thread for it OR thread per device), if you actually connect to real device qemu will pass...

@manu first of all you are not passing a real disk (at least it does not look like that from your example), second of all have you got that: cpu: host scsihw: virtio-scsi-pci S.M.A.R.T. is continuously monitored on all drives and there is no problem with any of them (even level of helium on...

pveversion -v proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve) pve-manager: 4.4-2 (running version: 4.4-2/80259e05) pve-kernel-4.4.35-1-pve: 4.4.35-76 pve-kernel-4.4.19-1-pve: 4.4.19-66 lvm2: 2.02.116-pve3 corosync-pve: 2.4.0-1 libqb0: 1.0-1 pve-cluster: 4.0-48 qemu-server: 4.0-102...

Local disks (sata / sas) passed through directly to VM: scsi_hw:virtio_scsi_pci (or _single, gives same issue with 4.4) scsiX: /dev/disk/by-id/disk_name,size=XYZ In guest operating system any FS on this device can go: etx3, etx4, xfs, btrfs (this is what I mean by passing on disk directly to...

Nobody ? Seriously nobody is bothered that most important milestone of pravirtualisation is broken for no good reason in new proxmox ... and nobody in proxmox is bothered that proxmox took a giant step back ?

Hi folks, I was successfully using proxmox 4.3 with hard drives passed to VM's with virtio_scsi (both single & pci) without any issue and with any mix of configuration flags (aio, threads, ect ect). After upgrading to 4.4 all VM's corrupted their file systems on passthrough disks (fun). Right...