Enable Virtio block device https://www.softaculous.com/board/index.php?tid=7356 <![CDATA[Enable Virtio block device]]> https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p28090 1. Let us take all the risks about enabling/disabling virtio for disk.
I don't care about disk naming because I need this feature for such scenario:
- Client bought VPS with linux and virtio.
- Then he decided to install windows/mikotik/any other os without virtio.
So why should I care if disk will become hda or blablabla? :)
2. If you worry about your customers - make configurable option which is disabled by default. So this will not affect hosts which don't care.
3. SolusVM has this feature with no problems at all. Was SolusVM customer for more then 1 year.
4. There are no any security reasons for disabling this.

]]> Tue, 29 Sep 2015 22:50:41 GMT https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p28090 <![CDATA[Enable Virtio block device]]> https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25568
Quote From : alons March 30, 2015, 3:25 pm
Quote From : mitgib March 30, 2015, 12:07 pm
Quote From : alons March 30, 2015, 11:56 am


When Virtio is disabled many a times, the VPS would not boot as the VPS disk name changes accordingly i.e. from /dev/sda to /dev/vda.

Hence it was better to disable virtio rather than have complaints for a VPS not booting after virtio is enabled/disabled.
We infact had many tickets about this and hence we disabled the option while editing.


You have not listed anything about security, your initial reason for not making the option editable.

You have only listed support issues.

2.6.32 RHEL kernels and Ubuntu and Debian auto sense virtio.  The ability to change between virtio is a feature SolusVM has had for years.  You need to stay consistent with your story, as what I am seeing here is amature backpeddling.


Hi,

Its definitely not a security issue. I guess Asim used the term wrongly.
The issue is that a VPS fails to boot if virtio is enabled and one disables it.
I guess we can have an option to enable it, but not disable it.
What do you think ?

Regards


Making it so I can enabled it would be a start. I am avoiding Virtualizor right now as without this, I cannot migrate 40 nodes worth of clients and convert them to sparse files as I update the node to Ubuntu.  I am looking at a large job, so a little help from your side would go a long way. 



]]> Mon, 30 Mar 2015 15:31:30 GMT https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25568 <![CDATA[Enable Virtio block device]]> https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25566
Quote From : mitgib March 30, 2015, 12:07 pm
Quote From : alons March 30, 2015, 11:56 am


When Virtio is disabled many a times, the VPS would not boot as the VPS disk name changes accordingly i.e. from /dev/sda to /dev/vda.

Hence it was better to disable virtio rather than have complaints for a VPS not booting after virtio is enabled/disabled.
We infact had many tickets about this and hence we disabled the option while editing.


You have not listed anything about security, your initial reason for not making the option editable.

You have only listed support issues.

2.6.32 RHEL kernels and Ubuntu and Debian auto sense virtio.  The ability to change between virtio is a feature SolusVM has had for years.  You need to stay consistent with your story, as what I am seeing here is amature backpeddling.


Hi,

Its definitely not a security issue. I guess Asim used the term wrongly.
The issue is that a VPS fails to boot if virtio is enabled and one disables it.
I guess we can have an option to enable it, but not disable it.
What do you think ?

Regards]]> Mon, 30 Mar 2015 15:25:08 GMT https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25566 <![CDATA[Enable Virtio block device]]> https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25564
Quote From : alons March 30, 2015, 11:56 am


When Virtio is disabled many a times, the VPS would not boot as the VPS disk name changes accordingly i.e. from /dev/sda to /dev/vda.

Hence it was better to disable virtio rather than have complaints for a VPS not booting after virtio is enabled/disabled.
We infact had many tickets about this and hence we disabled the option while editing.


You have not listed anything about security, your initial reason for not making the option editable.

You have only listed support issues.

2.6.32 RHEL kernels and Ubuntu and Debian auto sense virtio.  The ability to change between virtio is a feature SolusVM has had for years.  You need to stay consistent with your story, as what I am seeing here is amature backpeddling.]]> Mon, 30 Mar 2015 12:07:04 GMT https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25564 <![CDATA[Enable Virtio block device]]> https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25563
Quote From : ZXHost March 25, 2015, 9:28 pm
Quote From : mitgib March 25, 2015, 8:19 am
Quote From : asim_shaikh March 25, 2015, 5:49 am
Hi,

Virtio can be enabled for block device in virtualizor while creating the VPS in the advance options, however  we have disabled it while editing the VPS for security reasons.


Provide your source for security concerns, I cannot find any unresolved bugs in the past 5 years for this.  Only old bugs were for large >1.5TB qcow2 but was resolved in qemu-kvm 0.12.5


I would also be interested in the reason behind this, I can understand maybe a warning message for example if it's a Windows OS without Virtio drivers.


When Virtio is disabled many a times, the VPS would not boot as the VPS disk name changes accordingly i.e. from /dev/sda to /dev/vda.

Hence it was better to disable virtio rather than have complaints for a VPS not booting after virtio is enabled/disabled.
We infact had many tickets about this and hence we disabled the option while editing.]]> Mon, 30 Mar 2015 11:56:01 GMT https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25563 <![CDATA[Enable Virtio block device]]> https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25496
Quote From : mitgib March 25, 2015, 8:19 am
Quote From : asim_shaikh March 25, 2015, 5:49 am
Hi,

Virtio can be enabled for block device in virtualizor while creating the VPS in the advance options, however  we have disabled it while editing the VPS for security reasons.


Provide your source for security concerns, I cannot find any unresolved bugs in the past 5 years for this.  Only old bugs were for large >1.5TB qcow2 but was resolved in qemu-kvm 0.12.5


I would also be interested in the reason behind this, I can understand maybe a warning message for example if it's a Windows OS without Virtio drivers.]]> Wed, 25 Mar 2015 21:28:30 GMT https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25496 <![CDATA[Enable Virtio block device]]> https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25492
Quote From : asim_shaikh March 25, 2015, 5:49 am
Hi,

Virtio can be enabled for block device in virtualizor while creating the VPS in the advance options, however  we have disabled it while editing the VPS for security reasons.


Provide your source for security concerns, I cannot find any unresolved bugs in the past 5 years for this.  Only old bugs were for large >1.5TB qcow2 but was resolved in qemu-kvm 0.12.5]]> Wed, 25 Mar 2015 08:19:20 GMT https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25492 <![CDATA[Enable Virtio block device]]> https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25490
Virtio can be enabled for block device in virtualizor while creating the VPS in the advance options, however  we have disabled it while editing the VPS for security reasons.
]]> Wed, 25 Mar 2015 05:49:53 GMT https://www.softaculous.com/board/index.php?tid=7356&tpg=1#p25490 <![CDATA[]]> https://www.softaculous.com/board/index.php?tid=7356&tpg=0#p25455
Also tried testing out moving a container from SolusVM to Virtualizor, so I made a dd .img file which I moved over to Virtualizor then virt-sparcify --convert to qcow2, this is an older CentOS 5 install that had virtio enabled for block and network, but only seeing network while viewing lspci

Code

[root@dns2 ~]# lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01)
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:02.0 VGA compatible controller: Cirrus Logic GD 5446
00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
00:04.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 01)
00:05.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon
]]> Mon, 23 Mar 2015 02:02:50 GMT https://www.softaculous.com/board/index.php?tid=7356&tpg=0#p25455