Hey,
I have some problems with debain12 standalone VM. As it seems, the error is known, but I don’t really understand, what could I try in my special case.
I had some freeze within the VM while installing python stuff, then I had to kill the VM. After that the starting problem is there.
qvm-prefs qrexec_timeout 300 didn’t take any effect.
the xen log for the VM shows following suspicious stuff:
- failed to start xendriverd…- Xen driver domain device daemon
- error: Driver pcspkr is already registered, aborting…
- SMBus Host Controller not enabled
- mount: can’t read /proc/mounts: no such file or directory
- file system check … was skipped because of unmet condition check (ConditionPathIsReadWrite)
tried to use older kernel, increased the space/memory, changed from HVM to PVH, kernel provided by qube… but nothing helps.
any idea?
corrupted filesystem with this workaround? But I didn’t get the EXT4-fs error
Cheers
qun
edit1:
So I suppose corrupted files. As it seems, I must run fsck manually with the help of this workaround: How to mount LVM images | Qubes OS
I came till the 4th step: 4: “Mount the partition you want to, and do what you want with it”. So I can see xvdi, xvdi1, 2 and 3 in the /dev of the created dispVM.
While mounting xvdi, xvdi1 and 2, I got “wrong fs type, bad option, bad superblock on …, missing codepage or helper program…” Maybe because the dispVM is fedora and standaloneVM debian? Suppose not. But anyway, I don’t need to mount them for fsck, as I understand.
So I run: sudo fsck.ext4 /dev/xvdi3 and got: clean …
While running it for xvdi / xvdi 1 and 2, I got:
“Bad magic number in super-block… superblock invalid, trying to backup blocks”
“The superblock could not be read or does not describe a valid ext2/3/4 filesystem… if it really contains it, then the superblock is corrupt and you might try running e2fsck with alternative superblock: e2fsck -b 8193 ”
If I want to fsck my vm-myVM-private, I get "qvm-block: error: backend vm dom0 doesn’t expose device ‘’
Is it mounted somewhere, but where??
And by the way,
systemctl status xendriverdomain.service
shows me “Unit … could not be found”
