subject:"\[partitionmanager\] \[Bug 378607\] virtio devices not found \(vda\)"

[partitionmanager] [Bug 378607] virtio devices not found (vda)

2017-06-28 Thread Harald Sitter

https://bugs.kde.org/show_bug.cgi?id=378607 --- Comment #13 from Harald Sitter --- Git commit 984a4e9acee45dca1aa5bcc69294b536930a20c2 by Harald Sitter. Committed on 28/06/2017 at 11:51. Pushed by sitter into branch 'master'. fix device RO check Summary: - mark deviceNode const

[partitionmanager] [Bug 378607] virtio devices not found (vda)

2017-06-21 Thread Andrius Štikonas

https://bugs.kde.org/show_bug.cgi?id=378607 Andrius Štikonas changed: What|Removed |Added Status|VERIFIED|RESOLVED Latest

[partitionmanager] [Bug 378607] virtio devices not found (vda)

2017-06-21 Thread Andrius Štikonas

https://bugs.kde.org/show_bug.cgi?id=378607 Andrius Štikonas changed: What|Removed |Added Version Fixed In||kpmcore 3.2.0 ---

[partitionmanager] [Bug 378607] virtio devices not found (vda)

2017-06-21 Thread Harald Sitter

https://bugs.kde.org/show_bug.cgi?id=378607 --- Comment #10 from Harald Sitter --- Created attachment 106210 --> https://bugs.kde.org/attachment.cgi?id=106210=edit lsblk -a -O output -- You are receiving this mail because: You are watching all bug changes.

[partitionmanager] [Bug 378607] virtio devices not found (vda)

2017-06-21 Thread Harald Sitter

https://bugs.kde.org/show_bug.cgi?id=378607 --- Comment #9 from Harald Sitter --- Created attachment 106209 --> https://bugs.kde.org/attachment.cgi?id=106209=edit lsblk -a output I am also attaching lsblk output for reference -- You are receiving this mail because: You are

[partitionmanager] [Bug 378607] virtio devices not found (vda)

2017-06-21 Thread Harald Sitter

https://bugs.kde.org/show_bug.cgi?id=378607 Harald Sitter changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #8 from

[partitionmanager] [Bug 378607] virtio devices not found (vda)

2017-06-20 Thread Andrius Štikonas

https://bugs.kde.org/show_bug.cgi?id=378607 --- Comment #7 from Andrius Štikonas --- Looks like it might be possible to improve device detection by looking at lsblk's TYPE column and check for "disk". Then we can avoid using major numbers entirely. I'll try to do this later

[partitionmanager] [Bug 378607] virtio devices not found (vda)

2017-06-20 Thread Andrius Štikonas

https://bugs.kde.org/show_bug.cgi?id=378607 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED

[partitionmanager] [Bug 378607] virtio devices not found (vda)

2017-06-20 Thread Andrius Štikonas

https://bugs.kde.org/show_bug.cgi?id=378607 --- Comment #5 from Andrius Štikonas --- Looks like virtio can use various device numbers often in the range 240-254 (https://lkml.org/lkml/2016/3/2/930) In principle I can add the whole range to whitelist. Any better solutions?

[partitionmanager] [Bug 378607] virtio devices not found (vda)

2017-06-20 Thread Andrius Štikonas

https://bugs.kde.org/show_bug.cgi?id=378607 --- Comment #4 from Andrius Štikonas --- Hmm, I was told virtio major device number is 253. But when I'm trying here locally I see 252. What does lsblk report to you? -- You are receiving this mail because: You are watching all

[partitionmanager] [Bug 378607] virtio devices not found (vda)

2017-06-20 Thread Harald Sitter

https://bugs.kde.org/show_bug.cgi?id=378607 --- Comment #3 from Harald Sitter --- Created attachment 106187 --> https://bugs.kde.org/attachment.cgi?id=106187=edit screenshot -- You are receiving this mail because: You are watching all bug changes.