On the side note, i forgot to say that i can boot if i pass /dev/sde to
qemu, which according to redhat documentation is not what one is suppose to
do as it can compromise the host system.


2016-04-19 19:55 GMT+02:00 thibaut noah <thibaut.n...@gmail.com>:

> Hi guys, so i made the jump today !
>
> I backed up my windows 10 qcwo2 container on another hdd, then i booted my
> guest with the backup with thebackup.
> I  passed to the vm the ssd i used before to store my vm container as a
> block device (passing /dev/sde instead of /dev/sde1, this way i could
> remove all linux partitionning from within windows and do a native install)
>
> From there i used acronis true image to clone my windows install to the
> ssd.
>
> So now that it is done i try to boot my vm from the biggest partition on
> the ssd which i assume is what i want do to?
>
> this is what i got with lsblk for the ssd :
> sde            8:64   0   477G  0 disk
> ├─sde1         8:65   0   128M  0 part
> ├─sde2         8:66   0   450M  0 part
> ├─sde3         8:67   0    99M  0 part
> └─sde4         8:68   0 476.3G  0 part
>
> and this is how i passed the block device to the vm :
>
>     <disk type='file' device='disk'>
>       <driver name='qemu' type='raw' cache='none'/>
>       <source file='/dev/sde4'/>
>       <target dev='vdb' bus='virtio'/>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x06'
> function='0x0'/>
>     </disk>
>
> My problem is after launching the guest i found myself back to the uefi
> shell.
> So, can someone enlighten me on what is wrong here and what path should i
> take to fix this?
> Thanks
>
_______________________________________________
vfio-users mailing list
vfio-users@redhat.com
https://www.redhat.com/mailman/listinfo/vfio-users

Reply via email to