Once upon a time, without Windows or HVM being in the picture, I had
to use the true path instead of the LVM path (I don't have any LVM machines
to reference, but it was more like /dev/lvm/volgroups/volgroup00/logvol01
instead of /dev/volgroup00/logvol01. Don't get caught up on the
/lvm/volgroups/ reference, it is an example, I honestly don't remember what
the real path was at all. However, you might try this if you haven't, there
could be some problem with links (sym and/or hard), I have certainly read
about problems with symlinks. I have also read about problems with LVM
partitions for Windows HVMs, but I thought that was only with GPLPV drivers.
Dustin
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Pim van Riezen
Sent: Monday, October 06, 2008 09:37
To: Ross Walker
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Xen3.1 and win2k8 hvm: lvm-backed disk sized 0
bytes
On Oct 6, 2008, at 15:33 , Ross Walker wrote:
> Try creating a blank mbr on the lv with fdisk first.
>
> # fdisk /dev/vpsvg-006/win2k8
>
> Just 'w' write out an empty one then try to run install again.
I already went over it with fdisk. Even tried creating a full
partition table on the volume with an NTFS partition. Windows keeps
reporting it as a 0.0 MB drive.
Pi
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home