Hi, Do you need the exact error message (the codes)? I don't want Virtio. I want to boot my image first. As I mentioned I can't use the mergeide.req on the physical machine but I can do anything with the image (if I don't het error messages from the virt-win-reg). I don't know if my restore to iSCSI volume was perfect. There wasn't any error messages and the imag is able to boot until BSOD which means missing system disk. Is that right? First time I choosed SATA type for the image without success and I don't know why. Of course I read many M$ KB. I think my problem is the driver. Or anything else? TIA, Ruzsi
BTW: I checked the image with chkdsk from Win Repair Console. There wasn't any error found. TIA, Ruzsi
On Sat, Jul 11, 2015 at 9:28 AM, Ruzsinszky Attila < ruzsinszky.attila@gmail.com> wrote:> Hi, > > Do you need the exact error message (the codes)? > >The error message "No system disk" means the disk is booting from a KVM perspective so no.> I don't want Virtio. I want to boot my image first. >You already have it seems like.> As I mentioned I can't use the mergeide.req on the physical machine but I > can do anything with the image (if I don't het error messages from the > virt-win-reg). >I don't know if my restore to iSCSI volume was perfect.>It looks liek your restore to the ISCSI volume went well.> There wasn't any error messages and the imag is able to boot until BSOD > which means missing system disk. Is that right? >Correct.> First time I choosed SATA type for the image without success and I don't > know why. > > Of course I read many M$ KB. I think my problem is the driver. Or anything > else? > > TIA, > Ruzsi > > _______________________________________________ > libvirt-users mailing list > libvirt-users@redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users >
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/07/2015 18:28, Ruzsinszky Attila wrote:> Do you need the exact error message (the codes)?Basically, what's required is the "STOP:" line + the image where it fails (so, the line below). Image being likely to be NTOSKRNL.EXE> I don't want Virtio. I want to boot my image first. As I mentioned > I can't use the mergeide.req on the physical machine but I can do > anything with the image (if I don't het error messages from the > virt-win-reg).Well, then, you can mount the image in a Linux machine and use the chntpw tool to edit manually the registry and add the missing driver information? Basically, most you're missing here is linking some hardware classes to proper device (likely intelide.sys) so that your Windows can properly setup its storage stack. - -- Pierre Schweitzer <pierre at reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVoUXeAAoJEHVFVWw9WFsLYcUP/iEuE+B6P1XGZCXT1Bu5gkHA 74/vHvxh+Ko1suvJGq4pxDkeZACB2+yVFaCQAWTLn3kiq70zoZOK0Dl35glwjKDm iQGE/nJYNgxgkOw9YtKyfBwL9yyOQgnRSlsHfrsegTo5E/EEU5m/gzojtLDcN4OC d/lfMOKskvPMZU9x/rPstpdh1mWpgowxanS3ucMB/zUEy3VV1IVN9XGQHYLKLJzr 2QJTkVNZJ3xkmt++MEcCkq1jqSIA6iALFPSLeLxea9NAU6AZ5fnrJ4HEenroNFZw KznhOG+cMh4mIJCKTj7RLd1UGpvYCd3I/0BlfPeezrPk6PCAJXNBN3DeJQ5nULDd TRXiIOqcxuaKxHhROupO6VN4zXKoCrF0LpxM+0XkhJDG5TJLZsvCRZSysQoak1vi lWfqMMi9HuLK2JuQwkv0QzK7WyD00o2n8tzuqZQhJGqk8kk9eBWi4+TkdOa3myho rRtlndgIlw7O96a5NQIaz0Vfr92G6OP10SG/gYjPsDsgKjUjOytV7Oo8Q+DzdrHG WSXFRMx2ntO2MRqTyQOXQRXza4A0gC4Skx7Jj5CcLGkGj8zqIs1wmsS0sdxZBdf4 ziy1rukWqG7lOAP2hdJYgopyhcL6VF5sRlAt8ifIJsTA2EsmK30g6OusVIzsZiUU XN5x4wUY2dMbnyV5tUW1 =YFMq -----END PGP SIGNATURE-----
Hi, Do you need the exact error message (the codes)?>> >> > The error message "No system disk" means the disk is booting from a KVM > perspective so no. >Wait a moment! There isn't any text format error messages! So no explicite "No system disk", either. There are long hexa codes. One of them is 0x0...7b if I remember well and the machine always reboot (of course I can disable automatic reboot).> >> I don't want Virtio. I want to boot my image first. >> > > You already have it seems like. >Yes, I found a howto about virtio and I tried to use it. In the 1st time I choosed SATA.> As I mentioned I can't use the mergeide.req on the physical machine but I >> can do anything with the image (if I don't het error messages from the >> virt-win-reg). >> > I don't know if my restore to iSCSI volume was perfect. >> > > It looks liek your restore to the ISCSI volume went well. >Nice. ;-)> There wasn't any error messages and the imag is able to boot until BSOD >> which means missing system disk. Is that right? >> > > Correct. >OK.My diagnostic is almost perfect (with Google help). TIA: Ruzsi
Hi, The error line is: *** STOP: 0x0000007B (0xF789AA94, 0xC0000034, 0x00000000, 0x00000000) Nothing more! (Of course there are some inrelevant text line about chkdsk, etc.)> Basically, what's required is the "STOP:" line + the image where it > fails (so, the line below). Image being likely to be NTOSKRNL.EXE >Nothing about NTOSKRNL.EXE on the blue screen!> > I don't want Virtio. I want to boot my image first. As I mentioned > > I can't use the mergeide.req on the physical machine but I can do > > anything with the image (if I don't het error messages from the > > virt-win-reg). > > Well, then, you can mount the image in a Linux machine and use the > chntpw tool to edit manually the registry and add the missing driver > information? >Yes, I think.> Basically, most you're missing here is linking some hardware classes > to proper device (likely intelide.sys) so that your Windows can > properly setup its storage stack. >I think this is the problem. How can we solve it? TIA, Ruzs