Hi,

We try to connect usb harddrive to windows 7 hvm, but unfortunately cannot attach or read by windows 7.

dom0 ~]$ qvm-block
...
dom0:sde1 MQ01ABD100 (Data) 443 GiB

when we do qvm-block to add it error messages appear :
dom0 ~]$ qvm-block -a win7 dom0:sde1
ERROR: Timeout while waiting for block defice connection             <-- yes it was 'defice' not typo, correctly is 'device'

check again its that attach correctly
dom0 !]$ qvm-block
...
dom0:sde1 MQ01ABD100 (Data) 443 GiB (attached to 'win7' as 'xvdi')

but, on Qubes manager the device are attached and can't be detached..
Only showing the bubble messages
win7 - detaching dom0:sde1

but, it wasn't

also we do detach manual from command still can't detach
dom0 ~]$ qvm-block -d dom0:sde1

quickly go to shell again, when we check:

dom0 ~]$ qvm-block
...
dom0:sde1 MQ01ABD100 (Data) 443 GiB (attached to 'win7' as 'xvdi')

still attached.



Sometimes, Qubes Manager doesn't know what kind device are attached although the QM already shutdown and restart.

How to attach the usb harddrive to windows 7 hvm correctly ?

Hi Rafal

Unfortunately, i'm not install for Qubes Tools for Windows, due to after installation windows 7 wont boot or looping boot.

any other options ?

On Tue, Feb 17, 2015 at 01:17:39AM -0800, Manz Tiha wrote:
> Hi Rafal
>
> Unfortunately, i'm not install for Qubes Tools for Windows, due to after
> installation windows 7 wont boot or looping boot.
>
> any other options ?

If so, the only option is to attach the disk in VM settings (advanced
tab) before VM startup.

--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

On 2015-02-17 10:17, Manz Tiha wrote:
> Hi Rafal
>
> Unfortunately, i'm not install for Qubes Tools for Windows, due to after
> installation windows 7 wont boot or looping boot.
>
> any other options ?
>

Did you try version 2.4.2-1 of the tools published recently? It fixes
problems with the previous build.

Hi,

We already install the QWT with 2.4.2-1 version and it was successful. and running seamless mode.

And we can attach the external hdd to the Windows, but, i think this still have the problem.

in qvm-blocks listed as :

dom0:sde MQ01ABD100 () 931 GiB
dom0:md127 () 0 B
dom0:sde2 MQ01ABD100 (Data2) 443 GiB
dom0:sde1 MQ01ADB100 (Data) 488 GiB
dom0:md126p4 () 1024 G
dom0:md126p2 (System_Reserved) 100 MiB
dom0:md126p1 (Recovery) 11 GiB

but on Qubes Manager when we try to attach the device, the device only listed as :

dom0:sde 931 GiB ()
dom0:md127 0 B ()
dom0:md126p4 1024 G ()
dom0:md126p2 100 MiB (System_Reserved)
dom0:md126p1 11 GiB (Recovery)

My Question, where is :
dom0:sde2 MQ01ABD100 (Data2) 443 GiB
dom0:sde1 MQ01ADB100 (Data) 488 GiB

Then, when we attach on Qubes Manager to dom0:sde 931 GiB () successfull attached to my appVM (win7)
Because of 931 GiB it have 2 partitions on it, so on appVM only mounted dom0:sde1

Why qubes can't recognize 2 partition when we mount by Qubes Manager dom0:sde only ?

its a bugs or by design ?

I can't take the screen shot for Qubes Manager with device menu poped up.

Thanks
Man'z

Sorry typo:
...

dom0:sde2 MQ01ABD100 (Data2) 443 GiB

dom0:sde1 MQ01ABD100 (Data) 488 GiB
...

This is by design - many tool do not handle nicely device without
partition table (this is what you'll got when you attach partition
directly). So GUI tool provides only the safe way. If you want to attach
individual partition, you'll need to use qvm-block tool.

Both Linux and Windows you show you both partitions in this case.