[Bug 651822] New: xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk - openSUSE Bugs - openSUSE Mailing Lists

newer
[Bug 641395] New: new html style...

[Bug 651822] New: xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

older
[Bug 679331] New: Window titlebar...

bugzilla_noreply＠novell.com

5 Nov 2010 5 Nov '10

21:37

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c0 Summary: xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Minor Priority: P5 - None Component: Xen AssignedTo: jdouglas@novell.com ReportedBy: brianlgilbert@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.41 Safari/534.7 Happens about 25-50% of the time for me. Seems to happen more often if the snapshot is taken while domU disk io is high. Reproducible: Sometimes Steps to Reproduce: 1. dom0: xm start xpsp3 --vncviewer 2. domU: boots, start regedit and search for some random string 3. dom0: xm snapshot-delete xpsp3 snap1 && xm snapshot-create xpsp3 snap1 (while search is still running in domU) 4. domU: Shutdown regedit and windows after search completes 5. dom0: xm snapshot-apply xpsp3 snap1 && xm vncviewer xpsp3 6. domU: Shutdown regedit and windows after search completes 7. dom0: xm start xpsp3 --vncviewer 8. domU: boots and reports that a chkdsk is needed Actual Results: Windows domU reports that a chkdsk is needed Expected Results: Windows domU should boot without issue Same xpsp3 qcow2 disk image on bug 642078 (i.e. no snapshots to start with) Built and installed xen-devel, xen-tools, xen-libs, and xen-tools using xen-4.0.1_01-84.1.src.rpm, with and without the patch for bug 64207, that doesn't seem to matter. Installed kernel-xen-2.6.34.7-31.1.x86_64.rpm So far after the chkdsk completes the guest is usable, but there shouldn't be any corruption should there? Observed that performing an extra iteration of step 3 between steps 5 and 6 i.e. after applying the snapshot, delete and recreate it before shutting windows down, seems to prevent subsequent chkdsk problems. Thinking that there may be some weird refCount issues in the qcow2 code, I tried making sure the qcow2 file contains a second snapshot the whole time and never deleting that. It didn't seem to help. This could very well be a bug in QEMU's qcow2 code (or Xen's version), but since I am hitting it via the xm snapshot-create/apply/delete scripts I am reporting here first. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

Show replies by date

bugzilla_noreply＠novell.com

8 Nov 8 Nov

15:41

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c Charles Arnold changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfehlig@novell.com AssignedTo|jdouglas@novell.com |lidongyang@novell.com QAContact|qa@suse.de |jdouglas@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

10 Nov 10 Nov

09:19

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c1 --- Comment #1 from Dongyang Li 2010-11-10 09:19:53 UTC --- hm, I can reproduce it on my box, but I think snapshots are not writable, according to http://people.gnome.org/~markmc/qcow-image-format.html and writable snapshot is usually called "clone" I think, I tried to apply a snapshot then shutdown the vm with a kill -9 to make sure it won't make disk write, and then start the vm normally, seems it's fine, so we gonna handle the write after applying the snapshot to somewhere and the change caused by the write will not be kept after you shutdown the vm, looking into it, Thanks a lot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

14:30

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c2 --- Comment #2 from Brian Gilbert 2010-11-10 14:30:57 UTC --- I don't understand your plan to "handle the write after applying the snapshot to somewhere and the change caused by the write will not be kept after you shutdown the vm" My understanding is that xm snapshot-apply should set the image to match the snapshot, but the image should remain writable and any changes the vm makes to disk should be kept after shutting down the vm. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

13 Nov 13 Nov

12:53

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c3 --- Comment #3 from Dongyang Li 2010-11-13 12:53:09 UTC --- ok, this is embarrassing, I think I've found the reason: right now when we do the snapshot without -d, we save the vmstat and tell qemu-dm to create the snapshot inside the qcow2 image, this is all done, and after taking the snapshot, if any write request come to the image, the internal L1 and L2 table of qcow2 has changed due to the snapshot ref count. that's normal by far, and when we apply the snapshot, we restore the vmstat, but doesn't tell qcow2 to switch to the snapshot just created, now you may guess what happened next: the vmstat contains the memory of the vm, thus including the page cache(which might has some dirty data to flush), the inode cache, the dcache and so on, and if we make a write request, we will use the newer L1 and L2 table of qcow2,and our memory is expecting the old ones, so the inconsistent vmstat -- qcow2 image state will result the corruption. you can make a experiment to reflect this: make a snapshot with -d option: only same the disk image after taking the snapshot, make some changes to the disk, and shut the vm down. apply the snapshot, you'll find the changes made *after* the snapshot appears. and here is a patch for this: fix the regression - record the snapshot name in the snapshot control file so qcow2 snapshot will be loaded. diff --git a/tools/python/xen/xend/XendCheckpoint.py b/tools/python/xen/xend/XendCheckpoint.py index 49c2729..bb00ddc 100644 --- a/tools/python/xen/xend/XendCheckpoint.py +++ b/tools/python/xen/xend/XendCheckpoint.py @@ -79,6 +79,9 @@ def save(fd, dominfo, network, live, dst, checkpoint=False, node=-1, name=None, sxprep = dominfo.sxpr() + if name: + sxprep.append(['snapshotname', name]) + if node > -1: insert_after(sxprep,'vcpus',['node', str(node)]) you'd better restart your xend and to the snapshot - clone question: after reading the comments in the qcow2 source, I think the snapshot of qcow2 should be called "clone" as you said the changes will be remained, but according to the source code of qcow2, everytime you apply a snapshot of qcow2, the L1 and L2 table will be re-written to the snapshot's so after applying the snapshot, you'll always using the snapshot, not the original image, it that what you want? and correct me if am wrong, thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

15:32

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c7 --- Comment #7 from Brian Gilbert 2010-11-13 15:32:24 UTC --- Wow, I thought I had verified that snapshot-apply actually restored the disk, but maybe I wasn't checking deeply enough and the guest vm restore was enough to fool me. I am on vacation this upcoming week, but I will test ~11/22. Also I have seen snapshot names not being stored in the qcow2 file, (qemu-img snapshot -l file) just an id and time/date, but I didn't think it was related. Re: snapshot - clone, I think we're in agreement, with one note. After "xm snapshot-apply vm snap1", the L1 and L2 tables match snap1, but snap1 (and all snaps) should still be preserved via COW in case I want to apply it again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

15 Nov 15 Nov

09:07

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c8 --- Comment #8 from Dongyang Li 2010-11-15 09:07:16 UTC --- Created an attachment (id=400158) --> (http://bugzilla.novell.com/attachment.cgi?id=400158) remove duplicate qcow_snapshot_goto() call in handle_blktap_ctrlmsg() ok, those two lines was removed before in order to avoid the duplicate qcow_snapshot_goto() calls while using PV guest or HVM guest with PV driver, but, if we don't add the snapshot name into the snapshot config file as the two lines did, xenstore won't add the snapshot param to the vdb backend, thus the qcow_snapshot_goto() will not get called at all, both true for PV guests and HVM guests. and that's the reason why this bug appears. qcow_snapshot_goto() gets called by two places, 1. xenstore_parse_domain_config() this will be called as long as qemu is up, no matter we are using PV or HVM guests. 2. handle_blktap_ctrlmsg() this gets called if we are using PV guest or HVM guest with PV driver. so we can remove logic at 2 since qcow_snapshot_goto() has already been called by xenstore_parse_domain_config, and make sure we store the snapshot name in the config file. I've tested it on a PV guest, an HVM guest and an HVM guest with PV driver, seems good. any comments? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

16 Nov 16 Nov

05:57

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c9 --- Comment #9 from James Fehlig 2010-11-16 05:57:00 UTC --- (In reply to comment #8)

I've tested it on a PV guest, an HVM guest and an HVM guest with PV driver, seems good. any comments?

I didn't test the patch but it looks good. Thanks for the detailed comments. ACK. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

30 Nov 30 Nov

15:43

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c13 --- Comment #13 from Brian Gilbert 2010-11-30 15:43:04 UTC --- The above fix introduces additional problems for me. The chkdsk problem goes away, but that seems to be the side effect of a larger bug. It seems that once snap1 has been applied to the vm, the xpsp3 xenstore is set so that "xm start" will also cause the snapshot to be applied. Perhaps the sxprep.append() needs to be undone somewhere? Steps: 1. dom0: xm start xpsp3 --vncviewer 2. domU: boots, create file a 3. dom0: xm snapshot-create xpsp3 snap1 4. domU: create file b, shutdown 5. dom0: xm start xpsp3 --vncviewer 6. domU: boots, files a & b exist, create file c, shutdown 7. dom0: xm snapshot-apply xpsp3 snap1 && xm vncviewer xpsp3 8. domU: starts (already booted), as expected file a exists but b & c do not, create file d, shutdown 9. dom0: xm start xpsp3 --vncviewer 10. domU: boots, as expected file a exists and b & c do not, unexpectedly file d does not exist, create file e, shutdown 11. dom0: xm start xpsp3 --vncviewer 12. domU: boots, as expected file a exists and b & c do not, unexpectedly file d & e do not exist, create file f, shutdown 13. dom0: xm snapshot-delete xpsp3 snap1 14. dom0: xm start xpsp3 --vncviewer 15. domU: "Boot from Hard Disk failed: could not read the boot disk" 16. dom0: xm delete xpsp3 && xm create xpsp3.hvm 17. dom0: xm start xpsp3 -- vncviewer 18. domU: boots, as expected file a exists, no other files exists - not sure what to expect for them given the above errors -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

1 Dec 1 Dec

08:50

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

The above fix introduces additional problems for me. The chkdsk problem goes away, but that seems to be the side effect of a larger bug. It seems that once snap1 has been applied to the vm, the xpsp3 xenstore is set so that "xm start" will also cause the snapshot to be applied. Perhaps the sxprep.append() needs to be undone somewhere? as I said in comment#3, after applying the snapshot, the disk state is reverted to the stat of the snapshot, so this is expected.

Steps:

1. dom0: xm start xpsp3 --vncviewer 2. domU: boots, create file a 3. dom0: xm snapshot-create xpsp3 snap1 4. domU: create file b, shutdown

5. dom0: xm start xpsp3 --vncviewer 6. domU: boots, files a & b exist, create file c, shutdown

7. dom0: xm snapshot-apply xpsp3 snap1 && xm vncviewer xpsp3 8. domU: starts (already booted), as expected file a exists but b & c do not, create file d, shutdown

9. dom0: xm start xpsp3 --vncviewer 10. domU: boots, as expected file a exists and b & c do not, unexpectedly file d does not exist, create file e, shutdown

11. dom0: xm start xpsp3 --vncviewer 12. domU: boots, as expected file a exists and b & c do not, unexpectedly file d & e do not exist, create file f, shutdown

13. dom0: xm snapshot-delete xpsp3 snap1 14. dom0: xm start xpsp3 --vncviewer 15. domU: "Boot from Hard Disk failed: could not read the boot disk"

16. dom0: xm delete xpsp3 && xm create xpsp3.hvm 17. dom0: xm start xpsp3 -- vncviewer 18. domU: boots, as expected file a exists, no other files exists - not sure what to expect for them given the above errors however files created after applying the snapshots are gone, this is another

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c14 --- Comment #14 from Dongyang Li 2010-12-01 08:50:57 UTC --- (In reply to comment #13) problem, looking into it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

14:10

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c15 --- Comment #15 from Brian Gilbert 2010-12-01 14:10:06 UTC --- (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). But 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? I also note that the value is changed when a later snapshot is taken. That might mean we can only apply the most recent snapshot, I didn't test. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

2 Dec 2 Dec

02:57

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

(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. without the patch the snapshot is never applied, so you are writing files to

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c16 --- Comment #16 from Dongyang Li 2010-12-02 02:57:54 UTC --- (In reply to comment #15) the original disk.

More info: I don't understand the sxprep.append (or xenstore in general). But 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 you are right. but that only get used once when we start up.

I also note that the value is changed when a later snapshot is taken. That might mean we can only apply the most recent snapshot, I didn't test. nope, the snap param is used for informing the qemu-dm to create the disk snapshot, and the former param is already been used at startup.

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

08:49

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

(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). But 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,

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c17 --- Comment #17 from Dongyang Li 2010-12-02 08:49:15 UTC --- (In reply to comment #15) 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 snapshot, I didn't test.

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

6 Dec 6 Dec

10:39

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c18 --- Comment #18 from Dongyang Li 2010-12-06 10:39:08 UTC --- ok, we should not save the snapshot name in the config.sxp so next time when xm start a domU, we won't apply the formal snapshot again and again. this should work for HVM guests, but, for PV guests and HVM guests with PV driver, they are not so lucky and need something more to make the changes correctly hit the backend file, I'm looking into it, Thanks diff --git a/tools/python/xen/xend/XendDomain.py b/tools/python/xen/xend/XendDomain.py index ba27de7..a87a40c 100644 --- a/tools/python/xen/xend/XendDomain.py +++ b/tools/python/xen/xend/XendDomain.py @@ -320,11 +320,16 @@ class XendDomain: fd, fn = tempfile.mkstemp() f = os.fdopen(fd, 'w+b') try: + snapshotname = '' + if dominfo.info.has_key('snapshotname'): + snapshotname = dominfo.info.pop('snapshotname') + prettyprint(dominfo.sxpr(legacy_only = False), f, width = 78) finally: f.close() - + if snapshotname: + dominfo.info['snapshotname'] = snapshotname try: shutil.move(fn, self._managed_config_path(dom_uuid)) except: diff --git a/tools/python/xen/xend/server/blkif.py b/tools/python/xen/xend/server/blkif.py index 1e36bf9..de9d5e2 100644 --- a/tools/python/xen/xend/server/blkif.py +++ b/tools/python/xen/xend/server/blkif.py @@ -90,6 +90,7 @@ class BlkifController(DevController): if 'snapshotname' in self.vm.info: back['snapshot'] = self.vm.info['snapshotname'] + self.vm.info.pop('snapshotname') if security.on() == xsconstants.XS_POLICY_USE: self.do_access_control(config, uname) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

16:32

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c19 --- Comment #19 from Brian Gilbert 2010-12-06 16:32:27 UTC --- Seems to be working very well for me with HVM guest. No chkdsk issues, xm start vs xm snapshot-apply behaves as expected, no hard disk failure, etc. I did apply both sets of changes (https://bugzilla.novell.com/attachment.cgi?id=400158 plus those in comment 18). Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

21:41

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c20 --- Comment #20 from James Fehlig 2010-12-06 21:41:30 UTC --- (In reply to comment #18)

ok, we should not save the snapshot name in the config.sxp so next time when xm start a domU, we won't apply the formal snapshot again and again.

Yeah, we definitely don't want to store the snapshot name in persistent domain config. How is it getting there? When doing a snapshot-apply (restore)? If so, is it possible to strip 'snapshotname' from the config read from save file before creating XendConfig object? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

7 Dec 7 Dec

02:27

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c21 --- Comment #21 from Dongyang Li 2010-12-07 02:27:33 UTC --- (In reply to comment #20)

(In reply to comment #18)

...
ok, we should not save the snapshot name in the config.sxp so next time when xm start a domU, we won't apply the formal snapshot again and again.

Yeah, we definitely don't want to store the snapshot name in persistent domain config. How is it getting there? When doing a snapshot-apply (restore)?If yes, when we apply the snapshot, we read the config from the save file and create a domain with that. so, is it possible to strip 'snapshotname' from the config read from save file before creating XendConfig object? we still need to send the 'snapshotname' to xenstore to inform the device model to revert the disk image, so we can't create XendConfig without that, what am I doing is strip it before we save the domain config and put it back, it will be eventually popped when we give the snapshotname to xenstore. Thanks

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

03:30

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c22 --- Comment #22 from James Fehlig 2010-12-07 03:30:19 UTC --- (In reply to comment #21)

what am I doing is strip it before we save the domain config and put it back, it will be eventually popped when we give the snapshotname to xenstore. Thanks

Heh, another hack to the hack that is snapshot support :-). It will be interesting to see how this functionality can be implemented in the new xen tools stack (xl/libxenlight). I haven't looked close enough to see how extensions are handled. Regardless, we'll need to figure out what to do with the snapshot patches once xm/xend are deprecated/disabled. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

21 Dec 21 Dec

08:18

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c25 Dongyang Li changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED Severity|Minor |Critical --- Comment #25 from Dongyang Li 2010-12-21 08:18:27 UTC --- The patches are submitted, closing as fixed, Thanks to you all. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

27 Dec 27 Dec

15:56

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c27 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Minor --- Comment #27 from James Fehlig 2010-12-27 15:56:50 UTC --- Severity was accidentally raised to Critical when this bug was closed. Reverting to previous Severity value. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

11 Feb 11 Feb

13:30

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c28 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:running:38651:moderat | |e --- Comment #28 from Swamp Workflow Management 2011-02-11 13:30:46 UTC --- The SWAMPID for this issue is 38651. This issue was rated as moderate. Please submit fixed packages until 2011-02-25. Also create a patchinfo file using this link: https://swamp.suse.de/webswamp/wf/38651 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

24 Mar 24 Mar

13:51

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c34 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:38651:moderat |maint:running:38651:moderat |e |e maint:released:11.3:39281 --- Comment #34 from Swamp Workflow Management 2011-03-24 13:51:00 UTC --- Update released for: libvirt, libvirt-client, libvirt-client-debuginfo, libvirt-debuginfo, libvirt-debugsource, libvirt-devel, libvirt-doc, libvirt-python, libvirt-python-debuginfo, virt-manager, vm-install, xen, xen-debugsource, xen-devel, xen-doc-html, xen-doc-pdf, xen-kmp-default, xen-kmp-default-debuginfo, xen-kmp-desktop, xen-kmp-desktop-debuginfo, xen-kmp-pae, xen-kmp-pae-debuginfo, xen-libs, xen-libs-debuginfo, xen-tools, xen-tools-debuginfo, xen-tools-domU, xen-tools-domU-debuginfo Products: openSUSE 11.3 (debug, i586, x86_64) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

18:16

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c35 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:38651:moderat |maint:running:38651:moderat |e maint:released:11.3:39281 |e maint:released:11.3:39281 | |maint:released:sle11-sp1:39 | |282 --- Comment #35 from Swamp Workflow Management 2011-03-24 18:16:01 UTC --- Update released for: libvirt, libvirt-debuginfo, libvirt-debugsource, libvirt-devel, libvirt-doc, libvirt-python, virt-manager, virt-manager-debuginfo, virt-manager-debugsource, vm-install, xen, xen-debuginfo, xen-debugsource, xen-devel, xen-doc-html, xen-doc-pdf, xen-kmp-debug, xen-kmp-default, xen-kmp-pae, xen-kmp-trace, xen-kmp-vmi, xen-libs, xen-tools, xen-tools-domU Products: SLE-DEBUGINFO 11-SP1 (i386, x86_64) SLE-DESKTOP 11-SP1 (i386, x86_64) SLE-SDK 11-SP1 (i386, x86_64) SLE-SERVER 11-SP1 (i386, x86_64) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

25 Mar 25 Mar

08:25

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:38651:moderat |maint:released:11.3:39281 |e maint:released:11.3:39281 |maint:released:sle11-sp1:39 |maint:released:sle11-sp1:39 |282 |282 | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

6 Apr 6 Apr

21:14

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c36 --- Comment #36 from Brian Gilbert 2011-04-06 21:14:51 UTC --- Why was this reopened? I ask because I have started having chkdsk problems again with xen-4.1.0. I have switched to taking a disk-only snapshots, each time I start the vm: #qemu-img snapshot -d snap1 xpsp3.qcow2 #qemu-img snapshot -c snap1 xpsp3.qcow2 #xm start xpsp3 --vncviewer If I need to revert: #xm shutdown xpsp3 #qemu-img snapshot -a snap1 xpsp3.qcow2 #xm start xpsp3 --vncviewer After reverting sometimes the vm performs a chkdsk. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

21:23

New subject: [Bug 651822] xm snapshot-xxx scripts lead to an XP SP3 HVM domU to chkdsk

https://bugzilla.novell.com/show_bug.cgi?id=651822 https://bugzilla.novell.com/show_bug.cgi?id=651822#c37 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #37 from James Fehlig 2011-04-06 21:23:04 UTC --- (In reply to comment #36)

Why was this reopened?

It was reopened due to some confusion concerning the last maintenance update (released March 24). That confusion was cleared up and the bug should be closed again. I'll do so now.

I ask because I have started having chkdsk problems again with xen-4.1.0.

xen4.1.0 from Factory? Be warned that it has not gotten much testing at all and could have lots of problems. I hope to do some real testing on it soon and fix up any issues that keep it from being at least minimally usable. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

4775

Age (days ago)

4927

Last active (days ago)

Download

25 comments

1 participants

tags

participants (1)

bugzilla_noreply＠novell.com