Further to below, I figured I'd try a re-install using virt-manager -
something I couldn''t get working earlier. I noticed when I installed
virt-manager, it installed a whole raft of software related to the qemu
(not qemu-kvm) package.
It also seems to be recognizing qemu-kvm, but I can't get Windows XP to
install.
Basically, I can connect to qemu (it won't connect to, or even
recognize, qemu-kvm - the problem I was having earlier), create a new
virtual machine (I have to pre-create the virtual disk file or it will
try to create it on my system partition instead of in my home
directory), tell it that it's a Windows XP partition then begin the
install. Unfortunately, after copying files to the virtual disk, the XP
install tries to reboot but can't find a bootable disk.
I don't know if you can help out on that issue. But the various extra
bits that virt-manager installed made me wonder if there is something in
the qemu install (that is not in the qemu-kvm install) that could cause
the issue I am having?
I recall that when I was initially setting up my virtual machine I did
have qemu installed, along with virt-manager, before I eventually got to
qemu-kvm and a manual set up.
Just a thought. Any ideas?
On 25/04/10 01:34 PM, Michael Tokarev wrote:
25.04.2010 17:17, Gary Dale wrote:
[]
I've tried converting my original .qcow file to a new .qcow file and
also to a raw file (which took a long time but seems faster than qcow,
but is also larger - it seems to occupy the full space I initially
created the virtual partition with). Unfortunately the problem still
remains.
No, the raw image will actually use almost as much space as the qcow[2]
one. Use `du' command to verify that. If you're curious, the key word
"sparse file" is for you to find.
Interestingly, neither format releases freed space. They just grow to
the total allocated amount. DU does show they occupy the same amount of
disk space, while dolphin shows the .qcow file at 46.4G and the raw file
as the 50G I allocated for it when I initially create the virtual drive.
The Pinnacle Studio program had been running but I don't know if there
was a qemu-kvm update as part of my Squeeze re-install. How do I revert
to an earlier package to test it?
What exactly do you want to test? Is the issue you were experiencing
(Pinnacle Studio not writing dvd images) still exist after you converted
your disk image(s)? Or do you want to reproduce the problem you had(?)
by installing earlier version?
As of reproducibility(sp), it's not really worth to try to reproduce
it - as I already mentioned before, there are lots of possible causes,
and the bugs in qcow image handlers I mentioned aren't easy to trigger
either, and they're fixed too.
So if the issue is fixed, let's close the bug and move on. If not, and
the program still does not work, please provide some more details about
that.
Thanks!
/mjt
The problem is NOT fixed. Prior to my re-installing Squeeze, Pinnacle
Studio running in qemu-kvm was able to produce the proper video_ts
directory. After the reinstall it reports that it has completed
successfully but the files in the video_ts directory are not correct.
The total video length is reported as correct by vlc, but the last
VTS_01_x.VOB file is usually the wrong one, is too small and is
corrupted after a certain point.
For example, a typical DVD5 video with a simple menu structure would
have VTS_01_0.VOB through VTS_01.5.VOB files, with the 0 file being the
menu, the 1 though 4 files being the main content files (about 1G each
in size) and the 5 file containing the remain 200M - 300M of video.
Instead what I am getting is usually 0 and 1 files, perhaps a normal 2
and the next file (3) being only a couple of hundred megs but showing
the length of the remainder of the movie. In my last test, for example,
the 1 and 2 files where about 30 minutes each while the 3 file claimed
to be about 90 minutes but only the first part would actually play.
It's like Windows starts discarding writes to the 3 file so it never
grows to the size where Studio would start another .VOB. Studio then
terminates thinking it has produced a valid DVD directory (on my hard
drive, not on optical media - burning is a separate step), not realizing
that half of its work has never made it to disk.
As I said, it sounds like file system corruption but chkdsk doesn't
report any errors and two passes through the kvm convert should have
fixed any problems. Moreover, my last test with the raw file was using
an external usb hard drive while my previous runs were on my RAID5 array.
BTW: my virtual drive is NTFS format so there should be no problems with
large files.
I never had this problem before the reinstall of Squeeze but get it
consistently since the reinstall. The version of Pinnacle Studio I run
is no longer supported so there were no updates to it. I don't recall
any Windows XP updates either.
I hate to have to go back and reinstall Windows XP - it's such a painful
and long process that may or may not cure the issue if it is a bug in
qemu-kvm. Do you have any other ideas before I resort to a complete
fresh start?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
