12:28 a.m.
Hi,
I made a disk image with CloneZilla from the original physical machine.
That image was restored on an iSCSI volume.
It isn't booting. I got BSOD.
I tried IDE, SATA, SCSI disk type without any success.
I tried to using virtio driver and if I use my image+W2k3 install CD+virtio
VFD the Windows repair console see the disk and I can use the repair
console with my image but the windows not start
(or not booting because the system disk can't be seen by original
"registry").
The drivers from virtio VFD image were copied to Windows' Driver directory
manually.
I tried to use virt-win-reg:
rattila@amd1:~$ virt-win-reg SJ-SIMISPC
/dev/disk/by-path/<iSCSI-path>:simispc-lun-2: Engedély megtagadva at
/usr/bin/virt-win-reg line 260.
(it means: Permission denied.)
What can I do changing the original driver to virtio (or IDE/SATA/SCSI in
KVM)?
I can't do anything with the physical machine so the only option is playing
with the disk image.
TIA,
Ruzsi
12:40 a.m.
- What format is the image is?
- Can you post an XML file of the VM config?
Changing the driver to VirtIO via registry edits may exacerbate the
problem. I've never done this but wouldn't it make sense to stick to the
more supported IDE drive emulation until you get it booted and thus remove
possible variables of it not booting?
Are you able to boot the image any other way?
On Sat, Jul 11, 2015 at 8:28 AM, Ruzsinszky Attila <
ruzsinszky.attila(a)gmail.com> wrote:
12:51 a.m.
Hi,
Thanks for your prompt answer!
I don't know the format of the image. It was made by CloneZilla. Is that
then a raw image?
Of course I can post the XML of the VM config.
I tried out all of the possibilities: IDE, SATA, SCSI and Virtio.
The image was taken from a SATA hardware which is a normal Intel chipset.
(I can check
the real machine again, if it is important).
I don't know whether the image booting or not. :-( How can I check it? The
boot process is
working because I can see the BSOD screen and the no system disk error
message.
Any ideas would be appreciated!
TIA,
Ruzsi
2015-07-11 17:40 GMT+02:00 Jeff Tchang <jeff.tchang(a)gmail.com>:
12:56 a.m.
Hi,
Here is the XML file of the my VM:
<!--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
OVERWRITTEN AND LOST. Changes to this xml configuration should be made
using:
virsh edit SJ-SIMISPC
or other application using the libvirt API.
-->
<domain type='kvm'>
<name>SJ-SIMISPC</name>
<uuid>b503aeb4-23e6-8c99-cce2-67c36558b950</uuid>
<memory unit='KiB'>1048576</memory>
<currentMemory unit='KiB'>1048576</currentMemory>
<vcpu placement='static'>1</vcpu>
<os>
<type arch='i686' machine='pc-i440fx-trusty'>hvm</type>
<boot dev='hd'/>
<bootmenu enable='yes'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/kvm-spice</emulator>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/kvm-img/isok/Windows_2003_Server.iso'/>
<target dev='hdc' bus='ide'/>
<readonly/>
<address type='drive' controller='0' bus='1'
target='0' unit='0'/>
</disk>
<disk type='block' device='disk'>
<driver name='qemu' type='raw'/>
<source
dev='/dev/disk/by-path/ip-192.168.52.142:3260-iscsi-iqn.2015-06.hu.mavrt.bbf.fc.amd2:simispc-lun-2'/>
<target dev='vda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x07'
function='0x0'/>
</disk>
<disk type='file' device='floppy'>
<driver name='qemu' type='raw'/>
<source file='/kvm-img/isok/virtio-win-drivers-20120712-1.vfd'/>
<target dev='fda' bus='fdc'/>
<address type='drive' controller='0' bus='0'
target='0' unit='0'/>
</disk>
<controller type='usb' index='0'>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x01'
function='0x2'/>
</controller>
<controller type='pci' index='0' model='pci-root'/>
<controller type='ide' index='0'>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x01'
function='0x1'/>
</controller>
<controller type='fdc' index='0'/>
<filesystem type='mount' accessmode='passthrough'>
<source dir='/kvm-other'/>
<target dir='/source'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x05'
function='0x0'/>
</filesystem>
<interface type='network'>
<mac address='52:54:00:bb:cc:a7'/>
<source network='belso0'/>
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x03'
function='0x0'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
</console>
<input type='mouse' bus='ps2'/>
<input type='keyboard' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes'/>
<sound model='ich6'>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x04'
function='0x0'/>
</sound>
<video>
<model type='cirrus' vram='9216' heads='1'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x02'
function='0x0'/>
</video>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x06'
function='0x0'/>
</memballoon>
</devices>
</domain>
TIA,
Ruzsi
1:18 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Having the BSOD value (first ID) should provide intel about what's
getting wrong in your setup.
It's likely that your storage stack is incomplete in your setup due to
hardware change for HDD, and thus, Windows cannot find its boot device
any longer.
Reading this KB might help: https://support.microsoft.com/en-us/kb/314082
Once you get proper booting with IDE, you can consider installing
virtio drivers and switching to virtio.
With my best regards,
On 11/07/2015 17:56, Ruzsinszky Attila wrote:
<target dev='vda' bus='virtio'/>
- --
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
1:28 a.m.
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
1:29 a.m.
BTW:
I checked the image with chkdsk from Win Repair Console.
There wasn't any error found.
TIA,
Ruzsi
1:33 a.m.
On Sat, Jul 11, 2015 at 9:28 AM, Ruzsinszky Attila <
ruzsinszky.attila(a)gmail.com> wrote:
The error message "No system disk" means the disk is booting from a KVM
perspective so no.
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(a)redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-users
I don't want Virtio. I want to boot my image first.
You already have it seems like.
I don't know if my restore to iSCSI volume was perfect.
2:45 a.m.
Hi,
Do you need the exact error message (the codes)?
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).
Yes, I found a howto about virtio and I tried to use it. In the 1st time I
choosed SATA.
Nice. ;-)
OK.My diagnostic is almost perfect (with Google help).
TIA:
Ruzsi
1:35 a.m.
-----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
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.
3:01 a.m.
Hi,
The error line is:
*** STOP: 0x0000007B (0xF789AA94, 0xC0000034, 0x00000000, 0x00000000)
Nothing more! (Of course there are some inrelevant text line about chkdsk,
etc.)
Nothing about NTOSKRNL.EXE on the blue screen!
Yes, I think.
I think this is the problem. How can we solve it?
TIA,
Ruzs
5:21 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/07/2015 20:01, Ruzsinszky Attila wrote:
The error line is: *** STOP: 0x0000007B (0xF789AA94, 0xC0000034,
0x00000000, 0x00000000)
Perfect, this is what was expected. This should be easy to fix.
Great, then, it opens possibilities. Let's try the following:
- - Install chntpw
- - Mount your disk on Linux
- - Move to Windows/System32/config (beware the case!)
- - Now, start registry editor: chntpw -e sam system security software
(beware the case, again!)
The following commands are to type in chntpw prompt:
- - hive 1 (to move to system)
- - cd ControlSet001
- - cd Control
- - cd CriticalDeviceDatabase
- - Check you have the following keys: primary_ide_channel,
secondary_ide_channel, pci#ven_8086&dev_7010, pci#ven_8086&dev_7111
keys. Some will be missing (otherwise, you'd boot ;-)).
- - Add the missing ones. For example: 'nk pci#ven_8086&dev_7111'
followed by: 'cd pci#ven_8086&dev_7111' followed by 'nv 1 Service' (1
for REG_SZ) followed by 'ed Service' and type intelide. Proceed like
that will all the missing keys & values[1], 'cd ..' when you're done
with all the values of a key, to proceed for the others
- - cd .. (you're now in Control)
- - cd .. (you're now in ControlSet001)
- - cd Services
- - Check you have the following keys: atapi and intelide
- - Add the missing ones[2]. REG_DWORD type is 4 when doing nv. (like nv
4 ErrorControl)
- - You're done, so: q to quit chntpw (of course, reply 'y' to write hives)
Back to your linux term:
- - cd ../drivers/
- - Check you have atapi.sys and intelide.sys. In case you don't,
extract them from the cab file you can find in Windows\Driver Cache\i386
- - Umount
- - Try to boot again, and report.
What did you do? You just added the missing hardware ClassGUID for
Intel IDE (which is what Qemu uses) to Windows registry. When
installing, Windows just sets the strictly minimalistic ones to match
your hardware. And then, you defined the associated drivers with these
ClassGUID. These are defined as service to allow defining how they
boot. When Start is set to 00000000, it means that you want them to be
started at boot: when Windows needs to find its boot device.
I hope this helped!
[1]:
key {value(type): data}
primary_ide_channel
{
ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318}
Service(REG_SZ): atapi
}
secondary_ide_channel
{
ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318}
Service(REG_SZ): atapi
}
pci#ven_8086&dev_7010
{
ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318}
Service(REG_SZ): intelide
}
pci#ven_8086&dev_7111
{
ClassGUID(REG_SZ): {4D36E96A-E325-11CE-BFC1-08002BE10318}
Service(REG_SZ): intelide
}
[2]:
atapi
{
ErrorControl(REG_DWORD): 00000001
Group(REG_SZ): SCSI miniport
Start(REG_DWORD): 00000000
Tag(REG_DWORD): 00000019
Type(REG_DWORD): 00000001
DisplayName(REG_SZ): Standard IDE/ESDI Hard Disk Controller
ImagePath(REG_SZ): system32\drivers\atapi.sys
}
intelide
{
ErrorControl(REG_DWORD): 00000001
Group(REG_SZ): System Bus Extender
Start(REG_DWORD): 00000000
Tag(REG_DWORD): 00000004
Type(REG_DWORD): 00000001
ImagePath(REG_SZ): system32\drivers\intelide.sys
}
- --
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
6:09 p.m.
Hi Pierre,
On 11/07/2015 20:01, Ruzsinszky Attila wrote:
Good news! ;-)
Great, then, it opens possibilities. Let's try the following:
- - Install chntpw
Is that a Linux program? I use Ubuntu 14.04 64 bit.
- - Mount your disk on Linux
Clear.
- - Move to Windows/System32/config (beware the case!)
OK.
- - Now, start registry editor: chntpw -e sam system security
software
"system security software" is parameters?
I think I'll find SATA something, because the original image was taken from
a
SATA system.
- - Add the missing ones. For example: 'nk
pci#ven_8086&dev_7111'
What does it mean "'nk"?
followed by: 'cd pci#ven_8086&dev_7111' followed by
'nv 1 Service' (1
... and "'nv"?
Maybe I'll have question with registry. Tomorrow morning I'll try your
steps.
Can I a backup file from the registy before I start the procedure? And how?
Now I copied the virtio drivers to the ./Drivers directory.
I understand the 1st goal is booting from IDE. What about SATA?
Thanks for your howto!
I think I'll ask you about registry.
Question not just for you:
Why did I get error message "permission denied" for vir-win-reg command?
TIA,
Ruzsi
6:38 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/07/2015 11:09, Ruzsinszky Attila wrote:
Yes. And Ubuntu provides a package for this program.
All are parameters. '-e' means you want to start the program as
registry editor. Then, the rest if just the list of the hives you want
to open. SAM is mandatory, chntpw is always looking for it. Security &
software might actually not be mandatory for what we do.
You'll likely find pci#vend_XXXX&dev_XXXX keys matching your SATA buses.
It's the command for creating a 'new key'
It's the command for creating a 'new value' in a key.
Backup the config directory files. They are the hives containing your
Windows registry.
I unfortunately don't happen to have a VM using SATA buses, so I've no
idea what HW IDs is Qemu using for its buses. It could be interesting
to have a look though.
- --
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
1:31 a.m.
I agree with Pierre.
Basically the image you have from CloneZilla has lots of settings inside it
that tell the image itself where the boot drive is.
The way I've done it in the past is to mount the image using whatever
filesystem it uses (NTFS in this case). Make sure it is writable. And then
start mucking around with the boot settings of the Windows image.
I don't know if Windows 2013 still uses boot.ini but that is one source.
You need to try and change the default system disk on the image. One other
way you can do it is possibly by booting the Windows 2013 rescue disk and
using command line utilities. This may or may not work. If it does let me
know.
Something like this:
http://stackoverflow.com/questions/20239172/how-do-i-find-a-missing-hard-...
On Sat, Jul 11, 2015 at 9:18 AM, Pierre Schweitzer <pierre(a)reactos.org>
wrote:
3558
days inactive
3559
days old
14 comments
3 participants
participants (3)
-
Jeff Tchang -
Pierre Schweitzer -
Ruzsinszky Attila