Adding disk device to Windows VM in Incus 6.19

Incus
1

Hi,

I upgraded to Incus from 6.15 to 6.19.1 today and it now seems I can no longer share a disk between host and guest with a command like:

incus config device add winvm workspace disk source=$PWD path=FOO

Previously this would share the current host directory with the Windows VM appearing as Z:\

For a Linux container this still works.

2

Does your Windows VM have WinFSP and the virtiofs service enabled?

3

Yes it does. Images were created using GitHub - antifob/incus-windows: Toolset for creating Windows images for Incus

They have been working well for a long time now, until today.

Has something changed with 6.19 in this area?

4

6.15 to 6.19 is quite the wide gap so quite a bit may have happened :slight_smile:
What distribution is that on?

Can you also confirm that the Windows VM has image.os set to something that starts with Windows or windows?

5

Debian 12 host

I saw the recent change with incus agent for windows and thought I’d try setting image.os to Windows. I set it on the VM image is that correct?

incus image set-property windows/11e/robot image.os Windows

Then launched my VM from that image.

When I run incus config device add winvm agent disk source=agent:config I get a D: but it seems to be the linux agent as there is an install.sh

6

Ok, I set the VM instance config image.osto Windows

incus config set winvm image.os Windows

and all is working again now :grinning_face:

Thanks @stgraber

7

Excellent!

8

@stgraber is the value case sensitive, does it have to be Windows, windows or either?

9

It’s case insensitive and only needs the prefix, so you can do Windows 2025 Datacenter or windows 11 and they should work fine.

1 Like
10

If you want to set the property on the image, you need to name the property os, not image.os! Otherwise when the instance is created, it becomes image.image.os :slight_smile: