Mailinglist Archive: opensuse-bugs (3378 mails)

< Previous Next >
[Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 2 Dec 2010 08:49:17 +0000
  • Message-id: <20101202084917.181A5245523@xxxxxxxxxxxxxxxxxxxxxx>

--- Comment #17 from Dongyang Li <lidongyang@xxxxxxxxxx> 2010-12-02 08:49:15
UTC ---
(In reply to comment #15)
(In reply to comment #14)
however files created after applying the snapshots are gone, this is another
problem, looking into it.

Thanks. Without the patch, files created after applying a snapshot aren't
lost, so it doesn't seem like a separate problem.

More info: I don't understand the sxprep.append (or xenstore in general).
it appears that with the patch, after the snapshot is created, the command
"xenstore-ls" shows an extra value snapshot="snap1" associated with the disk.
I assume this is read during start up. I noticed that this value is never
deleted, that's why I asked about undoing sxprep.append(). It seems like for
an "xm start" that value shouldn't be there, and its presence is causing the
snapshot to be applied?
yes, thanks for pointing out this,
so we are always applying the snapshot with xm start after a xm snapshot-apply,
that's why we can not see the files d e and f.
and also this is why we get "Boot from Hard Disk failed: could not read the
boot disk"
qemu-dm will try to search the snapshot which is just deleted, so if that
fails, we will just skip the device thus there's no bootable device.
I think the problem is sits in the xm scripts, looking into it, thanks
I also note that the value is changed when a later
snapshot is taken. That might mean we can only apply the most recent
I didn't test.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >