[virt-tools-list] Connecting to a physical drive

[Blake McBride]

After hours of updates and installs, the VM wouldn't boot anymore.  After
two 12+ hour days, I have given up.  Today I installed VirtualBox and tried
it there.  Everything installed and ran perfectly without a single
problem.  Was able to use the raw drive in minutes.  Never a boot problem.
Install went very fast.

Being a long-time user of KVM, my takeaway is that KVM works well with
Linux.  I seem to have pretty good luck with 32 bit Windows too.  64 bit
Windows support is not ready for prime time.

Thanks.

Blake


On Thu, Jan 1, 2015 at 12:35 PM, Blake McBride <blake1024 at gmail.com> wrote:

> Found the problem.  If you wait a couple of hours - it works.  After it
> reboots, it's fine.
>
> On Thu, Jan 1, 2015 at 10:32 AM, Blake McBride <blake1024 at gmail.com>
> wrote:
>
>> I'd like to add that the drive (/dev/sdb) initially had no partition
>> table.  I rebooted the VM.  The next time around, the drive had a partition
>> table so it seems it can write to the drive.  Still stuck at "Copying
>> Windows files" though.
>>
>> On Thu, Jan 1, 2015 at 10:29 AM, Blake McBride <blake1024 at gmail.com>
>> wrote:
>>
>>> Thanks.  I tried booting the real machine with the Windows CD and it can
>>> see the drives (i.e. shouldn't need any additional drivers).  I then
>>> created a new VM with KVM.  I tried numerous drive types (SCSI, Virtio SCSI
>>> Disk, Virtio SCSI Lun, Virtio Disk) that did not work, but SATA Disk did!
>>>  when I set the VM to SATA Disk the install sees it.  I selected the disk
>>> and told Windows to install there.  It accepted the selection and went to
>>> the next screen.  The problem now is that it stays on:
>>>
>>> Copying Windows files (0%) ...
>>>
>>> forever.  It is hung there.
>>>
>>> Any suggestions would be greatly appreciated.
>>>
>>> Thanks.
>>>
>>> Blake McBride
>>>
>>>
>>> On Wed, Dec 31, 2014 at 6:51 PM, Richard W.M. Jones <rjones at redhat.com>
>>> wrote:
>>>
>>>> On Wed, Dec 31, 2014 at 11:58:06AM -0600, Blake McBride wrote:
>>>> > Greetings,
>>>> >
>>>> > I am using Virtual Machine Manager on a 64 bit LinuxMint 17.1 host.
>>>> The
>>>> > host has a second physical SCSI drive (/dev/sdb) that I want a
>>>> Windows 7 VM
>>>> > to use.  I am booting from a CDROM ISO image.  The system boots fine
>>>> but
>>>> > the Windows installs keeps saying that it sees no hard disk.
>>>> >
>>>> > The host is a local / desktop machine with X.
>>>> >
>>>> > What I have tried so far:
>>>> >
>>>> > 1.  Under Managed or other existing storage I put:
>>>> > /dev/sdb
>>>> > Device Type:  SCSI
>>>> > cache mode: default
>>>> > Storage format raw
>>>> >
>>>> > I made sure I had write access to that device:
>>>> > chmod 666 /dev/sdb
>>>> >
>>>> > I also tried:  chown me /dev/sdb
>>>> >
>>>> > 2.  Under Connection Details / storage I added
>>>> > Storage pool type:  disk
>>>> > Target path:  /dev
>>>> > Source path: /dev/sdb
>>>> > Volume name: sdb
>>>> > Max capacity:  465GB
>>>> > Allocation:  465GB
>>>> >
>>>> > I have tried everything I can think of but the Windows install keeps
>>>> saying
>>>> > no storage device.
>>>>
>>>> You'd be better off using the libvirt tools to see how the disk
>>>> is being passed to the guest, ie:
>>>>
>>>> virsh dumpxml guestname
>>>> virsh edit guestname
>>>>
>>>> Most likely Windows doesn't have the right driver but it's
>>>> hard to tell without seeing the libvirt XML.
>>>>
>>>> Rich.
>>>>
>>>>
>>>> --
>>>> Richard Jones, Virtualization Group, Red Hat
>>>> http://people.redhat.com/~rjones
>>>> Read my programming and virtualization blog: http://rwmj.wordpress.com
>>>> virt-df lists disk usage of guests without needing to install any
>>>> software inside the virtual machine.  Supports Linux and Windows.
>>>> http://people.redhat.com/~rjones/virt-df/
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/virt-tools-list/attachments/20150102/8d09b4bc/attachment.htm>